Backup Before Change: The Copy That Makes Undo Possible

Last updated September 6, 2026

Just before anything that overwrites your site, a copy of it is taken first. An update, a staging publish, a restore. Each one takes a copy of the site as it was a second earlier, so that any of them can be undone.

This is the switch behind the Undo button. With it on, a plugin update that breaks a page is one click from not having happened. With it off, that click does not exist.

Three kinds of backup, and this is one of them. Automatic — taken nightly, kept in our cloud, free. Manual — taken when you press the button, downloadable. Before a change — taken for you, and what Undo restores from.

Taken: Before every update, publish and restore
Kept in: Your own space on the server
Costs you: Disk from your plan allowance
Downloadable: Yes

What Sets One Off

Three things, and only three:

An update — WordPress core, a plugin or a theme, whether you pressed the button or it ran on schedule.
Publishing a staging copy over the live site.
Restoring a backup, including restoring one of these.

Ordinary work does not set one off. Editing a page, uploading an image, changing a setting: no copy is taken, and none is needed, because none of those replace the site wholesale.

Where It Is

The switch is at the top of Backups, under the automatic one. The chip beside it shows how much of your disk these copies are currently using.

The two backup switches: Automatic backups kept in the cloud for free, and Backup before change kept in your own files — The two switches. The one below decides whether a copy is taken before an update, a publish or a restore.

The copy itself appears in the website’s list under Backup before change, and it carries the reason it was taken — “before updating 4 plugins” — which is the whole basis for choosing it over the copy next to it.

The How backups work dialog on the Before a change tab, explaining that this is what the Undo button restores from — The “Before a change” tab of How backups work. This is what the Undo button restores from.

Using It

After an update, the panel offers Undo. That restores this copy: the site exactly as it was immediately before the update ran.

You can also reach it the long way: open the website in Backups, find the copy under Backup before change, and press Restore. Same copy, same result.

Only the most recent is kept. Your plan allows a small number of these per website, often one, so the copy from before today’s update replaces the copy from before last week’s. It is protection against the change you just made, not a history. For a copy that survives, take a manual backup.

What Happens When There Is No Room

These copies come out of your own disk allowance. If there is not enough space for one, the action refuses to run rather than running unprotected. An update that cannot be undone does not start.

That is deliberate, and it is the opposite of what most systems do. A silent update with no way back is exactly the situation this exists to prevent, so we would rather tell you the update did not run than let it run without a net.

If you hit that, free some disk (delete an old manual backup, or clear something out of the site) and run it again.

Turning It Off

There is one honest reason to: space. If your disk is genuinely tight and updates are refusing to run, turning this off lets them run.

The confirmation for turning off backup-before-change, warning that the Undo button will no longer appear — Turning it off. The warning is the point: without these copies, the Undo button does not appear.

What you lose. Updates, staging publishes and restores stop keeping a copy of the site as it was. If one of them breaks something, there is nothing to undo it with and the Undo button does not appear. Your nightly backups are unaffected, being in our cloud and costing you nothing, but the newest of those is from last night, not from one second before the change.

Our advice is to leave it on and solve the disk problem instead. Being unable to undo an update costs more than the space, the first time it matters.

Questions

Is this the same as an automatic backup?

No. Automatic backups run nightly, live in our cloud and cost you nothing. This one is taken at the moment of a change, lives in your own space and uses your disk. The nightly copy is from last night; this one is from a second before the thing that broke.

Why did my update refuse to run?

Most likely there was not enough disk for the copy that has to be taken first. Free some space and try again. The panel says so in the message.

How long is it kept?

Until the next one replaces it. It is not a history; it is the most recent way back.

Can I download it?

Yes. It is in your own space, so its row carries Download like a manual backup’s does.

Does it protect me from a hack or a bad edit?

No. Nothing sets one off except an update, a publish or a restore. For anything else, that is what the nightly copies and your own manual backups are for.