How to Back Up Your Website (and Make Sure You Can Actually Restore It)
November 17, 2026
In short
To back up your website properly, copy both the files and the database, run backups automatically on a schedule that matches how often the site changes, and keep at least one copy somewhere other than your hosting account. Then test a restore, because a backup you have never restored is only a hope.
If you are wondering how to back up your website, the short answer is this: copy both the files and the database, automate it, store at least one copy away from your web host, and test that you can restore it. Most of the panicked messages I get from business owners start with "we thought the host had backups". Sometimes they did. Often the backups were too old, stored on the same server that failed, or simply never tested.
In this guide I will walk you through what a website backup actually contains, how often to take one, where to keep it, and how I set up backups for the sites I build and maintain. It applies to WordPress, WooCommerce, custom PHP or Laravel sites, and most other platforms.
Why backing up your website matters more than you think
A backup is your undo button for problems you cannot predict. The situations where I have seen backups save a business include:
- A plugin or theme update that breaks the site. One bad update can take down your checkout or white-screen the whole site.
- Hacking and malware. Cleaning an infected site is far easier when you have a known clean copy to compare against or roll back to. I cover this in detail in what to do when your WordPress site is hacked.
- Hosting problems. Servers fail, accounts get suspended over unpaid invoices, and small hosts occasionally shut down.
- Human error. Someone deletes a page, overwrites a product catalogue, or runs a bulk edit on the wrong data.
- Losing access to a developer or agency. If the person who built your site holds the only copy, you are exposed. I wrote about that situation in my web developer disappeared.
What a complete website backup includes
A common mistake is backing up only part of the site. A complete backup has two halves, and you need both to restore.
1. The files
These are the code and uploaded media on the server: your theme, plugins, core platform files, configuration files and the uploads folder with every image and PDF you have added. On a WordPress site, the uploads folder is usually the largest and most irreplaceable part.
2. The database
The database holds your actual content: pages, blog posts, products, orders, customers, form entries, settings and user accounts. On a dynamic site, the database changes far more often than the files. An online store might record new orders every few minutes, so a database backup from last week can mean lost orders.
3. The things people forget
Beyond files and database, keep a record of:
- Email: if your email is hosted with your website, it is usually not included in a website backup. Business email on a dedicated provider is safer, which is one reason I recommend a proper business email setup.
- DNS records: a screenshot or export of your domain's DNS settings saves hours if you ever need to move hosts quickly.
- Access details: logins for your domain registrar, hosting, and any connected services, stored in a password manager you control.
How often should you back up your website?
Match the frequency to how much data you could afford to lose. I ask clients one question: "If the site broke right now, how much work would you be willing to redo?"
- Brochure or portfolio site that rarely changes: a weekly backup is usually enough, plus a manual backup before any update or edit session.
- Business site with a regularly updated blog or news section: daily backups.
- Online store, membership site or booking system: daily full backups at a minimum, and ideally more frequent database backups, because orders and bookings arrive continuously.
Whatever the schedule, always take a fresh backup immediately before updates, redesigns, migrations or any significant change. That single habit prevents most disasters I see.
Where to store your backups: the 3-2-1 rule
The most widely used guideline is the 3-2-1 rule: keep three copies of your data, on two different types of storage, with one copy offsite. For a website, I translate that into something practical:
- Copy one: the live website itself.
- Copy two: your host's own backups, which are convenient for quick restores.
- Copy three: an independent offsite copy in cloud storage that you control, such as Amazon S3, Backblaze B2, Google Drive or Dropbox.
The offsite copy is the one that matters most. If your backups live only inside the same hosting account, a hacked account, a billing dispute or a server failure can take your website and its backups down together. I have seen exactly that happen.
How long to keep backups
Keep a rolling history rather than only the latest copy. Malware can sit unnoticed for weeks, so if you keep only yesterday's backup you may be restoring an infected site. A sensible pattern is daily backups for the last two weeks, weekly for the last two months, and a monthly copy or two beyond that, adjusted to your storage budget.
How to back up your website: the main methods
There are several ways to do it. The right one depends on your platform and how hands-on you want to be.
Option 1: Your hosting provider's backups
Many hosts include automatic backups, and control panels such as cPanel or Plesk often offer a backup tool. Check four things: how often they run, how long they are kept, whether they include the database, and whether restoring is free or charged. Treat host backups as a convenience layer, not your only safety net. If you are choosing a host, my guide to web hosting for business owners explains what to look for.
Option 2: A backup plugin (WordPress)
For WordPress sites, a reputable backup plugin can schedule full backups and send them automatically to cloud storage. Look for scheduled backups of files and database, remote storage destinations, retention settings, and a one-click or well-documented restore process. The official WordPress documentation has a useful overview of WordPress backup approaches.
Option 3: Server-level backups
For custom applications, Laravel projects or sites on a VPS, I usually set up server-level backups: automated database dumps and file archives on a schedule, pushed to separate cloud storage, plus snapshots of the whole server where the provider supports them. This needs some technical setup, but it is reliable and does not depend on the application itself being healthy.
Option 4: Manual backups
You can download your files over SFTP or the hosting file manager and export the database through a tool like phpMyAdmin. It works, and it is worth knowing how, but manual backups depend on someone remembering to do them. I use manual backups only as an extra step before major work, never as the main strategy.
Platforms like Shopify, Wix and Squarespace
Hosted platforms manage the servers, so you will not get a traditional file and database backup. The platform protects its infrastructure, but it does not necessarily protect you from your own mistakes, such as a bad bulk edit. For Shopify, regular product, customer and order exports, or a dedicated backup app, cover that gap.
Test your restore, or you do not really have a backup
This is the step almost everyone skips. A backup file can be incomplete, corrupted, or missing the database, and you will only find out when you need it. Every few months, I restore a recent backup to a staging site or a local copy and check that:
- The site loads without errors and pages display correctly.
- Images and downloads are present.
- You can log in to the admin area.
- Recent content, orders or form entries are there.
Write down the restore steps while you do it. When something goes wrong, a short checklist is far better than trying to remember the process under pressure.
Protecting the backups themselves
Backups contain everything about your site, sometimes including customer data, so treat them as sensitive:
- Store them in an account protected with a strong password and two-factor authentication.
- Never leave backup archives in a publicly accessible folder on your web server, where anyone could download them.
- Use encryption where your backup tool or storage provider offers it.
- Make sure the business owns the storage account, not only the developer.
My simple website backup checklist
- Confirm your backups include both files and database.
- Set an automatic schedule that matches how often your site changes.
- Send at least one copy to offsite cloud storage that the business owns.
- Keep a rolling history of several weeks, not just the latest copy.
- Take a manual backup before every update, redesign or migration.
- Test a restore every few months and document the steps.
- Secure the backup storage with strong passwords and two-factor authentication.
If you would rather not manage this yourself, backups, updates, monitoring and restore testing are a core part of my website maintenance service. I set up the system once, check it regularly, and you get peace of mind that your site can be recovered.
Frequently asked questions
Doesn't my web host already back up my website?
Many do, but the frequency, retention period and restore fees vary widely, and some cheaper plans include no backups at all. Even when your host does back up your site, those copies usually sit in the same company's infrastructure. Keep at least one independent copy that you control.
How much storage do website backups need?
It depends mostly on your media library. A small business site might produce backups of a few hundred megabytes, while a store with thousands of product images can be many gigabytes. Retention settings that delete old backups automatically keep storage costs under control.
Will running backups slow down my website?
Backups use server resources while they run, which can briefly slow a site on a small hosting plan. Scheduling them for your quietest hours and using incremental backups, which only copy what has changed, keeps the impact low.
How long does it take to restore a website from a backup?
For a typical small site with a good backup and a documented process, a restore can often be done within an hour or two. Large stores, damaged hosting accounts or untested backups can take much longer, which is exactly why restore testing matters.
Should I back up my website before updating plugins?
Yes. Always take a fresh backup before updating plugins, themes or the platform core. If an update breaks something, you can roll back in minutes instead of troubleshooting a broken live site.
