Where is your novel, actually?

This is not a scare piece about the cloud. I use cloud services daily and so do you. It's about one specific asymmetry: a novel takes a year or three, and no writing service can promise you it'll still be trading at the end of that. When those two timelines cross, the question stops being philosophical.

The email nobody wants

Here's a live example rather than a hypothetical. NovelEasy, a browser-based novel-writing service, currently carries a notice on its own site: it "is no longer being maintained and will be shut down on October 1, 2026," and users are told to download their work from the link at the top of each novel, because all content on the server will be erased.

Read that the way a writer reads it. Every novel has to be downloaded by hand, one at a time. If you drafted something there in 2021 and forgot about it, nothing will remind you. If you've changed email addresses since, no warning reaches you. The company isn't behaving badly — it gave months of notice and a working download button, which is more than some do. That's the point. This is what a responsible shutdown looks like, and it still ends with a hard deadline after which your file is gone.

It isn't a one-off, either:

• Editorially, a much-loved collaborative writing tool, closed on 30 May 2014. Users were given advance notice and an export window. Good behaviour again — and the site is still gone.
• NaNoWriMo, the nonprofit behind the November writing challenge, dissolved on 31 March 2025 after 25 years, and its website went offline. Writers on Reddit and elsewhere reported losing years of stats, project entries and forum history, with less warning than they'd have liked. Whatever you think of how it ended, a quarter-century-old organisation with half a million participants is not the kind of thing most people file under "might vanish".

And shutdowns aren't the only way access changes. In December 2023 Evernote limited free accounts to fifty notes and a single notebook; existing users over the limit could still read, edit and export, but not create. In 2017 Ulysses — a writing app people had bought outright for $45 — moved to subscription-only, and long-time owners who declined the new deal stopped getting the app they'd paid for. Both companies had defensible reasons. Both changed the terms of a deal writers had already organised their work around.

Copyright isn't the same as a copy

Every reputable writing service says in its terms that you keep the copyright in what you write. That's true, and it's worth having. It is also not the thing that protects you.

Copyright says nobody else may publish your novel. It does not oblige a company to keep its servers running, to keep supporting the file format, to keep your account open, or to send you a copy when it closes. Owning the rights to a book you can no longer open is a legal position, not a manuscript. The practical test is blunter: can you produce a file, today, with no help from the company?

The three storage classes

Almost every writing tool falls into one of three groups, and the group matters far more than the feature list.

1. Pure cloud

Your words live on the company's servers. You reach them through a browser or an app that's really a browser. There is no copy on your machine unless you made one. Google Docs, Novlr, most browser-based novel platforms, most "AI writing assistant" services.

Not automatically bad — this class gets you sync, collaboration and access from a borrowed laptop, which are real benefits. But your exposure is total: account lockout, outage, price change, acquisition or shutdown all sit between you and the book. Everything depends on exports you made on purpose.

2. Cloud-synced with a local copy

The app keeps files on your disk and mirrors them to a server. Scrivener with Dropbox, Plottr's desktop tiers, Ulysses with iCloud, Obsidian with a sync add-on.

Much safer, with one thing to check: does the local copy open without a sign-in? Some apps store files locally but still gate them behind an account or a current subscription, which means a lapsed payment can lock you out of a file sitting on your own hard drive. Plottr is a documented example of how much this varies by tier — as of July 2026, letting a base subscription lapse costs you future updates, while letting a Pro subscription lapse restricts access to your projects. Same company, same files, different exposure.

3. Local-first

The file is on your disk, in a folder you can find, and the app is just a program that opens it. Scrivener's projects, bibisco, Aeon Timeline's files, a folder of Markdown, Plotloft. The company disappearing is an inconvenience — no more updates — rather than an emergency.

The trade-off is honest and you should hear it: backups are now your job. There's no server keeping a spare copy of your novel. That's the deal, and it's a better deal than it sounds, because a folder is something you already know how to back up in three different ways.

What "export" actually gives you

Export buttons are not equivalent. There are two very different things inside a novel-planning tool, and they export with wildly different success rates.

The manuscript — the prose — generally survives. DOCX, RTF, Markdown and plain text are widely understood formats, and an export in any of them will open somewhere else in ten years. If your app can produce one of those, your words are portable.

The planning — outline, beats, character sheets, timelines, which scene belongs to which subplot, the notes-to-self that make the structure legible — is where portability quietly dies. It typically comes out as either a proprietary project file only that app can read, or a JSON dump that's technically readable and practically unusable, or nothing at all. A year of structural thinking can evaporate while the prose survives intact, and most writers only discover this on the day they try to move.

Two questions separate a real export from a decorative one:

• Can something else open it? Not "is it a file" — can a second, unrelated program read it. Export, then actually open the result in Word, or a text editor, or a rival app. This takes two minutes and answers everything.
• Is the format documented, or at least legible? Plain text and Markdown you can read with your eyes. JSON you can read with some squinting. An opaque binary blob is only readable by the app that made it, which is the app we're assuming has gone away.

Run this audit today — it takes ten minutes

For each tool holding part of a book you care about:

1. Find the export. If you can't find it in two minutes, that's already a finding. Note whether it exports one project at a time or everything at once — per-project export is the difference between a ten-minute rescue and a lost weekend if you have six books in there.
2. Export everything, in every format offered. Disk space is cheaper than rewriting.
3. Open what came out, in a different program. Word, a text editor, anything that isn't the app you exported from.
4. Check the planning data specifically. Is your outline in there? Your character notes? The scene order? Or just chapter prose in a row?
5. Put the export somewhere the app doesn't control. An external drive, a different cloud account, a USB stick in a drawer. Date the folder name.
6. Answer the shutdown question out loud. "If this service ended on the first of next month, what would I have lost?" If the answer is "nothing", you're done. If it's anything else, you now know what to fix.

Then put it in the calendar. Once a quarter, and once more the day any app emails you about "changes to your plan".

How Plotloft answers this

My product, so weigh this accordingly — but the whole app is built around the audit above, so it would be strange not to show my working.

Plotloft is a Windows desktop app with no server and no account. Your projects are ordinary files in Documents\Plotloft\projects\, one .plotloft file per project, named after the project's title. Inside, each one is plain JSON — you can open it in Notepad and read your own scene text with no special tooling. There is no other copy of your novel anywhere, which is both the point and the responsibility: the app writes timestamped backups to Documents\Plotloft\backups\, but the off-machine copy is yours to make.

What that means for the shutdown question: if I stopped work on Plotloft tomorrow, your files would sit exactly where they are, openable by the copy of the app already installed, and readable as text by anything else. You'd lose future updates. You would not lose the book. The docs page on where your novel lives spells out every path, including where the licence key is kept and why it's deliberately not in the same folder as your writing.

Two honest limits while I'm here. Plotloft is a planning board, not a drafting app with a manuscript compiler — today it exports its own .plotloft project files, not DOCX. And it's Windows-only, and in pre-release. If either of those is disqualifying, the roundup of planning software you buy once covers several tools that pass the same audit.

Fair questions, straight answers