How to Back Up Your Website and How Often to Do It
A website backup is a saved copy of your site that you can restore after a hack, a failed update, a deleted file or a hosting problem. Back up the files, the database if your site has one and the settings, keep at least one copy away from your host, and try a restore once so you know it works.
Why a backup matters
Most site problems are not dramatic. A plugin update breaks the layout, someone deletes the wrong folder, a form tool overwrites a page. A recent backup turns each of these from a crisis into a few minutes of work. The bigger risks, such as a hacked site or a host that goes offline, are the reason the copy must not live only on the same server as the site.
What a website backup contains
What you need to copy depends on how the site is built.
- Static sites consist of page files, images, styles and scripts. The source files and content are the whole backup, and a version history tool can help.
- Content management systems store pages and settings in a database as well as files. You need both, plus uploaded media and any custom theme or plugin files.
- Website builders keep the site on the platform. Check whether it offers an export or a version history, and save the text and images yourself.
The difference between these setups is explained further in static sites and content management systems.
How often to back up
Match the rhythm to how often the site changes. A portfolio that changes twice a year needs a copy after each change. A blog that publishes every day benefits from a daily copy. Whatever the schedule, make a manual copy right before any big change, such as updating the platform, changing the theme or moving to a new host.
Where to keep the copies
A sensible setup has more than one place.
- The backup tool of your host or platform, for fast restores.
- A second copy on a different service, such as cloud storage, so a problem at the host does not take the backup with it.
- Optionally, a copy on a computer or an external drive that you control.
Protect copies with a strong login and two-step verification, because a backup contains the same private data as the site. The security basics guide covers account protection in more detail.
Automatic or manual
Automatic backups are better, because people forget. Many hosts and platforms offer them, and plugins exist for content management systems. Do not assume they run, however. Check the settings, look at the date of the latest copy and confirm that it is stored somewhere you can reach. A manual export is a good extra before changes.
Test the restore
A backup you have never restored is only a guess. Once, try restoring it to a copy of the site or to a test location and see whether pages, images and forms work. If the restore fails or confuses you, it is better to find out on a calm day. Write down the steps in a short note, including where the files are kept and who to contact at your host.
How long to keep old copies
Keep several versions, not only the latest. A problem is sometimes noticed days later, and the newest copy may already contain it. A common approach is to keep recent daily copies, a few weekly ones and one monthly one. Delete older copies you no longer need, because stored backups take space and carry private data.
A simple routine you can follow
- List what your site consists of: files, database, uploaded media, settings, and the accounts that hold them.
- Choose the main backup method: the host's tool, a plugin, or a manual export.
- Pick a second place for copies, such as cloud storage with its own login.
- Put a recurring reminder in your calendar to check that the latest copy exists.
- Once a quarter, restore a copy to a test location and look at it.
Writing the routine down matters more than the tool you pick. A short note that says where the copies are and how to restore them is what saves the day when the person who set it up is not available.
Backups before changes
Make a fresh copy before anything that rewrites the site. That includes updating the platform, changing the theme, installing a new plugin, editing code and moving to another host. If something breaks, you return to the state from a few minutes ago instead of the state from last month. For moves between hosts or domains, see the guide to moving a website safely.
Common backup mistakes
- Keeping the only copy on the same server. If the server is lost or compromised, the copy goes with it.
- Backing up only the files. A site that uses a database needs the database too.
- Never opening the file. A corrupted or empty archive looks fine until you need it.
- Leaving copies unprotected. A backup holds the same private data as the site and needs the same care.
- Forgetting the domain and email settings. Note the DNS records and the email setup, so the site and its messages can be rebuilt together.
FAQ
Does my host already back up my site?
Many do, but the terms differ. Check how often it runs, how long copies are kept and whether you can restore them yourself. Keep your own copy as well.
What is the difference between a backup and a snapshot?
A snapshot is a quick image of a server or disk at a moment in time, usually taken by the host. A backup is a copy you can store elsewhere and restore on its own. Use both if both are available.
Can I back up a website builder site?
Often only in part. Look for an export function or a version history, and keep the original text and images in your own folder.
Do I need to back up a static site?
Yes, but it is simple. Keep the source files in a version control tool or a cloud folder so every change has a history.
How do I know the backup is complete?
Restore it to a test copy and compare. Check pages, images, forms and any login areas.
Your next step: find out when your site was last backed up and where that copy is stored. If the answer is unclear, make a manual copy today and save it away from your host.