What You Need to Back Up
A WordPress site has two parts, and you need both to restore it fully.
| Part | Contains | Where it lives |
|---|---|---|
| Database | Posts, pages, comments, users, settings, orders | A MySQL or MariaDB database on your host |
| Files | WordPress core, themes, plugins, uploads (images, PDFs), wp-config.php | Your hosting account's file system |
WordPress core files can be downloaded again from WordPress.org, so the most important files are the wp-content folder, which holds themes, plugins and uploads, and wp-config.php, which holds your database connection details.
Choosing a Backup Method
| Method | Effort | Automatic | Restore difficulty | Best for |
|---|---|---|---|---|
| Host backups | Very low | Yes, if included | Easy | Everyone with a plan that includes them |
| Backup plugin | Low | Yes | Easy to moderate | Most site owners |
| Manual backup | High | No | Moderate | Before big changes, or as an extra copy |
| WP-CLI | Moderate | Can be scheduled | Moderate | Developers with SSH access |
The safest approach combines methods: automatic host backups for quick restores, and a plugin that stores copies in your own cloud storage. Read the best WordPress backup plugins for tool comparisons.
Method 1: Use Your Host's Backups
Many hosts back up sites automatically. For example, Hostinger's Premium plan includes weekly backups and higher plans daily backups, and WPX keeps daily backups for 28 days.
To use host backups:
- Check what your plan includes: frequency, retention period and whether files and database are both covered.
- Find the backup tool in your hosting dashboard, often under Backups or Site Tools.
- Create an on-demand backup before major changes, if your host offers it.
- Download a copy occasionally and store it elsewhere.
- Learn the restore process before you need it.
Limitation: host backups usually live with the same company. If your account is suspended or the host has a serious problem, you may not be able to reach them. Keep an independent copy too.
Method 2: Use a Backup Plugin (UpdraftPlus Example)
A backup plugin automates backups from inside WordPress and sends them to remote storage. UpdraftPlus, with more than 4 million active installations, is the most popular free option.
- Install UpdraftPlus from Plugins → Add New and activate it.
- Go to Settings → UpdraftPlus Backups → Settings.
- Set schedules: for example, files weekly and database daily, keeping several copies of each.
- Choose remote storage, such as Google Drive, Dropbox or Amazon S3, and authorize it.
- Select what to include: plugins, themes, uploads and other wp-content folders.
- Save changes, then click Backup Now to run the first backup.
- Check your remote storage to confirm the backup files arrived.
Other strong options include WPvivid, which adds free staging and migration, and BlogVault, which stores backups on its own servers and can restore a site that will not load. See the best WordPress backup plugins.
Method 3: Back Up WordPress Manually
A manual backup is useful before major changes or if you cannot install plugins.
Back Up the Files
- Connect to your site with an SFTP client or open your host's file manager.
- Navigate to your WordPress folder, usually public_html.
- Download wp-content and wp-config.php at minimum, or the entire folder for a full copy.
- Compress the files first if your file manager offers it; downloading one archive is faster than thousands of small files.
Back Up the Database
- Open phpMyAdmin from your hosting control panel.
- Select your WordPress database in the left column. If unsure which one, check DB_NAME in wp-config.php.
- Click Export, choose the Quick method and SQL format.
- Click Export to download the .sql file.
Store the files and database together, labeled with the date, in at least two places, such as your computer and cloud storage.
Method 4: Back Up With WP-CLI
If your host provides SSH access and WP-CLI, backups take seconds:
- Connect via SSH and go to your WordPress folder.
- Export the database with WP-CLI's database export command, which creates an SQL file.
- Archive the files, for example by compressing the wp-content folder and wp-config.php with a standard archive command.
- Download the files or copy them to remote storage.
Developers often schedule these commands with cron jobs and send backups to remote storage automatically.
How to Restore a Backup
Restoring From Your Host
Open the backup tool in your hosting dashboard, choose a backup date and select whether to restore files, database or both. Restoring both returns the site to that point in time.
Restoring With a Plugin
In UpdraftPlus, go to Existing Backups, choose a backup set and click Restore. Select the components to restore: plugins, themes, uploads, other files and database. If WordPress will not load, install a fresh copy of WordPress, install UpdraftPlus, connect your remote storage, rescan for backups and restore.
Restoring Manually
- Upload your backed-up files to the server, replacing the existing wp-content folder and wp-config.php.
- In phpMyAdmin, select the database, then use Import to upload your .sql file. You may need to empty the existing tables first.
- Check wp-config.php contains the correct database details.
- Visit the site and log in to confirm it works.
- Re-save permalinks under Settings → Permalinks if pages return errors.
Restore only what you need. If a plugin update broke the site, restoring just the plugins folder may be enough. Restoring the database overwrites newer posts, comments or orders.
When Backups Save You
It helps to picture the situations backups are for, because each one suggests a slightly different setup.
A plugin or theme update breaks the site. This is the most common emergency. A recent backup of the plugins or themes folder, or your host's one-click restore, gets you back in minutes. Making a manual backup right before updating makes this even simpler.
You delete or overwrite something by mistake. A page, an image library or a settings change can disappear with one click. A database backup from the day before restores the content without touching the rest of the site.
The site is hacked. Restoring a clean backup from before the infection, then updating everything and changing passwords, is often the fastest recovery. This is why keeping several weeks of history matters: infections are sometimes noticed days after they happen.
The server fails or your hosting account is lost. Only backups stored somewhere else help here, such as in your own cloud storage or with a backup service.
You move to a new host. A full backup is the starting point for most migrations. See how to migrate WordPress to a new host.
Choosing Where to Store Backups
| Storage | Pros | Cons |
|---|---|---|
| Google Drive or Dropbox | Easy, familiar, free tiers | Storage limits; shared with personal files |
| Amazon S3 or similar | Durable, scalable, pay for what you use | More technical to set up |
| Backup service's own cloud | No setup, restores even when the site is down | Tied to the subscription |
| Your computer | Free, fully in your control | Manual, and at risk if the computer fails |
| Same server | Fast to create | Lost if the server or account is lost |
For most small sites, a backup plugin sending copies to Google Drive or Dropbox, plus your host's backups, gives good protection at little or no cost.
Backups for Online Stores
Stores need extra care because orders arrive continuously. Restoring yesterday's database would erase today's orders and customer accounts. To protect a store:
- Back up the database very frequently, ideally in real time, with a service such as BlogVault's WooCommerce plan or Jetpack's real-time backups.
- Avoid restoring the whole database to fix a problem with a plugin or theme; restore only the affected files.
- Schedule updates during quiet hours and take a fresh backup immediately before.
- Export recent orders before any restore if you must roll back the database.
How Often to Back Up

| Site type | Database | Files | Keep backups for |
|---|---|---|---|
| Blog updated weekly | Daily or weekly | Weekly | At least 30 days |
| Business site, few changes | Weekly | Weekly | At least 30 days |
| Membership or active community | Daily | Daily | 30–60 days |
| Online store | Real-time or several times a day | Daily | 90 days or more |
Always make an extra backup before updating WordPress, changing themes, installing major plugins or migrating hosts.
How to Test a Restore Without Risk
A backup you have never restored is only a hope. Testing takes less than an hour:
- Create a staging site with your host's staging tool, or install WordPress on a subdomain or locally.
- Restore your latest backup onto the staging site using the same method you would use in an emergency.
- Check key pages, images, forms and, for stores, recent orders and customer accounts.
- Log in as an administrator and confirm settings and plugins look right.
- Note how long the restore took and any steps that needed extra work, such as updating the site address.
- Delete or password-protect the staging copy when you finish.
Do this twice a year, and after changing hosts or backup tools. The first test often reveals something important, such as a folder missing from the backup or an expired cloud storage connection.
Best Practices
- Follow the 3-2-1 idea: at least three copies, on two types of storage, with one off-site.
- Automate so backups never depend on remembering.
- Keep enough history to go back before a problem started, since some issues are noticed days later.
- Test restores on a staging site a few times a year.
- Protect backup files: do not leave archives in public folders where anyone could download them.
- Back up before every major change.
Common Backup Mistakes
- Backing up files but not the database, or the reverse
- Keeping backups only on the web server
- Never testing a restore
- Keeping too few backups to undo a problem discovered late
- Leaving backup archives in publicly accessible folders
- Running two scheduled backup plugins, which doubles server load
Final Word
Backing up WordPress takes a few minutes to set up and can save weeks of work. Use your host's automatic backups if your plan includes them, add a plugin such as UpdraftPlus that stores copies in your own cloud storage, and make a manual backup before major changes. Then test a restore so you know it works. For tool comparisons, see the best WordPress backup plugins, and for the rest of your routine, the WordPress maintenance checklist.
Frequently Asked Questions
What Is the Easiest Way to Back Up WordPress?
The easiest way is to use your host's automatic backups, if your plan includes them, and a backup plugin such as UpdraftPlus that sends copies to cloud storage like Google Drive or Dropbox on a schedule.
What Should a WordPress Backup Include?
A complete backup includes the database, which holds posts, pages, settings, users and orders, and the files, which include themes, plugins, uploads and the wp-config.php file.
How Often Should I Back Up WordPress?
Back up at least as often as your site changes. Daily backups suit most active sites, weekly backups suit sites that rarely change, and online stores benefit from real-time or very frequent database backups.
Where Should I Store WordPress Backups?
Keep at least one copy away from your web server, such as in cloud storage or on your computer. Backups stored only on the same server can be lost along with the site.
Can I Back Up WordPress Without a Plugin?
Yes. You can download your files with FTP or your host's file manager and export your database with phpMyAdmin, or use WP-CLI if your host provides SSH access. Hosts often provide backup tools in their dashboards too.
How Do I Restore a WordPress Backup?
Use the same tool that created the backup: your host's restore button, your backup plugin's restore option, or a manual restore that uploads files and imports the database. Test restores on a staging site when possible.
Want Backups Handled for You? WPX Includes Daily Backups Kept for 28 Days on Its WordPress Plans
Check the current plans, site limits and refund terms on the official WPX website.
See WPX Plans