iPhone alarm not going off? 8 fixes that actually work
"My alarm didn't go off" usually means it did go off — silently. Here's every known cause, in the order you should check them.
1. Raise the Ringtone & Alerts volume
This is the cause in the majority of cases. Alarm loudness follows Settings → Sounds & Haptics → Ringtone & Alerts — not the volume buttons you use for music and videos (unless "Change with Buttons" is on, which makes accidental muting even easier). If that slider sits near the bottom, your alarm "rings" as a whisper. Keep it above 50% and consider turning "Change with Buttons" off so a pocket press can't silence tomorrow's alarm.
2. Check the alarm's sound isn't "None" or haptic-only
Open the alarm and look at its Sound setting. If it's set to None, or to a tone with haptics but no audio, the alarm fires visibly and buzzes — and that's all. This commonly happens after experimenting with custom tones.
3. Turn off attention-aware volume dipping
On Face ID iPhones, Settings → Face ID & Passcode → Attention Aware Features lowers alert volume when the phone believes you're looking at it. A phone propped on a nightstand facing your sleeping face can misread "attention" and quiet the alarm. Disable it if your alarms have been mysteriously faint.
4. Look for a Sleep schedule conflict
If you use the Health app's Sleep schedule, its wake-up alarm is managed separately from your Clock alarms. People often edit one and assume they edited the other — then "the alarm" doesn't go off because it was never the alarm they thought. Check Health → Sleep and the Sleep section at the top of the Clock app's Alarms tab.
5. Don't trust the charging cable
A phone that dies overnight fires nothing. If your battery is marginal, charge overnight — and check that the cable actually seated. A powered-off iPhone cannot ring; alarms resume only after it boots.
6. After an iOS update, re-check everything once
Major iOS updates have occasionally shipped bugs that caused silent or missed alarms, and updates can also reset sound choices. The morning after any big update, give your alarm a 2-minute test fire before trusting it with a flight.
7. If it's a third-party alarm app: know the architecture
Here's the one most people never find: most third-party alarm apps schedule alarms as notifications. Notifications are muted by the Ring/Silent switch, suppressed by Do Not Disturb and Focus modes, and historically unreliable after force-quits and restarts. The app didn't malfunction — iOS did exactly what Silent Mode promises.
Since iOS 26, Apple's AlarmKit framework lets third-party apps schedule true system-level alarms with the same privileges as the built-in Clock app. If you rely on a third-party alarm, make sure it's AlarmKit-based — Rouse is built natively on it, which is why its alarms sound through Silent Mode, every Focus, and restarts.
8. Make the wake-up survivable, not just audible
If the alarm rings and you sleep through or dismiss it half-consciously, the fix isn't volume — it's engagement. Escalating sounds (ramping 30%→100%), wake-up missions that require math or steps before dismissal, and a follow-up Wake-Up Check all exist for exactly this. Rouse includes all three.
Or use an alarm that can't be silenced
Rouse is built on Apple's AlarmKit — alarms fire through Silent Mode, DND, Focus, force-quits, and restarts. Free to start, with escalating sounds and wake-up missions included.
Get Rouse FreeRequires iOS 26 or later.
Quick reference
- Alarm silent but visible: Ringtone & Alerts volume, sound set to None, attention-aware features.
- Alarm never appeared: wrong alarm edited (Sleep schedule vs. Clock), phone dead, third-party app suppressed by Focus/Silent.
- Alarm rang, you slept through: escalating volume, missions, Wake-Up Check — see how Rouse handles wake-ups.