If you’re a serious indie author, your manuscript files are your livelihood. They represent months or years of work. So where those files live — and who controls access to them — is not a minor technical detail. It’s a business decision.
What “local-first” means
A local-first app stores your data on your machine as the primary copy. You don’t need an internet connection to access your work. You don’t need to log into a cloud service to open your book. Your files are right there, in a folder, on your computer.
Why this matters for authors
You own your files. If the company behind your formatting tool shuts down, your projects don’t disappear. They’re files on your machine.
You can work anywhere. On a plane, at a cabin with no wifi, in a coffee shop with terrible internet. Your book doesn’t care.
No sync conflicts. Cloud-synced writing tools can create version conflicts that corrupt or merge your work incorrectly. With local-first storage, the file on your machine is the truth.
The core workflow does not wait on a server. A local app uses your own computer for editing and typesetting. There is no manuscript upload step or remote render queue in the core workflow. Actual performance still depends on the machine, manuscript, fonts, and images, but a network outage does not make the project inaccessible.
Local-first is not the same as automatically safe
The primary copy being on your computer changes who is responsible for resilience. A cloud service may maintain redundant infrastructure for you. A local-first workflow gives you control, but it also requires a real backup plan. A laptop can be lost, a drive can fail, and a project can be overwritten whether or not a vendor is involved.
Use the 3-2-1 principle as a practical target: keep three copies of important work, on two kinds of storage, with one copy off-site. For an author, that could mean the active project on the laptop, an automatic external-drive backup, and an encrypted online backup. Periodically restore a project to prove the backup can actually be used. A green checkmark in a backup menu is not the same as a tested recovery.
Versioned backups matter too. Synchronization mirrors the current state, including mistakes. If a damaged file immediately syncs everywhere, a simple mirror is not enough. Choose a backup system that can recover yesterday’s or last month’s version.
What about backups?
Local-first doesn’t mean no backups. It means your backup strategy is in your control. Use Time Machine, Backblaze, Dropbox, or any backup tool you trust. Your project files are standard files on your disk — back them up however you want.
Some local-first tools also offer optional cloud backup as a convenience layer. That’s fine, as long as it’s optional and your app works fully without it.
A simple manuscript ownership test
Before choosing any writing or formatting tool, ask five questions:
- Can I open and edit the project without an internet connection?
- Where is the primary project stored, and can I include it in my normal backup?
- Can I export the manuscript and finished files in documented, portable formats?
- What happens if I stop paying, lose access to the account, or the company closes?
- Can I move the project to another computer without asking support to release it?
No architecture answers every need. Real-time coauthoring and browser access are areas where cloud-first tools can be genuinely useful. A local-first desktop app is strongest when ownership, offline access, predictable file handling, and a durable production archive matter more than simultaneous collaboration.
Keep a portable publishing archive
The editable project is only one part of the record. At each release, preserve the source manuscript, the project, the exact print PDF, the EPUB, the cover files supplied by the designer, the ISBN and edition details, and a short note naming the software version used. Store them together under a versioned edition folder.
That archive makes corrections and new editions far less risky. You can distinguish the file that was actually uploaded from a newer draft, reproduce an old edition when necessary, and migrate to another tool without reconstructing the entire publishing history from email attachments.
The bottom line
Your manuscript is too important to depend on someone else’s server staying online. A local-first tool puts you in control of your work, your workflow, and your business.