Does a Bluetooth disconnect stop a voice recording on iPhone?

This one gets asked after the fact, usually by someone who checked a long recording and noticed the audio changes character partway through, with no gap and no obvious cause. The AirPods case is the box, and the case was closed twenty minutes into an hour-long session. The recording is still one continuous file — it just stopped sounding the same the moment that happened.

Two different things, treated differently by iOS

A phone call and a Bluetooth disconnect both change what is happening to an app's audio while it runs, but iOS files them under two different mechanisms, and the difference matters for what you should expect afterwards.

An incoming call is an interruption: the system takes the microphone away entirely and tells the app so, with a clear "began" and, later, a clear "ended". Losing a Bluetooth accessory is a route change instead: the system does not take the microphone away, it just decides which physical microphone answers to that name next. One is a stop; the other is a swap.

What actually happens when the Bluetooth mic goes away

A dying AirPods battery, a case snapping shut, walking out of range of a car's Bluetooth, or another device stealing the connection all end with the same result: the accessory that was serving as the microphone is no longer available. iOS does not treat "the current input vanished" as a reason to stop recording. It picks the next available input — normally the phone's own microphone — and recording keeps going through that instead, without the app being asked to approve the swap or having any say in which mic gets chosen next.

What you are left with is one file that used two different microphones for two different stretches, back to back, with nothing marking the boundary except the sound itself. If you know what to listen for, it is usually obvious: audio recorded over Bluetooth already tends to sound thinner and more distant than the phone's own mic, for reasons that have nothing to do with this specific disconnect, so the file often gets noticeably fuller and closer right at the point where the accessory dropped out.

Why nothing pauses, and why that is not a bug

It is tempting to expect the same pause-and-resume behaviour a phone call gets, since both involve the microphone changing hands mid-recording. That behaviour is specific to interruptions, though, and a route change was never one. Pausing on every route change would mean pausing every time a car's Bluetooth connects on start-up, every time a call ends and the system reconsiders inputs, every time a second Bluetooth accessory comes into range — disruptions to a recording that nobody asked for, for an event that, unlike a call, does not actually need the microphone to stop. Letting the recording keep running and just switching which physical mic feeds it is the more useful default, even though it is the one that leaves a seam in the audio rather than a silent gap.

Common ways this happens without anyone doing anything wrong

• AirPods running out of battery partway through a long recording, with no warning loud enough to notice while you are talking.
• Walking far enough from a paired accessory — a car, a speaker, a headset left in another room — that the link drops.
• A second device with the same Bluetooth accessory paired taking the connection away, which can happen without either device visibly doing anything.
• Putting AirPods back in their case out of habit partway through, forgetting a recording is still running.

Checking whether it happened to a specific recording

There is no marker in the file or the app announcing a mid-recording route change, so the check is the same one that works for spotting a Bluetooth-routed recording in the first place: listen for a change in how full or thin the voice sounds partway through, rather than a gap or a click. A short section that suddenly sounds closer and clearer than what came before it is the signature of the input switching back to the phone's own mic, not a sign the file is damaged.

If you need one consistent input for the whole recording

The only way to guarantee this cannot happen mid-session is to remove the possibility before you start: turn off Bluetooth, or make sure the Bluetooth accessory you are relying on will not lose its connection for the duration you need. For anything long and unrepeatable — a lecture, an interview, a full meeting — deciding on the phone's own microphone in advance removes an entire class of problem you would otherwise only discover afterwards, the same way choosing Airplane Mode in advance removes the risk of a call interrupting a recording outright.

How Voice Studio fits into this

Voice Studio records through whichever microphone iOS has active at any given moment, the same as any app that does not override the system's routing decision — it does not pin the input to a specific device or refuse to continue when an accessory disconnects. What it does handle explicitly is the call case: an AVAudioSession interruption pauses the recorder and resumes it into the same file once the call ends. A Bluetooth disconnect is a different kind of event entirely, so that specific pause-and-resume behaviour is not what happens here — the recording just continues, uninterrupted, through whatever microphone iOS switches to next. Because the app declares background audio, none of this depends on the screen being on or the app being in the foreground either. Whichever mic ends up capturing a given stretch, the file stays mono AAC in the .m4a at whichever quality tier you picked, and transcription still attempts the on-device path first regardless of where the audio came from.

Common questions

Will a recording stop if my AirPods die or disconnect mid-session?

No. The recording keeps running — iOS switches the input to another available microphone, usually the phone's own, rather than stopping anything. You end up with one continuous file, not two.

Why does part of my recording sound different from the rest with no gap?

That is usually the input switching between a Bluetooth accessory and the phone's own microphone partway through, most often because the accessory disconnected. The two microphones sound different, and iOS does not mark the boundary in the file — it just keeps recording through whichever one is available.

Is a Bluetooth disconnect the same as a phone call interrupting a recording?

No, and iOS treats them differently. A call is an interruption that pauses the recorder and resumes it afterward. A Bluetooth disconnect is a route change — the system just picks a different microphone and keeps going, without pausing anything.

How do I make sure a long recording uses one microphone the whole time?

Turn off Bluetooth before you start, or otherwise make sure the accessory you are using will not lose its connection during the session. That removes the possibility of a mid-recording switch entirely, rather than relying on catching it afterwards.