A Webflow app for people who look after CMS content
Snapback keeps snapshots of your collections. When something gets overwritten or deleted, you can see what changed and put back the items you choose. The rest of the site stays as it is.
Currently in Webflow marketplace review. The free tier stays free. No card, just an email when it's live.
A client writes at 14:37 on a Tuesday: "Can you get Monday's product descriptions back? Just the descriptions." Restoring Monday's site backup would also throw away everything else edited since Monday. Here is the same Tuesday with Snapback:
Free
Capture a collection whenever you like and export it as CSV or JSON. This part only ever asks Webflow for read access.
Free
Compare two snapshots, or a snapshot against the live CMS. You see which items changed, which fields, and both versions of the text.
Paid
Put back one item, several, or a whole collection, in place. Changes land staged so you can review before publishing. Paid plans also add nightly snapshots.
Paid plans are priced per protected site. A protected site gets nightly snapshots and unlimited restores. Snapshots, diffs and exports cost nothing on any site, and that stays true. Annual billing gives you two months free.
Free
any number of sites
Studio
3 protected sites
Agency
15 protected sites
Agency+
unlimited protected sites
| Option | Restores | Granularity | Undoes other work? |
|---|---|---|---|
| Webflow site backup | Pages, design and CMS together | Whole site | Yes. Everything since the backup. |
| CSV export, then re-import | CMS, if you exported in time | Collection | No, but reference fields and rich text often break, and items duplicate. |
| Backup apps that restore as copies | CMS | Item, as a duplicate | No, but you re-link references and delete the originals by hand. |
| Snapback | CMS | Item, in place | No. Staged changes, you publish. |
Field data and asset URLs for the items you pick, in the primary locale. Restored items land as staged changes and publishing is a separate step you take yourself. Deleted items are re-created, and if other items referenced the old one you get a warning listing them.
Not until you restore something. Installing grants read access only. The first time you restore, Webflow shows a second consent screen asking for write access, and you can say no.
Snapback takes a fresh snapshot automatically, so the restore itself can be undone.
Site backups take the entire site, pages and design included, back to a moment in time. Snapback works at the level of individual CMS items and leaves everything else alone.
Why this exists
I build and look after Webflow sites, and one too many bulk edits taught me that "restore backup" is a scary button when only twelve items are broken. So I built the tool I wanted that Tuesday. Questions or doubts, write me: support@ausiejus.lt. I read everything. Ignas