Backups & maintenance · Guide
How to Back Up a WordPress Site (And Test the Restore)

Short answer
A complete WordPress backup holds your site files and a database export made at about the same time. Back up weekly for a small site and daily for a busy one, keep 3 to 5 recent copies in different places, store at least one copy off the server, and prove each backup works by restoring it on a staging site.
Key takeaways
- A complete backup needs both the site files and a database export; downloading the folder alone misses the database.
- Back up weekly for a small site and daily for a busy site, and always before an upgrade.
- Keep at least 3 to 5 recent backups in different places, such as the server, cloud storage, and your computer.
- Back up the database first and the files second; restore the files first and the database second.
- Jetpack VaultPress Backup runs a full backup at least once a day plus real-time backups after each change.
- A backup you have never restored is a guess, so test restores on a staging site.
What does a complete WordPress backup include?
A complete backup holds two parts: your site files and an export of your database, made at about the same time.
The files are everything in your WordPress folder on the server: WordPress core, your themes, your plugins, your uploads, plus wp-config.php and .htaccess. The database lives in a separate system, usually MySQL or MariaDB, and holds your posts, pages, comments, users, and settings.
WordPress.org states the point plainly: you need both parts to fully restore a typical WordPress site, as its backup guide explains (checked November 2026). Downloading your WordPress folder does not back up the database, because the database lives outside that folder. Treat the two halves as one backup set, and make them close together so they describe the same moment.
How often should you back up?
Back up once a week for a smaller site with few posts, and daily for a site with high activity, plus a fresh backup before every upgrade.
That is the general suggestion in the WordPress backup guide, which also says to back up your database regularly and always before an upgrade (checked November 2026). A store that takes orders every day should back up daily at least, since each day of lost orders costs real money.
Frequency is only half the question. The same guide says to keep at least 3 to 5 recent backups, stored in different locations, for example one on the hosting server, one in cloud storage, and one downloaded to your own computer (checked November 2026). One backup in one place is a single point of failure, and a backup you cannot reach is no backup at all.
How do you back up with UpdraftPlus?
Install UpdraftPlus, connect one remote storage location such as Google Drive, set a schedule for files and database separately, then click Backup Now.
UpdraftPlus is the most widely installed backup plugin on WordPress.org, and its free version covers the full backup and restore flow. Go to Settings, then UpdraftPlus Backups, and open the Settings tab. Pick a file backup schedule and a database backup schedule, choose how many of each to keep, then connect your remote storage and save.
The free version sends backups to one remote location at a time. Google Drive, Dropbox, Amazon S3, FTP, and email are among the free destinations. A free Google account includes 15 GB of Google Drive storage, which is enough for most small sites.
Backing up to several locations at once needs the Premium version, which starts from $70 a year.
To run a backup, open the Backup / Restore tab and click Backup Now. Leave both the files and the database ticked, and tick the option to send the backup to remote storage. When it finishes, open your storage account and confirm the files actually arrived.
A schedule that silently fails is worse than no schedule, because it looks safe while it is not.
How do you back up with Jetpack VaultPress Backup?
Jetpack VaultPress Backup runs a full backup at least once a day, plus real-time backups after each change, and stores everything on Jetpack servers.
Real-time backups trigger after events such as a post or page being published or updated, a comment, a media change, a theme or plugin install or update, a settings change, or a user change.
The first backup starts as soon as you buy a plan and connect Jetpack, and you can also run one on demand with the Back up now button, as the Jetpack backup documentation explains (checked November 2026).
WooCommerce orders and products are backed up in real time in an immutable way, so restoring to a point before an order does not erase that order. That makes Jetpack a good fit for a store that changes many times a day. The plan starts at $9.95 a month billed yearly, includes 10 GB of storage, and does not support multisite sites.
One limit to know: Jetpack does not back up WordPress core files, cache folders, log files, or other backup plugins' folders. It also skips database tables that do not look like WordPress tables. For most sites that is fine, since core files can be downloaded again from WordPress.org.
How do you back up files by hand?
Connect with SFTP, download the whole WordPress folder to a dated folder on your computer, and check that wp-config.php and .htaccess came with it.
Use SFTP rather than plain FTP, because SFTP encrypts your password before it travels over the network. The Learn WordPress lesson on backups walks through this with FileZilla (checked November 2026). Create a folder on your computer named with the date, for example backup-2026-11-21, so you can tell backups apart later.
Select all the files on the server and copy them into that folder. The download may take a few minutes on a large site. When it finishes, open the folder and confirm the three main folders are there: wp-admin, wp-content, and wp-includes, plus the root files.
A partial download that stops halfway is easy to miss if you never look.
| Method | What you need | Best for |
|---|---|---|
| UpdraftPlus free | Plugin plus a Google Drive or Dropbox account | Most small sites |
| Jetpack VaultPress Backup | Paid plan, Jetpack connected | Stores that change often |
| Manual SFTP plus phpMyAdmin | Hosting login, SFTP client | Learning what a backup holds |
| Host backup tool | Hosting panel access | A second copy, not your only copy |
How do you export the database with phpMyAdmin?
Open phpMyAdmin from your hosting panel, pick your database, click Export, choose Quick and SQL format, and save the file with your file backup.
Find your database name in wp-config.php on the line that defines DB_NAME. Open phpMyAdmin, select that database on the left, and click Export. The WordPress backup guide describes the Custom option too: select all tables, check Save output to a file, pick SQL as the format, check Add DROP TABLE and IF NOT EXISTS, then click Go (checked November 2026).
The export downloads as a .sql file, or a compressed .gz or .bz2 file if you choose compression. Store it in the same dated folder as your file backup so the two halves stay together. Quick export is enough for most sites; use Custom when you need to leave out a table or add the drop-table options.
Where should you store the copies?
Keep at least one copy off the server, in cloud storage or on your own computer, so a server failure cannot take your backups with it.
A backup that lives only on the same server as your site dies with that server. WordPress.org suggests three places: one on the hosting server, one in cloud storage such as Google Drive or Dropbox, and one downloaded to your local computer (checked November 2026).
That spread matches the 3-2-1 rule, which calls for three copies on two kinds of storage with one copy off-site, as CISA's backup guidance recommends (checked November 2026).
Also check what your host already does. Most hosts back up the whole server, but getting your site's copy from their backups takes time you may not have in a crisis, according to the WordPress backup guide (checked November 2026). Treat host backups as a second copy, not your only one.
For more detail on storage choices, see the guide on where to store WordPress backups.
The guide on whether host backups are enough explains what your host already covers.
How do you test that a backup restores?
Restore the backup on a staging site, log in, and click through your key pages, forms, and checkout before you trust it.
A backup you have never restored is a guess, not a plan. The WordPress backup guide says it is highly recommended to check automated backups with a manual backup once in a while to make sure the process works (checked November 2026). The real test is a restore, not a file size.
Restore in the order the guide gives: files first, then the database. If you changed database credentials during a move, update wp-config.php to match. After the restore, open the home page, a post, the contact form, and the checkout.
Then log in to the admin and check that users, settings, and recent posts are all there. For a full walkthrough, see the guide to testing a WordPress backup.
If the test restore fails, fix the backup process now, while your live site still works. A failed test on staging costs an afternoon. A failed restore on your live site costs your content.
What should you do before updates and after a restore?
Back up before every core, plugin, or theme update, and keep a dated copy from before the change until you confirm the site still works.
The WordPress backup guide says to back up before every upgrade, and the Learn WordPress lesson repeats it for installing new plugins too (checked November 2026). Updates rarely break a site, but when they do, the backup from an hour ago is the difference between a quick rollback and a long rebuild.
After a restore, change your passwords if the problem was a hack, and review your backup schedule. A restore is also a good time to confirm your copies still sit in different places and that the next scheduled backup runs. For step-by-step restore instructions, see the guide to restoring a WordPress site from backup.
To set the right rhythm, read the guide on how often to back up WordPress.
Frequently asked questions
Are my host's backups enough on their own?
No. Your host backs up the whole server, and getting your site's copy from those backups takes time. WordPress.org advises you to learn how to back up your own files and restore them. Treat host backups as a second copy, and keep your own copy off the server.
Is UpdraftPlus free good enough for backups?
Yes, for the free version. UpdraftPlus free schedules backups, restores from the dashboard, and sends copies to Google Drive, Dropbox, Amazon S3, FTP, or email. It sends to one remote location at a time. Sending to several locations at once needs the Premium version.
Should I use Quick or Custom export in phpMyAdmin?
Use Quick export for most sites. It exports all tables as SQL in one click. Use Custom when you need to pick tables, add DROP TABLE and IF NOT EXISTS options, or compress a large database. Both produce a .sql file you can import to restore the database.
How much storage does Jetpack VaultPress Backup include?
It depends on the plan and the size of your site. Jetpack's VaultPress Backup plan starts with 10 GB of storage, and Jetpack emails administrators before storage runs low. Check your site size on the Backup page and buy a storage add-on if your history needs more room.
My restore finished but the site shows old content. What went wrong?
Check that the database export and the file backup were made at about the same time, and that you restored in the right order: files first, then the database. If you moved hosts, check that wp-config.php has the new database name, user, and password.
Sources
- Backups: Advanced Administration Handbook WordPress Developer Resources
- Backing Up Your WordPress Site Learn WordPress
- Back up your site with Jetpack VaultPress Backup Jetpack
- Back Up Government Data CISA
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.


