Backups

An editor backup is a snapshot of your whole project as it was at a given moment: your pages, sections, components, design system, workflows, formulas, variables, tables, APIs, authentication settings, environment variables, and integrations. If a change breaks something, you can restore one of those snapshots and get your project back the way it was.

WeWeb saves backups for you on a schedule, and you can also save one yourself before a risky change.

Opening your editor backups

1. Open the Settings tab in the top bar.
2. Click Editor Backups.

You will see the list of every backup available for the project, with its name, who created it, and when. A search field and a date filter above the list help you narrow things down when the list gets long.

On the right, the Your workspace plan panel tells you what your current plan includes: how often WeWeb backs up your editor, and whether you can create backups manually.

Automatic backups

WeWeb backs up your editor on its own:

• Once a day, at 11:59 PM UTC, on an Essential plan.
• Once an hour on a Pro or Partner plan.
• Every time you publish your app to staging or production.

A scheduled backup is only created if you actually worked on the project since the last one. If nothing changed, WeWeb skips it, so the list stays readable.

Automatic backups are named for you, and the Created By column shows 🤖 Automation:

• Automatic backup For a scheduled one.
• From publish v3 For the one taken when you published version 3 of your app.

FINDING THE RIGHT VERSION

The From publish backups are the easiest anchors to work with. If your app worked fine when you published v3 and something broke afterwards, the From publish v3 backup is the state your app was in at that moment.

Manual backups

Before a change you expect to be messy (reworking a whole page, changing your authentication provider, deleting tables that other parts of your app rely on), save a backup yourself so you have a clear point to come back to.

1. In the Editor Backups panel, click Create Editor Backup.
2. Give it a name that describes the state you are saving, for example Before pricing page rework.
3. Click Create.

Your backup appears at the top of the list with your name in the Created By column. There is no limit on how many manual backups you can create.

PLAN REQUIRED

Manual backups are available on a Pro or Partner plan. On other plans the Create Editor Backup button is disabled, and you can use the Upgrade plan button in the Your workspace plan panel.

Rolling back to a backup

1. Find the backup you want in the list.
2. Click Rollback Editor on that row.
3. In the Confirm Editor Rollback window, type Replace editor data in the field. This unlocks the Restore button, so you cannot roll back by accident.
4. Click Restore.

WeWeb replaces the current state of your editor with the state saved in that backup. Everything you have done since that backup is gone, and that cannot be undone, so create a backup of your current state first if you are not certain.

Once the rollback is finished, every editor open on the project reloads, including the ones your teammates have open.

Rolling back changes your editor only. It does not republish your app: your live version stays exactly as it is until you publish again.

YOUR DATA IS NOT PART OF AN EDITOR BACKUP

An editor backup saves how your project is built, not what is stored in it. The records in your tables and the files in your storage are not restored by a rollback. To restore data, use database backup and restore instead.

Learn more about database backup and restore →

Restoring with AI

If you use the WeWeb MCP server, your AI agent can list your editor backups, save a new one, and roll your project back to one for you. It saves the current state as a backup right before any rollback, so the operation stays recoverable.

Learn more about the WeWeb MCP tools →

CONTINUE LEARNING

Editor backups protect how your project is built. Your tables and files need their own safety net, with its own way of copying data between the editor, staging, and production.

Database backup and restore →