Guide · checked 28 October 2026

How to restore an old version of a Framer site

Framer keeps two different kinds of old version, and they get back different things. Published versions let you put an older site back on your domain. Editor snapshots let you copy old layers back into the project. Neither one simply turns the whole project back to yesterday.

We run FrameVault, a Framer backup service, so we have a stake in this. Claims about Framer link to Framer's own help pages.

If the live site is broken: roll back the published version

From Framer's Staging and versions help page:

  1. Open Site Settings and go to Staging & Versions. Every time you click Publish, Framer adds a version to this list.
  2. Click a version ID to open its versioned link. Framer says these links are static: later publishes don't change them. This is the quickest way to see what the site looked like on a given day.
  3. If staging is on, click Deploy next to the version you want on your custom domain. The live site goes back to it while you fix the project.
  4. If staging is off, turn it on first (it needs a working live version), then deploy the older version.

To get old work back into the editor: Version History

From Framer's version history help page and Academy lesson:

  1. Open Version History from the Framer menu: File, then Version History (⇧⌘H on Mac, ⇧Ctrl H on Windows).
  2. Pick a snapshot. Framer keeps one every five minutes for the last four hours, one an hour for the last day, and one a day after that.
  3. Old versions are view-only. Select the layers or sections you need, copy them, go back to the latest version and paste.
  4. Repeat for every page and every breakpoint. Framer's own lesson says to check each breakpoint after pasting, because the page around it may have changed.

Some people report a whole-version restore option in Version History. Framer's help pages don't document one. If you see it, duplicate the project first so you can go back if the result isn't what you expected. A deleted page needs its own steps; see how to restore a deleted Framer page.

What these don't do

  • Rolling back the live site does not change the project

    The domain shows the old version, but the editor still has the broken one. The next publish from the project puts the broken version live again, so fix the project before you publish.

  • Copy and paste is one section at a time

    Fine for one hero or one footer. For a whole site, or a change that touched many pages, it is hours of work, and links between pages or to components can break on the way.

  • CMS content is a separate question

    Framer's version history help doesn't say it covers CMS items. Check each collection after a rollback. A CSV or JSON export is the safe way back for CMS content.

  • It all lives inside the project

    Version history goes with the project. If the project is deleted, or a client's workspace is closed, the history goes too.

Before a big change

  • Duplicate the project. A duplicate is the only full, editable copy Framer gives you.
  • Publish once before you start, so there is a known good version to roll the domain back to.
  • Export the CMS. Our free CMS export saves every collection, or keep an offline copy of the published pages with the free site-to-HTML tool.

What FrameVault does here

FrameVault archives your site on a schedule and keeps the copies outside Framer. Pro, Studio and Agency save the editable layout of every page with its CMS. One-click Restore puts a single page or the whole site back into the same project, CMS included, and Undo takes it back if you change your mind. Every plan keeps CMS backups you can download as JSON or CSV.

Start 7-day free trial →How restore works

7 days free, then $12/month. Cancel any time before day 7 and you pay nothing. Free: weekly CMS backups for one site · no card. Start free.