Does starting a screen recording stop a voice recording on iPhone?

This comes up in a specific, common situation: a lecture or a video call is being recorded for audio, and partway through it seems useful to also screen record the slides, or a walkthrough someone is giving on-screen. Starting the second recording is where people get nervous — will it kill the first one, or can both run at once?

Screen recording actually captures two different things

Control Center’s screen recording control does one thing by default: it captures the screen and whatever audio the phone itself is producing — a video playing, a call’s audio, a game. Long-press the control before tapping it and there is a separate option for microphone audio, off by default, that lets you narrate over the recording. Most people who screen record a tutorial or a reaction video turn it on; most people who just want to capture what is on the screen never touch it.

Those are two different requests to the operating system, and only one of them touches the microphone at all.

Why the microphone toggle is the deciding factor

iOS does not generally let two apps treat the microphone as if nothing else were using it. When something asks for the microphone while another app already has an active recording session open, the system interrupts the session that had it — the same mechanism that hands the microphone to a phone call mid-recording, just triggered by a different request.

With the microphone option left off, screen recording never makes that request. It has no reason to touch the input a separate voice recorder is using, so the two run alongside each other without either one noticing the other — the lecture recording keeps going underneath the red screen-recording indicator with nothing interrupted.

With the microphone option turned on, screen recording becomes a second app asking for the same input. That is what triggers the interruption, not the act of screen recording itself.

What happens to the recording that was already running

Once that interruption fires, what happens next depends entirely on how the app that was recording is written. An app that listens for the interruption can pause cleanly the moment it loses the microphone, and pick back up once it gets it back. An app that does not listen for it can end the recording outright, or leave it in a state where it looks like it is still running but has actually stopped capturing anything — which is the more frustrating failure, because you do not find out until you go back to listen.

Either way, the portion of audio that overlaps with the screen recording’s microphone use will not be in the original recording — that microphone input went to the screen recording instead, for as long as it held it. What a well-behaved app controls is everything on either side of that gap: whether it comes back cleanly afterwards, in the same file, or whether the interruption ends the session for good.

How to check it on your own phone

• Start a voice recording and let it run for a few seconds.
• Open Control Center and start screen recording with the microphone option left off. Confirm the voice recording is still going.
• Stop both, then start the voice recording again.
• This time, long-press the screen recording control first, turn the microphone option on, then start it. Check whether the voice recording paused, kept going, or stopped.

Thirty seconds, and you know exactly how the app you are using behaves, rather than guessing from a general rule that has one real exception built into it.

The simplest way to avoid the collision

If you do not actually need your voice narrated over the screen recording, leave the microphone option off. You still get the screen and any audio the phone itself is playing, and whatever is recording audio separately continues untouched. Turning the microphone on is really a different goal — mixing your commentary into a video — not something a clean audio recording needs at all.

How Voice Studio handles it

Voice Studio listens for the same interruption notification that lets it survive a phone call mid-recording: a "began" event pauses the recording, and an "ended" event resumes it into the same file rather than starting a new one. A screen recording that takes the microphone away triggers that identical mechanism, so a Voice Studio session pauses rather than ending outright, and picks back up once the microphone is free again. Because it is declared for background audio, none of this depends on which app is on screen at the time.

Common questions

Does screen recording without the microphone option affect a running voice recording?

No. Without that option, screen recording never requests the microphone, so it has nothing to interrupt — the voice recording continues untouched underneath it.

How do I check whether screen recording’s microphone option is turned on?

Long-press the Screen Recording control in Control Center before tapping it. It opens a small panel with a microphone toggle, off by default.

Will I lose the part of my recording that overlapped with the screen recording?

The portion where the screen recording held the microphone will not be in the original audio, because that input went to the screen recording instead for as long as it had it. Voice Studio pauses and resumes into the same file around that gap rather than losing the recording entirely.

Does this happen with a normal camera app recording video too?

The same principle applies whenever another app requests the microphone while a voice recording is running — a camera app recording video with sound is asking for the same input, and would trigger the same interruption.