How to Back Up and Restore a WordPress Site

Every WordPress site will eventually need a backup. A plugin update goes wrong, a client deletes the wrong page, a server fails, or malware slips in through an outdated add-on. When that day comes, the only question that matters is whether you can restore a clean, recent copy in minutes instead of rebuilding for days.

This guide explains what a complete WordPress backup includes, how often to make one, where to store it, and how to restore it calmly when something breaks.

What a Complete Backup Includes

A WordPress site lives in two places, and a real backup captures both.

• The database: posts, pages, Elementor layouts, settings, users, comments, menus, form entries and WooCommerce orders. Elementor stores its page designs here too.
• The files: the wp-content folder with your uploads, themes and plugins, plus the wp-config.php file that connects WordPress to the database.

Backing up only the database loses your images. Backing up only the files loses your content. Most backup tools handle both, but always check the settings before you rely on them.

The 3-2-1 Rule

A simple rule used by IT teams works perfectly for websites. Keep three copies of your data, on two different types of storage, with one copy off-site.

• Copy 1: the live website itself.
• Copy 2: your hosting provider's automatic backups.
• Copy 3: a backup sent to separate cloud storage you control, such as Google Drive, Dropbox or an object storage bucket.

The off-site copy is the one that saves you if your hosting account is suspended, hacked or closed. Never keep your only backups on the same server as the website.

How Often Should You Back Up

Match the schedule to how often the site changes.

• Brochure or portfolio sites that change monthly: a weekly full backup is usually enough.
• Active blogs: daily database backups and weekly file backups.
• WooCommerce stores and membership sites: database backups every few hours or real-time backups, because every order and signup matters.

Always make a manual backup right before big changes: core updates, theme changes, Elementor version upgrades, or redesigns.

Choosing a Backup Method

Hosting backups

Most good hosts make daily backups and offer one-click restore. They are convenient and fast, but they live with the host. Use them as your first layer, not your only one.

Backup plugins

Dedicated backup plugins can schedule full backups, send them to cloud storage, and restore from inside the dashboard. Look for scheduling, remote storage, incremental backups for large sites, and a restore feature that works even when the site is broken.

Manual backups

You can export the database with phpMyAdmin and download files over SFTP. It works anywhere, but it is easy to forget. Use it for occasional extra copies, not as your main system.

Elementor templates and kits

Exporting templates or a full website kit is useful for reusing designs, but it is not a site backup. It does not include every post, user, order or setting. Read how to save, export and import templates for what kits are good for.

How to Restore a WordPress Site

Restoring is where people panic. Follow the same calm order every time.

1. Stop making changes. Do not keep clicking updates or deleting files while the site is broken.
2. Pick the right backup. Choose the most recent one from before the problem started, not simply the newest.
3. Restore to staging first if possible. Check that the backup works before overwriting the live site.
4. Restore files and database together. Mixing a new database with old files, or the reverse, can cause new errors.
5. Clear every cache. Regenerate Elementor CSS, then purge the caching plugin, server cache and CDN.
6. Test key pages. Home page, a few posts, forms, the cart and checkout if you run a store.

Test Your Backups Before You Need Them

A backup you have never restored is only a hope. Every few months, restore a recent backup to a staging site and check that pages, images, forms and logins all work. It takes thirty minutes and turns a future emergency into a routine task. If you do not have a staging environment yet, see how to create a WordPress staging site.

What You Can Safely Exclude

Large backups are slow to create and slow to restore. Some folders can be left out without losing anything important.

• Cache folders created by caching plugins. They are rebuilt automatically.
• Old backup archives stored inside the site. Backing up backups doubles the size quickly.
• Log files and temporary folders created by plugins.

Never exclude the uploads folder, the active theme, or the plugins folder unless you have another reliable copy of them.

Backups for WooCommerce Stores

Stores need special care because data changes constantly. If you restore yesterday's backup at noon, every order placed this morning disappears. Use real-time or very frequent database backups, and when you must restore, export recent orders first so you can re-enter them. Before restoring a store, put it into maintenance mode so no new orders arrive during the process.

A Simple Backup Checklist

1. Automatic backups of files and database are scheduled.
2. At least one copy is stored off-site, outside your hosting account.
3. Backups are kept for 14 to 30 days.
4. You receive an email when a backup fails.
5. A manual backup is made before every major update.
6. A test restore has been done in the last three months.

Common Backup Mistakes

• Storing backups only on the same server as the site.
• Excluding the uploads folder to save space, then losing every image.
• Keeping only one backup, which gets overwritten by a copy that already contains the problem.
• Never checking that scheduled backups actually finished.
• Forgetting to back up before a major update.

Backups When You Manage Client Sites

If you build sites for clients, make backups part of your service. Agree in writing who is responsible for them, how long copies are kept, and how quickly you will restore after a problem. Clients rarely think about backups until something breaks, and a clear answer at that moment builds a lot of trust.

Frequently Asked Questions

How long should I keep old backups?

Keep at least 14 to 30 days of history. Some problems, such as malware or a broken plugin setting, are only noticed weeks later, and you need a clean copy from before they started.

Do backups slow down my site?

They can, briefly, on large sites. Schedule backups for quiet hours and use incremental backups so only changed files are copied each time.

Is a backup enough to recover from a hack?

A clean backup is the fastest recovery, but you must also close the hole that let the attacker in. Update everything, change passwords, and follow our checklist on how to secure a WordPress site.

Wrapping Up

A reliable backup plan is simple: back up both files and database, follow the 3-2-1 rule, match the schedule to how often the site changes, and test restores before you need them. Set it up once and every future mistake becomes something you can undo.

Related tutorials

• How to Secure a WordPress Site Against Common Attacks
• How to Create a Staging Site to Test WordPress Changes Safely
• How to Save, Export and Import Templates in Elementor