ButterCMS now has Autosave. If a tab closes or your session expires before you save, the edits you made to a Page, Collection Item or Blog Post are waiting for you the next time you open it.
Autosave keeps those unsaved changes in your browser. It never saves anything to ButterCMS on its own: you decide what comes back.
The problem it solves
Picture a long Blog Post. You've rewritten the intro, fixed a few headings and swapped an image, and then a browser update restarts everything. Before Autosave, that work was gone, and the best advice our docs could give was to save often.
Now the same restart costs you a few clicks.
What you see when you come back
Open the item again and a banner tells you how many unsaved changes Autosave found in this browser. Until you act on it, the form shows the saved version, untouched.
The review lists only the fields that differ from the saved version, so a Page with dozens of fields and two edits shows you two rows. Restore the ones you want, discard the rest, or handle all of them at once. Restored or discarded everything by mistake? You can undo it until you edit a field.
To try it yourself:
- Open a Blog Post and edit a field.
- Close the tab or reload the page, then open the post again. If your browser asks whether to leave, confirm.
- Check the banner for the number of unsaved changes.
- Restore your change, then save or publish to keep it.
When a teammate saved first
Shared content raises an obvious question: what if someone saved the same field while your edits sat in your browser? Autosave flags that field and puts three values next to each other: what it held when you started, what's saved now, and what you typed. You pick which one stays, so nobody's work gets overwritten without you seeing it.
Schema changes are covered too. If a field you edited was removed or changed in the content type, Autosave still shows your text, so you can copy it before it's gone.
Three things to know before you rely on it
It isn't a save. Restoring puts values back in the form. They reach ButterCMS when you save or publish, not before.
It lives in one browser. A different browser, a different device or another person on the same browser won't see your changes, and open tabs don't sync with each other. If your browser can't store data, the editor tells you, so you know to save.
Saving clears it. Unsaved changes you haven't restored or discarded are cleared when you save. That includes previewing a Page or Blog Post, because preview saves first. Look at the banner before you hit save.
Who has it
Everyone who can edit a Page, Collection Item or Blog Post. It's on by default and doesn't appear on content you can only view. If you'd rather work without it, turn it off in Settings. That choice applies only to you, in that browser.
Give it a try
Autosave is already running in your dashboard. The next time a tab closes on you, reopen the item and pick up where you left off.
New to ButterCMS? Start a free trial and see it on your first Blog Post.
