The worst version of this happened to a friend of mine before a 6am flight. He fell asleep listening to a podcast, one AirPod stayed in, the other rolled under the pillow, and at 4:15 his alarm went off — quietly, politely, into a pillow and half an ear. He heard nothing. The phone did everything right.
This is one of those iPhone problems where the settings are all correct and the outcome is still a disaster, because the question isn't whether the alarm played. It's where.
Where the Alarm Is Supposed to Play
Apple's design intent is straightforward: alarms and timers are meant to come out of the iPhone's own speaker, so they're not dependent on whatever audio device happens to be connected. In most everyday situations, that's exactly what you get. AirPods in your pocket, alarm rings from the phone.
Where it gets murky is when there's an active audio route pointing somewhere else. Behaviour here has varied across iOS versions and across devices, and there are enough credible reports of alarms landing in AirPods, in a car stereo, or on a Bluetooth speaker that I wouldn't treat "it always uses the phone speaker" as a promise you can bet a flight on.
So rather than trying to memorise a rule that shifts, treat it as a routing question and check the route.
The Connection States That Matter
Bluetooth audio isn't a simple on/off. There's a meaningful difference between these states, and it's where most of the surprises come from.
AirPods in a closed case. Not an active audio route. Your phone will use its own speaker. This is the safe state.
AirPods in an open case on the nightstand. This is the trap. An open case can keep the buds discoverable and connected, so the phone may still consider them a live output. Close the lid.
One bud in, one bud out. Still connected, still a route. Whatever plays goes into the bud you're not really wearing, or into the mattress, at whatever volume it was left at.
A Bluetooth speaker still powered on. Same story. A bedside speaker you used at 11pm and never turned off is a live output at 6am.
Car, TV, or smart speaker in range. Anything with auto-connect behaviour can grab the route without you noticing.
Apple Watch on your wrist. A watch adds its own layer — depending on your settings, an iPhone alarm can produce a wrist tap or the watch may be handling its own alarms entirely. Worth knowing which is true for you before you rely on either.
What Happens When the Buds Disconnect Mid-Alarm
Here's a subtlety worth understanding, because it produces genuinely confusing mornings.
If an alarm starts playing to a Bluetooth device and that device then disconnects — the AirPod falls out and goes idle, the speaker times out, you walk out of range — the audio doesn't necessarily transfer cleanly to the phone speaker. You can end up with an alarm that's technically running, technically not muted, and producing no sound anyone can hear.
The reverse also happens: the alarm starts on the phone speaker, your AirPods reconnect a few seconds in, and the sound vanishes mid-ring. Either way, the alarm state is fine. The output isn't.
This is exactly the kind of failure that survives a settings check and only shows up on a live test.
Why the Alarm Can Be Quiet Even in Your Ears
If the alarm did play into your AirPods and still didn't wake you, two things are usually at work.
First, whatever volume was left over from the podcast or music you fell asleep to. Bluetooth output volume is tracked per device, so a comfortable bedtime listening level is also your alarm level.
Second, iOS has hearing-protection settings that limit headphone output. Those apply to whatever is playing through your headphones, alarm included. If you've capped headphone volume — or if a reduce-loud-sounds threshold is active — an alarm routed there will be politely held below the level that would actually wake you. That, plus the general volume mess I break down in why your iPhone alarm is too quiet, covers most of these cases.
There's also a plain physical factor: an AirPod that has drifted out of your ear canal is producing sound into a pillow. No setting saves you from that.
How to Make Sure It Plays on the Phone Speaker
The reliable approach is to remove the ambiguity rather than trying to out-think the routing logic.
- Put AirPods in the case and close the lid. Not on the nightstand, not on the charger with the lid open. In the case, closed.
- Turn off Bluetooth speakers at the wall or the button. Standby-connected is still connected.
- Check Control Centre before bed. The audio output control tells you exactly where sound is currently going. If it names anything other than your iPhone, deal with it now.
- Turn Bluetooth off entirely on high-stakes nights. Flights, exams, interviews. It costs you nothing overnight and eliminates the whole category.
- If you must sleep with audio, use a sleep timer that stops playback and, ideally, use a wired setup or the phone speaker at low volume rather than earbuds.
Then, as with every alarm problem, test it. Set an alarm two minutes out, put your phone exactly where it will be overnight, leave the earbuds and speakers in exactly the state they'll be in, walk out of the room, and listen for where the sound comes from. Ten minutes of testing beats a month of assumptions, and it's the only way to know how your specific combination of devices and iOS version behaves.
Third-Party Alarm Apps and Bluetooth
If you use a third-party alarm app rather than the Clock app, the routing question gets its own wrinkle: the app is playing audio through the system, so it's subject to the same output route. A connected Bluetooth device can take that audio the same way it takes anything else.
That's an argument for choosing an alarm app that's stubborn in other ways too. The behaviours worth checking before you trust one: does it keep ringing when the phone is on silent, does it survive being force-closed from the app switcher, does it come back after a restart, and does the volume climb rather than fade out after thirty seconds.
Captain Wake is built to hold up on all of those — it re-arms through silent mode, app kills and phone restarts, and its volume escalates the longer you leave it. What it doesn't have is a swipe to dismiss. It ends when you complete a mission: photograph a specific object (checked on-device with Apple Vision, so nothing leaves your phone), scan a barcode you stuck somewhere across the flat, solve math, shake or spin the phone. Snooze is one five-minute round, maximum. But even the most stubborn alarm can't choose your audio route for you, so the pre-bed Bluetooth check still applies.
The Part Bluetooth Isn't Responsible For
Worth saying plainly, because AirPods make a convenient scapegoat: if your alarm reliably comes out of the phone speaker at full volume and you're still late, the routing was never the problem. The failure is happening in the ten seconds after the sound starts, and that's the behavioural side I dig into in why your iPhone alarm isn't waking you up.
Fix the route first — an alarm playing into a pillow is unwinnable. Then fix the part where you turn it off without waking up. They're different problems and they need different fixes.
