How often you should back up your website depends on how often it changes. A brochure site that’s updated a few times a year can get by with monthly backups, while an online store or booking site that takes new orders every day needs daily backups at minimum. Whatever the frequency, keep at least one copy off your hosting server and test that you can actually restore it.
Key takeaways
- Match backup frequency to how much data you could afford to lose – a day, a week or a month.
- A full website backup includes both the files and the database.
- Keep copies in more than one place, including at least one external to your hosting account.
- Always take a backup before updating WordPress, plugins, themes or PHP.
- A backup you’ve never restored is a hope, not a plan.
Why website backups matter
Backups are the safety net under everything else you do with your website. Updates sometimes break things. Hosting accounts get suspended. Plugins conflict. Someone deletes the wrong page. Sites get hacked. In every one of those situations, the question that decides whether you lose an hour or a week is simple: do you have a clean, recent copy you can restore?
Rebuilding a website from scratch because there’s no usable backup is expensive and slow, and some things – blog posts, customer accounts, order history, form entries – may be gone for good.
What a complete website backup includes
A WordPress website is two things working together, and a useful backup captures both:
- Files – WordPress core, your theme, plugins, uploaded images and documents, and configuration files.
- Database – your pages, posts, settings, users, form entries and, on e-commerce sites, products, customers and orders.
A files-only backup won’t bring back your content, and a database-only backup won’t restore your theme or images. Make sure your backup tool or provider captures both, and that you know how long backups are kept.
How often should you back up your website?
Ask yourself: if the site broke right now and you had to roll back to the last backup, how much work would be lost? That’s your recovery point, and it should drive your schedule.
| Type of website | How often it changes | Suggested backup frequency |
|---|---|---|
| Brochure or service site | A few edits a year | Monthly, plus before every update |
| Site with a regularly updated blog | Weekly content changes | Weekly to daily |
| Booking, membership or lead-capture site | New entries every day | Daily |
| Online store (e.g. WooCommerce) | Orders and stock change constantly | Daily at minimum; more often for busy stores |
Whatever your schedule, take an extra backup immediately before any update. The WordPress documentation on upgrading recommends backing up before you update so you can restore if something goes wrong. Online stores have extra considerations covered in website maintenance for e-commerce.
Where to store backups: onsite and external copies
Backups stored on the same server as your website are convenient for quick rollbacks, but they share the same risks. If the hosting account is hacked, suspended, or the server fails, those backups can disappear with the site. That’s why good practice is to keep:
- Onsite backups on or near your hosting for fast restores after a bad update.
- External backups stored with a separate provider or cloud storage, so a problem with your host doesn’t wipe your only copies.
- Several versions going back in time. If a hack goes unnoticed for a few weeks, last night’s backup may already be infected.
Isn’t my host already backing up my website?
Many hosts do run backups, but check the fine print: how often, how long they’re kept, whether restores cost extra, and whether they’re stored off the server. Host backups are a useful extra layer, not a replacement for backups you control. We explain where hosting ends and maintenance begins in website hosting and maintenance: what’s the connection?
Test your backups by restoring them
The most common backup failure isn’t a missing backup – it’s discovering at the worst possible moment that the backup is incomplete, corrupted or can’t be restored. Every so often, restore a backup to a staging copy of your site and check that pages, images, forms and logins work. If you can’t do that, your maintenance provider should be able to tell you when a restore was last tested.
How So Cloudy’s maintenance plans handle backups
Backup frequency is one of the main differences between our plans, as published on our maintenance plans page:
| Plan | Onsite backups | External backups | Daily backups |
|---|---|---|---|
| Basic ($89/month) | Monthly | Quarterly | – |
| Optimiser ($129/month) | Monthly | Monthly | – |
| Premium ($299/month) | Monthly (as Optimiser) | Monthly (as Optimiser) | Yes |
If your site changes daily, the Premium plan’s daily backups and live staging site are the better fit; for a stable service site, Basic or Optimiser may be plenty. You can read more about what’s included on our website maintenance in Adelaide page, and our guide to choosing between monthly maintenance plans walks through the decision.
Backups are also central to recovering from an attack – see website security maintenance – and to limiting the damage from an outage, covered in website downtime: how long is too long? And remember your website isn’t the only thing worth backing up; email, files and Microsoft 365 data need a plan too, which our IT support team can help with.
Frequently asked questions
How long should I keep website backups?
Keep enough history to roll back past a problem you didn’t notice straight away. Hacks and broken changes sometimes go unnoticed for weeks, so a mix of recent daily or weekly backups plus older monthly copies is sensible. Storage is cheap compared with rebuilding a site. Check how long your host and backup tool retain copies, as some only keep the last few.
Can I back up my WordPress website myself?
Yes. Backup plugins can schedule file and database backups and send them to external cloud storage. The hard parts are remembering to check they’re actually running, storing copies away from your hosting, and knowing how to restore when you’re under pressure. If you DIY, set a calendar reminder to confirm backups are completing and do a test restore occasionally.
What’s the difference between a backup and a staging site?
A backup is a saved copy of your site at a point in time, used to restore after something goes wrong. A staging site is a separate working copy where updates and changes can be tested before they touch the live site. They work well together: staging helps prevent problems, and backups help you recover from the ones that still happen.
Do I need to back up a Shopify or Wix website?
Hosted platforms look after their own infrastructure, so you won’t lose the whole platform. But their protection doesn’t necessarily cover mistakes you make, such as deleting products or overwriting content. Exporting key data regularly or using a reputable backup app for your platform is a sensible extra layer, especially for online stores.
If you’re not sure when your website was last backed up, or whether that backup would actually restore, that’s worth finding out before you need it. Our team can check your current setup and recommend a backup schedule that suits how your business uses its site.