How to Back Up Your WordPress Database Without a Plugin

Your WordPress database holds everything that makes your site yours: every post, page, comment, user account, and setting. If it gets corrupted, deleted, or hacked, your theme files alone cannot bring your content back. That is why a database backup belongs on your calendar before every major update, migration, or cleanup. You do not need a backup plugin for this. In this guide you will learn how to back up your WordPress database without a plugin using two proven manual methods – the phpMyAdmin export and the cPanel Backup wizard – plus how to restore the backup if you ever need it.

What a Database Backup Covers (and What It Does Not)

A database backup saves all the content and configuration stored in MySQL: posts, pages, comments, users, plugin settings, menus, and widget positions. It does not save your files: the theme and plugin code, the images in your uploads folder, or wp-config.php itself. Think of it this way: the database is the text of your book, and the files are the printing press. To fully recover from a disaster you need both, which is why this guide also explains when a full backup plugin still makes sense. The official WordPress documentation on backing up your database describes the same two-part reality.

Before You Start: Find Your Database Name and Credentials

Both methods below ask you to pick the right database, so grab its name first. In cPanel, open File Manager, go to your WordPress root folder, and open wp-config.php. Look for the line define( 'DB_NAME', 'your_database_name' ); – the value in quotes is your database name. Note DB_USER and DB_PASSWORD too; some hosts require them when opening phpMyAdmin. If you are unsure which database belongs to your site, our post-installation checklist for new WordPress sites walks through the key files every site owner should know.

Method 1: Back Up Your Database with phpMyAdmin

phpMyAdmin is the database manager almost every shared host provides. The whole export takes about two minutes.

1. Log in to your hosting control panel. In cPanel, scroll to the Databases section and click phpMyAdmin. Other panels (hPanel, Plesk, DirectAdmin) have their own database icon – the steps after this are identical.
2. In the left sidebar, click the name of your WordPress database (the one from wp-config.php). You will see a list of tables like wp_posts, wp_options, and wp_users.
3. Click the Export tab at the top.
4. Choose Quick as the export method and SQL as the format. Quick is perfect for most sites.
5. Click Export (or Go). Your browser downloads a .sql file containing your entire database. Done – that file is your backup.

For large databases, use the Custom method instead: select all tables, check Add DROP TABLE under Object creation options so the backup can overwrite an existing database during restore, choose gzipped compression to shrink the download, and then export. The gzipped option can turn a 50 MB export into a 5 MB download.

Method 2: Back Up Your Database with the cPanel Backup Wizard

If phpMyAdmin feels intimidating, cPanel has a simpler one-click path.

1. In cPanel, go to Files and click Backup (on some hosts it is called Backup Wizard).
2. Under “Download a MySQL Database Backup”, click your database name.
3. Your browser downloads a compressed .sql.gz file. Save it somewhere safe.

This method is the fastest of the two and needs no decisions about export options, which makes it ideal for beginners. The trade-off is less control: you cannot choose compression or exclude tables, and non-cPanel hosts do not offer it.

How to Restore Your Database from the SQL File

A backup you cannot restore is just a souvenir. Here is the restore process in phpMyAdmin:

1. Open phpMyAdmin and select the database you want to restore into. If you are rebuilding after a disaster, create a fresh empty database first (in cPanel: Databases and click MySQL Databases), then update wp-config.php with the new DB_NAME, DB_USER, and DB_PASSWORD.
2. Click the Import tab.
3. Click Choose File, select your .sql backup (or the unzipped .sql if you saved a .gz), and click Import.

For very large backups that exceed phpMyAdmin’s upload limit, use SSH instead:

mysql -u dbusername -p dbname < backup-file.sql

Type your database password when prompted. This command has no practical size limit, which is why hosts recommend it for databases over a few hundred megabytes. For the full list of command-line options, see the official MySQL mysqldump documentation.

Where to Store Backups and How Often to Make Them

A backup on the same server as your site protects you from your own mistakes, but not from server failure. Follow this routine:

• Name files with dates, like yoursite-2026-10-11.sql, so you always know which backup is newest.
• Keep at least one copy off the server. Your computer plus a cloud drive (Google Drive, Dropbox) is enough for most sites.
• Keep 3 to 5 recent backups before deleting old ones. One backup is good; a short history is better.
• Match frequency to activity. A blog that publishes weekly can back up weekly; a WooCommerce store or busy forum should back up daily. Always back up before updating WordPress core, themes, or plugins, and before any troubleshooting – our guide on fixing a slow WordPress site starts with exactly this precaution.
• Back up before planned downtime work, like switching your site into maintenance mode. Take a fresh export first – see our guide on WordPress maintenance mode without a plugin for the safe sequence.

When a Backup Plugin Still Makes Sense

Manual backups are free and teach you how your site works, but they depend on you remembering to do them. Consider a plugin when you want scheduled automatic backups, one-click restores, off-site storage to Google Drive or Dropbox, or full-site backups that include your files alongside the database. For a set-and-forget safety net on a business site, automation wins. For learning and occasional manual backups, the two methods above are all you need.

Frequently Asked Questions

How often should I back up my WordPress database?

Match the frequency to how often your content changes: weekly for quiet blogs, daily for stores and active communities, and always before updates or major changes.

Is a database backup the same as a full site backup?

No. The database holds your content and settings; your theme, plugin, and media files live on the server separately. A complete backup needs both parts.

My .sql file is too big to import through phpMyAdmin. What now?

Ask your host to raise the upload limit, split the file, or import via SSH with the mysql command shown above, which has no practical size limit.

Can I back up just one table instead of the whole database?

Yes. In phpMyAdmin’s Custom export, uncheck Select All and tick only the tables you need – handy for exporting just wp_posts before a risky content operation.

Your database is the irreplaceable half of your website. Files can be reinstalled from fresh downloads, but your content cannot. Fifteen minutes today – one export, one safe copy – is the cheapest insurance your site will ever have. Make it a habit, and pair it with the rest of our post-installation checklist for new WordPress sites.

Last updated: October 2026.