How do you back up your website, and why?

The short answer: a website backup is your own copy of everything your website is made of, kept somewhere that is not the website. If you built your website with a website builder, the company already protects its platform against crashes. What it cannot protect you from is a page you delete by mistake, an account you get locked out of, or the company itself changing. One well-kept folder on your computer covers almost all of that, and it takes about an hour to set up.

Quick answer

• A backup is a copy of your website's raw material, stored outside the website: the words, the photos, your logo, and the facts like prices and opening hours.
• Your website builder protects its platform, not your mistakes. If you delete a page and save, that is on you.
• You do not need special software. A folder in a cloud-synced drive, filled once and updated after changes, does the job.
• Save each page as a PDF too, so you have a visual record of how everything was laid out.
• Update the copy after any change that took real effort, and set a reminder to check it every few months.
• The payoff: if anything goes wrong, you rebuild in an afternoon instead of starting from a blank page.

Here is what a backup really is, what can actually go wrong, and the folder habit that makes all of it survivable.

What is a website backup?

A backup is a copy of everything your website is made of, stored somewhere the website is not. The words on your pages. The photos and your logo. Your prices, your menu, your list of services. If the website disappeared tomorrow, the backup is the pile you would rebuild from.

That last sentence is the whole idea. The point of a backup is not the copy itself. The point is how fast you can come back. With a copy, rebuilding a small website is an afternoon of work. Without one, you are starting over from nothing, trying to remember sentences you wrote a year ago and hunting for photos that only ever existed on the website.

For a first-timer, there is one more thing worth naming. Your website is probably the only place some of this material lives. The paragraph you finally got right about what you do, the photo of your best work, the menu you typed in item by item. If the website is the only home those have, they are one bad day from gone.

Doesn't the website builder back everything up for you?

Partly, and the part it covers is not the part that usually bites.

When you use a hosted website builder, the company runs the computers your website lives on. Protecting that platform from crashes and broken hardware is the company's job, and you never have to think about it. That is a genuine advantage of building this way.

But the company's copies protect the platform, not your decisions. The things that actually take small websites down look like this:

• You delete a page, or type over text you meant to keep, and hit save.
• You get locked out of your account, because of a lost password or someone else getting in.
• The card on file expires quietly, and the domain or hosting lapses while you are busy running your business.
• The builder itself shuts down, gets bought, or changes its plans.

Some builders keep a history of your changes so you can undo a mistake, and some do not. It is worth finding out which kind yours is before you need it. Look in the help pages for words like "version history" or "restore". But even the best undo feature only covers the first item on that list. For everything else, the copy that saves you is the one you hold yourself.

What should you keep a copy of?

Not the website itself. The material the website is made from. That distinction is what makes this easy, because the material is just files, and you already know how to keep files.

• The words. The text of every page, pasted into one document, page by page. If you ever need them again, you will be very glad past you did this. Our guide on writing the words for your website explains why this text is the hardest part to recreate.
• The photos and your logo. The original files, at full size, not screenshots taken off the website. Screenshots are smaller and blurrier than what you uploaded. Here is what photos your website actually needs if you are still collecting them.
• The facts that change. Prices, the menu, the service list, opening hours, product descriptions. These are the details you typed in one at a time and would dread typing again.
• The description you gave the AI builder. If you described your business to get the website built, keep that description. It is the seed the whole website grew from, and it gives any rebuild a running start.
• A map of where everything lives. One note that says which company has your domain, which builder hosts your website, and which email address each account is under. Not the passwords, just the map. Passwords belong in a password manager, but the map is what lets you, or someone helping you, act fast on a bad day.

How do you actually make the backup?

No software to buy, no technical steps. One sitting, about an hour for a small website.

1. Make one folder and give it an obvious name. Something like "Website master copy". Put it inside a cloud-synced drive such as Google Drive, iCloud, Dropbox, or OneDrive, so every file automatically exists in two places: your computer and the cloud.
2. Fill it. Work through your website page by page. Paste the text into a document. Drop in the original photos and logo. Add the facts file and the account map from the list above.
3. Save each page as a PDF. Open each page in your browser, choose print, and pick "save as PDF" instead of a printer. This captures how everything was arranged, which a text file cannot. In a rebuild, the PDFs are the "what it looked like" reference sitting next to the "what it said" documents.
4. Check what your builder can export. Many builders let you download at least something, like your product list or your contact submissions. Grab whatever is offered. Our guide to website data portability walks through how to find out what your builder lets you take.
5. Update the folder when the website changes. Made a new page or rewrote an old one? Paste the new text in. The steps for changing a page after your website is built pair naturally with this habit: edit the website, then update the copy.

How often should you back up?

Match the effort, not the calendar. The honest rule: back up after any change you would hate to redo. A new page, a rewritten section, a fresh batch of photos, a season's new menu. If the change took you twenty minutes or more, it has earned a place in the folder.

For everything else, a reminder every three months is plenty for a small website that does not change much. Put it in your calendar now, because "I will remember" is how every lost website story starts.

And do one extra save before anything big: a redesign, switching builders, or handing the login to someone helping you. Big changes are when mistakes happen, and a copy made five minutes before one takes almost no effort, while skipping it can cost you the whole website.

That is the whole habit. One folder, filled once, touched after real changes. Most people who lose a website lose it slowly, through an expired card or a forgotten login, and find out on the worst possible day that the only copy of their words was the website itself. An hour this week means that day, if it ever comes, is an inconvenience. You open the folder, and you start rebuilding.