Why Your Changes Are Safe: Autosave Explained

Storynote has no save button because it saves for you, continuously. Understanding how this works will put your mind at ease and tell you exactly what to do in the rare case something looks off.

How autosave works

As you write, Storynote tracks your changes and saves them in the background. It does this on a regular interval while you work, and again at the moments most likely to matter: when you switch away from the tab, when your connection comes back online, and when you navigate to another card or away from the app. Even closing the tab triggers a final save of your latest changes.

The effect is that your work is captured continuously without you thinking about it. There is no single risky moment where unsaved work could vanish.

If something looks unsaved

In the vast majority of cases your work is saved even when you are not sure. If you are ever uncertain, here is what to do:

• Wait a moment. Autosave runs on an interval, so a very recent change saves shortly after you make it. Give it a beat before worrying.
• Stay on the page until it settles. If you have just typed something and immediately want to close the tab, pause for a second so the save can complete.
• Check your connection. Saving needs the network. If you were offline, your work is held and saved when the connection returns, so reconnect before closing the app.
• Reload to confirm. If you want certainty, reload the card. Your saved content will be there.

A note for collaborators

In a shared story, saving and syncing keep everyone's view current. If you are co writing and something looks out of date, a reload usually brings you back in sync. For how shared stories behave, see co-writing in real time.

If problems persist beyond a quick reload, check browser and device support to make sure you are on a supported setup.