WordPress Backup: What to Save and How to Restore Your Site
WordPress backup in plain terms: files and database, how often, where to keep copies and how to check that restoring your site actually works.
Published 10 min read
A WordPress site can break in plenty of ways: an update that clashes with the theme, a plugin that deletes data, a hack, a hasty mistake by someone on the team. In every case, the backup decides whether you lose an hour or a month. Below you’ll find what a WordPress backup needs to contain, how often to run it, where to keep the copies and how to check, before an emergency, that restoring actually works.
What a full WordPress backup includes
A WordPress site has two parts, and both need saving:
- The files. WordPress core, the theme, the plugins and, above all, the
wp-content/uploadsfolder with every image and document you’ve uploaded.wp-config.phpis here too, with the database connection details. - The database. Pages, posts, settings, users, shop orders, messages sent through forms. Everything except the images.
A backup with only the files gives you an empty site. A backup with only the database gives you a site with no images. And the two need to be taken at the same moment: if the database is from Monday and the files from Friday, Tuesday’s posts will have missing images.
For an online shop, the database is the most valuable part. Orders, customers and stock change daily, while the files stay almost the same from week to week. Some tools let you back up just the database more often, which shortens the window of orders at risk.
A few things outside the site are worth saving separately: the domain’s DNS zone, email settings and a list of paid plugins with their licences. In a full restore to a different server, you’ll be looking for them.
How often to back up and how long to keep copies
How often depends on how often the site changes:
- A brochure site edited a few times a month: an automatic daily backup is enough.
- An active blog, or a site with forms that store data: daily, plus a manual backup before any update.
- An online shop: at least daily. Orders placed between two backups are lost when you restore, so the more traffic you have, the shorter the interval should be.
How long you keep copies matters just as much. A hack can go unnoticed for weeks. If you keep only the last three days, every copy already contains the malicious code. A history of several weeks, with a few older monthly copies, covers problems that are spotted late.
The official WordPress guide to hardening WordPress recommends exactly that: regular backups that include the database, and dated copies of the whole installation, so you can go back to a point before the compromise.
Backups on the server, and backups you control
Most hosting companies back up their servers. That’s a good start, but it shouldn’t be your only copy.
The host’s backup saves you when you make a mistake on the site or a disk fails. It won’t help if:
- you lose access to the hosting account (an unpaid invoice, a dispute with an agency);
- the provider has a serious problem that affects the backups too;
- you want to move the site and the old provider won’t hand over the copies.
So apply the 3-2-1 rule here as well, described in our guide to small business backup and the 3-2-1 rule: three copies, on two types of storage, one away from the main location. For a website, that usually means the host’s backup, an automatic backup sent from the server to external storage and, now and then, a copy downloaded to a company NAS or drive.
Three ways to back up WordPress
From the hosting control panel. In Plesk, under Backup Manager, you can take a full copy of the subscription (site, databases, email) or just the site. You can schedule automatic backups and send them to an external FTP server. WordPress Toolkit also takes quick snapshots before updates.
With a WordPress backup plugin. Backup plugins archive the files and database and can send them automatically to external storage. They’re useful when you don’t have access to the server panel. Two caveats: a backup plugin runs inside the site, so if the site is hacked the backup can be affected too; and archives left in the site’s directory can be downloaded by anyone who guesses the file name.
Manually. Download the files over SFTP and export the database from phpMyAdmin (Export, SQL format). It’s slow and easy to forget, but worth knowing for when the other options don’t work.
Whichever you use, check what the backup leaves out. Some plugins skip the images folder or large files by default, to keep the archive small. Others save only the WordPress tables and ignore tables added by a shop or booking plugin. Open an archive and look at what’s inside.
The right setup for most businesses: an automatic server backup run by the host, plus an automatic copy off the server and a monthly local download.
Where to keep copies and how to protect them
A site backup contains sensitive data: the database password in wp-config.php, users’ email addresses, possibly customer orders. Treat it like any other copy of company data.
- Not in the site’s public directory. A
backup.zipleft there can be downloaded from a browser. - Encrypted, where possible. Many plugins and backup tools can encrypt the archive with a password you keep separately.
- With limited access. The external storage has its own account, with a unique password and two-factor authentication.
- At least one copy an attacker can’t delete from the site or the hosting panel. The WordPress guide also suggests read-only media.
If your copies hold customers’ personal data, they fall under the same GDPR rules as the original data: keep them only as long as needed and delete them when they’re no longer required.
How to restore a WordPress site: test it first
A backup you’ve never restored is an assumption. The typical problems show up on the day of the emergency: the archive is corrupt, the database is missing, nobody remembers the encryption password, or the restore takes a whole day.
A simple test, every few months:
- Make a test copy of the site, on a subdomain such as
test.yourcompany.roor on a test server. WordPress Toolkit in Plesk can make a clone. - Restore yesterday’s backup there, following the procedure you’d use in an emergency.
- Check: the home page, a few posts with images, logging in to the dashboard, a test order if you have a shop.
- Write down how long it took and the steps you followed. Next time, the list saves you time.
- Delete the test copy or password-protect it, so search engines don’t index it.
If the test fails, that’s good news: you found out now, not on the day the site is down and customers are calling. Fix the backup setup and repeat the test until it passes.
For a real restore on the same server, first take a backup of the current state, even if it’s broken. If the restore doesn’t go as planned, you have something to go back to, and the broken copy can show what happened.
A written plan for the day you need it
On the day the site goes down, nobody has the patience to hunt for passwords or remember the steps. A page written in advance, kept somewhere other than the site, makes the restore much faster.
What goes in the plan:
- Where the backups are: the hosting provider, the external storage, the local copy, with exact addresses.
- How to get into each one: which account, who has the password, where it’s stored (ideally in a company password manager, not a file on the desktop).
- The archive encryption password, if you encrypt them. Without it, the backup is useless.
- The restore steps, as you noted them at the last test.
- Who to call: hosting support, the agency or the technician who maintains the site, with phone numbers.
- What to check after the restore: the main pages, forms, the shop, email.
Someone other than the author should be able to follow the plan. The simple test: hand it to a colleague and ask them to find yesterday’s backup using only the plan. If they get stuck, fill in the plan where they stopped.
Update the plan when you change host, backup plugin or the people responsible. A plan with old passwords creates the very problem it was meant to solve.
Back up before every update
Most of the time, backups get used not after hacks but after updates. A new plugin that clashes with the theme, a new PHP version an old plugin doesn’t support, an updated theme that loses its customisations.
The safe routine:
- take a backup or snapshot immediately before;
- update one major component at a time, not ten at once;
- check the site after each one;
- if something breaks, restore the snapshot and hold off on that update until you find the cause.
Updates are still necessary for security, as we explain in our guide to WordPress security. The backup is what makes them safe.
Frequently asked questions
Is the backup included with my hosting enough?
For everyday mistakes, usually yes. For full protection you also need a copy off the server that you control yourself. Ask the provider how often it backs up, how many days it keeps and how a restore works.
How much space does a WordPress backup take?
It depends mainly on the uploads folder and the size of the database. WordPress core and plugins take up relatively little. If backups are kept on the same hosting account, they use up the plan’s storage, so keep an eye on how much they take.
Can I restore just one deleted page, not the whole site?
For a single page or post, check the WordPress Trash and the page’s revisions first. If it isn’t there, some backup tools allow a partial database restore, but that’s delicate work. Sometimes it’s simpler to restore the backup to a test copy and copy the content across by hand.
What if I have no backup and the site has disappeared?
First ask your hosting provider whether it has its own server copies. Then look for old copies with the agency that built the site or with former contractors. Public web archives may hold the page text, but not the database, so the rebuild will be partial.
Do I need a backup if my site is very simple?
Yes. Even a five-page site has text, images and settings that took time to put together. Without a backup, a hack or a failed update means rebuilding it from scratch. If you’re wondering how complicated hosting is in general, the page is web hosting easy? gives a short answer.
When to hand backups over to someone else
Backups usually fail silently: a full disk, a changed password, a plugin switched off after an update. It’s worth delegating this part when nobody in the company reads the backup reports, or when the site brings in orders and a day offline costs money.
TECH Consult web hosting includes daily R1Soft backup on every plan, and WordPress Toolkit in Plesk helps you take copies before updates. For backing up the rest of your company data, from computers to servers, see our IT maintenance service.