Does using AirDrop stop a voice recording on iPhone?

This comes up in ordinary moments: recording an interview and wanting to AirDrop over a document the other person just mentioned, or recording a lecture and wanting to send yesterday's recording to a classmate without stopping today's. Either way, the instinct is to wonder whether opening that share sheet is going to do something to the file currently being written. It is not, and the reason is worth knowing rather than just trusting.

What AirDrop actually asks iOS for

AirDrop moves files between nearby devices over a direct Wi-Fi and Bluetooth connection — it uses Bluetooth to discover the other device and a peer-to-peer Wi-Fi link to move the actual data. None of that has anything to do with audio input or output. Sending a photo, a document or a recording to someone, or accepting one from them, is a networking and file-transfer operation from start to finish. It never asks the system for control of the microphone, because it never needed the microphone in the first place.

Why that means a recording in progress is untouched

On iPhone, only something that genuinely needs audio input or output for itself gets to take over the shared audio session that a recording depends on — a phone call, Siri being invoked, an alarm going off, or another app starting its own recording or playback that demands exclusive control. That is a short, specific list, and a recording app is notified when one of those events happens so it can pause and resume. AirDrop is not on it, for the same reason a text message notification is not on it: moving a file and playing a notification chime are both things iOS handles without ever touching the part of the system that arbitrates who gets the microphone.

Practically, that means you can open the AirDrop sheet, pick a device, accept an incoming transfer, or watch a file copy over, all while a recording keeps writing to its file in the background exactly as if nothing had happened on screen. The waveform is not watching either — recording and AirDrop simply do not compete for the same resource.

The part that is genuinely different: which file you can send

Here is the actual limit, and it has nothing to do with the microphone. A recording that is still in progress is not yet a finished entry in the library — it becomes one once you stop it. AirDrop, like any other way of sharing a file out of the app, works from that library, so the recording currently being written simply is not on the list of things you can pick yet. If the thing you actually want to send over AirDrop is the recording happening right now, the only way to do that is to stop it first, which has nothing to do with AirDrop and everything to do with how a recording becomes a shareable file at all.

That is easy to mistake for AirDrop "blocking" something, when the real cause is more mundane: an unfinished file has no reason to be selectable, the same way you cannot attach a document to an email while it is still being saved somewhere else.

What you can safely do at the same time

• Receive an incoming AirDrop — a photo, a document, another recording — while a new recording keeps running underneath it.
• Send an already-stopped recording, or a TXT or JSON transcript export, to someone nearby over AirDrop while a separate, unrelated recording is in progress.
• Do both of the above with the screen locked partway through, since background audio keeps the in-progress recording going regardless of what else is on screen.

The one thing worth noticing: attention, not audio

The AirDrop acceptance sheet takes over the screen and needs a tap before anything moves, which means you cannot watch whatever screen you were on while it is up. That is a visual interruption, not an audio one — the recording underneath does not pause because you looked away from it, the same way it does not pause when you glance at any other app. If you specifically wanted to see the waveform tick along in real time, an AirDrop prompt gets in the way of that for a few seconds. It does not get in the way of the recording itself.

How Voice Studio handles this

Voice Studio is declared for background audio, so a recording keeps writing to its file whether the screen is locked, another app has focus, or an AirDrop sheet is sitting on top of everything — none of that is the kind of event that takes the microphone away. The short list of things that actually do pause a recording, and resume it into the same file afterward, is limited to a phone call, and anything else that genuinely needs exclusive control of the microphone. Once a recording is stopped and sitting in the library, it can be shared out as the .m4a itself, or exported as a TXT or JSON transcript, through the ordinary share sheet — AirDrop included — the same way any file on the phone can.

Common questions

Does accepting an incoming AirDrop pause my recording?

No. AirDrop is a file transfer over Wi-Fi and Bluetooth and never asks for the microphone, so it never enters the mechanism that hands audio control between apps. A recording in progress keeps running exactly as it would if nothing had arrived.

Can I AirDrop the recording that is currently in progress?

Not until you stop it. A recording still being written is not yet a finished entry in the library, and sharing — over AirDrop or any other way — works from the library. Stop the recording first if that specific file is the one you want to send.

Does AirDrop use the microphone at all?

No. It moves files over a direct Wi-Fi and Bluetooth-discovered connection. There is no audio component to the transfer itself, whether you are sending or receiving.

Can I AirDrop a transcript instead of the audio file?

Yes. Once a recording is stopped, you can export the transcript as TXT or JSON, or share the .m4a itself, and send either one over AirDrop from the ordinary share sheet.