Is it safe to transcribe a voice memo on public wifi on iPhone?

The worry behind this question is usually specific: an interview on the way through an airport, a voice memo dictated at a coffee shop with nothing but the shop's open network available, and a vague memory that public wifi is where things get intercepted. That memory is not wrong in general. It is just aimed at the wrong layer for this particular case.

What public wifi actually puts at risk

An open network is one where anyone else on it, or whoever runs the router, can in principle watch the raw traffic passing through. That was a real problem in the era when a lot of ordinary web traffic went out unencrypted — a login form on plain HTTP, say, sent as readable text over the air. Someone on the same network with the right tools could read it as it went by.

That era is mostly over for anything built on current platform conventions, transcription included, for a reason that has nothing to do with the wifi itself: encryption happens before the network is involved at all, so what the network carries is already unreadable to anyone else on it.

Where transcription touches the network at all

Most transcription never gets near this question, because it never reaches the network in the first place. iOS attempts speech recognition on the phone itself first, using a language model already downloaded to the device. That pass reads the audio file and writes out text without a single packet leaving the phone — there is nothing for a network, public or private, to see.

A network request only happens if that local pass comes back empty or errors, at which point iOS retries the same audio with on-device recognition turned off. That retry is the entire surface area where public wifi could plausibly enter the picture, and it only exists at all for the recordings that needed it.

What happens on the one request that does go out

When that retry runs, it is ordinary HTTPS traffic to an ordinary Apple domain — the same kind of encrypted connection your phone already makes constantly for the App Store, iCloud, or a browser tab, and the same one that has always carried keyboard dictation. iOS requires apps to make network connections this way by default; an app has to deliberately opt out of it to send anything unencrypted, and Apple's own speech service was never going to opt out of its own platform's rule. The audio is encrypted before it leaves the phone, arrives at Apple's server still encrypted, and is only readable at the two ends of that connection.

That is what actually defeats the public-wifi scenario people picture: someone else on the same network, watching the traffic go by, sees an encrypted connection to a domain they can identify, not the contents of what is inside it. The open network the coffee shop is running does not get a window into that stream that a private one would have closed.

Why the network you are on barely changes this one request

Because the encryption happens regardless of what carries it afterward, the same request looks the same whether it travels over the coffee shop's open wifi, your home network, or cellular data with no wifi involved at all. None of those is meaningfully safer than another for this specific transmission — the protection is built into the connection itself, not into which network happens to be carrying it. A transcript produced over public wifi is not less private than one produced at home; the privacy question that actually matters here is whether the request happened at all, which is a question about the language and the recording, not about the network.

What public wifi risk is actually about, if not this

None of this makes an open network risk-free in general — it just means transcription specifically is not where that risk shows up. The genuine concerns with public wifi are elsewhere: a network named to look like the venue's own but actually run by someone else, a captive portal page asking for more than it needs, or an older app somewhere on the phone that never adopted encrypted connections in the first place. Those are worth being alert to on any open network. They are just a different category of problem from "can a stranger read my transcript," which the encrypted connection already rules out.

If you want zero doubt for one specific recording

For a transcript sensitive enough that you would rather not send anything anywhere, regardless of how well protected that connection is, the direct way to guarantee it is Airplane Mode. With no network available at all, the retry has nowhere to go — either the on-device pass produces a transcript, or you get nothing back, and either way nothing was transmitted over any network, public or otherwise. That sidesteps the whole question rather than relying on trusting the encryption, for the recordings where you would rather not have to.

How Voice Studio handles this

Voice Studio always attempts on-device transcription first, for any of its 38 transcription languages, and only retries against Apple's speech service if that local pass comes back empty or throws an error — the same fallback described in the on-device versus cloud transcription guide. That retry is a standard encrypted request to Apple's own servers, not to anything of ours; Voice Studio has no account, no server of its own and no analytics SDK, so there is nothing else reaching out over the network regardless of which wifi the phone is connected to.

Common questions

Can someone on the same public wifi network read my transcript as it is being sent?

No. The one network request transcription can make is encrypted before it leaves the phone, so someone watching the network traffic sees an encrypted connection to Apple, not the contents inside it.

Is transcribing over home wifi safer than a coffee shop's network?

Not for this specific request. The encryption is built into the connection itself and applies the same way regardless of which network carries it, so the transcription request looks the same on either one.

Does using public wifi make transcription more likely to use the network instead of on-device recognition?

No. Which network you are on has no bearing on whether the on-device pass succeeds — that depends on the language, the audio, and whether the local model is installed, not on wifi.

Is there a way to be certain nothing is sent, instead of relying on the connection being encrypted?

Yes — put the phone in Airplane Mode before transcribing. With no network reachable at all, the retry simply cannot run, so either you get a transcript from the local model or you get nothing, and no data leaves the phone either way.