A flight with in-flight Wi-Fi that never quite connects. A client site where visitors' devices sit outside the corporate network entirely. A rural office an hour from the nearest reliable connection. None of these are edge cases for the people who actually hit them — they are Tuesday — and every cloud-based meeting notetaker shares the same failure mode in all three: no connection, no transcript, because the audio has to reach a server before anything happens to it.
What goes wrong with a cloud notetaker offline
Granola, Otter, Fireflies and the rest of the hosted category all work the same way underneath: the recording, or a live stream of it, goes to a server, and both the transcript and the summary come back from there. Cut the connection and that pipeline breaks — some of these tools will queue a local recording and upload it once a connection returns, but the transcript and summary are not available until that upload finishes and the vendor's servers process it, which is exactly backwards for someone who needed the notes written up before landing, or before driving back out of range again.
Recorded and transcribed on the machine that's already offline
Coii AudioNotes transcribes the meeting on the Mac, segment by segment, while it happens — there is no upload step for the transcription to wait on, because none of it leaves the machine in the first place. The microphone and the system audio are captured as two separate tracks, which matters for a call taken over an unreliable connection specifically: if the call itself drops or glitches, the two local recordings are unaffected, since they never depended on the same connection the call did.
The summary is the part most "offline" tools quietly skip
Plenty of tools that call themselves offline mean only the recording step. superwhisper's own site states its offline models run on Apple Silicon Macs, with older Intel Macs steered toward cloud models instead — a distinction worth checking against the specific machine in hand before assuming "offline" applies uniformly. MacWhisper transcribes fully locally, but its summary step connects to an AI provider of the user's choosing, which means the write-up itself can still depend on a connection even when the transcript did not.
Decisions
- Delay the install by one week pending the parts order
Actions
- Confirm the revised schedule with the site foreman
Open questions
- Does the client need a written change order before work resumes?
In Coii AudioNotes, that summary step runs on the Mac too, using a language model bundled inside the app rather than one reached over a network. The transcript and the minutes are both finished by the time the meeting ends, regardless of whether a connection ever existed during it.
What actually needs a connection, and what genuinely never does at all
Only two things touch a network at all, deliberately kept to that short a list on purpose: activating the licence once, and a brief clock check performed each time the app launches. Recording, transcription, speaker separation and the summary are unaffected by whether the Mac is connected to anything at all — a genuinely offline machine, disconnected for the entire meeting, produces the same finished notes as one sitting on a fast office connection.
A day where the signal was never coming
A field engineer visiting a client site where guest devices sit outside the corporate network for the entire day. A consultant on a long-haul flight, using the layover to write up notes from the client call taken before boarding. A researcher in a rural facility an hour past the nearest reliable connection, running interviews back to back all afternoon. None of these situations are unusual for the people who actually live in them, and in each one, a cloud-based notetaker's usual behaviour — record now, transcribe once uploaded — turns "written up by the time I land" into "written up whenever a signal eventually shows up," which can mean hours or a full day later. Recording and transcribing on the machine itself removes that wait entirely, because there was never an upload step for the signal to interrupt.
What it deliberately doesn't do
Being local-first is not the same as being feature-complete, and it's worth naming the trade plainly. There is no cloud backup of recordings built in — a Mac that is lost or wiped takes its recordings with it, unless backed up the same way any other file on that Mac would be. There is no way for a colleague to open a transcript from their own device or account; a recording made offline stays on the Mac that made it, on up to three machines per licence, rather than syncing anywhere for someone else to read. And activating the licence itself does need a connection once, at the start — the offline promise covers every meeting after that, not the very first minute the app is ever opened.
What it costs, what it runs on
Coii AudioNotes is $19, paid once, for three of your own Macs, with a 30-day trial that needs no card and no account — enough time to test it on an actual flight or an actual site with no signal before deciding. It runs on macOS 13 Ventura or later, Apple Silicon or Intel, with no separate "offline mode" to turn on, because there is no online mode it is falling back from. Full comparisons against the two other local-first Mac apps worth knowing about are here and here; against the two cloud notetakers that stop working without a signal, comparisons are here and here.
Why the queue-and-retry approach isn't the same fix
A few hosted tools soften the offline problem with a queue: the recording saves locally and uploads automatically once a connection returns. That genuinely helps against total data loss, and it's worth crediting as a real improvement over tools with no offline fallback at all. What it doesn't fix is the timing — the transcript and the summary still don't exist until the queued file finishes uploading and a server processes it, so the actual wait a traveller or a field worker experiences is identical to having no offline handling in the first place — hours, sometimes a full day, until a connection shows up — just with the audio safely preserved in the meantime rather than lost outright, which is a real improvement on the worst case without being a fix for the actual complaint.
What "local model" actually buys, beyond just working offline
It is worth being specific about why the summary step matters as much as the recording does, since it's the part most competitors quietly route through a server even when they market themselves as offline-capable. A transcript on its own is already useful — searchable, readable, something to scan for the one line that mattered — but the write-up that actually gets reread, the decisions and action items pulled out of an hour of back-and-forth, is what a language model produces from that transcript. When that step depends on a reachable server, "offline transcription" quietly becomes "offline recording, online everything after it," which is a smaller promise than the name suggests. Coii AudioNotes keeps that entire chain — recording, transcription, and the summary written from it — inside the one machine, so the distinction between "recorded offline" and "usable offline" never actually comes up.
Why two tracks still matter with no connection at all
The choice to record the microphone and the system audio as two separate files rather than one blended recording has nothing to do with being online or offline — it is about what happens when more than one voice is active on the same side of the call, in person, while the meeting is also playing audio back. That matters even more in a genuinely offline setting, where there is no fallback cloud service to lean on if a blended recording turns out to be hard to make sense of afterward. Two clean tracks, captured locally, mean the same quality of transcript and speaker separation whether the meeting happened over a fast office connection or on a plane with the Wi-Fi switched off entirely.
The device matters as much as the app
"Offline" claims are only as good as the hardware behind them, which is why it's worth checking a specific Mac rather than trusting a product category as a whole. superwhisper's documented Apple-Silicon-versus-Intel split is a useful reminder that a vendor's offline claim can be accurate for some of its own customers and not others, on the very same pricing tier, depending on which chip happens to be inside the machine. Coii AudioNotes runs the same way on Apple Silicon and Intel alike — recording, transcription and the summary all process locally regardless of which chip the Mac has — so there is no separate hardware check required before trusting the offline claim on this specific page.
Who this genuinely isn't built for
A team that never leaves a well-connected office, working in one building on one steady connection, and shares transcripts across a shared workspace all day, has genuinely less reason to care about any of this — the offline case simply never comes up for them, and a hosted tool's other conveniences may matter more than a guarantee they'll rarely test. This page is written for the specific person who has actually sat through a meeting knowing the write-up was stuck behind a connection that wasn't coming back for hours, not as a universal argument that local processing beats a server in every situation. If that specific frustration has never happened, it's a reasonable sign the offline guarantee is not the deciding feature for that particular job, and a hosted tool's shared workspace or calendar integration may genuinely matter more day to day than a guarantee against a specific scenario that particular job simply never encounters in practice.
The actual test is the meeting with no signal, not the one with a strong one
Any transcription tool looks the same on a fast office connection with a clean recording — the differences only show up the day the connection actually fails, which is precisely the day nobody wants to discover that the tool they picked needed one. Worth testing before it matters, rather than assuming it: put the Mac in airplane mode, record an ordinary meeting start to finish, and check that a finished transcript and a written summary both genuinely exist afterward without ever once turning the connection back on. A round-up of the other tools that pass that same test is here, and a wider list built around the "no signal" version of that requirement specifically is here. The broader case for treating a Mac's own audio as the whole notetaker, signal or not, is covered here.