WordPress Backups Explained: What to Save and How to Test a Restore

Illustration of a WordPress website being placed into a safe, with a database cylinder, a folder, circular arrows, and a shield checkmark

Imagine logging in tomorrow and your site is gone. An update broke the database, a plugin conflict wiped your pages, or someone got into your hosting account. Now the only question that matters: do you have a copy you can put back, and do you know it actually works? For most site owners, the honest answer to the second half is “I think so,” and that gap is where real damage happens. Backups are the boring insurance policy inside our web hosting and website guide – until the day they are not boring.

WordPress’s own documentation puts the stakes plainly: your database contains every post, every comment, and every link on your site, and if it gets erased or corrupted you stand to lose everything you have written. The same documentation is equally plain about the fix: with a proper backup of your database and files, you can restore things back to normal quickly.

This guide covers the whole loop: what a WordPress site actually consists of, what to save, how often, the main ways to back up, and the step almost everyone skips, which is testing a restore before you need it. If you are still setting your site up, our website launch checklist pairs well with this one.

Key takeaways

  • A WordPress site is two things: files (WordPress core, themes, plugins, uploads, configuration) and a database (posts, pages, comments, settings). Backing up only one leaves you with half a site.
  • WordPress’s official guidance: keep at least three to five recent backups, stored in different places such as your hosting server, cloud storage, and your own computer.
  • How often depends on how often you publish: roughly weekly for small, quiet sites and daily for active ones, and always right before an update.
  • Host backups help but are not a plan. Restoring from them can take time, so you need your own copies you control.
  • A backup you have never restored is a hope, not a backup. Test restores on a staging or local copy until the process is boring.

The two halves of a WordPress site

WordPress’s developer documentation lists what your site physically consists of: the WordPress core installation, your plugins, your themes, your images and uploaded files, code files like JavaScript and PHP, and any additional static files. All of these live in your site’s directory on the server, including critical configuration files like wp-config.php and .htaccess.

The second half lives somewhere else entirely. Your posts, pages, comments, menus, widget settings, and most plugin settings sit in a database, usually MySQL or MariaDB, which is a separate system from your files. WordPress’s documentation warns about a common misunderstanding here: backing up the files does not back up the database, because the database lives outside your WordPress directory. Downloading your site folder over FTP saves zero posts.

The reverse is also true. A database export without your files gives you back your text but not your uploaded images, your theme, or your plugins. You need both halves to rebuild the site you actually had, which is why every serious backup method captures both.

What exactly to save

WordPress’s documentation recommends treating files and database as one “backup set,” created around the same time so they stay consistent. Its suggested order is to back up the database first, then the files, and optionally to store the database export inside the same folder or zip as the file backup so the pair never gets separated.

On the file side, the folder that matters most is wp-content, which holds your themes, plugins, and every image you have ever uploaded. Add wp-config.php, which contains your database credentials and settings, and .htaccess, which controls URLs and security rules. WordPress core itself can be re-downloaded, but in practice a full copy of the directory is simpler to restore than a partial one.

On the database side, a backup means an export file, typically a .sql file or a compressed .gz or .bz2 version of it. That file is small compared to your files, and it is the half that changes every time you publish, so it deserves the more frequent schedule.

How often, and how many copies

WordPress’s official documentation ties frequency to activity: for smaller sites with fewer posts, back up once a week; for high-activity sites with many posts, back up daily. The honest test it offers is to ask how you would feel if the database were lost along with your recent posts. Whatever amount of work you could not bear to redo is your interval.

Two rules sit on top of that schedule. First, back up before every change, not just on a timer: WordPress’s training materials say backups should happen before any core, plugin, or theme update and before installing new plugins, because those are the moments most likely to break something. Second, keep depth. The official guidance is to hold at least three to five recent backups in different locations, for example one on the hosting server, one in cloud storage like Google Drive or Dropbox, and one downloaded to your own computer. Copies in one place are one accident away from being zero copies.

1. Back up Database first, then files, as one set 2. Store Three to five copies in different places 3. Test Restore on staging or a local copy 4. Repeat On schedule, and before updates Step 3 is the one most people skip. An untested backup is a hope, not a plan. 1. Back up Database first, then files, as one set 2. Store Three to five copies in different places 3. Test Restore on staging or a local copy 4. Repeat On schedule, and before updates
The backup loop. Copies and schedules matter, but the loop only counts once a test restore has produced a working site.

Four ways to back up a WordPress site

There is no single right method, and the WordPress documentation explicitly frames these as options to combine. What matters is that at least one of them is automatic, and at least one copy lives somewhere you control.

Your host’s backup tool

Most hosting companies provide backup software, and WordPress’s documentation suggests checking what your host offers first. Host-level backups usually run daily and cover the whole account, which makes them a good safety net. The catch, also from the official documentation: getting a copy of your site out of a host’s backups takes time, and a speedy recovery is critical when the site is down. Treat host backups as the floor, not the plan. What your host includes also depends on the type of plan you are on, which we compare in shared vs VPS vs managed WordPress hosting.

A backup plugin

Backup plugins automate the whole job: they capture files and database on a schedule and ship copies to remote storage like Google Drive or Dropbox. This is the option WordPress’s documentation points to when you want to skip the manual work, with one caveat: it recommends verifying the automation with an occasional manual backup, so you know the process is actually working rather than assuming it is.

Manual files over SFTP

For the file half, connect to your server with an SFTP client such as FileZilla or Cyberduck and download your WordPress directory, or at minimum the wp-content folder plus wp-config.php and .htaccess. WordPress’s training materials stress using SFTP rather than plain FTP, because SFTP encrypts your credentials instead of exposing them on the network. Once downloaded, compress the folder into a zip so you can keep several dated versions.

Manual database export with phpMyAdmin

For the database half, most hosting panels include phpMyAdmin. WordPress’s documentation walks through finding it in common panels, and the export itself is short: select your site’s database, use the Export tab, and save the resulting .sql file next to your file backup. It takes a few minutes and works even when every plugin on your site is broken, which is exactly when you need it.

How to test a restore

Backups exist to be restored, yet most site owners have never restored one. A test restore answers the only question that counts in a crisis: does this copy actually produce a working site? Do it on a staging site or a local copy, never on the live one.

The typical sequence, per WordPress’s documentation, is the reverse of the backup: restore the files first, then import the database. If the test environment uses different database credentials, update wp-config.php to match, which the documentation calls out as the step people forget during migrations.

With a plugin like UpdraftPlus, its official restore guide describes a short wizard: open the Existing Backups tab, click Restore on the set you want, choose which components to bring back (plugins, themes, uploads, database, and others), confirm, and watch the progress until the “Restore successful” message. Two reassuring details from the same documentation: if a restore times out partway, you can resume it, and the backup files themselves are ordinary zip and SQL files, so you can restore them manually even if the plugin cannot run.

After any test restore, spend five minutes clicking. Open the homepage and a few posts, log into wp-admin, submit the contact form, and check that images load. A restore that completes with errors you never noticed is only slightly better than no restore at all.

Backup methods compared

Method What it covers Effort Good for
Host backups Usually the whole account, files and database, run by the host on its own schedule None to set up; restoring can take time and may need a support request A baseline safety net under your own backups, not as the only copy
Backup plugin Files and database on an automatic schedule, with copies sent to remote storage One-time setup, then automatic; verify occasionally with a manual backup Everyday protection for most site owners
Manual SFTP + phpMyAdmin Whatever you download: full directory or wp-content, plus the database export A few minutes per backup, done by hand Independent copies before updates, and proof your backups restore
Sync / mirror copy A continuously updated mirror of site files on your computer (tools like WinSCP) Setup once, then mostly automatic; files only Keeping the newest files close at hand alongside scheduled database exports

The strongest setup combines rows from this table: automatic plugin backups to cloud storage for everyday coverage, host backups underneath, and a manual set taken before every update. That combination gives you the three to five copies in different places that WordPress’s documentation recommends, without any single point of failure.

Common backup mistakes

Backing up only the files, or only the database. Each half is useless alone: files without the database lose every post, and the database without files loses every image, theme, and plugin. Always capture both as one set.

Storing every copy on the server being backed up. A backup that dies with the server protects against almost nothing. At least one copy belongs off the server, in cloud storage or on your own machine.

Trusting the host completely. Host backups are real but slow to retrieve, and some hosts keep few restore points. The WordPress documentation is explicit that you should learn to back up your own site rather than depend on the host’s copies.

Skipping the backup before an update. Updates to core, themes, and plugins are the single most common cause of sudden breakage. A two-minute backup before clicking Update turns a disaster into a rollback.

Never testing a restore. Corrupt archives, missing tables, and wrong credentials all look fine until the day you need them. A quarterly test restore on staging is the difference between a backup and a wish.

WordPress backups: quick answers

Is my host’s automatic backup enough?

Usually not on its own. WordPress’s documentation notes that hosts typically back up the whole server including your site, but requesting a copy takes time when recovery speed matters. Keep your own copies in at least one place you control.

How many backups should I keep?

WordPress’s official guidance is at least three to five recent backups in different locations, such as the hosting server, cloud storage, and your computer, so one failed or lost copy never leaves you with nothing.

Do I need to back up if I rarely publish?

Yes, on a slower rhythm. The documentation suggests weekly backups for smaller, quieter sites, and a manual backup before any update regardless of how often you post. Quiet sites break too, usually at update time.

Can I restore a backup if my site is completely down and wp-admin will not load?

Yes, with the manual route. Plugin backups are typically stored as ordinary zip and SQL files, so you can upload the files over SFTP and import the database through phpMyAdmin without WordPress running at all. This is one more reason to learn the manual method before you need it.

Sources

  • WordPress Developer Resources, “Backups” – files versus database, backup and restore order, the three-to-five copies rule in different locations, weekly versus daily frequency, host backup caveats, and phpMyAdmin exports: https://developer.wordpress.org/advanced-administration/security/backup/
  • Learn WordPress, “Backing Up Your WordPress Site” – manual backups with SFTP clients, why SFTP beats FTP, and backing up before core, plugin, and theme updates: https://learn.wordpress.org/lesson-plan/backing-up-your-wordpress-site/
  • UpdraftPlus documentation, “How to restore a WordPress site with UpdraftPlus” – the restore wizard steps, resuming a timed-out restore, and the note that backups are standard zip and SQL files usable manually: https://teamupdraft.com/documentation/updraftplus/topics/restoration/faqs/how-to-restore-a-wordpress-site-with-updraftplus/

Similar Posts

5 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *