Chapter 7 · Where Your Work Lives

Versions: Checkpoints, Named Saves, and Restoring

Version history is the part of a writing tool nobody thinks about until the afternoon they need it. Storskarvia keeps two kinds: one you make, and one it makes for you.

Two kinds of version

Automatic checkpointNamed version
Made byStorskarvia, while you workYou, when a moment deserves a name
How oftenOn a ten-minute cadence, and only when the document has changed since the last oneWhenever you ask
Shown in the list ascheckpointThe name you typed
How many are keptThe twenty most recent per documentAll of them. Named versions are never pruned

The "has it changed" test covers structure as well as words, so splitting a row, moving a scene, or repositioning an image counts as a change even when the plain text is identical. A document with nothing in it yet is never checkpointed, which is why a brand new file shows no history for the first few minutes.

Checkpoints are a safety net measured in hours. Named versions will still be there in March. Name the drafts you would grieve.

Versions ▾ sits in the editor's top bar, beside Share ▾ and Export ▾. It appears on documents you own. If you are working in someone else's draft through a share link, there is no Versions menu, because the history belongs to the person whose document it is. Share Links, Reviewers, and Editors covers what a reviewer or an editor can do instead.

Open the menu and you get Save version… at the top and the list below it, newest first. Each row carries:

  • The version's name, or the word checkpoint for an automatic one.
  • The date and time it was taken, in your own timezone.
  • Its word count. This is the fastest way to find the version from before you cut forty pages.
  • A Restore button.

The menu lists the 80 most recent versions. With checkpoints capped at twenty, reaching that ceiling means you have named a great many drafts.

Saving a named version

Click Save version… and type a name at the prompt, which suggests something in the shape of "Draft 2 before notes". Names are capped at 120 characters. A longer one is trimmed to fit and saved.

Storskarvia flushes any unsaved typing before it takes the snapshot, and it waits for that flush to land. Without that wait, the version would capture the document as it was before your last change.

If the flush fails, no version is kept, and the status bar says so in as many words: "Could not save the document, so no version was kept". A version of the wrong text, filed under the right name, would be worse. Wait for the sync chip in the status bar to settle, then try again. Chapter 3 explains what the chip is telling you.

Name versions for the decision you made. The date is already on the row.

Restoring

Click Restore on any row. A confirmation asks: "Restore this version? Your current text is saved as a backup version first." It means exactly that. In order:

  1. Your current text is saved as a version called pre-restore backup.
  2. The document on screen is replaced with the restored text.
  3. For a Dropbox or Google Drive document, the storage state returns to pending, and the restored copy is pushed back to your cloud while that account is connected.
  4. For a novel, the per-chapter text files that travel with the document are rebuilt from the restored draft, so they match the manuscript you now have.
  5. For a document saved to a folder on this computer, the restored text is written straight back into that folder. See Chapter 6.

If the restore fails, the manuscript on screen is left exactly as it was. A dropped connection or a server error puts "Could not restore that version. Nothing was changed" in the status bar. A refusal with a reason opens a dialog that gives the reason. The one you are most likely to meet is for a cloud document whose newest text Storskarvia could not read back from your Dropbox or Google Drive: "Storskarvia could not load this document's current text from your cloud file, so it cannot restore a version over it yet. Reload the page and try again." Restoring then would leave an empty pre-restore backup, so Storskarvia stops. When a restore works, the status bar reads "Version restored".

Restored the wrong one? Open Versions again and restore the pre-restore backup sitting at the top of the list.

The versions you did not make

Two named versions appear in the list without you asking, and both are there to catch something:

NameWhere it came from
pre-restore backupThe text that was on screen immediately before a restore.
conflict backup 2026-08-14 09:12Your unsynced working copy, kept at the moment Storskarvia found a newer file in your cloud and adopted it. Both drafts survive and you choose between them here. The time in the name is UTC, so it can differ from the time shown under it.

Both carry names, so neither is ever pruned. If a conflict backup turns up you did not expect, something edited that file outside Storskarvia: another machine, another editor, or a collaborator with access to the same folder. Chapter 3 covers how that adoption works.

What lands in .versions/

Saving a named version on a Dropbox or Google Drive document, while that account is connected, also uploads a copy into the .versions/ folder beside the document, named title-date-time-version name.skarvia.json. Each file is a complete document.

Automatic checkpoints for an ordinary cloud document are not uploaded. They live on Storskarvia's side and appear only in this menu. The exception is zero retention, below.

For a document saved to a folder on your own machine, your browser writes named versions into a .versions folder inside the folder you chose, using the same shape of filename. Checkpoints for those documents stay on Storskarvia's side.

The folder name starts with a dot, so most file browsers hide it by default. Leave it where it is. Deleting .versions/ during a tidy-up throws away your own copies of the history.

Zero-retention documents

Zero retention is the setting that stops Storskarvia holding a copy of your manuscript at rest. Version history has to follow that promise, so it works differently:

  • Save version… is refused. Honouring it would mean storing the manuscript, which is the one thing the setting forbids. The status bar explains that this document's history lives in your cloud .versions/ folder instead.
  • Automatic checkpoints still happen, written straight into that .versions/ folder and filed under the name auto.
  • Restore is refused too, because it would keep a pre-restore backup on Storskarvia's side. The dialog says "Zero retention is on for this document. To restore a version, untick Zero retention in the storage dialog, restore it, then tick the box again."
  • A zero-retention document with no storage path set gets no checkpoints at all. There is nowhere to put one that keeps the promise, so none is taken. Give the document a home before you rely on its history.

One sharp edge is worth planning around: turning zero retention on deletes every version Storskarvia is currently holding for that document. The checkbox is a claim about what is stored, and leaving a table full of old copies behind would make it a false one. Copies already in your cloud .versions/ folder are untouched. If there is a draft in the list you want to keep on hand, restore it or export it before you turn the setting on.

Using a version as a revision mark

Under Export ▾, PDF with revision stars… asks which version to compare against, offering the nine most recent, then asks for a revision name to print in the page header. What changed since that version comes out marked in the margin, which is how a production draft is circulated.

With no versions saved at all, that export declines and tells you to save one first, so a script heading into revisions is worth naming a version before the notes arrive. Watermarked Drafts and Revision Stars covers the export itself, in Part VIII.

Updated 2026-10-15 · Full contents · Something wrong or missing?

Start writing free