How to Back Up WordPress by cPanel File Manager and phpMyAdmin is for site owners who need a clean manual backup of one WordPress site, especially when one cPanel account hosts several websites. Use this method when single-site backups before troubleshooting, redesigns, plugin tests, migrations, or developer handoffs.
A good WordPress backup includes the website files and the database. The files carry themes, plugins, uploads, configuration, and custom code. The database carries posts, pages, users, settings, WooCommerce orders, booking records, form entries, menus, and plugin data. Before you change WordPress core, PHP, DNS, plugins, themes, checkout, or a page builder, make sure you know which backup contains both halves.
When this backup method makes sense
cPanel File Manager and phpMyAdmin is a good fit when you already have that tool available and need a practical restore path. It is especially useful before updates, redesign work, hosting migrations, malware cleanup, PHP changes, database work, and plugin troubleshooting.
Before you begin
- Confirm the WordPress URL and document root so you back up the right site.
- Find the database name in
wp-config.phpor the hosting panel. - Check free disk space; many backup failures start with a full account.
- Pause risky work until the backup finishes and you can see the file.
- For stores and booking sites, note the last order, booking, or form entry before the backup.
Backup steps
- Open cPanel File Manager and locate the site document root, usually public_html or a domain folder.
- Compress the WordPress folder or document root into a zip or tar.gz archive.
- Download the archive and confirm it contains wp-content, wp-config.php, plugins, themes, and uploads.
- Open wp-config.php or cPanel MySQL Databases to identify the correct database name.
- Open phpMyAdmin, select the database, and use Export to download an SQL file.
- Save the files archive and SQL export together with the site URL and backup date in the filename.
Automated backups and cron
This is a manual backup method. For automation, pair it with a scheduled panel backup, Softaculous/Installatron automated backups, a backup plugin, or a server-side cron/WP-CLI workflow.
For WordPress plugin backups, remember that WordPress scheduled tasks often depend on WP-Cron. WP-Cron runs when WordPress receives traffic and notices a task is due. That is fine for many small sites, but low-traffic sites can run late. For business-critical sites, pair plugin schedules with a real server cron, hosting-panel backups, or provider backups where available.
How to test restore readiness
Restore by uploading the files archive, extracting it into the document root, creating or selecting a database, importing the SQL file, and confirming wp-config.php points to the right database credentials.
Do not test your only restore for the first time during an outage. Use a staging copy, temporary subdomain, local development environment, or provider restore preview when available. After restore, check login, home page, important pages, media, forms, checkout, email delivery, permalinks, and cache behavior.
Common mistakes
- Backing up wp-content only when the site also has custom files outside wp-content.
- Exporting the wrong database from phpMyAdmin.
- Forgetting hidden files such as .htaccess.
- Not testing the zip before deleting anything on the server.
Where to store the backup
Keep at least one copy outside the web server. Good destinations include your own Google Drive, Dropbox, OneDrive, S3-compatible storage, Backblaze B2, Wasabi, SFTP, a provider backup vault, or a secure internal backup server. The exact tool matters less than the restore test, retention policy, and separation from the production account.
Fix I.T. Phill recommendation
Use cPanel File Manager and phpMyAdmin as one layer, not the whole plan. Keep a second backup path for important sites, especially WooCommerce, bookings, memberships, and agency-managed sites. Before major updates, take a fresh manual backup even if automatic backups are already scheduled.
Related Fix I.T. Phill guides
- Complete WordPress backup methods guide
- How to Back Up WordPress: Complete Methods Guide
- How to Back Up WordPress by cPanel Backup Wizard
- How to Back Up WordPress by WHM Full Account Backups
- How to Back Up WordPress by cPanel WP Toolkit
- How to Back Up WordPress by Plesk WP Toolkit
- WordPress 7.0 safe upgrade checklist
- Install essential PHP extensions for WordPress in WHM/cPanel
- Disable WordPress plugins with phpMyAdmin when wp-admin is broken
- Help4 Network hosting and website support
Sources checked
- cPanel site backup with File Manager and Backup
- cPanel phpMyAdmin import/export documentation
- cPanel MySQL backups with phpMyAdmin
2026 Backup and Restore Support Update
Manual cPanel backups are strongest when files and database exports are treated as separate evidence with matching timestamps.
What to verify before trusting this recovery path
- Confirm the backup includes both WordPress files and the active database, not only one side of the site.
- Record the backup date, storage location, restore target, and who can access the recovery file or dashboard.
- Check plugins, themes, uploads, media paths, forms, login, search, cache, SSL, and email after any restore.
- For WooCommerce, confirm recent orders, subscriptions, payment callbacks, stock, customer emails, and HPOS state before reopening checkout.
- Keep one rollback option untouched until the restored public page, admin login, and key customer workflow are verified.
When to ask for WordPress support
Open a support request when the backup is incomplete, the restore point is unclear, the database import fails, orders may be newer than the backup, or the site comes back with missing media, broken logins, white screens, cache mismatches, or email problems.
