Chapter 3 · Where Your Work Lives
Where Your Work Lives: Storage, Autosave, and Versions
Most writing apps keep your manuscript and lend it to you. Storskarvia is built the other way round: your Dropbox, your Google Drive, or a folder on your machine holds the real files, and Storskarvia keeps a working copy so it can do its job. This chapter explains exactly what is written, where, and when.
The model
Your manuscript's home is your storage. Storskarvia writes real files into it as you work, in formats that outlive this application, and holds a working copy on its own side for checks, pagination, and rendering. If Storskarvia disappeared tomorrow, your book would still be sitting in your Dropbox in a form you can open.
That is why Storskarvia asks where a document lives the moment you open it, instead of burying the choice in a settings page nobody visits.
The storage question
When you open a document of your own that has no home yet, a dialog asks "Where should this document live?" with three choices in the Provider list:
- This computer (choose a folder)
- Google Drive
- Dropbox
Someone you have shared the document with never sees this question. Where a document lives is the owner's decision about the owner's storage.
Choosing a cloud provider you have not connected yet shows a Connect Dropbox or Connect Google Drive button first. That is a standard OAuth handoff, and the permissions are scoped as narrowly as each provider allows. Once connected, you get a Folder & file name field:
- For Dropbox, the path you type is the path used.
- For Google Drive, the path is inside your My Drive, and Storskarvia proposes a
Storskarvia/folder by default.
Below the field, a line previews what will be created. Press Save here to commit, or Not now to keep writing and decide later. Answering "Not now" is safe: your work is still held and still autosaved, it has no home of its own yet, and the status bar reads ⚠ choose where this doc lives until you pick one.
What gets written
For a cloud destination, Storskarvia writes:
| File | What it is |
|---|---|
title.skarvia.json | The full document, with all its structure, formatting, and metadata. This is the file Storskarvia reads back. |
title.txt | Plain text of the same document. No app is required to open it, now or in thirty years. |
.versions/ | A folder beside your document holding copies of the versions you name yourself. |
title.chapters/ on Dropbox,
title chapters on Google Drive | Novels only, once Storskarvia has
detected at least two chapters: one plain-text file per chapter, numbered and named
(01 - Opening.txt). Renaming or removing a chapter deletes its old file, so no
orphans pile up. |
A folder on your own machine gets the first two, plus .versions/ copies of the
versions you name yourself. Only the cloud sync writes chapter files, so a local folder receives
the whole document in one file.
Chapter 6 covers the differences.
The path Storskarvia suggests follows your binder: the project title, then the binder folder the document sits in, such as a part or a season, then the document title. Change it if you prefer another layout.
Dropbox paths are full paths and must start with a slash, in the form
/My Novel/Chapter 1. They are relative to the app folder Dropbox gives Storskarvia, so
that document lands at Apps/Storskarvia/My Novel/Chapter 1; see
Chapter 4. Google Drive
paths are relative to your My Drive. In both cases you are naming the document, and the extensions
above are added for you.
Storskarvia will not overwrite a file it did not write. If you point a new
document at a path where its .skarvia.json, its .txt, or its chapters
folder already exists, the first push stops. The status bar reads ⚠ name already taken
in followed by the path, and the file that was there stays untouched: Storskarvia neither
loads it into your document nor writes over it. Click the status bar, choose a different name or
folder, and the document syncs to the new path.
Saving to this computer
"This computer" uses your browser's folder-access permission and writes the same files into a folder you choose. It needs a browser that supports it: Chrome, Edge, or Brave. In other browsers the option is greyed out.
The one thing that catches almost everybody: your browser will not let any website save directly into your Desktop, Documents, or Downloads folder. It treats them as system folders and refuses, usually with a message along the lines of "can't open this folder because it contains system files". Nothing is broken. Every web application lives with the same rule.
The fix: make a dedicated folder and choose that instead. A new folder called "Storskarvia" inside your Desktop works fine. Only the Desktop itself is blocked, and its contents are not. If you would rather not think about it at all, Dropbox and Google Drive save anywhere with no such restriction.
Autosave and the status bar
Autosave runs as you type. There is no save button to remember. The button on the right of the status bar shows where this document lives and whether the last few sentences reached it:
| It reads | Meaning |
|---|---|
| ✓ saved to | Your cloud file is current. |
| … saving to | A push is on its way. |
| ✗ retrying: | The last push failed. Your changes are safe on Storskarvia and the next save tries again. |
| ✗ reconnect: | Dropbox or Google Drive signed Storskarvia out. A bar offers Reconnect Dropbox (or Google Drive) and Save somewhere else. |
| ⚠ name already taken in | Another file holds that path; see above. |
| Saved on this computer ✓ | The local folder is current. If it says (click to re-authorize), the browser wants your permission again. |
Clicking that button opens the same storage dialog at any time.
⌘S (Ctrl+S on Windows) still works. It sends the save immediately and the status bar flashes Saved, so the reflex is worth keeping and your browser's own "save this page" dialog stays out of the way.
Versions and checkpoints
Version history has two sources, and you should understand both:
- Automatic checkpoints. The server snapshots a document at most once every ten minutes while it is being worked on, and keeps the twenty most recent automatic checkpoints per document. You do not have to remember anything for this to happen. These stay on Storskarvia's side and are not uploaded to your storage.
- Named versions. Save one yourself whenever a moment deserves a name, with
Save version… in the Versions ▾ menu. "Draft 2 before notes"
is worth more than a timestamp six weeks later. These are also copied into
.versions/in your Dropbox, Drive, or local folder, so that history is yours as well.
Restoring is safe. When you restore an earlier version, Storskarvia first saves your current text as a version called pre-restore backup. Restoring the wrong one costs you a few seconds. Chapter 7 covers the Versions menu in full.
When the file changed elsewhere
Because the file is yours, you can edit it somewhere else: another machine, another editor, a collaborator with access to the same Dropbox folder. Storskarvia handles that on open:
- If the cloud copy changed since your last sync, Storskarvia adopts it. The newer file wins, which is what "your storage is the home" has to mean.
- If you also had unsynced edits, those are saved first as a version named conflict backup with the date and time. Both survive, and you choose between them in Versions.
- For a local folder, Storskarvia asks first: "The copy in your local folder is newer than this one. Load the local copy?"
Nothing is silently discarded in either direction, with one exception that belongs to the next section.
Zero retention
The storage dialog has a Zero retention checkbox for Dropbox and Google Drive. It is not offered for a folder on this computer. With it on, Storskarvia purges its working copy after every successful sync. Your cloud file becomes the only copy at rest, and Storskarvia re-fetches the text transiently when you open the document or run a check.
Weigh four consequences before you tick it:
- Ticking it deletes every version Storskarvia holds for that document, named
versions and checkpoints alike. Copies already in your
.versions/folder stay. If a draft in the list matters, restore or export it first. - From then on, history lives only in your
.versions/folder. Automatic checkpoints are written there, Save version… is refused, and so is restoring until you untick the box. Do not delete that folder while tidying up. - The conflict backup does not happen. Saving your unsynced text as a new version at the moment a sync arrives is the thing zero retention exists to prevent. Let the status bar read ✓ saved to before you edit the same document somewhere else.
- Everything else still works, but each open and each check has to fetch the file first.
If you are handling something sensitive, this is the setting you want. If you are writing a novel and would rather have a safety net you did not have to think about, leave it off.
Changing where a document lives
Click the storage button in the status bar, pick a different provider or path, then Save here. Storskarvia begins writing to the new location.
Files already written to the old location stay where they are. Nothing deletes your previous copies, which is deliberate, and it does mean you should tidy up the old folder yourself if you do not want two copies drifting apart.
The neighbouring subject, getting a finished document out as PDF, Word, Final Draft, or Fountain, is Part VIII. Storage is where the living document sleeps; export is what you hand to somebody else.
Updated 2026-10-11 · Full contents · Something wrong or missing?