Local-first means the real copy of your work lives on your own device, and any sync is
an optional convenience layered on top. It is not the same as "works offline." The test
that separates them: if this company shut down tomorrow, would I still have my manuscript
in a form I can open? If yes, it is local-first. If you would need an export window,
it is not.
The longer version
Where the term comes from
It was coined in a 2019 essay by researchers at Ink & Switch — Local-first software: You
own your data, in spite of the cloud. The argument was not anti-cloud. It was that
software quietly moved from files on your machine to documents on a server, and in exchange
for genuine conveniences, users gave up something previously unquestioned: the software
kept working whether or not the company did.
The three architectures people confuse
Cloud-first. The server holds the authoritative copy; your device shows a view. No
service, no document.
Cloud-first with offline mode. Identical, plus a local cache so you can work through a
dropped connection. This is the one most often mislabeled — an app that works on a plane
is not local-first.
Local-first. Your device holds the authoritative copy. Sync, where offered, is
additional, and the file stays complete without it.
Why writers specifically
Four reasons this matters more for authors than for most software users:
- The time horizon is absurd. A novel takes years; a backlist compounds for decades.
Very little software survives fifteen years. File formats do
- The file is the asset. There is no exported deliverable that matters more than the
manuscript
- The work is confidential for a long time before it is public — and then, sharply, it
is not
- Authors mostly work alone. The strongest argument for cloud-first is real-time
collaboration, which most authors rarely use
The five-question check
- Where is the authoritative copy?
- What happens if the company shuts down?
- Can I open my files with something else?
- Is an account required?
- Does it survive a restart in airplane mode?
Question 5 is the practical one. A cache survives a dropped connection; it does not always
survive a quit and reopen.
What it costs you
Local-first is not free, and advocacy usually omits the bill:
- Backup becomes your job. This is the big one — going local without fixing backups
makes your situation worse, not better
- Multi-device access takes deliberate effort
- No automatic version history unless you set it up
- Collaboration is genuinely worse. For simultaneous co-writing, cloud-first wins
Most working authors land on a split: unpublished work local with an encrypted off-site
copy, published and public material wherever is convenient.
Common exceptions
- Local-first does not mean open format. A proprietary binary file on your disk is still
a bet on one vendor. Plain text and Markdown are the safest.
- Optional sync can be genuinely local-first if the local copy remains authoritative and
complete.
- "On-device processing" describes where computation happens, which is related to but
not the same as where the file lives.
Related questions
Sources
- Kleppmann, M., Wiggins, A., van Hardenberg, P., McGranaghan, M. Local-first software: You
own your data, in spite of the cloud. Ink & Switch, 2019.
Verified 9 August 2026.
Related AuthorAZ resources