How do I make sure I never lose my novel draft again?

By Brenn and Lindsay, the two writers who built Inkling

Drafts almost never die in a fire. They go missing in quiet, ordinary ways. Here is how it happens, and the small weekly habit that means it never happens to you.

Every writer we know has a version of the same story. The chapter that was there last night and gone this morning. The file that opened as a page of question marks. The app that said it was syncing right up until it wasn't. If you have landed here after losing work, we are sorry. It is a specific kind of grief, and the advice below is what we wish someone had handed us the first time.

If you have not lost work yet, good. Read this anyway. The habit takes ten minutes to set up and about thirty seconds a week to keep.

How do drafts actually get lost?

Almost never in a fire. In our experience, and in every forum thread we read while writing this, drafts go missing in four quiet ways.

Sync conflicts. Two devices both think they hold the latest version, and the sync service has to pick one. On the Scrivener forum, a writer described losing about a tenth of a draft after a Dropbox sync conflict on iOS, and asked whether there was any hope of getting it back. There was not. (The thread is here.) Loreteller keeps a catalog of the ways Scrivener and Dropbox can fall out of step, and the pattern is the same in every entry. It is not that the tool is bad. It is that two copies of one file are a negotiation, and negotiations can go wrong.

Offline edits that never saved. Browser editors feel safe because they save constantly. They save constantly when they are online. In a Google Docs support thread, a writer turned on offline editing, wrote, refreshed the page, and found nothing had saved. (That thread.) The little "saved" indicator is a promise from the app, not proof from your disk.

One copy on one machine. This is the oldest one. NPR told the story of a novelist who lost 100 pages to a tech glitch and had to make himself keep going. A laptop is a single point of failure with a keyboard attached.

A subscription lapsing. Newer, and sneakier. You stop paying for an app, or forget to, and the door closes with your manuscript on the other side. Whether you can still get in to export depends entirely on the company's policy, which most of us never read.

Notice what all four have in common: the writer thought a copy existed somewhere. The problem was never a lack of caring. It was trusting a system nobody had checked.

What is the 3-2-1 rule for a manuscript?

It is a rule borrowed from people who back up servers for a living, and it translates cleanly to a novel.

• Three copies of your draft.
• On two different kinds of storage.
• With one of them somewhere else.

For a novelist, that might look like: the working copy inside whatever app you write in, a dated export on your own laptop, and a copy of that export in a cloud folder or on a thumb drive at a friend's house. The working copy and the cloud folder are not two separate copies if the app is the cloud folder. That is the mistake most of us make. The point of three is that no single failure takes out more than one.

Should I keep a copy off the cloud?

Yes. Not because the cloud is unreliable, but because "the cloud" is usually one company, and one company is one point of failure. An account can be locked. A password can be lost. A sync can conflict. A service can shut down, and plenty have.

A file on your own machine, in a format that opens without any particular app (a .docx, a .txt, a PDF), is the copy nobody can take away. It does not need to be fancy. A folder called Backups with a file called novel-2026-09-16.docx inside it is a perfectly good backup. A thumb drive in a drawer is a perfectly good second one.

The Goodreads thread on what to do when your computer eats your manuscript is worth reading for the tone alone: writers trading the habits they adopted after the loss. Almost all of them come down to some version of "keep a copy that does not depend on the thing that failed."

How often should I export?

Our answer: a dated copy at the end of every week, and one more after any big session.

Weekly is frequent enough that the worst case is a few days of work, which stings but survives. The "after a big session" rule covers the day you wrote four thousand words in a fever and would genuinely weep to lose. If a session felt important, export when you stand up.

Put the date in the filename. Not "novel-final" or "novel-final-2" or "novel-FINAL-real". novel-2026-09-16. Future you, at two in the morning, trying to work out which file is newest, will thank present you. Keep the old ones. Text is tiny; a whole year of weekly exports of a long novel fits on the smallest thumb drive sold.

If you are writing toward a deadline, say a November novel challenge, tie the export to your word count check-in. You are already looking at the number. Save the file while you are there.

How do I know my backup actually works?

Open it.

That is the whole answer, and it is the step nearly everyone skips. A backup you have never opened is a rumor. Once a month, or the first time you make one, open the export on a machine that is not the one you wrote it on, or at least in an app that is not the one you wrote it in. Scroll to the end. Check that the last scene you remember is there. Check that the chapter breaks survived and the curly quotes did not turn into question marks.

It takes a minute. It is the difference between a backup and a hope.

What happens to my draft if I stop paying for an app?

It depends on the app, and you should find out before you need to know. Some let you keep reading and exporting after a plan ends. Some lock the door. Some delete after a grace period. The honest answer for any tool is buried in a help page, and the time to read it is now, while you are calm and your novel is safe.

Two questions to ask of any writing app, ours included: can I export everything in a format that opens elsewhere, and does that still work if I stop paying? If either answer is no or unclear, keep your own copies more often, not less. For the same reasons we wrote about in Your words stay yours, a draft should never be a hostage to a login.

How Inkling handles this

Since you would ask, here is the plain version.

Your writing is saved to your account as you go, so there is no save button to forget. You can export everything as Word, plain text, or print PDF whenever you like, and no plan switches that off. If a trial ends, the desk becomes read-only and nothing is deleted: you can still open every story and export every word. If you connect a Google Doc, it is one file at a time, with permission for that file only, so your Drive is never a wide-open door. And if you are bringing an existing draft in, you can paste it, upload a .txt or .md file, or connect a Google Doc. (We cannot read a .docx yet, so copy and paste that one.)

Now the part where we talk against our own interest: keep your own dated export anyway. Of any app. Including ours. We built Inkling to be careful with your words, and we would still tell you to keep a dated export in a folder that has nothing to do with Inkling. Not because we expect to fail you, but because "trust me" is not a backup strategy, and we would rather you never have to find out whether we deserved it.

The ten-minute version

• Pick one place outside your writing app for exports. A folder, a drive, both.
• Export a dated copy at the end of every week, and after any big session.
• Keep one copy somewhere other than the machine you write on.
• Open a backup once a month and scroll to the end.
• Know what your app does when you stop paying, before you stop paying.

Then go back to the book. The point of all this is to never have to think about it again.