If you need Mac dictation without the internet, start by deciding which problem you have. A train journey with poor Wi-Fi is an offline-use problem. A laptop that handles sensitive material but normally connects to the internet needs a verifiable local route. A machine that must never have a network path is an air-gap deployment.
Those are not three names for the same thing. They demand different evidence.
Three levels of isolation
| Requirement | What must be true | Minimum useful test |
|---|---|---|
| Occasional offline use | The full dictation task can finish with no connection | Download everything first, disconnect, relaunch and dictate |
| Sensitive work on a connected Mac | Dictated content stays on the chosen local route | Repeat the offline test, observe network behaviour and inspect local copies |
| Managed air gap | Installation, entitlement, models and updates all work inside the controlled boundary | Test the complete deployment on the isolated machine beyond any licence renewal point |
"On-device" usually describes where a processing stage runs. "Offline-capable" says the task can finish without a live connection. Neither phrase tells you whether the app checks for updates, refreshes a licence or synchronises settings when networking returns.
An air gap is stricter. The machine has no route to an external network, and the organisation controls how software and files cross that boundary. You cannot create one by clicking Wi-Fi off for ten minutes.
Apple Dictation: check the setting, not the Mac model
Apple does not give every Mac a permanent "local" or "cloud" label. Its current support page tells you to open System Settings > Keyboard and read the text below Dictation. That message says whether voice input and transcripts for general text Dictation are processed on your device and not sent to Siri servers. Apple excludes some contexts, including dictation in a search box, from that statement. [1]
That makes the setting more useful than a rule based on chip, macOS version or language. Apple's privacy notice is explicit about the alternative: when the device does not indicate on-device processing, dictated material is sent to Apple for processing. It also describes retention of transcripts and related request data. [2]
Use Apple Dictation as an offline candidate only after checking the active language and routing message on the exact Mac. Then test it disconnected. Do not assume that a successful English test also proves another language or dictation context.
The offline acceptance test
Do this before trusting any dictation route with real work:
- Install the app or enable the macOS feature while online.
- Download every speech and clean-up model you intend to use.
- Record the app version, macOS version, language, selected modes and licence state.
- Quit the app completely.
- Disable Wi-Fi, unplug Ethernet and disconnect any tethered phone or VPN.
- Relaunch the app. Dictate a fresh, identifiable sentence into a plain text editor.
- Quit and relaunch again, then repeat the test.
- Leave the machine disconnected for the longest period your work requires and test again.
Use a sentence you have not dictated before. That removes the easy confusion between a new transcription and a cached result. Include a name, a number and punctuation so you can recognise the output.
A pass means that the exact workflow completed in the recorded state. It does not prove that every mode is local, that the app made no blocked connection attempts or that its licence will remain valid indefinitely.
Add evidence for sensitive connected work
A Mac that reconnects after the test needs another layer of checking.
Watch the app's network totals during a controlled run. If traffic appears, identify the destination and repeat the test with that traffic denied. A successful transcription while a firewall blocks an operational endpoint can show that content processing does not depend on that endpoint. It cannot show what the blocked request would have contained.
Inspect local storage too. Check whether the app keeps transcript history, temporary audio, logs or crash reports. Local processing keeps material away from a remote processor, but it may still leave readable copies on the Mac. Decide whether those copies fit your retention policy and whether FileVault, account access and backups protect them.
Keep the test record. Product behaviour changes with app releases, model choices and settings. A result without the version and configuration is hard to reproduce and easy to overstate.
Commercial licensing is often the hidden dependency
A dictation engine can be fully local while the product around it still expects a network.
Ask the vendor four precise questions:
- Must the app activate online before first use?
- How long does an activated installation remain usable without renewal?
- Does the app attempt feature, licence or update checks when a connection exists?
- Can models and updates be transferred through your approved offline process?
"Works offline" is not an answer to the second question. You need a duration. If the vendor cannot provide one, test beyond the period you expect the machine to remain isolated and keep a fallback that does not depend on that entitlement.
ShoutFlow is a useful example of the boundary. Its public pages say local transcription and clean-up run on an Apple silicon Mac after the models are downloaded. They also say the app uses separate operational requests for licensing, feature entitlements and release checks. [3] [4] That makes local mode suitable for disconnected sessions, but it is not evidence of a network-silent application or an indefinite air-gap entitlement. Anyone planning long-term isolation should get the current offline lease terms before choosing it.
A permanent air gap needs a deployment plan
For a managed isolated Mac, write down how each dependency crosses the boundary:
- the signed installer and its checksum;
- speech and clean-up model files;
- licence or entitlement material;
- macOS and app security updates;
- dictated text leaving the machine;
- logs, backups and disposal.
Test on the real hardware, not a connected development Mac. Reboot during the test. Let the entitlement age. Try the approved update procedure. Confirm that the dictation workflow still works after each step.
If the requirement is strict enough that a failed licence check would stop legal, clinical or operational work, a consumer app with an undocumented offline window is the wrong dependency. Use software and models that your organisation can install, verify and operate inside the boundary, then treat the Mac itself as part of the controlled system.
The practical rule is simple: match the proof to the isolation period. A five-minute Wi-Fi-off test is useful for a five-minute connectivity problem. It is nowhere near enough for a machine expected to stay isolated for months.