Backup WordPress Database Like a Pro: 5 Methods That Work

A backup WordPress database task can sound simple.

It seems smaller than a full site backup. Easier to store. Easier to export. Maybe easier to restore too.

But that is where many site owners get caught out.

A WordPress database backup is useful, but it is still a partial backup. It does not include your full site. So if a plugin update breaks your site, malware damages files, or your theme needs to be restored, a database-only backup will not be enough.

That does not make it useless. It means you need to use it for the right reasons.

So if you are here because you want to backup WordPress database, this guide will show you how to do it, when it makes sense, and where it falls short. It will also show you why a full site plugin backup that can be partially restored is usually the safer choice.

TL;DR: You need the best-in-class WordPress backup plugin to take backups of your site. That is BlogVault. Whether you want to restore a plugin, some content, a theme, or even the whole site, BlogVault has you covered. All the benefits; none of the issues.

Here’s how we will go about it:

If you are in a hurry, you can jump to the plugin method. If you want the bigger picture too, keep reading. It will help you make a better backup decision.

What does WordPress database backup contain?

The database of your WordPress site holds much of the content and many of the settings that make your site unique.

A typical WordPress database backup includes:

This is important data, and often the part of the site you care about most. But it is not the whole site.

Your theme, plugin files, uploaded media, custom code, and WordPress core files usually live outside the database. A custom theme is a good example. It is stored in your site files, not in the database.

One detail that often gets missed is that some plugins save their settings in the database, while the plugin itself still lives in the files. So even if the settings are there, the plugin may not be.

That is why a WordPress database backup is useful for preserving content and settings, but it is not enough for a full restore. If you want full protection, you need a full site backup.

A) Backup plugin [recommended]

The easiest way to backup WordPress database is to use a backup plugin. 

Install BlogVault for a full backup, and then extract the database from there. 

Here is why this route works better:

That matters because many people searching for backup WordPress database actually need a recovery solution. A full backup with selective restore is safer and more useful than a manual database backup in phpMyAdmin.

Install and activate BlogVault: As soon as you connect your site to BlogVault, it will sync your site. Within minutes, your backup is ready.

Head to backup download section: Once a backup is done, check the Backup Details in the Backup section of your site dashboard. Here, click on More on the top right and select the Download Backup option.

Select backup and initiate download: You are in the backup download section. All you have to do is select the BACKUP VERSION and the tables you want to download and hit Continue followed by Download. 

🚨 Note: There are a few ways to take a backup manually. We’ll go through each method carefully, however please note that none of these methods guarantees an error-free backup like a backup plugin does.

B) phpMyAdmin

To create a WordPress database backup from phpMyAdmin, you need to export the entire database into an SQL file. 

You can access phpMyAdmin in a few ways:

Viewing the structure of a database.

Log into phpMyAdmin: Look for credentials with your web host, or in your wp-config.php file. 

Locate the right database: Click the Structure tab. Select the database you need to export. One phpMyAdmin screen can show databases from different sites, so confirm the right database name in wp-config.php first.

Export all the database tables as an SQL file: Select all the tables and click Export.

If your web host does not provide phpMyAdmin, they may use another database management tool like Adminer to backup database. The steps are usually similar.

📝 Note: phpMyAdmin works well for many small and medium sites, but larger databases can run into timeout or size limits, especially during import.

if phpMyAdmin shows export options, do not rush past them. The default export is usually fine, but make sure you are exporting the full database, not just one table.

C) cPanel’s Backup Wizard

If you are not comfortable using phpMyAdmin, cPanel can feel easier.

A fair few hosts use cPanel, and many include a Backup Wizard feature. Downloading a copy of the WordPress database from there is simple.

Open the Backup Wizard: Head to the Files section of cPanel and click Backup Wizard.

Then move to the cPanel backup area: Click cPanel Backups and then head to the Full or Partial Backup section.

Choose the MySQL database you want to download: In the Partial Backup section, find Download a MySQL database and click the name of the database.

Give it a minute and it should download as a .sql.gz file.

Downloading a database backup this way is easy. Restoring a large database is not. Anything over 500 MB can fail during restoration because cPanel is not designed to handle large file transfers well.

So this method is handy for exports. It is less dependable if you are counting on it for a large restore later.

D) SSH

If you are comfortable with the command line, you can use SSH to export the database to an SQL file as well.

You will need WP-CLI installed for this method.

Connect to your site server using SSH: In most cases, the credentials will be the same as your WordPress FTP ones. 

Navigate to the wp-config.php file: This is most likely in your site’s root directory. Execute the following command. Replace filename with an appropriate name for your database export.

wp db export filename.sql

Replace filename.sql with an appropriate name for your database export.

Download the file to your local machine: Exit the server and download the database file using the following command:

scp username@serveraddress:rootfolder/filename.sql localfolder

This method is useful if you are comfortable with terminal access. It can also avoid browser timeout issues. Give the export file a name that includes the site name and date. When you come back to it later, that small detail makes life much easier.

E) mysqldump utility

phpMyAdmin cannot always handle large databases. For those situations, you can use MySQL commands and the mysqldump utility.

It is efficient and secure. It is also more technical, so move carefully and check your values before running anything.

Connect to the server: Replace the username and IP address with your real values, then enter the password when prompted.

ssh username @ouripaddress

Navigate to the right location: First, navigate to the correct directory using the following command. Replace the text after cd with the actual path.

cd /path/to/your/site/directory/MYSQLDB.com/tables

Exporting the database: Use the mysqldump utility. The command is as follows. Replace username with the correct username, database name, file name and the format you’d like it to export as.

mysqldump -u USER_NAME -p DB_NAME >file_name.format

It is often the best choice for large databases and more reliable than browser tools.

But it only exports the database. To fully restore WordPress, you also need the site files.

Before running mysqldump, double-check the database name. On servers with multiple databases, the wrong one may not be obvious until later.

Why backup your WordPress database

We do not recommend relying on only a database backup. A full site backup is safer. Still, backing up your database is useful in a few common situations.

Restoring a crashed site: Plugin and theme updates can break your site. A backup gives you a safe version to return to. It is smart to back up before and after major changes. 

Reversing a wrong: If you accidentally delete a page, change settings by mistake, or roll out a design that hurts conversions, a backup can help you undo the damage quickly.

Malware infections: Malware can change content and settings, not only files. A security plugin like MalCare can remove malware, but it may not restore your site content to its earlier state.

Migration: If you are moving to a new host or server, your database is part of what needs to move. But migration still needs your site files too, which is why a full backup matters.

If you want a simpler way to stay covered, use BlogVault. It supports automatic, scheduled, and real time backups. 

If you run a store, WooCommerce database backups need extra care because orders and customer data change constantly.

Issues with database backups

Database-only backups can look simpler than they really are. The problem is not taking one. The problem is expecting it to do more than it can.

They are not easier to restore than a full backup

If you only have a WordPress database backup, you cannot restore the full site. A proper restore needs both the database and the site files.

Even for content-only restores, manual tools can be unreliable. Some can download large databases, but then fail when you try to upload them again.

They can still slow down your site

Backing up your database can be just as resource-heavy as a full backup. On shared hosting, that can mean timeouts, slowdowns, or failed exports.

This is where incremental backups help. Instead of exporting everything every time, you take one full backup and then save only the changes after that. With that said, it is worth mentioning that BlogVault has the capability to handle incremental WordPress backups well.

They do not always save meaningful space

A database backup may be smaller than a full backup, but large sites can still have very large databases. Some exports can take up several GB, which is a lot of local storage for a backup that is still incomplete.

With BlogVault, backups are stored on Amazon S3 servers, so storage is much less of a burden for you.

They can fail quietly

Manual backups can fail because of a dropped connection, timeout, server limit, or a small mistake during export. The worst part is that you may not know the backup is incomplete until you need it.

If possible, test the backup restore on a staging copy first.

They take more time to manage than people expect

Large databases can take a while to export, download, organize, and store safely. That gets harder if you keep multiple copies and do not name them clearly.

A simple habit helps here. Name each backup file with the site name and date. It is wise to follow a good backup strategy to have multiple recovery points.

Parting thoughts

A WordPress database backup is useful for exports, settings, content recovery, and migration work. But it is still only part of your site.

If you want stronger protection, use a full backup that lets you restore only what you need later. That is why we recommend using a backup plugin like BlogVault. It supports automatic, scheduled, and real-time backups, along with partial restores.

For extra safety, keep an off-site copy on Google Drive or Dropbox.

FAQs