Does a voice recorder need internet access on iPhone?

It is a fair question to ask before you trust an app with something private, or before you rely on it somewhere with no signal at all. The answer is not one word, because "voice recorder" and "transcription" are two different jobs with two different relationships to the network.

Recording itself never touches the network

Capturing audio is a microphone, an encoder and a file. The phone listens, compresses what it hears into AAC, and writes the result to storage on the device. There is no step in that chain that involves a server, because there is nothing for a server to do — nobody needs to process the raw waveform anywhere but on the phone that made it. This is true of every recording app worth using, not just one: recording has always worked in Airplane Mode, on every iPhone.

The same goes for playback, markers, renaming and browsing your library. All of it reads and writes files that already live on the device. None of it has a reason to reach out.

The first transcription pass does not need it either

iOS transcribes speech through Apple’s Speech framework, and that framework can run entirely on the phone. When an app asks for on-device recognition, a model that is already downloaded to your phone does the work, and the request completes with no network at all — the same as dictating into a text field with Wi-Fi off. If a language’s on-device model is installed, transcribing in Airplane Mode works.

Where a connection can start to matter

The on-device pass is a request, not a promise. It can come back empty, or throw an error — quiet audio, an unusual accent, a language whose local model is thin, a chunk of a long recording that the phone’s smaller model just does not resolve. A well-behaved app does not leave you with nothing in that case: it retries the same audio with on-device recognition turned off, which sends it to Apple’s server-based recognizer instead. That retry is the one place a network connection actually gets used.

Which means the honest version of "does it need internet" is: not for recording, not for a transcription pass that succeeds locally, and only for the retry that catches the passes that do not. If you are offline when that retry would fire, there is nothing for it to reach, so it simply cannot produce a result — you get an error or an empty transcript for that clip rather than a silently uploaded one. Nothing is sent either way; you just do not get text back until you try again with a connection.

The part connectivity is quietly required for

There is one dependency that catches people who plan to go offline for a while: the on-device language model itself has to be downloaded before it can run locally, and that download needs a network the first time. It arrives through the system, tied to adding a language to your keyboard or dictation settings, and it typically fetches over Wi-Fi. A language you have never used for dictation before may simply have nothing installed yet — in which case the on-device pass has no model to run, fails, and the retry is the only path left, which needs the connection you do not have.

The fix, if you know you are heading somewhere offline, is to settle this in advance rather than discover it there. Dictate a sentence in that language through the keyboard while you still have Wi-Fi, or transcribe a short test clip. If text comes back, the model is on the phone and will keep working with the network off. If nothing comes back, it was never going to work offline regardless of which app you used.

Sharing and backing up are local operations too

Getting audio and text off the phone does not require a connection by itself, either. Exporting a transcript writes a TXT or JSON file; sharing a recording hands over the .m4a file itself; a full backup is a single JSON file with everything in it. Each of those is a file being written or handed to the share sheet — what happens after that, whether it lands on AirDrop, a cable, or an email you choose to send, is a decision you make afterwards, not something the export step forces on you.

How Voice Studio handles it

Recording in Voice Studio has no network dependency at all, at any quality setting. Transcription attempts on-device recognition first, every time; if that pass comes back empty or errors, it retries with on-device recognition turned off, and that retry is the only moment a connection gets used. There is no account to sign into and no server of our own involved anywhere in the app, so beyond that one retry, nothing about recording, transcribing, exporting or backing up needs you to be online.

Common questions

Can I record a voice memo with Wi-Fi and cellular both off?

Yes. Recording is local audio capture — a microphone, an encoder and a file on the device — and has never needed a network connection on any iPhone.

Does transcription work in Airplane Mode?

It can, if the language’s on-device model is already installed on your phone. That pass runs locally with no network involved. If it fails and there is no connection for the fallback to use, you get an error or an empty result for that clip rather than a delayed upload.

Why did my transcription fail when I had no signal?

Most likely the on-device pass could not handle that clip — quiet audio, an unfamiliar accent, or a language whose local model is thin — and the retry that would normally catch it needs a connection you did not have at the time.

Do I need internet to export a transcript or back up my recordings?

No. Exporting a transcript writes a TXT or JSON file, sharing a recording hands over the .m4a itself, and a full backup is one JSON file — all local file operations. Any network use after that is whatever transport you choose, not something the export requires.