A meeting recorded on a plane, in a basement conference room, or at a site with no signal at all puts a specific question to whatever's doing the recording: does any part of this stop working once the network does? For most notetakers built around a server somewhere, the honest answer is "some of it" — usually the part that turns a recording into readable notes. Here's what actually has to be true for none of it to stop.
The three steps this actually breaks down into
"Recording offline" sounds like one capability, but it's really three separate ones stacked together, and a tool can support one or two of them without supporting all three. Recording the audio is the easiest part for almost anything to get right — a microphone doesn't need a network to capture sound. Turning that audio into a transcript is the step that trips up a tool built around a server-side transcription service. Writing a summary from the transcript is a second, separate step that can depend on a connection even when the transcript itself didn't. All three need to hold for a whole meeting, start to finish, to come out the other side as finished notes with the Mac never connected.
Step 1 — nothing to configure before the meeting starts
There's no offline mode to switch on, no setting that says "work without a connection today." Coii AudioNotes doesn't behave differently based on connectivity because none of the three steps above were ever built around calling out to a server in the first place — the app that records a meeting in a well-connected office is the same app, doing the same thing, in a basement with no signal at all.
Step 2 — press record the same way regardless of connection
The microphone and the call's own audio get captured as two separate tracks the instant recording starts, and neither of those tracks involves the network at any point — audio capture is a local operation on any machine, connected or not. This part of the story is true of most recording tools, including the built-in ones; it's rarely where an offline meeting actually runs into trouble.
Step 3 — the transcript keeps building while the meeting runs
This is the step that separates tools that work offline from tools that merely claim to. Transcription happens on the Mac, segment by segment, as the conversation happens — there's no audio being sent anywhere and no response being waited on before the next line of the transcript appears. A dropped connection partway through changes nothing about this step, because there was no connection this step depended on to begin with.
Step 4 — the summary finishes without a signal either
The step that most commonly needs a server, even in tools that record and transcribe locally, is generating the summary — decisions, actions and open questions distilled from the transcript. Here, a language model bundled with the app does that work on the same Mac, which means the minutes are finished by the time the meeting ends regardless of whether there was ever a connection during it. That's the piece worth checking for specifically in any tool being considered for genuinely offline use, because it's the one most often quietly excluded from an "offline" claim.
Step 5 — reconnecting afterward changes nothing about what already happened
Turning Wi-Fi back on once the meeting's over doesn't trigger anything — no sync, no upload, no notes that were "pending" and now resolve. The recording, transcript and minutes were already complete files on the Mac before the connection came back, which means there's nothing waiting on the network to finish a job that had already finished without it.
Where a cloud notetaker's version of this actually stalls
Some cloud notetakers document, in their own support material, that generating notes depends on reaching a remote transcription service — a VPN, a firewall or a dead connection is named as a cause of notes failing to appear. Whether Granola specifically works offline covers one documented example of that pattern in detail: the recording itself may survive a dropped connection, but the readable notes it's supposed to become wait on a server being reachable again. That's a reasonable architecture for a cloud product built to improve centrally — it's just a different tradeoff than one built to need nothing but the Mac in front of you.
The one genuine exception
None of this claims the app never talks to a server for anything, ever. Licence activation happens once, when the app is first set up, and a launch-time clock check runs each time the app opens — neither of those is part of recording, transcribing or summarizing a meeting, and neither one has to happen in the middle of a call. A Mac that's been offline for the length of an entire flight can still record a meeting during that flight without either of those checks getting in the way, because they aren't gating anything about the meeting itself.
Working from a flight, a basement, or a site with no signal
These are the scenarios where the difference stops being theoretical. A flight with no wifi purchased, a conference room built into a building that blocks a cell signal, a factory floor or a rural site visit with no reliable connection at all — in each of these, a meeting still gets recorded, transcribed and summarized in full by the time it ends, because none of those three steps was waiting on a signal reaching that room in the first place. The wider list of tools built for exactly this covers the field beyond just this one app, and what an offline-first meeting recorder is actually built to do goes into the rest of the picture beyond one flight or one meeting.
Testing this yourself before it matters
The most convincing way to trust any offline claim is to check it directly rather than take a product page's word for it. Turning on Airplane Mode before a low-stakes internal call, then recording it start to finish, shows exactly what does and doesn't happen without a connection — the transcript building in real time, the minutes appearing once the call ends, nothing stalling or queueing. Doing this once, deliberately, before relying on it for a meeting that actually matters is worth the five minutes it takes.
Battery, not bandwidth, is the practical limit
Once the network stops being the constraint, the thing actually worth planning around on a long flight or a full day disconnected is battery life — recording, live transcription and summary generation all use the Mac's processor for the length of the meeting, the same as any other demanding task would. A Mac plugged in or freshly charged handles a normal meeting's length without concern; a laptop already low on battery before a long, unplugged session is a more practical risk to a finished recording than the network ever was.
What this looks like across a whole day of travel
Someone recording three separate meetings across a day with no connection — a flight, a taxi, another flight — ends that day with three complete sets of recordings, transcripts and minutes, none of them half-finished or waiting on a sync. Each meeting is processed independently as it happens rather than queued for later, so there's no backlog building up that suddenly has to catch up once a connection finally appears.
The difference between "works offline" and "downloaded something once, then went offline"
It's worth being precise about what's actually being claimed here, because the phrase "works offline" gets used loosely. This isn't a tool that needs an internet connection once to download something and can then be used offline until that download expires or needs refreshing — the language model that writes the summary is bundled with the app itself from installation, not fetched separately before first use. There's no background download to complete before offline recording becomes possible, and no expiring cache that eventually forces a reconnection to keep working.
Recording an in-person meeting with no connection at all
Not every offline meeting is a video call with a dropped signal — some never had a network dependency to begin with, like an in-person conversation in a room with no wifi and no cell coverage. The distinction barely matters here: the microphone captures the room the same way regardless of whether there's a signal to lose, and the transcript and summary get produced the same way whether the "offline" part was a deliberate choice, a dead zone, or simply a building with bad reception.
Why some tools quietly fall back to "record now, transcribe later"
A common compromise in tools built around a remote transcription service is to keep recording locally when the connection drops, then queue the audio to be sent once a connection returns — which produces a transcript eventually, just not while it would have been most useful, and not without the audio eventually making a trip to a server it wouldn't have taken on a well-connected day. That's a reasonable fallback for a cloud-first design, and it's worth checking for specifically in any tool being considered for offline use, since "the recording survived" and "the notes were ready when the meeting ended" are two different claims, and only one of them is usually advertised.
What Coii AudioNotes gives up by working this way
Being honest about the other side: running everything locally means there's no server doing the transcription work on faster, more powerful hardware than a laptop has — accuracy and speed both depend on the Mac actually doing the recording rather than infrastructure a vendor controls and can upgrade centrally. For someone whose meetings mostly happen somewhere well-connected, that tradeoff may not matter day to day. It's the specific case of "the network can't be relied on" where it stops being a hypothetical benefit and starts being the reason a tool is usable at all.
A quick way to explain this to someone skeptical of the claim
"Works offline" is a claim people have learned to distrust, usually because it's been stretched to cover something narrower than it sounds. The clearest way to describe what's actually true here, to a colleague or a client asking, is the three-step version: the recording is local because a microphone doesn't need a network, the transcript is local because the processing that builds it runs on the Mac rather than being sent out, and the summary is local because the language model writing it is part of the app rather than a service reached over the internet. Each of those three is independently true, which is what makes the combined claim hold up rather than being a stretch of one true fact into a broader-sounding one.
Offline recording on more than one Mac
A licence covers up to three Macs, and each keeps its own independent archive — recording offline on a laptop while traveling and recording offline on a desktop back at the office are two separate instances of the same behavior, not one shared state. There's nothing to sync or reconcile between them once a connection returns, because neither Mac was ever waiting on the other, or on a server, to finish producing its own transcripts and minutes.
What it costs, what it runs on
Working fully offline isn't a separate tier of Coii AudioNotes — it's how the app works by default, for $19 paid once, with a 30-day trial that needs no card and no account either. It runs on macOS 13 Ventura or later, Apple Silicon or Intel, with local transcription and Wispr Flow's notetaker compared against it covering the two things most worth reading next: how the underlying mechanism works, and how this holds up against a specific well-connected competitor.