Independent app · every restore is one item, in place, never the whole site
RevertKit keeps a version history for every CMS item (who changed what, field by field) and rolls back a single item with one click. Same item ID, same references, nothing else moves. Deleted items included.
The Wishlist request for CMS undo has sat unanswered for a decade with 625 votes. Webflow's own backups can't do it: restoring one rolls back your entire site, design, pages, every collection. So we're building the missing layer as an independent app.
Item history · Blog post: “Pricing update 2026” · preview
| Version | When | What changed | |
| v14 · current | Today 14:02 · Editor | Body −1,412 words · Slug /pricing-update /test-2 | the bad edit |
| v13 | Today 09:15 · You | Hero image replaced · CTA link updated | Restore this version ↩ |
| v12 | Mon 13 Jul, 16:40 · Client | Title Our 2026 pricing Pricing update 2026 | compare |
| v1 – v11 | Jun 2026 | Full field-level history, every change captured automatically | … |
None of this is your team's fault. There is simply no history layer under the CMS. Until now.
One mis-paste into a rich-text field and the old copy is gone the moment it saves. Client edits overwrite your work silently. There's no Cmd-Z after save, and no way to even see what it looked like before.
RevertKit: every save becomes a version, automatically.
Webflow's backups snapshot the whole site. To recover one mangled collection item you must roll back everything: design changes, new pages, every other item edited since. Nobody does it, so the bad edit stays.
RevertKit: restore one field, one item, or one collection. Nothing else moves.
There is no trash can for CMS items. A wrong click while cleaning up a collection (or a client "tidying" the site) and the item, its content and its images are unrecoverable.
RevertKit: deleted items stay in the timeline, restorable with their content and captured references.
Why "in place" matters: tools that restore by creating a copy of the old item give it a new ID, breaking links, collection references and integrations, and leaving you to clean up duplicates. RevertKit writes the previous values back into the same item. Your site never notices anything happened.
On Framer instead? Same gap: Framer's version history covers the canvas, explicitly not CMS content. We're building RevertKit for Framer's CMS on the same engine. Pick your platform in the form and you join that queue.
Founding subscription
$99
/first year, up to 5 sites
Then $9/site/month, price locked for as long as you subscribe. Full version history, field diffs, in-place restore, deleted-item recovery, daily snapshots, CSV/JSON export.
Agency founding
$299
/first year, up to 25 sites
Flat, not per-site. One dashboard across every client site, per-site history timelines, and a client-safe activity view you can forward instead of investigating "what changed" yourself.
More than 25 sites, or white-label under your agency's name: mention it in the form.
No card now. We'll email you to confirm before anything is charged.
For the site as a whole, yes, and they're good at what they do. But they're snapshots of everything at once: restoring one means rolling back your design, pages and every CMS item together. There is no per-item history, no field diff, no way for an editor to undo a single change, and no recovery for a single deleted item. RevertKit adds exactly that layer, and only that layer.
RevertKit restores by writing the previous field values back into the same item through the official API. The item ID never changes, so internal links, collection references and any integrations keyed to the item keep working. No duplicate items to clean up. For an item that was deleted, Webflow requires creating it anew; RevertKit recreates the content and automatically re-points the reference fields it had captured toward the restored item.
Official Webflow API with OAuth: you authorize with your Webflow login, we never see your password, and access is limited to CMS scopes. Your design, classes, pages and custom code are untouchable by us. Version data is encrypted at rest, exportable as CSV/JSON at any time, and deleted on request. Revoke access from your Webflow dashboard whenever you like.
RevertKit captures changes as they're saved, whether or not the site has been republished, so it also answers the classic "who changed this and did it go live" question. Restores land as staged changes, and you choose when to publish them, exactly like any other edit.
Any Webflow site on a site plan with API access (CMS, Business or Enterprise), which is every site that has a CMS in the first place. Localized content is versioned per locale.
You export everything, every version of every item as CSV/JSON, and go. A safety product you're locked into isn't a safety product.
No. RevertKit is an independent product built on the platforms' public APIs. Webflow is a trademark of Webflow, Inc.; Framer is a trademark of Framer B.V. This site and product are not affiliated with, or endorsed by, either.
Webflow first, to founding customers in waitlist order. Framer follows on the same engine. Its queue is ordered the same way, so picking Framer in the form is not a "maybe later" bucket, it's a position in line.