How to Back Up Your WordPress Site Properly

How to Back Up Your WordPress Site Properly
Direct answer: A proper WordPress backup saves two things — your files (themes, plugins, uploads, and WordPress itself) and your database (posts, pages, comments, and settings) — and stores the copy somewhere other than your own server, automatically, on a schedule. A backup that sits on the same server as your site is barely a backup at all: if the server fails or the site is hacked, both copies go down together. Set up an automated backup that runs at least weekly, keep copies in cloud storage like Google Drive, and test a restore at least once — a backup you have never restored is a guess, not a safety net.
What does a WordPress backup actually include?
A WordPress site is two separate things, and a complete backup must cover both. Miss one and the restore will fail — or produce a site that looks right and is missing its content.
Your files. Everything stored on the server’s disk: the WordPress core files, your theme files, your plugins, and everything in the uploads folder — every image, PDF, and video you have ever added to a post. On a small site this is usually a few hundred megabytes; on a media-heavy site it can be several gigabytes. The uploads folder is almost always the biggest part, and it is the part people forget.
Your database. A single database (usually MySQL) holds all of your content and configuration: posts, pages, comments, categories, menus, widget settings, plugin settings, and user accounts. It is small — often just a few megabytes — but it is irreplaceable. You can reinstall WordPress core and re-upload a theme in minutes; you cannot recreate three years of posts from memory.
A good backup plugin captures both in one package. A manual backup needs both steps done separately: download the files by FTP or your host’s file manager, and export the database from phpMyAdmin. Either approach works — the one that runs automatically is the one that will actually be there when you need it.
Why do you need your own backups?
Most hosting companies take backups. Many managed WordPress hosts take them daily and keep them for 30 days. So why do the work yourself? Because your host’s backup protects your host, not necessarily you.
Host backups have limits. They are usually kept for a short window — 7, 14, or 30 days. If a problem goes unnoticed for longer than that (a hacked file injected quietly, a plugin update that slowly corrupts data, a post deleted by mistake and discovered a month later), the clean copy is already gone from the host’s rotation. Your own backups can keep copies for months.
Restores can be slow or limited. Some hosts charge a fee to restore a backup, limit how many restores you get, or only let you restore the whole account rather than a single site. If you move to a new host, your old host’s backups do not come with you.
Things go wrong in ways backups cannot predict. A bad plugin update can take a site down in seconds. A hacked site can be defaced or locked out of its own admin area. An accidental delete is permanent without a backup. And a theme or plugin conflict after an update is one of the most common reasons a site suddenly shows a white screen — our guide to securing your WordPress site from hackers covers how to reduce the risk, but no amount of hardening makes backups unnecessary: they are the only defence that can undo damage after it happens.
How often should you back up?
A backup is only as fresh as its last run, and the content you lose in a disaster is everything created since then. Use this as a starting point:
| Site type | How often it changes | Backup schedule |
|---|---|---|
| Personal blog, brochure site | A post every week or two | Weekly |
| Active blog or business site | New posts or edits most days | Daily |
| WooCommerce or membership site | Orders, signups, or payments daily | Daily, plus before any change |
| Any site | Before updates, migrations, or redesigns | On demand, right before the change |
The last row is the one people skip and regret. Always take a backup immediately before updating WordPress core, a theme, or a plugin — and before any major change like switching themes or editing code. Updates are the most common trigger for a broken site, and a fresh backup taken five minutes earlier turns a disaster into a ten-minute restore.
For a store, the stakes are higher still: a daily backup that runs at midnight loses a full day of orders if the site breaks at 11 p.m. If your shop takes orders around the clock, look for a host or plugin that offers real-time or hourly backups, at least for the database. The database is small, so backing it up hourly is cheap — the uploads folder is what makes backups heavy, and it rarely needs hourly attention.
What are the ways to back up WordPress?
There are four practical methods. Pick the one you will actually maintain.
| Method | How it works | Best for |
|---|---|---|
| Backup plugin (e.g. UpdraftPlus, BlogVault, Jetpack Backup) | Runs inside WordPress, schedules itself, sends copies to cloud storage automatically; free versions cover scheduled backups and one-click restores | Almost everyone — the only method that keeps working when you forget about it |
| Host backups | Daily automatic backups with one-click restores from the host panel | A second layer on top of your own backups — check how long copies are kept and whether restores cost extra |
| Manual backups | Download files by FTP and export the database from phpMyAdmin | One-off copies before a big change; too easy to forget as a routine |
| cPanel / host panel backup | Creates a full account archive — files, databases, email, settings — in one file | Before a migration; overkill for a weekly routine |
Whatever method you choose, the test is the same: could you rebuild the site from the backup alone, on a different host, without logging into the old one? If the answer is no, the backup is incomplete.
How do you set up automated backups with a plugin?
Here is a complete setup using UpdraftPlus, the most widely used free backup plugin. The steps are similar for other plugins — the principles are what matter.
Step 1: Install and activate the plugin. From your WordPress dashboard, go to Plugins > Add New, search for UpdraftPlus, install, and activate. The free version is enough for a standard backup setup.
Step 2: Choose what to back up. In Settings > UpdraftPlus Backups, make sure both “Files” and “Database” are included, with themes, plugins, and uploads all checked. Excluding uploads to save space is the most common way to end up with a restore that has all your posts and none of your images.
Step 3: Set the schedule. Set files to back up weekly and the database daily — the database is small and changes every time you publish or edit, so a daily database backup costs almost nothing. If your site changes daily, set files to daily too.
Step 4: Connect cloud storage. In the same settings page, choose a remote storage option — Google Drive is the most popular free choice — and follow the authorisation steps. The plugin will test the connection. A backup that only exists on your server is one server failure away from being useless.
Step 5: Decide how many copies to keep. Retain at least 3–4 recent backups — keeping only one means a corrupted backup leaves you with nothing.
Step 6: Run the first backup now. Click “Backup Now” and confirm a copy appears in your Google Drive — not just in the plugin’s list. That first run confirms the whole chain works.
Where should you store your backups?
The rule is simple and non-negotiable: at least one copy must live somewhere other than your web server. A backup on the same server protects you from a bad update or an accidental delete. It does not protect you from a server failure, a hacked server, or a hosting account problem — the exact disasters where a backup matters most.
Google Drive or Dropbox. Free tiers offer 15 GB (Google) or 2 GB (Dropbox), which is enough for many small sites. Both connect directly to backup plugins, and both keep version history, so an overwritten backup is not instantly lost.
Amazon S3 or a similar object store. Extremely cheap for backup-sized storage (a few cents per gigabyte per month) and very reliable. Slightly more setup than Drive, but the best choice for large sites or for keeping many months of copies.
A second location on your own computer. Downloading a copy to your own hard drive is a fine extra layer, but do not make it your only off-site copy — hard drives fail too, and a backup on a laptop you travel with can be stolen or lost. Use it as a third copy, not the second.
The professional standard is the 3-2-1 rule: three copies, on two kinds of storage, one off-site. For a WordPress site: the live site, a backup on cloud storage, and a backup on your host or computer.
How do you restore from a backup?
A backup is only useful if you can restore it under pressure, so it helps to know the process before you need it. With a plugin like UpdraftPlus, a restore takes about ten minutes:
1. Open the plugin’s backup list. In Settings > UpdraftPlus Backups, find the backup you want — pick the most recent one from before the problem started. A backup taken after a hack may already contain the hacked files.
2. Click Restore and choose the components. Restore the database and the files together unless you know exactly which one is broken.
3. Let the plugin finish, then check the site. Visit the homepage, a post page, and the admin area. Check that images load and recent posts are present. Clear any cache — a cached copy of the broken site can make a successful restore look like it failed. Our guide to speeding up a slow WordPress site explains where caching layers hide.
4. If the admin area itself is broken, restore manually. Upload a fresh copy of WordPress core, then restore the backup’s wp-content folder by FTP and import the database backup into phpMyAdmin. It is slower, but it works even when the dashboard is unreachable — which is exactly when you need it most.
Test this once, on purpose, before anything goes wrong: restore a backup to a staging copy of your site (most hosts offer one-click staging) and confirm it works. A tested backup is a safety net; an untested one is a hope.
What are the most common backup mistakes?
Backing up to the same server. The number one mistake. A backup on the same disk as the site is one failure away from being gone with it.
Backing up files but not the database — or the reverse. Files without a database give you a theme and no content; a database without files gives you content and no site. Both, every time.
Keeping only one copy. If that one backup is corrupted, incomplete, or taken after the problem started, you have nothing. Keep at least three recent copies.
Never testing a restore. Backups can fail silently — a storage connection breaks, a file is skipped. Do not discover yours is broken on the day your site is down.
Backing up too rarely. A weekly backup on a site that publishes daily means losing up to a week of work. Match the schedule to how often the site actually changes.
Forgetting the backup before an update. Updates are the most common cause of a suddenly broken site. A backup taken five minutes before an update is the cheapest insurance in WordPress — it costs nothing and takes a minute.
Frequently asked questions
Does my hosting company already back up my site?
Probably, but do not rely on it alone. Host backups are usually kept for only 7–30 days, may cost extra to restore, and do not move with you if you change hosts. Keep your own automated backups in cloud storage as well — they are your copy, under your control.
How much storage do WordPress backups need?
It depends on your uploads folder. A small site with few images might back up to 100–300 MB; a media-heavy site can be several gigabytes. The database is usually only a few megabytes. Google Drive’s free 15 GB tier covers most small sites with several backup copies retained.
What is the best free WordPress backup plugin?
UpdraftPlus is the most widely used free option: scheduled backups, cloud storage to Google Drive or Dropbox, and one-click restores. BlogVault and Jetpack Backup are strong alternatives, especially if you want real-time backups for a store. Any of them beats a manual routine you will forget.
How do I back up WordPress manually?
Download all files by FTP or your host’s file manager, then export the database from phpMyAdmin as a .sql file. That gives you a complete backup. It works fine for a one-off copy before a big change, but for regular protection, automate it with a plugin — manual backups only happen when you remember them.
How do I know my backup actually works?
Restore it to a staging copy of your site and check that the homepage, posts, images, and admin area all work. If your host offers one-click staging, this takes minutes. Test at least once after setting backups up, and again after any major change to your backup setup.


