Website & Development
Website backups: how often, where, and how to test a restore
Copy for AI
A website backup is only worth something once you’ve tested the restore.
The verdict: back up often enough that you never lose more work than you can afford, keep one copy outside your own server, and restore a full backup in a test environment a few times a year.
Most companies get the first part sorted. They forget the last.
That’s exactly where it goes wrong, at the worst possible moment.
Below: what a backup contains, how often, where, per platform, and how to test a restore.
It’s part of the broader maintenance story from our B2B website guide.
What belongs in a good website backup?
A full backup holds everything needed to rebuild your site identically, not just the visible pages.
In practice it comes down to four layers:
- Files: templates, images, scripts and uploads
- Database: your content and settings
- Configuration: server and environment settings
- Separate data: form submissions and similar records
WordPress’s own documentation is blunt about the first two. There are “two parts to backing up your WordPress site: Database and Files”, and “you need both to be able to fully restore a typical WordPress site” (WordPress backup documentation).
What goes wrong with a partial backup
A database-only backup misses your images and theme.
A files-only copy misses your pages. It misses your blog articles too.
In a real emergency, think of a hacked site, a failed update or a crashed server, you need both to get back online fast. So check that your backup covers every layer and doesn’t quietly skip one.
Watch out: copying the WordPress folder doesn’t capture the database. It lives in a separate database system.
Data that falls outside the standard backup
Form submissions are stored separately on some platforms, and an ordinary site restore won’t bring them back.
If those leads are business-critical, arrange a separate export for them.
A strong contact page that brings in leads is worth little if those leads disappear during a restore.
How often should you make a website backup?
As often as needed to never lose more than you can afford.
The technical term is your recovery point objective (RPO): how many hours or days of changes you can lose in the worst case. That answer sets your frequency, not the other way around.
Match the rhythm to how often your site changes
WordPress’s documentation gives a simple baseline: “For smaller websites with fewer posts, backups should be made once a week. For high-activity websites with a lot of posts, backups should be made daily.”
Here’s how that translates to typical B2B sites:
| Site type | What changes | Sensible rhythm |
|---|---|---|
| Static company site | A page now and then | Weekly |
| Content-driven site | New articles every day | Daily |
| Lead generation site | Content plus form submissions | Daily, plus a separate lead export |
| Webshop-like flow with orders | Orders around the clock | Daily or continuous |
If you don’t sell products through your site but generate leads, the value sits mainly in your content and your submissions. Tune your rhythm to that.
For example, say your team publishes three articles a week and gets ten form requests a day. A weekly backup could cost you a week of articles and seventy leads. A daily one caps the loss at one day.
Always back up before a risky change
Rule of thumb: make a fresh backup right before every risky operation.
A plugin or platform update, a redesign or a website migration are the moments when sites break most often. WordPress’s guidance says the same: back up your database regularly, “and always before an upgrade.”
A manual backup right before it costs a few minutes. It can save you days of restoration work.
Don’t blindly trust your host’s default frequency. It’s chosen for the average site. It isn’t chosen for yours.
Where is it best to store your backups?
Not in the same place as your live site.
The most common guideline is the 3-2-1 rule, as US-CERT (now part of CISA) describes it in its data backup options paper.
Here’s the rule in one picture:
Keep 3 copies of any important file (one primary, two backups), on 2 different media types, with 1 copy offsite.
The rule has been around for years. Why? It works.
It protects you against a single disk, service or location failing.
What the three copies look like for a website
Concretely, it plays out like this:
- Copy one is your live site.
- Copy two is the automatic backup at your host or platform.
- Copy three sits outside that system, in separate cloud storage or a managed backup service.
Copy two often lives in the same environment as your site. If that environment is the problem (a hacked account, a bankrupt provider, a deleted project), you’re still exposed.
WordPress’s documentation points the same way. Keep at least 3 to 5 recent backups, and “store them in different places and on different mediums.”
Isolation is the core
A backup on the same server as your site isn’t real insurance. A problem that hits your site often hits that backup too.
So keep at least one copy technically and organizationally separated from production.
That also matters when you weigh managed hosting against self-hosting: ask who holds the offsite copy.
Backups and the GDPR
Personal data in backups must be secured. It may not sit somewhere indefinitely and uncontrolled, so set a retention period.
The GDPR sets no fixed term, as the UK regulator’s storage limitation guidance explains.
Data you delete from the live system should also leave your backups, or be put beyond use.
Our checklist for a GDPR compliant website covers the rest.
How does backing up differ per platform?
It depends on your platform how much you arrange yourself, and no approach is automatically safe.
Because we build websites in Webflow, WordPress and custom or headless, we see the differences up close.
Webflow and other hosted platforms
On a hosted platform like Webflow, the system usually keeps versions and backups automatically. You can roll back to an earlier point with a few clicks.
Webflow presents itself as a hosted, visual platform:
Webflow’s homepage, checked October 2026. A hosted platform takes hosting and core updates off your hands, but not every data type.
The convenience is great. But watch the details.
A restore often replaces the whole site to that moment. Separate data such as form submissions can sit apart and fall outside such a restore.
Our Webflow maintenance guide lists what still lands on your plate.
WordPress
With WordPress, you’re in charge.
Some hosts make automatic backups, but coverage, frequency and retention differ strongly. Many teams add a backup plugin or an external service.
WordPress.org is the open-source core you run on your own hosting:
The WordPress.org homepage, October 2026. The core is free, and backups are up to you and your host.
That freedom cuts both ways. A backup plugin is one more plugin to update, as our article on WordPress security explains.
Watch out: a host backup and a plugin backup on the same server are still one location. Add an offsite copy.
Custom and headless setups
With a custom or headless setup, your data spreads across a database, a CMS and file storage.
You set up backup and restore as part of your infrastructure, for each of those parts.
One lesson for every platform
Never assume “it will probably be fine”. Find out concretely what happens automatically, what’s missing and who’s responsible.
The right platform depends on your team, your content and your growth plans.
A tested backup strategy applies to all of them.
Why is a backup without a tested restore worthless?
Because a backup you’ve never restored is only an assumption, not certainty.
Almost everyone skips this part.
You see green checkmarks in your backup tool and assume everything’s fine. Only when you really have to restore do you find the file is corrupt, a layer is missing or the process works differently than expected.
Why restores fail
The reasons are annoyingly mundane:
- a backup that quietly ran incomplete for months
- a database export that doesn’t match the files
- a procedure nobody ever ran, with more steps in practice
Even WordPress’s own guidance says automated backups should be checked manually “once in a while to guarantee that the process is working.”
Why that discovery is so expensive
When your site is down, your revenue and your lead generation grind to a halt. The phone rings.
That’s the worst moment to test anything. If the cause is a hack, our guide on what to do when WordPress is hacked shows why a clean backup is your fastest way back.
So the rule holds: a backup’s value lies not in making it, but in the proven ability to restore it.
We’d rather tell you upfront that your restore has never been tested than have you find out during a crisis.
How do you test a restore in practice?
By periodically restoring a full backup in a separate environment and checking the site actually works.
You don’t test on your live site. You use a staging or test environment, so nothing breaks in production.
Here are the four steps at a glance:
Step 1: Pick a recent backup and restore it
Restore it fully on an isolated test or staging environment, separate from your live site.
Use a recent backup. You want to know whether today’s backup works.
Step 2: Check that everything is there
Walk through the restored site with a short checklist:
- Do the pages load and are the images correct?
- Is all the content present, including recent articles?
- Do the forms work and does the configuration hold?
Tip: compare a few recent pages with the live site. Missing recent content means your backup is older than you thought.
Step 3: Measure the restore time
Time the full process.
That’s your realistic downtime in a real emergency. For example, say the restore takes four hours: then four hours is what an outage costs you, not the ten minutes you hoped for.
Pair that number with uptime monitoring, so you know about an outage before your clients do.
Step 4: Record the steps in a playbook
Write the steps down.
In a crisis you then follow a known procedure and don’t improvise under pressure.
How often to repeat the test
Do this at least a few times a year, and always after a major change to your site or hosting.
Think of a fire drill. The drill isn’t the goal. The certainty is.
A restore you’ve calmly carried out three times gives you no stress the one time it’s for real.
Frequently asked questions
How often should I back up my website?
As often as you can afford to lose work. WordPress’s documentation suggests weekly for small sites with few posts and daily for high-activity sites. Always add a manual backup before an update.
Is my host’s automatic backup enough?
Usually not on its own. It often sits in the same environment as your site. Keep at least one copy offsite, following the 3-2-1 rule.
How do I know my backup actually works?
Only by restoring it. Restore a full backup in a staging environment a few times a year and check pages, content, forms and configuration.
Do backups fall under the GDPR?
Yes, when they contain personal data such as form submissions. Secure them, set a retention period, and make sure deleted data doesn’t live on indefinitely in old backups.
The short summary
Your backup strategy stands or falls with the restore.
Set your frequency by how much work you may lose. Back up right before risky operations, and keep one copy outside your live environment.
Then test a full restore a few times a year. You’ll know it works before you need it.
Want your site and lead flow to survive an emergency? Our team handles website maintenance services, including tested restores.
Contact us and we’ll check whether your current backup and restore setup really holds.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.