Local-first meeting notes: what it means and why it matters

The network is used only when you ask for something that needs it — an AI summary, a backup, a second device — and never as a condition of recording.

The term comes from software design, where it describes apps that keep your data on your device first and treat servers as an optional extra. For meeting notes it has a practical test, set out below, and a few trade-offs worth knowing before you choose.

A test for "local-first"

Many notetakers describe themselves as private or local. These questions separate the ones that are from the ones that are not:

1. Can you record with no account? If signing in gates the record button, the app is cloud-first with a local front end.
2. Can you record and transcribe with Wi-Fi off? Turn it off and try. If the transcript does not appear, transcription happens on a server.
3. Can you search and read old meetings offline? If they load from a server, your archive lives there.
4. What leaves the device, and when? A local-first app should be able to answer "nothing, until you ask for X" precisely.
5. Does the app keep working if the company's servers are down? The core features should.

An app that passes all five is local-first. Many good tools pass none, by design — they are built around a shared cloud workspace. That is a different product, not a worse one.

Why it matters

The conversation stays where it happened

Meeting audio is a detailed record of people who did not choose your software. Keeping it on your device means there is no vendor copy to secure, retain, delete or disclose. On-device transcription explains how speech recognition can run on the computer itself and what that costs in accuracy and languages.

It works where the network does not

Trains, planes, client sites with guest Wi-Fi that blocks everything, a meeting room with no signal: a local-first notetaker records and transcribes regardless. Transcribing a meeting offline on a Mac covers that case.

Fewer parties to explain

When a client, employer or regulator asks where meeting data goes, a local-first tool gives a short answer. The fewer services in the chain, the fewer contracts and questions.

Your archive outlives the vendor

If the app stops being developed, a local archive is still on your disk. Exports in open formats like Markdown make that archive readable without the app.

What local-first does not mean

It does not mean no network, ever. Useful things need one:

• AI summaries are usually written by a large model on a server, because the models that write well do not fit on a laptop. A local-first app sends the text it needs, only when you ask.
• Backup needs somewhere else to put copies. Done well, it is encrypted on your device first, so the service stores data it cannot read.
• A second computer needs a way to receive your meetings. Meeting notes on two Macs covers how that can work without giving up the local copy.

The distinction is who starts it. In a local-first app, the network is something you invoke, not something the app depends on.

The trade-offs

Be clear about what you give up:

• No shared workspace by default. Colleagues cannot open your notes in a browser. You send or export them.
• Your device is the archive. If it is lost and there is no backup, so are the meetings. Turn on an encrypted backup or export what matters.
• Your device does the work. Transcription uses the computer's processor while it runs, and recordings use disk space.
• Language and hardware limits follow the on-device model. Cloud services often support more languages.

Where the bot fits

A meeting bot is the opposite end of the scale: a participant run on the vendor's servers, which receives the meeting there. A notetaker that records on your computer is the first step towards local-first — but only the first. Some record locally and still upload the audio to be transcribed. Bot-free meeting notes explains the difference.

How Notey applies it

Notey is a Mac app for Apple silicon and macOS 26 or later, built to pass the test above.

• No account, no network to record, transcribe, search and read back. The Account screen says so when you are signed out.
• Two tracks on your disk. Your microphone and your Mac's audio are recorded separately and transcribed with Apple's on-device speech recognition. After an English meeting, Notey reads the recording again with two stronger on-device recognisers — about 1.2 GB in total, downloaded once and never during a recording — and keeps the words the recognisers agree on.
• Text leaves only when you ask. With an account, the transcript's text is sent for AI notes when you ask, or when a meeting ends if write-ups are on. Audio is never sent.
• Sync between your Macs is optional and encrypted on the Mac with a key derived from a recovery key only your Macs hold. Sign in on another Mac and enter the key, and transcripts and notes sync between them. Recordings stay on the Mac that made them and are never uploaded, not even encrypted. Lose the key and the synced copy cannot be recovered.
• Export as Markdown, to the clipboard or a file.

What it does not have: team workspaces, a web app, or apps for Windows, Intel Macs or phones.

Frequently asked questions

What does local-first mean for a meeting notes app?

That the core work — recording, transcribing, searching and reading back — happens on your device and works with no account and no network. The cloud is used only for things you ask for, such as AI summaries or backup.

Can I transcribe meetings offline?

Yes, with a tool that runs speech recognition on the device. The transcript is made from the recording on your computer without a connection.

Is local-first the same as offline-only?

No. A local-first app can use the network — for summaries, backup or a second device — but only when you ask, and it keeps working when the network is not there.

What do I lose with local-first meeting notes?

Mostly convenience features that depend on a server: shared team workspaces, access from a browser, and anything that needs your notes to be on someone else's computer. You are also responsible for your own backups.