Backups & version history
How Webflow's automatic backups and version history work, and how to restore a previous version of your site if something goes wrong.
Webflow automatically saves a history of every published version of your site. If something goes wrong — a bad edit, an accidental delete, or an update that broke something — you can roll back to a previous version.
Quick summary
Webflow saves a version of your site every time you publish. You can view the version history in the Designer and restore a previous version at any time. Restoring takes your site back to exactly how it looked at that point. This is your safety net for bad changes.
How version history works
Every time you click Publish in Webflow, the platform takes a snapshot of your site at that moment. These snapshots are stored as your version history.
If you ever need to go back — for any reason — you can select a previous snapshot and restore it. Your site will revert to exactly how it was when that version was published.
Accessing version history
Version history is accessed through the Designer (not the Editor). This means you may need Chykalophia's help to restore a version, unless you have Designer access.
Open the Designer for your project (from the Webflow Dashboard).
Look for the "Backup" or "Version history" option. In the Designer, this is usually found in the top navigation or under a menu option. The exact location may vary slightly by Webflow version.
Browse the version list. Each version is labeled with the date and time it was published.
Preview a version to see what it looked like.
Restore the version you want. Click the restore option and confirm. Your site will be set back to that version.
Publish after restoring. Restoring a backup doesn't automatically push it live. You'll need to click Publish to make the restored version live.
Restoring overwrites your current version
When you restore a previous version, your current site (including any recent changes) is overwritten. Make a note of anything you want to preserve before restoring.
CMS content and backups
CMS items (blog posts, team members, etc.) are stored separately from the site's design and page structure. Version history covers the site design and static content — but changes to CMS items may not be fully recoverable through version history.
If you accidentally delete or corrupt a CMS item, contact Chykalophia as soon as possible.
How many versions are saved?
Webflow retains version history for a period of time, but the exact number of versions depends on your plan. Older versions may eventually be pruned. Don't rely on version history as your only backup for critical content.
Best practices
- Publish frequently. Each publish creates a new restore point. If you publish after every meaningful change, you'll always have good restore points available.
- Note what you changed. Before making significant edits, take a screenshot or note what the site currently looks like, so you have a reference if you need to restore.
- Don't wait to report problems. If something looks wrong after an edit, contact Chykalophia quickly — the more recent the issue, the easier it is to fix.
Common questions
Related guides
- How publishing works in Webflow
- Staging vs the live site
- Troubleshooting Webflow problems
- Editing content safely in the Editor
Need a hand?