How to take a full backup of your WordPress site today

The short answer
To back up a WordPress site in full, you save two things together: the database, which holds your pages, posts, users and settings, and the site's files, which include the wp-content folder (your uploads, theme and plugins) and the wp-config.php file. Take both with your host's backup tool, a backup plugin or by hand, then download the result, open it to check both halves are there, and keep copies somewhere other than your web server.
You can do this today, in one sitting. You need four things: your WordPress admin login, your hosting account login, a place off the server to keep the copies (your computer and a cloud storage account in your name), and free space at least as large as the site.
- Know what "full" means. The database plus the files. One without the other brings back half a site.
- Leave Tools › Export out of it. It lists your content, but carries no images, theme, plugins or settings.
- Take the backup. Your host's tool is fastest, a plugin is easiest to automate, and doing it by hand installs nothing.
- Open it and check. A database file, a wp-content folder with your uploads, and wp-config.php.
- Store copies off the server. At least three, in different places, kept private.
- Restore one once, then schedule it. A backup proves itself only when it comes back.
1. Know what a full backup contains
A full WordPress backup has two halves that live in different places on your hosting: the database and the files. WordPress's own guide says "There are two parts to backing up your WordPress site: Database and Files. You need both to be able to fully restore a typical WordPress site" (WordPress developer docs). Here is what each part holds.
Part | Where it lives | What it holds |
|---|---|---|
The database | A separate database system on your host, usually MySQL or MariaDB | Every page, post, comment, user, menu and setting, and most plugin settings |
wp-content/uploads | The site's folder on the server | Every image, PDF and file you have uploaded, sorted into year and month folders |
wp-content/themes and wp-content/plugins | The site's folder | How the site looks and what it does, including paid themes and plugins you may not be able to download again |
wp-config.php | The top of the site's folder, next to wp-content | The details that connect the files to the database, and the site's secret keys |
.htaccess (on many hosts) | The top of the site's folder | Address rules, and often redirects someone added by hand |
The catch is that the database is not inside the folder. WordPress's guide explains that you "usually cannot back it up by downloading your WordPress directory, because the database lives outside of it." Copy only the folder and you keep the design without the words. Export only the database and you keep the words without the pictures.
2. Leave Tools › Export out of it
The file WordPress makes under Tools › Export is not a backup. It is an XML file that lists your posts, pages, comments, categories and authors, made for moving content into another site. It carries no images, no theme, no plugins and no site settings, so it cannot bring a broken site back.
EmDash's migration guide, written for people moving WordPress content, is plain about the images: a WordPress export "points to media on the WordPress origin; it does not contain the attachment bytes" (EmDash docs). In other words, the file holds the addresses of your images on your current server, not the images. If that server is gone, the addresses point at nothing.
The export is still a handy extra copy of your words. But even EmDash's guide, which can import that file, lists "A backup of the WordPress database and wp-content/uploads" first under what to prepare before you begin. Take the real backup first.
3. Take the backup: host, plugin or by hand
Pick one method and do it now; the backup that exists today beats the better one you plan for next week. Your host's tool is usually fastest, a backup plugin is the easiest to put on a schedule, and doing it by hand needs nothing new installed. All three must end the same way: the database and the files, downloaded to somewhere other than the server.
Method | Best when | Watch for |
|---|---|---|
Your host's backup tool | Your host lets you create and download a full backup | Backups that only stay on the host's servers, or that cover the files but not the database |
A backup plugin | You want backups to run on their own and land in cloud storage | Plugins set to back up the database only. The plugin is one more plugin to keep updated |
By hand | You would rather install nothing, or the site is too broken to run a plugin | Slowest, and easy to forget a part. Use the checklist in step 4 |
With your host's backup tool
- Sign in to your hosting account and find the site's backup page. Hosts call it Backups, Restore points or Snapshots. In a cPanel account it is the Backup page.
- Create a new backup now, rather than relying on last night's.
- Make sure it covers both the files and the database. If the page offers them separately, as cPanel does, download your home directory backup and the database backup.
- Download it. A backup that lives only on the host's servers is a convenience, not your copy.
WordPress's guide notes that most hosts back up the whole server, "but it takes time to request a copy of your site from their backups, and a speedy recovery is critical." Your own downloaded copy takes the wait out.
With a backup plugin
- In WordPress, go to Plugins › Add New Plugin and search for "backup". Choose one that backs up the database and the files, has been updated recently and has plenty of active installs. UpdraftPlus and BackWPup are two widely used examples. If you choose UpdraftPlus, install version 1.26.13 or later (2.26.13 for Premium). In October 2026 its maker, TeamUpdraft, had a security breach, and stolen connection keys for its UpdraftCentral remote tool were used to put backdoors on some sites. TeamUpdraft says the plugin's own files and downloads were not affected, according to Bleeping Computer.
- In its settings, include the database and all of wp-content. If it offers "other files" or the WordPress root, include those too, so wp-config.php is in the backup.
- Connect a storage place away from your server, such as a Google Drive or Dropbox account in your name.
- Run a backup now. When it finishes, download a copy to your computer as well.
- Set the schedule, using step 6 as the guide.
By hand
- Find the database name. In your host's file manager, open wp-config.php at the top of the site's folder and note the database name on the line that contains
DB_NAME. - Export the database. In your hosting panel, open phpMyAdmin, select that database, click Export, choose Quick and the SQL format, then click Go. You get a .sql file.
- Download the files. With the host's file manager or an SFTP app (a program that copies files to and from the server securely), download the whole site folder. If it is too large, take at least wp-content, wp-config.php and .htaccess.
- Keep them together. Put the .sql file and the folder in one folder named with today's date. WordPress's guide suggests treating the two as one "backup set", taken around the same time, with the database first and the files second.
4. Open the backup and check what's inside
Before you call it done, open what you downloaded and confirm both halves are there. A backup nobody has opened is a guess. This takes five minutes and catches the most common gap, a backup that quietly left out the database or the uploads.
- The database file. A file ending in .sql or .sql.gz, and more than a few kilobytes. If you can open it in a text editor, search for the title of a recent post.
- The uploads. A wp-content folder with an uploads folder inside, sorted into year and month folders. Open one recent image.
- Theme and plugins. themes and plugins folders inside wp-content.
- The settings file. wp-config.php, at the top level of the site's folder.
- Every piece. Some plugins split one backup into several zip files, one each for the database, plugins, themes, uploads and other files. You need all of them.
- A date in the name. So you always know which copy is newest.
If something is missing, go back to step 3 and take that part on its own. A database export from phpMyAdmin or a download of the uploads folder fills most gaps in minutes.
5. Store copies away from the server
Keep at least three copies, in more than one place, and treat them like a spare key. WordPress's guide says to "keep at least three backups on file, just in case one is corrupted or lost, and store them in different places", and suggests one on your hosting server, one in cloud storage and one on your own computer.
Where | Good for | Watch for |
|---|---|---|
Your hosting account | Fast restores when the server is fine | It goes down with the server or the account, and anyone who breaks into the server can reach it |
A cloud storage account | A copy off the server, filled automatically by a plugin | The account must be in your name, not a developer's, with room to spare |
Your computer or an external drive | A copy fully in your hands | It gets stale unless you replace it every month or so |
Two more rules keep the copies useful:
- Keep them private. wp-config.php holds your database password, and the database holds every user's email address. Do not email a backup or share its link openly.
- Keep some older copies too. A problem you notice three weeks late needs a copy from before it began. That matters most after a hack, where only a backup from before the break-in is clean; our guide to what to do when your WordPress site was hacked covers how to pick one.
If a developer set up your backups and holds the storage account, the copies are theirs in practice. Our guide to getting your site back after a web developer disappears starts with moving those accounts into your name.
6. Restore one once, then put it on a schedule
A backup has proven itself only when it has been restored somewhere and the site worked. Restore it into a separate private copy, never over your live site, then put backups on a schedule so you never have to remember. Both steps take an afternoon once, then run in the background.
The test restore. Many hosts offer a staging copy, a private copy of your site, and most backup plugins have a restore button. For a manual restore, WordPress's guide gives the order: restore the files first, then import the database, and update wp-config.php if the database details changed. Then open the home page, a page that brings in leads, a few images and a form, and write down the date and how long it took. Our website hosting checklist covers the full restore test, and how to ask your host for one.
The schedule. WordPress's guide says "Back up your WordPress database regularly, and always before an upgrade or a move to a new location", and suggests weekly backups for smaller sites with fewer posts and daily ones for busy sites. In practice:
- Automatic backups at least weekly, or daily if you edit the site most days.
- A fresh backup right before every WordPress, theme or plugin update.
- A new downloaded copy on your computer once a month.
- A manual backup now and then, which WordPress recommends "to guarantee that the process is working."
Why the backups never stop on WordPress
Backups on WordPress are not a one-time job, because the site keeps changing underneath you. WordPress itself, the theme and every plugin get updates, and each update is a moment when something can break. A fresh backup before each one is what makes an update safe to try.
Plugins are where most of that change comes from. Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 91% of them in plugins (Patchstack, State of WordPress Security 2026). Each fix reaches your site as an update, and each update wants a backup behind it. Even the backup plugin is one more plugin on that list.
The fix is a routine, not a product: backups that run on their own, leave the server, and get restored once in a while. If you would rather pay someone to run it, our guide to WordPress care plans covers what $50 to $250 a month buys, and what it doesn't.
When moving is the better fix, and who should stay
Stay on WordPress if your site is a store, has members or courses, or is built around one plugin feature such as bookings or a directory. Those sites need WordPress, and a working backup routine is the right fix. The same goes for a site that works, costs you little and now backs itself up.
If your site is mostly pages and posts and you are tired of the update-and-backup cycle, a site with fewer moving parts is the lasting fix. EmDash, the open-source CMS from Cloudflare that its makers call "the spiritual successor to WordPress" (emdashcms.com), is built on Astro. Once a whole site has moved to it, there is no WordPress core, theme or plugin left to patch, and plugins from its registry are sandboxed and permission-gated.
Moving does not make backups unnecessary. EmDash's docs say running it yourself "adds operational work: the team is responsible for the database, media storage, backups, upgrades" (EmDash docs). What changes is how many parts there are, and who looks after them.
The backup you took today is also the first step of any safe move. Our guide to moving a website without downtime walks through launch week from the owner's side: the private preview, the written rollback, the domain switched last and the old site kept ready.
Bring your WordPress site into the AI era on EmDash and Astro. We check every URL, redirect, form and search detail against your live site before anything changes, and switch only after you approve the preview, with the rollback written down. After launch we host the site and email you a monthly certificate listing the checks we ran and what changed, and if you ever cancel, you download your site and take it with you. Moving costs from $790 for up to 25 pages to $1,990 for up to 250 (pricing). A free, read-only check of your public pages shows whether your site is a good fit and the exact price before you ask.
Want to know where your site stands? Check your site for free.
Frequently asked questions
How do I back up my entire WordPress site?
Back up the database and the site's files together. Use your host's backup tool, a backup plugin set to include the database and all of wp-content, or do it by hand with phpMyAdmin and a file download. Then download the result, check that both halves are inside, and store copies away from your web server.
Is a WordPress export the same as a backup?
No. The file from Tools, then Export, lists your posts, pages and comments, but it holds only the addresses of your images, not the images themselves. It has no theme, no plugins and no settings. If your server fails, an export cannot bring the site back. A real backup copies the full database and all the files.
How do I back up my WordPress site without a plugin?
Use your host's backup tool if it offers a downloadable full backup. Otherwise, export the database in phpMyAdmin as a SQL file, then download the site's folder with your host's file manager or an SFTP app. At minimum, keep wp-content, wp-config.php and .htaccess with the database file.
Does my host's backup count as my backup?
It helps, but it should not be your only copy. A host's backup usually lives on the host's own systems, so it can be lost with the account or the server, and getting a copy can take time. Download a full backup yourself and keep it in your own cloud storage and on your computer.
How often should I back up my WordPress site?
At least weekly for a small site that changes now and then, daily if you edit it most days, and always right before an update. WordPress's own guide says to back up regularly and always before an upgrade or a move. Refresh the copy on your own computer about once a month.
Where should I store my WordPress backups?
In at least two places other than your web server, such as a cloud storage account in your name and your own computer or an external drive. Keep at least three copies in total, including some older ones. Keep them private, because a backup contains your database password and your users' email addresses.