In this post
You should back up a WordPress website often enough that losing the changes since the last copy would not hurt your business. For a site that rarely changes, that may be weekly. For a busy shop or a blog with daily edits, it means daily, plus a copy before every update.
Every backup must include two parts: the database and the files. This guide explains what to copy, how to choose a schedule and how to make sure the backup actually works.
What a WordPress backup must include
WordPress.org's developer documentation says a site backup has two parts: the database and the files.
- The database holds your posts, pages, comments, settings and, on a shop, orders and customer records.
- The files include your theme, your plugins, your uploaded images and the wp-config.php file. The wp-content folder holds themes, plugins and uploads.
A copy of only one part is not a full backup. Files without the database give you a site with no content. A database without the files loses your images and design.
How often to back up a WordPress website
There is no single correct schedule. The sensible rule is to match your backups to how often your site changes. Ask one question: if the site vanished tonight, how much work since the last copy would you have to redo?
| Type of site | Sensible starting point |
|---|---|
| Brochure site that changes a few times a year | Weekly, and before any change |
| Blog or news site | Daily database copy, files weekly |
| Online shop taking orders | Daily at least, and more often if orders are frequent |
These are our suggestions, not official rules. The database changes most often and is usually the smaller part, so it is the one to copy more frequently. Theme, plugin and image files change less often.
Always back up before changes
This habit matters more than any schedule. Updates can clash with a plugin or theme, and a broken page can cost you enquiries or sales while you work out what went wrong.
Take a fresh copy before you update WordPress, a theme or a plugin, and before you edit the design. Most disasters on small sites happen right after a change. A backup taken a minute earlier lets you undo it.
Where to store your backups
A backup stored only on the same server as your website can disappear with it. Keep at least one copy somewhere else, such as a separate cloud storage account that you control. A sound habit is to keep several copies from different dates, because you may not notice a problem for days.
- Do not keep the only copy on the web server.
- Do not store backups in a public folder where anyone could download them.
- Protect the storage account with a strong, unique password.
Ways to run backups
You have three common options:
- Your host's backup tool. Many hosts offer one. Ask how often it runs, how many copies it keeps and how you restore.
- A backup plugin. Plugins can schedule copies and send them to remote storage. Check the plugin's current reviews and update history before you install it, and note that some features may be paid.
- A manual copy. You can export the database and download the files yourself. It works, but it relies on someone remembering to do it.
Automatic backups are safer than manual ones for most small businesses, because people forget.
Test that you can restore
A backup you have never restored is a hope, not a backup. At least once, restore a copy to a test site and check that pages, images and forms work. If you run a shop, place a test order. If you find the problem now, it costs you an afternoon. If you find it after a hack, it costs far more.
What to do if something goes wrong
If your site breaks or is hacked, do not start deleting files at random. First work out when the problem began. Then choose a backup from before that date, restore it, and change your passwords. Update everything afterwards, because restoring an old copy also restores old software.
A simple checklist
- Back up the database and the files together.
- Set a schedule that matches how often your site changes.
- Take an extra copy before every update.
- Keep at least one copy off the web server.
- Keep several older copies.
- Test a restore.
- Write down who is responsible, so the task does not fall between people.
Plans and features from hosts and plugins change, so check the current details with the provider before you commit.
If you would rather hand this over, our WordPress development team can set up and check backups as part of looking after your site, and you can get in touch to discuss it.
Common questions
Is my hosting company's backup enough?
It can help, but do not rely on it alone. Ask your host how long it keeps copies and how you restore one, and keep a second copy somewhere else that you control.
Can I restore a backup if my site is hacked?
Often yes, but only if the backup was taken before the problem started. Keep several older copies, not just the latest one.