cPanel Backup Wizard can restore WordPress safely when you understand what it will overwrite. This method is best for restoring home directory files, MySQL backups, or a provider-restored full cPanel account after a bad update or accidental deletion.
Audience: shared-hosting users and small businesses with cPanel access. Use this with the matching backup method whenever possible. If you did not create the backup yourself, verify the backup date, scope, and site path before restoring production.
Before restore
- Confirm whether the backup is a full account backup or a partial files/database backup.
- Identify the correct WordPress document root and database name.
- Download the current broken site first if there is any chance you need newer uploads, orders, or form entries.
Restore steps
- Open Backup Wizard in cPanel.
- Choose Restore, then select Home Directory or MySQL Databases for partial recovery.
- Upload the matching backup file for the restore type.
- If restoring both files and database, restore the database and matching files from the same backup date.
- Check wp-config.php database settings after restore.
- Clear cache and test login, media, forms, checkout, and permalinks.
Post-restore verification
Visit the home page, wp-admin, an older post, a newer upload, and the most important form or checkout flow. If only files were restored, confirm content is still current.
Also check server and application logs, cache layers, CDN behavior, SSL, redirects, and whether scheduled tasks still run. A restore is not complete just because the home page loads.
Restore risks
- A full cPanel account restore may need the hosting provider or WHM.
- Restoring an older database can remove newer content.
- Restoring the wrong database can make WordPress show the wrong site.
Rollback planning
Before restoring, keep the current state long enough to recover anything the restore might erase. For stores and membership sites, that means orders, subscriptions, users, payments, form submissions, bookings, and logs. For agencies and hosts, it also means customer communication and a timestamped maintenance note.
Fix I.T. Phill recommendation
Use cPanel Backup Wizard when it matches how the backup was created. If the restore tool is not available, fall back to files plus database restore, but test on staging first. After restore, update the backup plan so the next recovery is easier.
Related Fix I.T. Phill Guides
- How to Restore WordPress: Complete Recovery Methods Guide
- How to Restore WordPress by File Manager and phpMyAdmin
- How to Restore WordPress by WHM Full Account Restore
- How to Restore WordPress by cPanel WP Toolkit
- How to Restore WordPress by Plesk WP Toolkit
- How to Restore WordPress by Plesk Backup Manager
- How to Restore WordPress by Softaculous
- How to Back Up WordPress: Complete Methods Guide
- How to Back Up WooCommerce Without Losing Orders
- How to Test a WordPress Backup Restore Before an Emergency
- Disable WordPress plugins with phpMyAdmin when wp-admin is broken
Sources Checked
- cPanel Backup Wizard documentation
- cPanel site backup with File Manager and Backup
- cPanel MySQL backups with phpMyAdmin
2026 SEO Refresh: cPanel Backup Wizard WordPress Restore Checklist
Admin action path: Use Backup Wizard for account-level recovery evidence, then verify WordPress-specific behavior outside cPanel.
What to verify before changing production
- Capture the cPanel backup date and account scope.
- Confirm files, databases, mail, DNS-related settings, and SSL material after restore.
- Keep the old account available until public DNS and forms are verified.
Source-backed references and next reads
- Official reference: cPanel Backup Wizard documentation.
- Official reference: cPanel WP Toolkit documentation.
- Related FixItPhill guide: WordPress backup restore point check.
- Related FixItPhill guide: test a WordPress backup restore.
- Related FixItPhill guide: cPanel full account backup migration.
- Related FixItPhill guide: Plesk Backup Manager restore.
Ticket evidence should include the tool used, backup timestamp, restore target, changed DNS or SSL state, visible public URL, and the exact verification steps completed after the change.
