How Your Writing Is Saved (You Can Stop Worrying) by node

If you’re wondering why there’s no save button. There is no save button because everything saves automatically, through several layers that protect your work. Here is what actually happens when you write. While You Type Three things fire in the background, on different timers: After 3 seconds of quiet your draft saves to your browser's local storage (IndexedDB). This is instant and works even if your internet drops. After 5 seconds the full document saves to the server. Title, body, formatting, everything. This is the real save. After 30 seconds a revision snapshot gets stored on the server. We keep up to 20 of these, so you can look back at earlier versions of your work. All three timers reset every time you type. So if you are writing steadily, the 3 second local save fires frequently, the 5 second server save follows close behind, and the 30 second revision snapshot captures periodic checkpoints. Books and Chapters Chapters follow the same pattern. When you switch between chapters, the current one saves automatically before the next one loads. During collaborative editing sessions there is also a 30 second interval timer that saves regardless of whether you are actively typing. If You Close the Tab The editor has a last resort safety net. When you close the tab or navigate away, a synchronous emergency save fires into localStorage. This is the browser's built in storage and it works even if the network request to the server does not complete in time. Next time you open the editor, it checks for this emergency save and offers to recover it. What This Means in Practice Your work is protected at three levels: local browser storage, the server, and revision history. Even a sudden power cut or browser crash would lose at most a few seconds of typing, because the local draft saves so frequently. You can just write. That is the whole point.