Backup

Keep restore points before important WordPress changes.

Backups are part of the free core workflow, so administrators can keep restore points before staging creation, imports, restores, and production publishing.

Buy PUSH add-on Compare free and paid

Backup role

Confirm how to recover before the work starts.

Backups do not remove production risk, but they make release decisions easier to judge. For important releases, keep a host-level or off-server backup as well.

01 Manual backup Save WordPress files and database data before important staging or migration work.

02 Scheduled backup Start routine backup coverage without a paid license.

03 Restore and download Keep restore, download, history, and import controls in the free workflow.

04 Independent backup reminder For production releases, keep a backup outside the plugin as part of risk control.

Backup flow

Backup before the operation, not after the incident.

Create or confirm a recent restore point.
Download or keep an independent backup for important production work.
Run the staging, import, or dry-run workflow.
Review warnings before the operation changes data.
Use restore only when a rollback is actually needed.

Use cases

How this page fits into real WordPress release work.

Each feature page answers the operational questions an administrator checks before production data changes.

Before any overwrite Keep a fresh restore point before GET, import, restore, or PUSH changes files and database tables.

Routine protection Use basic scheduled backups so evaluation does not depend on a paid license.

Host-level fallback For important releases, keep an independent host or off-server backup in addition to plugin-managed backups.

Rollback planning Clarify what you would restore before starting a production operation, not after a release goes wrong.

Feature FAQ

Questions to answer before using this workflow.

Are backups free?

Yes. Manual backup, restore, download, import, retention, and basic scheduling remain in the free core.

Is a plugin backup enough?

For important production work, keep an independent host-level or off-server backup as well.

Does backup make publishing risk-free?

No. It improves recoverability, but host limits, plugin conflicts, data size, and live changes still matter.

Should I back up before PUSH?

Yes. Confirm an independent restore path before any production publishing operation.

Risk control

Backup and restore stay available in the free core.

The paid boundary is production PUSH, not basic recovery preparation.

Buy PUSH add-on