A website backup is the single thing that turns a disaster into an inconvenience. A bad plugin update, a hacked site, a hosting account that lapses, or one wrong click can wipe months of work in seconds. If you have a recent, tested backup, you restore and move on. If you do not, you may be rebuilding from scratch. This guide explains what a real backup includes, where to keep it, how often to make one, and how to prove it will actually restore when you need it. Everything here reflects standard practice as of November 2026.
What a real website backup actually includes
Most owners assume a backup is “a copy of my website,” but a modern site has two separate parts, and you need both.
The first part is your files: the theme, images, PDFs, plugins, and any custom code. The second part is your database, which holds your pages and posts, settings, user accounts, form entries, and (for booking or store sites) orders and customer records. A copy of the files alone will not bring back your content, and a database export alone has no images or layout. A complete backup captures both, taken at the same moment so they match.
One more thing matters: a backup you cannot find is not a backup. Note where each copy lives and how you would download it if your hosting account were locked.
Where to store your backups
The golden rule is simple: never keep your only backup on the same server as your website. If the server fails or the account is suspended, the site and its backup vanish together. Experienced teams follow a “3-2-1” habit: keep three copies, on two different types of storage, with at least one copy offsite.
| Storage location | Good for | Watch out for |
|---|---|---|
| On your web server | Fast restores after a small mistake | Useless if the whole account is lost or hacked |
| Cloud drive (Google Drive, Dropbox, OneDrive) | Easy offsite copy you control | Set a reminder so it does not silently stop syncing |
| Dedicated backup service or plugin storage | Automated, versioned history | Confirm it is actually saving offsite, not back to the server |
| Your own computer or an external drive | A copy no online account can touch | Only as safe as the device it sits on |
A practical setup for a local business is one automated backup to a cloud drive plus an occasional manual copy you download and keep yourself.
How often should you back up?
The right frequency depends on how often your site changes and how costly it would be to lose recent data. A simple brochure site that rarely changes does not need the same schedule as a site that takes bookings or payments every day. Match the schedule to how much work you are willing to redo.
| Type of site | How often it changes | Suggested backup frequency |
|---|---|---|
| Brochure or service site | A few edits a month | Weekly, plus before any update |
| Active blog or news site | New content several times a week | Daily |
| Booking, quote, or store site | Orders and entries every day | Daily, or real time for payments |
Whatever the schedule, always take an extra manual backup right before you update a plugin, change your theme, or let anyone make a big edit. Those are the moments sites break, and a fresh backup turns a scary change into a safe one.
Automatic versus manual backups
Automatic backups run on a schedule without you remembering. This is how your routine backups should work, because a backup you have to remember is one you will eventually forget. Managed hosting and care plans usually include automated daily or weekly backups stored offsite, which removes the task from your plate entirely.
Manual backups are the deliberate copies you take before a risky change or a milestone, and the ones you download and store yourself so you are never fully dependent on one provider. Use both: automatic for coverage, manual for peace of mind at key moments.
How to back up your site step by step
If you are doing it yourself on a typical WordPress site, the process looks like this:
- Choose a reputable backup tool or confirm your host includes backups.
- Set it to capture both files and the database in one run.
- Point the storage to an offsite location, not the same server.
- Set the schedule to match the table above.
- Run one backup now, by hand, so you have a known good copy today.
- Download that copy to your own computer and label it with the date.
- Set a calendar reminder to download a fresh copy once a month.
- Write down, in one short note, exactly where every copy lives.
If that list feels like a lot to maintain, it is a strong sign to put backups on a managed website care plan so it happens automatically and correctly.
How to test that a backup actually restores
An untested backup is a guess, not a safety net. Plenty of owners discover their “backups” were empty or corrupted only on the day they needed them. Test yours at least once or twice a year. The safest way is to restore the backup onto a staging copy of your site, not the live one, and confirm the pages, images, and recent content all come back. If restoring is beyond your comfort level, ask your host or care provider to run a test restore and show you the result. Also review your monthly maintenance checklist so backups stay part of your routine rather than an afterthought.
Frequently asked questions
Does my web host already back up my site for me?
Sometimes, but do not assume so. Many budget hosts take only occasional backups, keep them on the same server, or treat restores as a paid service. Read your plan, and always keep at least one copy you control yourself.
How long should I keep old backups?
Keep a rolling history rather than a single copy, because problems are not always noticed the same day. A common pattern is to keep daily backups for two weeks, weekly ones for a couple of months, and a monthly copy for a year.
Will backups slow down my website?
A well-configured backup has little noticeable effect, especially if it runs during low-traffic hours. If backups ever drag your site down, schedule them overnight or move to a host that handles backups at the server level.
Is a backup the same as security?
No. A backup helps you recover after something goes wrong, while security tries to stop it from happening. You need both: strong passwords and updates to prevent trouble, and reliable backups to recover if trouble arrives anyway.
What is the difference between a backup and a staging site?
A backup is a stored copy you can restore from later. A staging site is a private working copy where you test changes before they go live. They work well together: you test on staging, back up, then publish.
Backups are not glamorous, but they are the cheapest insurance your website will ever have. If you would rather know it is handled correctly, offsite, and tested, we can set it up and watch over it for you. Get started here and tell us about your site.