How to back up a WordPress site manually

What this problem looks like

A complete WordPress backup has two parts: the MySQL database and the wp-content directory plus core files you customized. Missing either half makes restore impossible or incomplete.

Manual backups complement plugin schedulers. Run one before major changes even when your host promises daily snapshots.

Step 1: Export the database in phpMyAdmin

Open hosting → phpMyAdmin.
Select the WordPress database.
Click Export → Quick → SQL → Go.
Save the .sql file with the site name and date in the filename.

Step 2: Export with WP-CLI on SSH

Only run these commands if you have SSH access to the server. They will not work inside File Manager.

bash

cd /path/to/wordpress
wp db export ~/backups/mysite-$(date +%F).sql
wp db export --tables=wp_posts,wp_postmeta ~/backups/posts-only.sql

Step 3: Download files via File Manager, SFTP, or FTP

Connect with File Manager, SFTP, or FTP and download wp-content/ entirely. Include uploads, plugins, and themes.

Also save wp-config.php and .htaccess from your site root, next to wp-admin and wp-content.

Large uploads folders may take hours. Compress in File Manager when available.
Exclude cache folders inside wp-content/cache if space is tight.
WordPress core can be re-downloaded but custom core edits need saving.

Step 4: What a backup plugin adds

Plugins like UpdraftPlus bundle database and files into one archive on a schedule. Manual steps still matter when the plugin itself is broken or the site is down.

Step 5: Storage and retention

Keep at least three restore points: before updates, before migrations, and a recent weekly copy.

Store backups off the web server. Ransomware and host failures can destroy local copies.

When to stop DIY and hire help

If manual backups feel slow or you need tested daily restores, BugShield Shield maintenance includes cloud backups and restore help at a confirmed fixed price.

Questions answered

Manual WordPress backup FAQs

Answers about backing up files and databases, protecting WooCommerce data, secure storage, and checking that a backup can be restored.

Do I need to back up WordPress core files?

Usually no. You can reinstall core from wordpress.org. Back up core only if you edited files directly.

How large will my backup be?

Mostly uploads size. Media-heavy sites produce multi-gigabyte wp-content folders.

Can I backup while the site is live?

Yes, but busy shops may have inconsistent dumps during orders. Put the site in maintenance mode for the cleanest export.

How often should I backup manually?

Before every risky change at minimum. Complement with automated daily backups for routine protection.

What should a complete manual WordPress backup include?

Include the database, wp-content, WordPress configuration, web-server rules, and any custom files needed to rebuild the exact site.

Should I back up WordPress files and the database at the same time?

Yes. Keeping them from the same point in time reduces mismatches between plugin files, settings, orders, users, and database schema.

Which tools can create a manual WordPress backup?

Use your hosting backup tool, phpMyAdmin or WP-CLI for the database, and File Manager, SFTP, SSH, or an archive tool for files.

Where should I store a manual WordPress backup?

Keep it encrypted away from the web server, with access limited to authorised people. Do not leave database exports or ZIP archives in a public site directory.

How do I verify a manual WordPress backup works?

Check archive integrity and database export size, then perform a controlled restore on staging. A completed download alone does not prove recoverability.

How do I back up a live WooCommerce store safely?

Use a consistent backup method that captures files and database together, or briefly pause writes so new orders are not created between the two copies.

Keep troubleshooting

Learn how to back up a WordPress site manually.