What backing up your WordPress site actually means

A backup is a complete copy of everything that makes your website work — the files, the database, the settings, the posts, the images, everything. If something breaks, gets hacked, or you accidentally delete something important, a backup lets you restore your site to the way it was before the problem happened. Without a backup, a serious problem can mean losing months or years of work with no way to get it back.

WordPress sites have two parts that both need backing up: the files (your theme, plugins, and uploaded images) and the database (where your posts, comments, and settings live). A complete backup includes both. Many people think they only need to back up their posts, but if your site gets hacked or your hosting account gets corrupted, you'll need those files too.

Key Takeaways

  • A backup copies everything on your WordPress site — files, database, posts, images, and settings — so you can restore it if something breaks or gets deleted.
  • Automatic backups from your hosting provider happen on their schedule, not yours, and you should verify they actually work before you need them.
  • Backup plugins like UpdraftPlus or BackWPup let you set your own schedule and store copies off your server, which protects you if your hosting account fails.
  • A manual backup takes 10 to 20 minutes and requires downloading files via FTP and exporting your database through phpMyAdmin, but gives you complete control.
  • Test your backup by actually restoring it to a test site before you rely on it — a backup that won't restore is the same as having no backup.

Automatic backups from your hosting provider

Most hosting companies include automatic backups as part of their service. These run on a schedule set by the host — often daily or weekly — and store copies on their servers. The advantage is that you don't have to remember to do anything. The disadvantage is that you have no control over when they run, how many copies they keep, or whether they actually work.

Before you rely on your host's backups, log into your hosting control panel (usually cPanel or Plesk) and look for a Backups section. Write down exactly how often backups run and how many old copies they keep. Then contact your host's support and ask them to walk you through restoring a backup — not actually doing it, just confirming the process works. Many people discover their backups don't work only when they need them.

Hosting backups are a safety net, but they're not a complete solution. If your hosting account gets hacked or your host goes out of business, backups stored only on their servers won't help you. That's why most people use hosting backups plus one other method.

Backup plugins that store copies off your server

A backup plugin like UpdraftPlus, BackWPup, or Duplicator runs on your WordPress site and can store backup copies somewhere other than your hosting account — usually Google Drive, Dropbox, Amazon S3, or your email. This protects you if your hosting account fails completely, because you have a copy somewhere else.

To set up a backup plugin, install it from the WordPress plugin directory, connect it to a cloud storage service (most plugins have built-in buttons for this), and set a schedule. Many plugins offer a free version that backs up weekly and a paid version that backs up daily or multiple times per day. The free versions are usually enough for a site that doesn't change constantly.

After you set up the plugin, wait for the first backup to finish, then read one copy to your computer and keep it somewhere safe. This gives you three copies: one on your hosting server (from the plugin), one in cloud storage (from the plugin), and one on your computer. If two of those three fail, you still have a backup.

Manual backups if you want complete control

A manual backup means downloading your files and exporting your database yourself. It takes longer than using a plugin, but you know exactly what you're backing up and where it's stored. This method works if you're comfortable using FTP (a way to read files from your server) and phpMyAdmin (a tool for managing databases).

First, read your WordPress files using an FTP client like FileZilla. Connect to your server using the FTP credentials from your hosting control panel, navigate to the folder where WordPress lives (usually public_html or www), and read the entire folder to your computer. This takes 5 to 10 minutes depending on how many images you have.

Next, export your database through phpMyAdmin. Log into your hosting control panel, find phpMyAdmin, select your WordPress database from the list on the left, click the Export tab, and click Go. This downloads an SQL file — a text file that contains all your posts, comments, and settings. Save this file in the same folder as your downloaded WordPress files.

Now you have a complete backup on your computer. Compress the folder into a ZIP file and store it somewhere safe — your computer, an external drive, or a cloud storage service. Label it with the date so you know when it was made.

How often you should back up

How often you back up depends on how often your site changes. If you post daily or sell products, back up daily. If you post once a month, weekly backups are enough. If your site barely changes, monthly is fine. The rule is straightforward: you can lose everything since your last backup, so back up as often as you can afford to lose.

If you use a backup plugin, set it to run automatically on a schedule that matches how often your site changes. If you do manual backups, do one before you make big changes — before you update plugins, before you install a new theme, before you make changes to code. That way, if something breaks, you can go back to the version that worked.

Testing your backup before you need it

A backup that won't restore is useless. Before you rely on any backup method, test it by actually restoring it to a test site. This sounds like extra work, but it's the only way to know your backup actually works.

If you use a backup plugin, most of them have a Restore button in the plugin settings. Click it and let it restore to your live site (or to a staging site if your host offers one). Watch the process complete and check that your site still works. If you use manual backups, ask your host if they offer a staging environment where you can test a restore without affecting your live site.

If you've never restored a backup before, do a test restore now, while your site is working fine. You'll learn the process, you'll know your backup works, and you'll feel confident if you ever need to do it for real.

What to do if your site breaks and you need to restore

If your site stops working, your first step is to contact your hosting support and tell them what happened. They can often see what changed and may be able to fix it without a restore. If they can't, ask them to restore from their automatic backup — this is usually faster than you doing it yourself.

If your host can't restore, or if you need to restore to a point before their backups started, use your backup plugin or your manual backup. Most backup plugins have a one-click restore button. For manual backups, you'll need to delete the broken files, upload your backup files via FTP, and import your database through phpMyAdmin. This is more involved, but your host's support team can walk you through it.

After you restore, your site will be back to the way it was at the time of the backup. Any changes you made after that backup will be gone. This is why testing your backup before you need it matters — you'll know what you're about to lose.

Frequently Asked Questions

How much space does a WordPress backup take up?

A backup is roughly the same size as your entire WordPress folder plus your database. A small site with a few posts and images might be 100 megabytes. A site with years of posts and thousands of images might be several gigabytes. Check how much storage your cloud backup service offers before you set up automatic daily backups.

Can I back up just my posts and comments without the files?

You can export just your posts through WordPress's built-in export tool (Tools > Export), but this won't save your images, theme, or plugins. If your site gets hacked or your hosting account fails, you'll have your content but not the structure to display it. A complete backup is always safer.

What if I restore a backup and lose recent changes?

When you restore a backup, your site goes back to the way it was at that backup's date. Any posts, comments, or changes made after that date are gone. This is why you should back up frequently and test your restore process before you need it — so you know what you might lose and can decide if it's worth the risk.

Do I need to back up if my hosting company says they handle it?

Hosting backups are helpful, but they're not enough by themselves. If your host goes out of business, gets hacked, or loses your data, their backups won't help you. Having a second backup stored somewhere else — on your computer or in cloud storage — protects you from that risk.

Can I use a backup from an old version of WordPress on a new version?

Yes, but test it first. Restore your backup to a test site and check that all your posts, images, and plugins work. Sometimes plugins break between WordPress versions, but most backups restore without problems. Your host's support team can help if something doesn't work.