Back Up WordPress With wp-toolkit¶

Use this page when wp-toolkit offers backup or restore options for a site. wp-toolkit backups are useful before updates, security hardening, cloning, and testing, but they should not be the only backup for an important site.

wp-toolkit Backup Vs. cPanel Backup¶

For important sites, keep at least one backup outside the hosting account.

Create A wp-toolkit Backup¶

1. Open wp-toolkit.
2. Expand the correct site.
3. Look for Backup, Back Up, or a similar action.
4. Create a backup before updates, hardening, cloning, or removal.
5. Label the backup if wp-toolkit offers labels.
6. Confirm the backup completed.

WP-CLI Equivalent¶

Run these commands from the WordPress document root to create a database export and record the active WordPress software inventory.

wp db export ~/example-$(date +%F).sql
wp plugin list > ~/example-plugins-$(date +%F).txt
wp theme list > ~/example-themes-$(date +%F).txt

WP-CLI does not back up uploaded files by itself. Use a file archive or cPanel backup for the WordPress files and wp-content/uploads directory.

tar -czf ~/example-files-$(date +%F).tar.gz .

For important sites, store at least one backup outside the hosting account.

Before Restoring¶

Restores overwrite data. Before restoring:

1. Confirm the backup belongs to the correct site.
2. Confirm the backup date.
3. Create a backup of the current state if possible.
4. Consider what has changed since the backup was created.

Restoring an old backup can remove:

• New orders.
• Form entries.
• Membership changes.
• New users.
• Comments.
• Media uploads.
• Content edits.

When cPanel Backups Are Better¶

Use cPanel backups when:

• You need a copy stored locally or off-account.
• The entire account is being migrated.
• You need separate control over files and databases.
• wp-toolkit is not loading correctly.
• The site is too important to rely on one backup path.

Review WordPress backup guidance