Websites break. A plugin update goes wrong, a hacker adds spam pages, or a hosting problem wipes files. A recent backup turns these events into an inconvenience instead of a disaster. This guide explains what a WordPress backup contains, how often to take one, and how to make sure it actually works when you need it.
What You Need to Back Up
A WordPress site has two parts, and a complete backup includes both.
- Files: your theme, plugins and the uploads folder with all your images and documents.
- Database: your posts, pages, settings, users and, for a store, products and orders.
For a shop, the database is the most valuable part, because it holds customer and order records that cannot be recreated.
The 3-2-1 Rule
A simple rule used by many professionals is to keep three copies of your data, on two different types of storage, with one copy stored away from your main server. In practice, that means the live site, a backup on your hosting account, and another backup in cloud storage or on your own computer. If your host has a problem, the off-site copy still exists.
Do Not Rely Only on Your Host
Many hosting companies create automatic backups, but their rules differ. Some keep them briefly, some charge for restoring, and some do not include everything. Treat your host’s backup as a bonus and keep your own copies too.
How to Set Up Automatic Backups with a Plugin
Free plugins such as UpdraftPlus can handle this for you. The exact screens change between versions, but the steps are similar:
- Install and activate the plugin from the Plugins page.
- Open its settings and choose a schedule for files and for the database.
- Choose a remote storage destination, such as Google Drive or Dropbox, and authorize the connection.
- Decide how many backups to keep. Several recent copies are safer than one.
- Run a manual backup now and check that the files appear in your storage.
How Often Should You Back Up?
Match the schedule to how often your site changes.
- Blog or brochure site: weekly for files, and the database after each batch of new posts.
- Online store: the database daily, or more often if you receive many orders, and files weekly.
- Before any major change: always take a fresh backup before updating WordPress, switching themes or installing a large plugin.
Test Your Restore
A backup you have never tested is only a hope. At least once, practice restoring on a staging copy or a spare test site, not on your live site. Confirm that pages load, images show, and you can log in. If something fails, fix the process now, while nothing is at stake.
How to Restore a Site in a Crisis
- Stay calm and avoid making extra changes that could overwrite useful evidence.
- Find out what went wrong. A bad update is different from a hacked site.
- If the site was hacked, change all passwords and remove the cause as well, or the problem may return after the restore.
- Use your backup plugin’s restore option, or ask your host to restore from a known good date.
- Check the site thoroughly, including checkout and contact forms.
Protect the Backups Themselves
- Use a strong password and two-factor authentication on the cloud account that stores them.
- Do not leave backup files in a public folder on your website.
- Delete very old copies you no longer need, especially if they contain customer data.
Frequently Asked Questions
Will backups slow my site?
Backups use server resources while they run, so schedule them for quiet hours.
How big will my backups be?
The size depends mostly on your uploads folder. Compressing images before uploading keeps backups small.
Is a plugin enough for a large store?
For a busy shop, ask your host about server-level database backups as well, because they can be more frequent.
Final Thoughts
Set up automatic off-site backups once, test a restore once, and take a manual backup before big changes. That small routine can save you weeks of work.
