How to back up Webflow (and restore deleted data)

In short: Webflow's site backups restore an entire site to an earlier restore point. You cannot bring back a single deleted CMS item or asset, and a restore resets scheduled items, reCAPTCHA keys and every item's "Published on" date. ProBackup snapshots your Webflow CMS collections, items and assets every 24 hours and restores individual items without rolling back the whole site.

Why Webflow's own protection is not a backup

Webflow's backup feature is built for one job: undoing design work. It does that well. It was not built to recover a blog post an editor deleted last Tuesday, or 300 CMS items an integration wiped, without also rewinding every other change made to the site since.

What Webflow gives you natively (checked 2026-09-16):

• Site backups (restore points). "Restore points are created automatically on every 50th auto-save", and you can save one manually with Command + Shift + S. Paid Site plans (Basic, CMS, Business, Enterprise) keep unlimited backups. Sites on the free Starter plan "can only be restored from one of the two most recent backups, unless you have a paid Workspace plan". Only Site managers can access backups. Webflow does not offer scheduled backups. Source: Webflow, Save and restore backups
• A restore is all or nothing. Restoring puts the whole site back to that restore point. Side effects listed by Webflow: scheduled Collection items are moved to the publish queue, the "Published on" date of every Collection item is set to the current date, reCAPTCHA keys must be re-added, bot blocking is switched off, and backups created before 25 March 2024 reset Collection and item IDs used by API integrations. Same source.
• No CMS recycle bin. Deleting a Collection "can't be undone, unless you restore your site from a backup". Deleted Collection items are removed from the Collection (they stay on the live site only until the next full-site publish). Sources: Delete Collections, Collection items overview
• CSV export. Each Collection can be exported to CSV, one Collection at a time, manually. Reference and multi-reference fields come out as plain text and have to be re-linked by hand on import. Source: Migrate CMS Collection content to another project

Webflow's restore points and ProBackup are complementary. Keep using restore points for design. Use ProBackup for content.

How to back up Webflow with ProBackup

ProBackup is a SaaS backup service that takes automated daily snapshots of your cloud app data and lets you restore individual records, files or whole projects back to the original account. For Webflow, the unit of work is the CMS: collections, collection fields, collection items and assets, plus the site, page and user metadata around them.

1. Start a trial at app.probackup.io/onboarding. The 7-day trial needs no credit card.
2. Select Webflow and connect via OAuth. Webflow shows its own authorisation screen where you choose which sites ProBackup may access. ProBackup never sees your password; access is limited to the scopes you grant and can be revoked in Webflow at any time. [verify: site selection happens in Webflow's OAuth screen vs inside ProBackup]
3. Choose your storage region. Nine AWS regions are available; you select one at signup. Changing region after the first backup requires support assistance.
4. Let the first snapshot run. It starts automatically and completes within 24 hours. After that, ProBackup takes a new snapshot every 24 hours with no scheduling on your side, and only stores new revisions of items that changed.
5. Optional extras. Smart Alerts (Pro and Premium plans) warn you when a snapshot shows a mass deletion. Google Drive sync (Pro and Premium plans) keeps a spreadsheet copy of each Collection; if a Collection has more than 50,000 items no Sheet is created, but the AWS backup remains active.

Snapshots are stored on AWS S3 with AES-256 encryption at rest and TLS in transit. ProBackup is SOC 2 Type II certified (since May 2025) and GDPR compliant.

What is (and is not) backed up

The Webflow Data API exposes content, not the Designer canvas. ProBackup therefore backs up what the API exposes:

Not backed up: the visual design (classes, styles, interactions, component definitions), custom code, site settings and redirects, form submissions, Ecommerce orders and customers, Logic flows and Analyze data. [verify exclusion list with the Webflow integration owner] These are either not exposed by the Webflow Data API or outside ProBackup's scope, and Webflow's own restore points remain the right tool for the design layer. ProBackup captures only the first 2,000 characters of a text field. [verify: applies to Webflow rich text]

How to restore deleted Webflow CMS items, Collections and assets

1. Open your Webflow backup in ProBackup, pick the site and the Collection.
2. Choose the snapshot date, the last one taken before the deletion. Global Search finds an item by name across snapshots (unlimited on Pro and Premium; 3 free uses per month on Plus).
3. Select one item or a filtered set and click Restore.
4. ProBackup writes the item back through the Webflow API. "When you restore a collection item, a duplicate is created in the related collection." Restoring a Collection creates a duplicate Collection; restoring an asset adds it back to the site.
5. Publish your site (or the item) in Webflow. Restored items arrive as CMS content and follow Webflow's normal publish flow. [verify: restored items land as drafts or published]

Two things to know before you click:

• Restore mode. ProBackup supports two restore modes across its platforms: create new duplicate records, or overwrite existing records field by field. Webflow restores currently create duplicates, the safe option: nothing that still exists on your site is changed, and Webflow's own restore points are never touched. [verify: the landing page mentions merging selected fields into existing items; the support article documents duplicates only]
• IDs and references. A duplicate item gets a new Webflow item ID. Update any integration that stored the old ID, and check reference fields that pointed to the deleted item. [verify: how reference fields are handled on restore]

Restores go back to the original Webflow site only. ProBackup is not a migration tool; for moving content between sites use Webflow's CSV export.

Frequently asked questions

Does Webflow have a recycle bin for deleted CMS items?

No. Deleted Collection items and Collections cannot be recovered on their own; Webflow's only native path is restoring the entire site to an earlier restore point, which rewinds every other change made since and resets the "Published on" date of all items (checked 2026-09-16). ProBackup restores the single item instead.

How many backups does Webflow keep?

Paid Site plans keep unlimited restore points. Free Starter sites can only restore from the two most recent backups unless the Workspace is on a paid plan. Restore points are created on every 50th auto-save or manually; there are no scheduled backups. ProBackup adds a snapshot every 24 hours and keeps it for 6 months on Plus, 2 years on Pro and unlimited on Premium.

Can ProBackup restore my Webflow design?

No. ProBackup backs up and restores content: collections, collection items and assets. Design, custom code and site settings live in Webflow's restore points. Use both.

Start backing up Webflow today

Plans start at $25 per month, billed yearly (Plus $25, Pro $38, Premium $69 per month, billed annually), and one licence covers every connected app. Join the 4,000+ teams already protecting their SaaS data: start your 7-day free trial. No credit card required; your first Webflow snapshot is ready within 24 hours.