How to Back Up a WordPress Website: 6 Methods That Actually Work (2026 Guide)

Last Tuesday at 3:47 PM, I watched my client’s WooCommerce store turn into a blank white page. The database had silently corrupted during a plugin update—no warning, no error log, just a $12,000-a-month business reduced to a digital ghost. That’s when the panic set in, and it’s the exact moment I stopped treating backups as optional. Here’s the hard truth: if you run a WordPress site without a tested backup, you’re gambling with everything you’ve built. Most people skip backups because they think “it won’t happen to me,” or they assume their host has it covered. But shared hosting backups are often weekly snapshots stored on the same server—useless if the server catches fire. A real backup strategy means you can restore in under an hour, from an off-site location, with zero data loss. That’s what this guide delivers: six methods that actually work in 2026, no fluff, no guesswork.

In my own setup, I combine a free plugin with cloud storage—costs me nothing extra, and I’ve restored three sites from scratch using it. The methods below range from drag-and-simple to command-line pro, so pick the one that fits your comfort level. But first, let’s kill the most common excuse: “My host handles it.” Most hosts do offer backups, but they’re often daily-only, stored on the same server, and you can’t download them without a support ticket. That’s not a backup strategy—that’s a safety net with holes.

Method 1: Manual Backup via cPanel (or Your Hosting Control Panel)

When I started building WordPress sites fifteen years ago, this was the only game in town. It’s still the most reliable because you’re not trusting a plugin to work—you’re doing it yourself. Here’s how I do it every time. Log into your cPanel (most shared hosts provide this), scroll to the “Files” section, and click “Backup.” You’ll see two options: “Full Backup” and “Partial Backup.” For a full site backup, choose “Full Backup,” select “Home Directory” as the destination, and click “Generate.” This creates a compressed archive of your entire WordPress folder—themes, plugins, uploads, everything.

Next, you need the database separately. In cPanel, find “phpMyAdmin” under “Databases.” Click your WordPress database from the left sidebar—it’s usually named something like youruser_wpdb. Then click “Export” at the top, leave the method as “Quick,” and hit “Go.” This downloads a .sql file. Now you have two files: the file archive and the database dump. Store both somewhere off-site—I use a local folder and a Google Drive folder named “WP Backups.” The whole process takes about ten minutes for a 500MB site. The downside? It’s manual, so you’ll forget to do it. I set a recurring calendar reminder every Sunday evening. But when a client’s site crashed and their plugin backup failed, this manual method saved the day because I had a copy from three hours earlier.

Pro tip: Some hosts (like SiteGround) have a “Backup Manager” in their custom cPanel that lets you download a full site backup in one click. Check your host’s documentation—it might save you a step.

Method 2: Using a Dedicated Backup Plugin (UpdraftPlus, BackWPup, or Jetpack VaultPress)

This is the method I recommend to 90% of people I work with, because it automates the boring part and makes restore a one-click affair. I’ve used UpdraftPlus for years on my personal blog (a modest 2GB site with 50 plugins), and it’s never let me down. Here’s the setup: install UpdraftPlus from the WordPress plugin repository, go to Settings > UpdraftPlus Backups, and click the “Settings” tab. Under “Files Backup Schedule,” choose “Weekly” for the file backup and “Daily” for the database backup—this covers most scenarios. Under “Database Backup Schedule,” set it to “Daily.” Then scroll to “Choose your remote storage” and connect Google Drive, Dropbox, or Amazon S3. I use Google Drive because it’s free for 15GB and I already have it.

Click “Save Changes,” then immediately run a manual backup by clicking “Backup Now.” Check both “Include your database in the backup” and “Include your files in the backup,” then hit “Backup Now.” The plugin compresses everything and uploads it to your cloud storage automatically. Restoring is even easier: go to the “Existing Backups” tab, click the “Restore” button next to your latest backup, and follow the prompts. In my test restoration last month, it took six minutes to bring a 1.2GB site back to life.

What about BackWPup? It’s a solid alternative if you need more granular control—like backing up only the database or excluding certain folders. Jetpack VaultPress is the premium option (starts at $4.95/month) and offers real-time backups for WooCommerce stores, but you’re paying for convenience. The catch with plugins: they occasionally fail silently. That’s why I always test a restore every three months. If you can’t restore, your backup is worthless.

Method 3: Automated Backups via Your Web Host (SiteGround, Kinsta, WP Engine)

Managed WordPress hosts like Kinsta and WP Engine include automated backups as part of their service—daily snapshots stored on their infrastructure. This is the closest thing to set-it-and-forget-it. On Kinsta, your backups are stored for 14 days (or 30 on higher plans), and you can restore from the MyKinsta dashboard with a single click. I’ve used this for a client’s high-traffic news site; when a caching plugin broke the layout, I restored the previous day’s snapshot in under 90 seconds. No plugin, no FTP, no headache.

The pros are obvious: no plugin overhead (fewer attack vectors), no storage management, and fast restores. The cons? You’re locked into the host’s schedule—most offer daily backups, not hourly. If your site gets hacked at 11 AM, the backup you restore is from midnight the night before—you lose 11 hours of data. Also, if you leave that host, you can’t take your backups with you easily. WP Engine lets you download backups manually, but Kinsta requires a support ticket for off-site copies. For most blogs and small businesses, daily backups are fine. For ecommerce, you’ll want a plugin that does real-time database backups alongside the host’s daily snapshot.

Trade-off: Host backups are convenient but not portable. I use them as my secondary safety net, not my primary. The plugin method (Method 2) is my primary because I own the backup files.

Method 4: Command-Line Backup with WP-CLI (For Developers & Advanced Users)

If you live in the terminal, this is the fastest way to back up a WordPress site. WP-CLI is a command-line tool that lets you manage WordPress without the dashboard. I use it for client sites where I want a scripted, repeatable process. First, ensure WP-CLI is installed (most managed hosts and many VPS setups include it). Then SSH into your server and navigate to your WordPress root directory (cd /var/www/html or similar).

To export the database, run:
wp db export backup-$(date +%Y%m%d).sql
This creates a file like backup-20251209.sql in your current directory. To back up the files, use tar:
tar -czf site-files-$(date +%Y%m%d).tar.gz wp-content/
This compresses the wp-content folder (where your themes, plugins, and uploads live) into a single archive. Then download both files to your local machine using scp or rsync. To automate this, I wrote a simple bash script that runs daily via cron: it exports the DB, tars the files, and uploads them to an S3 bucket using the AWS CLI. The script logs every run, so I can verify it’s working.

Why bother? It’s scriptable, you control the compression level, and there’s zero plugin overhead. But it’s risky if you mistype a command—I once accidentally ran wp db drop instead of wp db export (luckily on a staging site). Always test your script on a non-production environment first. This method is best for developers managing multiple sites who want a fast, repeatable, and auditable backup process.

Method 5: Cloud Storage Sync (Google Drive, Dropbox, or S3 via Plugins)

This isn’t a standalone backup method—it’s how you make your backups survive a server meltdown. The principle is simple: your backup files live somewhere other than your hosting server. I learned this the hard way when a client’s hosting company went bankrupt without warning. Their server was wiped clean, and the on-server backups vanished with it. Since then, every backup I create goes to at least two off-site locations.

Most backup plugins (UpdraftPlus, BackWPup, Duplicator) support direct cloud uploads. In UpdraftPlus, you connect your Google Drive account in the settings, and every backup automatically syncs there. You can also use a dedicated plugin like WP Offload Media Lite to sync your entire wp-content/uploads folder to Amazon S3—this doesn’t back up the database, but it protects your images and media files. For a full off-site backup strategy, I combine UpdraftPlus (to Google Drive) with a weekly manual download to my local NAS. The cost is zero for the first 15GB on Google Drive, and Amazon S3 costs about $0.023 per GB per month for standard storage. For a 2GB site, that’s about 46 cents a month—cheap insurance.

Counter-intuitive insight: Many people think cloud storage is only for final backups. But I also use it as my staging area—when I move a site between hosts, I upload the backup to S3 first, then download it on the new server. It’s faster than a direct transfer over HTTP and more reliable.

Method 6: Full Site Export with All-in-One WP Migration (For Site Migrations Too)

This plugin is designed for migrations, but it works beautifully as a backup tool—especially if you need a single file that contains everything. Install All-in-One WP Migration, go to Export, and choose “File.” The plugin packages your database, files, themes, and plugins into one downloadable .wpress file. I used this recently to clone a client’s site from a staging server to production. The export took 4 minutes for a 1.8GB site, and the import on the new server took 8 minutes. Everything—user accounts, WooCommerce orders, custom post types—came through perfectly.

The catch: the free version has a 512MB upload limit (for imports). If your site is larger, you need the premium version ($69/year) or use the “Unlimited Extension” add-on. A workaround I’ve used is to exclude large media files from the export (the plugin has an option to skip certain folders), then upload them separately. Or you can use the “File Extension” add-on to increase the limit. For smaller sites (under 512MB), this is the simplest method I know—no cPanel, no SSH, no cloud config. Just one file that you can store anywhere and restore anywhere.

Which Method Should You Choose? A Quick Comparison

My recommendation: if you’re a beginner, use a backup plugin (Method 2) with cloud storage (Method 5). If you’re a developer managing multiple sites, learn WP-CLI (Method 4) and automate it. For everyone else, check if your host offers daily backups (Method 3) as a safety net, but still run a plugin backup weekly to an off-site location. The worst backup strategy is the one you never test—so restore a backup to a staging site right now, just to prove it works.

Frequently Asked Questions About Backing Up a WordPress Website

How often should I back up my WordPress website?

For active blogs or ecommerce sites, daily or weekly backups are recommended. For static brochure sites, weekly or bi-weekly may suffice. Always back up before major updates—plugin upgrades, theme changes, or core updates.

Can I restore just the database without the files?

Yes, with most backup plugins and manual methods you can restore only the database (e.g., via phpMyAdmin) or only the files. This is useful if only one part is corrupted, like a broken table after a plugin update.

What’s the safest place to store backups?

Off-site storage like Google Drive, Dropbox, or Amazon S3 is safest. Avoid storing backups only on your hosting server—if the server fails, you lose everything. I keep one copy in the cloud and one on a local hard drive.

Do free backup plugins work well enough?

Free plugins like UpdraftPlus or BackWPup are reliable for most small-to-medium sites. They may lack premium features like incremental backups or priority support, but they get the job done. I’ve restored dozens of sites using the free version of UpdraftPlus without issues.

What should I do if my backup file is too large to download?

Use a plugin that supports cloud uploads directly (e.g., UpdraftPlus sends to Google Drive without downloading). Alternatively, use your host’s file manager or SCP to transfer the file. For very large sites, consider incremental backups (premium feature) that only back up what changed.

Practical takeaway: Pick one method from this list today. Set it up. Test the restore. Then set a calendar reminder to test again in three months. That’s the difference between a real backup strategy and wishful thinking.