This WordPress backup guide is for site owners, freelancers, agency teams, and developers who run WordPress sites. Use it when you build a backup plan, replace a weak one, or prepare for a restore. Skip it if your host already gives you backups that you have tested and trust. I have managed WordPress sites for 10+ years. I have set up and restored backups on client sites throughout that time. My team has worked on W3SpeedX backups for 14 months, since September 2025.
Key Takeaways
- A WordPress backup has two parts. It holds your files and your database. You need both to restore a site.
- Match frequency to change. A busy store needs hourly or real time backups. A brochure site can use weekly ones.
- Keep copies in more than one place. The 3-2-1 rule asks for three copies, two media types, and one offsite copy.
- Test your restores. A backup you have not restored is a guess, not a plan.
- Back up before every risky change. Updates, migrations, and edits are the moments sites break.
- Restore fast, then fix the cause. After a hack, restore a clean point, then update everything and change passwords.
What Is a WordPress Backup?
A WordPress backup is a saved copy of your site that lets you rebuild it after a problem. It is the foundation of any website backup guide. A full backup holds two parts, and each part does a different job.
Part |
What it holds |
Why it matters |
|
Database |
Posts, pages, comments, users, and settings |
Without it, your content is gone |
|
Files |
WordPress core, themes, plugins, and uploads |
Without them, your design and media are gone |
According to the WordPress developer documentation, you need both parts to fully restore a typical WordPress site. The database holds your posts and comments. The files hold core, themes, plugins, and uploads. A backup of only one part restores half a site.
A backup is not the same as a staging copy or a cache. A cache speeds up pages. A staging copy lets you test changes. A backup is a dated restore point that you keep for recovery. Keeping these three apart avoids a common mistake. People assume a host cache or a staging site will save them.
Why Every WordPress Site Needs Backups
WordPress runs a large share of the web. According to W3Techs, WordPress is used by 39.5 percent of all websites. That popularity makes it a steady target, which means every site needs a way back.
Sites break for many reasons. Each reason below is a case where a recent backup turns a crisis into a short task.
- A bad update: A plugin or theme update can break a page or lock you out. A backup lets you return to the state before the update.
- Plugin vulnerabilities: According to Patchstack's 2025 mid-year report, 6,700 new vulnerabilities were identified in the WordPress ecosystem in six months. New flaws appear every week, which means exposure is constant.
- A hacked site: Malware and injected spam can ruin a site. A clean backup from before the attack is the fastest route to recovery.
- Human error: Someone deletes a page, a post, or a folder. A restore point brings it back.
- Host or server failure: A disk fails or a provider has an outage. An offsite copy means you can rebuild elsewhere.
- A failed migration: Moving a site is risky. A backup taken first gives you a safe fallback.
Each of these problems is common. None of them is rare enough to ignore. A backup costs little compared with a lost site, because a lost site costs you traffic, sales, and trust.
Types of WordPress Backups
Backup types differ in what they copy and when they run. Knowing the types helps you pick the right one for each site.
Type |
What it copies |
Best for |
|
Full backup |
All files and the full database |
A first backup, or a clean restore point |
|
Incremental backup |
Only what changed since the last run |
Frequent schedules with less storage use |
|
Database-only backup |
Posts, comments, and settings |
Sites where content changes daily |
|
Files-only backup |
Core, themes, plugins, and uploads |
Design changes and media updates |
|
Manual backup |
Whatever you choose, when you press the button |
Before a risky change |
|
Scheduled backup |
The same set on a repeating timetable |
Everyday protection |
|
Real time backup |
Changes as they happen |
Stores and membership sites |
Full and Incremental Backups
A full backup copies everything each time. It is simple, but it uses more storage and time. An incremental backup copies only what changed since the last run. That keeps each run small, which means you can back up more often.
W3SpeedX uses incremental backups. Each run stores what changed instead of a full copy. Each completed run still becomes a restore point on the backup calendar.
Manual and Scheduled Backups
A manual backup is one you start yourself. It suits the minutes before a risky change. A scheduled backup runs on a timetable without your help. Scheduled backups matter most, because people forget manual ones.
Use both. Schedule the routine backups, then run a manual one before each update or edit. W3SpeedX labels each restore point as manual or scheduled, so you can tell them apart.
Real Time Backups
A real time backup records changes as they happen. It suits sites where each minute of data matters. An online store taking orders is a clear example, because a daily backup can miss a full day of orders.
Build Your WordPress Backup Strategy
A WordPress backup strategy answers four questions. This part of the website backup guide covers each one. What do you back up? How often? Where do you store it? How do you restore it? A good plan answers all four in writing.
Follow the 3-2-1 Rule
The 3-2-1 rule is the standard starting point. According to TechRadar, you keep three copies of your data: the original plus two copies. You store them on at least two types of media. You keep one copy offsite, away from the other two.
For a WordPress site, the rule looks like this:
- Three copies. The live site, plus two backups.
- Two media types. For example, your host's storage and a cloud service.
- One offsite copy. A copy stored away from your host.
The offsite copy protects you from host failure. If your host and your only backup sit on the same server, one failure takes both. This is a common weakness in backup plans.
The WordPress developer documentation gives similar advice. It suggests keeping several recent copies, in different locations, such as your host, cloud storage, and a local computer.
Choose a Backup Frequency
Frequency should follow how often your site changes. Ask one question: how much data can I afford to lose? If losing a day of changes is acceptable, back up daily. If losing an hour is too much, back up hourly.
Site type |
Suggested frequency |
Reason |
|
Online store |
Hourly or real time |
Orders arrive all day |
|
Membership or forum site |
Hourly or daily |
Users post often |
|
Active blog or news site |
Daily |
New posts and comments each day |
|
Business site, few edits |
Weekly |
Content rarely changes |
|
Brochure site |
Weekly or monthly |
Almost no changes |
According to the WordPress developer documentation, smaller sites with fewer posts can back up once a week. High-activity sites with many posts should back up daily. According to SiteCare's backup guide, busy e-commerce and membership sites should back up in real time or at least hourly. The same guide puts moderate-activity sites at every 2 to 3 days.
These sources agree on the principle. Back up more often when the site changes more often.
Set Retention and Naming
Retention is how long you keep old backups. Keep several restore points, not one. A single backup fails you when the problem started before it ran. For example, malware planted 10 days ago sits inside every backup from the last 10 days.
A practical plan keeps daily points for 7 days, weekly points for 4 weeks, and monthly points for 3 months. Adjust the numbers to your storage and risk. Label each point clearly, so you can find the right date under pressure.
WordPress Backup Best Practices
These WordPress backup best practices apply to any site. Treat them as the core of your WordPress backup strategy. Each one comes with a reason, because a rule makes more sense when you know why it exists.
- Back up files and database together. A partial backup restores a partial site. You need both parts, which means one tool should capture both.
- Automate the routine. Manual backups depend on memory. Automation runs on time, because it does not forget.
- Store at least one copy offsite. A copy on the same server shares its fate. An offsite copy survives host failure.
- Back up before every change. Run a manual backup before updates, migrations, and theme switches. That gives you a point just before the risk.
- Keep multiple restore points. One backup cannot undo a problem that started earlier. Several points give you a choice.
- Test restores on a schedule. Restore a backup every 3 months on a test site. A restore you have practised is faster under pressure.
- Exclude what you do not need. Cache folders add size and no value. Exclude patterns keep backups small and fast.
- Protect your backups. Backups hold your whole site, including user data. Store them with the same care as the live site.
- Match frequency to change. Over-backing a quiet site wastes money. Under-backing a busy site risks data.
- Document the restore steps. Write down who restores, from where, and in what order. A short checklist saves hours in a crisis.
- Monitor your backups. A silent failure is the worst failure. Check that each site shows a recent last backup.
- Pair backups with monitoring. Backups restore a site, but uptime monitoring tells you it broke. See Website Uptime Monitoring.
Where to Store WordPress Backups
Where you store a backup decides whether it survives. Three common locations each have a place in a good plan.
- Your host. Many hosts offer backups, and they are convenient. They sit on your provider's systems, though, which means a provider failure can take them too. Retention and restore options vary by host.
- Cloud storage. Cloud storage keeps copies away from your host. It is the usual choice for the offsite copy.
- A local computer. A copy on your own machine adds a second media type. It suits occasional downloads, not daily automation.
A balanced plan uses at least two of these. For most sites, that means host backups plus a cloud service. W3SpeedX is a cloud website backup service, so your backups sit away from your host.
How to Back Up a WordPress Site
You have four main ways to back up a site. Each trades convenience against control.
Method 1: Your Host's Backup Tool
Many hosts include a backup feature in their control panel. You turn it on, pick a time, and restore from the panel. It is the quickest start. The limits are plan-specific retention and storage on the host's own systems.
Method 2: A Backup Plugin
A plugin installs on each site and runs backups from inside WordPress. Plugins add scheduling and cloud storage. They run on the site's own server, so a heavy backup can slow a busy site. You also manage each plugin per site.
Method 3: A Manual Backup
A manual backup uses your host's file manager or SFTP for files, plus a database export tool such as phpMyAdmin. It gives full control and costs nothing. It takes time and skill, and it relies on you remembering to repeat it.
Method 4: A Cloud Dashboard Service
A cloud dashboard service backs up many sites from one place. You connect a site, pick a schedule, and let the service run it. This method scales best for agencies and anyone with more than a few sites. W3SpeedX works this way.
Method |
Setup effort |
Offsite by default |
Scales to many sites |
|
Host tool |
Low |
No |
Poorly |
|
Backup plugin |
Medium |
Depends on setup |
Poorly |
|
Manual backup |
High |
No |
Poorly |
|
Cloud dashboard |
Low |
Yes |
Well |
Backup and Restore: How Restoration Works
Backup and restore is a pair. A backup is only useful if you can restore from it. Restoring replaces your current site with the saved copy, so treat it as a serious action.
Before You Restore
Take these steps first. They prevent a second problem on top of the first.
- Confirm the problem. Check that a restore is the right fix. A small error may need a plugin deactivated, not a full restore.
- Pick the right restore point. Choose a date before the problem began. For a hack, choose a date before the attack.
- Back up the current state. Save the broken site as it stands. You may need it to recover content added after the restore point.
- Decide on the database. A restore with the database brings back old posts and orders. A files-only restore keeps newer content.
- Tell your team or client. A restore pauses changes. People should know before it starts.
During the Restore
A restore copies the files, and the database if you include it, back onto the site. The time depends on the size of the site. Large media libraries take longer. Wait for the restore to finish before you edit anything.
In W3SpeedX, you press Restore on a completed backup and confirm. A progress counter runs from 0 to 100 percent. An Include DB checkbox is on by default. Clear it to replace only the site files. The confirmation states that the restore replaces current content and cannot be undone.
After the Restore
Check the site once it finishes. Load the home page, a few inner pages, and the login. Test a form, a checkout, or whatever your site depends on. Then clear any caches, because old cached pages can hide the restored content.
If you restored after a hack, go further. Update WordPress core, plugins, and themes. Change every password and key. Remove unused plugins and users. A restore returns the site to a clean state, but it does not close the hole the attacker used.
Restore Only What You Need
Sometimes you do not need a full restore. You may have lost one file or one folder. A good backup tool lets you download a single file or folder from a backup. W3SpeedX lets you download single files and folders as ZIPs. You recover one item without touching the rest of the site.
Website Recovery: Scenarios and Steps
Website recovery means getting a broken site back to working order. Every website backup guide should cover it. The right steps depend on what went wrong. The table below maps common problems to a first move.
Problem |
First move |
Restore from |
|
Update broke the site |
Restore the point just before the update |
Last manual or scheduled point |
|
Site hacked |
Isolate the site, then restore a clean point |
A date before the attack |
|
Page or post deleted |
Restore the database, or recover from a ZIP |
A point before the deletion |
|
Host failure |
Rebuild on a new host |
Your offsite copy |
|
Failed migration |
Return to the pre-move copy |
The backup taken before the move |
|
Lost media file |
Download that file from a backup |
A point that still holds it |
Recovering From a Bad Update
Updates are the most common cause of breakage. If a site fails after an update, restore the point taken just before it. That is why you run a manual backup before updating. Then update again with fewer changes at a time to find the culprit. For safe routines across many sites, see Bulk Plugin and Theme Updates.
Recovering From a Hack
A hacked site needs speed and care. First, take the site offline or put it in maintenance mode if you can. Next, find when the attack began. Then restore a backup from before that date. Finally, update everything and change all credentials.
The date matters most. If you restore a backup that already holds the malware, you restore the problem. This is why you keep several restore points, which means you can step back further until the site is clean. Steps for restoring a hacked site are covered on the Site Cloning and Restore page.
Recovering From Host Failure
If your host fails, only an offsite copy saves you. Set up a new host, install WordPress, and restore your backup there. Then update your domain's DNS to point to the new host. Keeping a copy away from your host turns a disaster into an afternoon of work.
Moving a Site With a Backup
A backup is also a moving tool. You can restore or clone a site onto another WordPress site on a new domain or server. W3SpeedX cloning copies files and the database onto another connected site. Only the site's owner can clone it. Every paid backup schedule includes cloning.
Common WordPress Backup Mistakes
These mistakes cause most failed recoveries. Each one is easy to avoid once you know it.
- Storing backups only on the live server. One failure takes the site and its backup together.
- Backing up files but not the database. The site restores without its content.
- Skipping restore tests. Many people find a broken backup only when they need it.
- Keeping only one restore point. If the problem started before that point, the backup does not help.
- Backing up too rarely. A weekly backup on a busy store loses up to a week of orders.
- Ignoring failed backups. A backup that fails each night leaves you unprotected without warning.
- Skipping the pre-change backup. Updates and migrations are the riskiest moments.
- Restoring without a plan. A rushed restore can wipe newer content you wanted to keep.
- Treating backups as security. A backup does not block an attack. It gives you a way back.
How W3SpeedX Handles WordPress Backups
W3SpeedX is a WordPress management platform with a cloud backup service built in. It backs up connected WordPress sites to cloud storage, away from your host. The sections below describe what it does today.
What Each Backup Covers
- Your WordPress files and the full site database
- A timestamped restore point on the backup calendar
- A manual or scheduled label on each restore point
- Exclude patterns, so you can skip paths such as cache folders
- Downloads of a whole backup, or of single files and folders as ZIPs
Schedules and Pricing
Each site picks one of 6 schedule options, billed monthly per site. Faster schedules cost more.
Backup frequency |
Price per site |
|
Monthly |
Free |
|
Weekly |
1 USD |
|
Daily |
2 USD |
|
Every 12 hours |
3 USD |
|
Hourly |
5 USD |
|
Realtime |
5 USD, billed at the Hourly rate |
Switching one site's schedule leaves your other sites unchanged. Every paid schedule includes site cloning, and the free Monthly schedule does not. A bundle plan covers up to 100 sites for 100 USD per month, with every W3SpeedX module included. Full details are on the WordPress Backup Service page and the pricing page.
How It Fits the Strategy Above
Here is how W3SpeedX maps to the guide you just read.
|
Strategy point |
How W3SpeedX covers it |
|
Files and database together |
Every backup covers both |
|
Automate the routine |
Each site has its own schedule |
|
Offsite copy |
Backups sit in cloud storage |
|
Backup before changes |
Backup Now runs on demand |
|
Multiple restore points |
Each run is a restore point on the calendar |
|
Partial recovery |
Single files and folders download as ZIPs |
|
Monitoring |
The dashboard shows last backup, next backup, and storage used |
Pair backups with the rest of the platform. Website Uptime Monitoring alerts you when a site goes down. Link Monitoring finds broken links. Web Performance Monitoring tracks speed. Together they cover a site from backup to recovery.
Case Study: How We Built the Backup Screens
We built the backup schedule settings in September 2025. We added the Every 12 hours and Realtime options on 30 January 2026, 4 months in. We found that pricing needed fixes, in February 2026 and again in April 2026. On 4 September 2026, we added a tracker for backup and restore runs.
In practice, each backup shows as a restore point labelled manual or scheduled. The result was a schedule menu with 6 options, from Monthly to Realtime. We have revised the backup screens 102 times over 14 months. That work taught us a lesson that matches this guide. A schedule only helps if people can see when the last backup ran. So the dashboard shows each site's last backup, next backup, and storage used.
WordPress Backup Checklist
Use this checklist to audit any site. Copy it into your own notes.
- Files and database are both backed up
- Backups run on a schedule that matches how often the site changes
- At least one copy sits offsite
- You keep several restore points, not one
- You run a manual backup before every update or migration
- You tested a restore in the last 3 months
- Someone checks that backups ran
- The restore steps are written down
- Cache and junk folders are excluded
- Backups are stored with the same care as the live site
Conclusion
A WordPress backup is simple in idea and easy to get wrong in practice. This WordPress backup guide gave you the parts that matter. Back up files and database together. Match frequency to change. Keep an offsite copy. Keep several restore points. Test your restores.
Follow the WordPress backup best practices above, and website recovery becomes a short task, not a crisis. Start with one action today. Check when your site last backed up, and where that copy lives. If either answer is unclear, fix it now. To run backups and restores for many sites, see the WordPress Backup Service and connect your first site.
Frequently Asked Questions
What is a WordPress backup?
A WordPress backup is a saved copy of your site's files and database. You use it to restore the site after an update, error, or attack.
What should a WordPress backup include?
It should include your database and your files. The database holds posts, comments, and settings. The files hold core, themes, plugins, and uploads.
How often should I back up my WordPress site?
Match the schedule to how often the site changes. Stores and membership sites need hourly or real time backups. Active blogs suit daily ones, and quiet sites suit weekly ones.
What is the 3-2-1 backup rule for WordPress?
Keep three copies of your data, on two types of media, with one copy offsite. For WordPress, that means the live site plus two backups, one stored away from your host.
Where should I store WordPress backups?
Store them away from your host. Cloud storage is the usual choice for the offsite copy. A local download adds a second media type.
What is the difference between full and incremental backups?
A full backup copies everything each time. An incremental backup copies only what changed since the last run. Incremental runs are smaller, so you can run them more often.
How do I restore a WordPress site from a backup?
Choose a restore point from before the problem began. Back up the current state first, then run the restore and confirm. Test the site and clear caches afterward.
Can I restore only one file instead of the whole site?
Yes, if your backup tool allows it. W3SpeedX lets you download single files and folders from a backup as ZIPs.
Do backups protect a WordPress site from hackers?
No. Backups don't block an attack. They give you a clean restore point afterward. After a hack, update everything and change all passwords.
How many backups should I keep?
Keep several restore points, not one. A practical plan keeps daily points for 7 days, weekly points for 4 weeks, and monthly points for 3 months.
How much does a WordPress backup service cost with W3SpeedX?
Monthly backups are free. Weekly costs 1 USD per site, Daily 2 USD, Every 12 hours 3 USD, and Hourly 5 USD. A bundle covers up to 100 sites for 100 USD per month.
How do I test a WordPress backup?
Restore it onto a test site and check that pages, forms, and logins work. Repeat this every 3 months. A tested backup is one you can trust.


