A cloud-based writing app is convenient right up until the moment it isn't: a login that won't authenticate, a service outage during a deadline, a company that shuts down or gets acquired and quietly sunsets the product a year's worth of chapters lives in. None of this is common. All of it is entirely outside a writer's control when it happens, which is the actual argument for working offline.
You don't control an account-based service's uptime
A cloud writing tool needs its servers running and your login working to open your own manuscript. Most of the time this is invisible and fine. Occasionally it isn't: an outage, a billing issue that locks an account, a password reset that goes wrong at an inconvenient moment. A local-first app has no equivalent failure mode, because opening the file doesn't depend on anything beyond your own computer.
Companies shut down products
Smaller and niche software, including writing tools, has closed with limited notice before. When that happens, what you get back depends entirely on the export options that particular service offered and how much warning it gave. A writer's real protection against this isn't picking the "right" company and trusting it forever; it's keeping work in a format you can open and move regardless of what any single vendor does.
Offline doesn't mean no backup
This is the part that trips people up: local-first isn't the opposite of backed up. A folder synced by OneDrive, iCloud Drive, or Dropbox gives a local file the same cloud redundancy a cloud-native app offers, as a byproduct of how your operating system already works, not something you have to set up specifically for writing. The difference is that the app itself doesn't require that connection to function; the backup is optional and under your control, not a dependency baked into every save.
What Quillen does with this
Quillen stores every book, character, and lore entry as plain files directly in your own Documents folder, and works fully offline, always, with no "you must be signed in" gate anywhere in the app. If that folder happens to already sync through OneDrive, iCloud Drive, or Dropbox, those files ride along automatically. Crash-safe writes (every save goes to a temporary file first, then swaps in only once it's confirmed complete) mean a crash or power loss mid-save can't corrupt a scene, character, or lore entry either.
Common questions
Can I still back up an offline manuscript to the cloud?
Yes. Offline doesn't mean no backup. A local-first app's files can sit inside a folder synced by OneDrive, iCloud Drive, or Dropbox, getting cloud backup as a byproduct of normal OS behavior, without the app itself requiring an account or an internet connection to function.
What happens to a cloud-only manuscript if the service shuts down?
It depends entirely on that service's export options and how much warning it gives before shutting down. Smaller or niche writing tools have closed before with limited notice, and a writer's only real protection is exporting their work to a plain, portable file format regularly, regardless of which app they use.