Does closing the app stop transcription on iPhone?

It is a reasonable thing to assume works the same way. You start a recording, lock the screen, go make coffee, and it is sitting there waiting when you get back — so surely tapping "transcribe" and then switching to email for a minute behaves the same. The two are not built the same way underneath, and the difference is worth knowing before you rely on it for a file that took an hour to record.

Why recording survives you leaving, specifically

A recorder that keeps going with the screen locked or another app in front does that because it declared a background-audio capability to iOS ahead of time — a narrow, specific permission that exists to keep one thing alive: an audio session already open, writing to a file. Locking the screen, a text arriving, switching to Maps — none of that closes the audio session, because that session is exactly what the permission was written to protect.

Why transcribing is not covered by the same thing

Transcribing is a separate step you take after a recording already exists, not a continuation of the recording itself — it does not open a microphone, and it is not an audio session in the sense that permission covers. It is a burst of processing: audio in, text out, done once. Because it is not the thing the background-audio capability was built to protect, leaving the app mid-transcription is not automatically covered by the same guarantee that protects a recording you walk away from.

That does not mean it definitely stops the moment you switch apps — only that there is no promise here the way there is for recording. The safest assumption is the cautious one: treat a transcription in progress as something that wants the app in front of you, the same way you would not casually background a big file upload and assume it is fine.

The one case that is not ambiguous

Force-quitting the app — swiping it out of the app switcher — ends the process outright, the same way it ends a recording. That is not backgrounding, it is telling iOS to stop running the app entirely, and nothing in progress, transcription included, keeps running once the process is gone. If you are going to check on something else while a long file transcribes, switch to the other app directly rather than opening the switcher and swiping through it.

What this actually costs you if it happens

Not much. Transcribing is not a one-shot opportunity tied to a specific moment — it is a request you can make against a recording at any point after it exists, as many times as you want. If a long file gets interrupted partway through processing, the recording itself is untouched; you have simply not gotten the words yet. Opening the app again and running transcription a second time picks up from a normal starting point, not from some broken half-state.

How to handle a long transcription without worrying about it

• For anything short — a voice note, a quick reminder — this barely matters. Short files are usually the fastest thing the recognizer does, and you will be looking at the result before you would have thought to leave.
• For a long one — a lecture, an interview, anything that noticeably keeps going — stay on the screen, or at least keep the app in the foreground, until the text actually appears.
• Plug the phone in for anything long. Running a speech model taxes the processor, and a plugged-in phone is one less reason to want to step away from it.
• If you do switch away and come back to find the transcript incomplete or missing, do not read that as something having gone wrong permanently — run it again and treat the first attempt as not having finished.

How Voice Studio handles this

Voice Studio declares the background-audio capability that keeps a recording alive through a locked screen or a switch to another app, and that protection is specifically for the recording itself. Transcription always attempts the on-device path first and only retries against Apple's server if that local pass comes back empty or errors — either way, it is a separate action you request afterward, not something riding along inside the recording's own background session. For a short memo that distinction rarely matters in practice. For a long lecture or interview, the reliable habit is the same one that applies to anything else worth waiting for: keep the app open until you see the words.

Common questions

Does locking the screen stop a transcription that is already running?

There is no guarantee it does not, the way there is for a recording — locking the screen is covered by the background-audio permission a recording uses, and transcribing does not use that same session. Treat a long transcription as something to keep the screen on for, rather than assuming it survives a lock the way recording does.

Does switching to another app stop transcription?

It is not protected the way recording is. A quick switch and back is usually fine for a short file, but for a long one it is safer to switch to the other app directly rather than leave the transcribing screen for an extended stretch.

If a transcription gets interrupted, do I lose the recording?

No. The recording and the transcription are separate things — the audio file was already finished and saved before you ever tapped transcribe. An interrupted transcription just means you do not have the text yet; you can run it again.

Does force-quitting the app definitely stop transcription?

Yes. That ends the app’s process outright, the same way it ends an in-progress recording, so anything the app was doing at that instant — transcribing included — stops with it.