Offline gets used for two different claims. Here is the line between them, step by step.
What does offline actually mean for a transcription app
Offline gets applied to two different claims. One is that the app was set up without a network at all. The other, far more common, is that the app runs the transcription step itself without a network, once it has what it needs on the device. A model download during setup, license activation and its periodic refresh, or an update check are all still network events. None of them are the same as the recording itself touching a server.
Which steps need a network connection, and how often
Four steps, checked against what actually needs a connection and how often. The question that matters is whether the transcription step itself depends on a network, and whether the app is clear about when the other steps go online.
- Model download: needs a network once, at install or first run. Not needed again unless the model is replaced.
- License: activation needs a network, and a licensed app may go online now and then to refresh it. Neither step carries a recording.
- Update checks: need a network on their own schedule, separate from recording activity, and skippable without breaking transcription.
- The transcription step itself: on a local architecture, needs no network for any recording while the model is on the device and the license is valid.
Where do the audio and the text go during and after transcription
On a local architecture, the audio file stays on the device it was recorded or imported on for the whole transcription step. It is not copied to a server to be processed and copied back. What happens to the file afterward, kept, exported, or deleted, is set by the app's own retention choice, not by the network.
Can a developer or an agent reach the same local processing without a cloud API
Where a transcription product ships a local API alongside its desktop app, a script or an agent can call the same on-device model and get the same transcript the desktop app would produce, with the audio staying on the machine either way. EdgeSpeak's local API works this way: the desktop app and a script or an agent calling it directly share the same local transcription engine.
How EdgeSpeak handles each step
EdgeSpeak transcribes with its local transcription engine on your own computer. The model downloads once; after that, recordings and transcripts stay on the device. The license is activated online and refreshed online from time to time, and none of that traffic carries audio or text. With a purchased license you can keep transcribing offline during the license grace period; once it runs out, go online once to refresh it. The free trial is different: it checks in online each time the app starts. The desktop app supports Apple Silicon Macs and Windows 10/11 x64 (the Windows installer is not yet code-signed); on Linux x86_64, the edgespeak-cli command line (CPU or CUDA) runs the same local engine. Every device can start with a 7-day free trial.