Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Backups & maintenance · Guide

How to Back Up WordPress Without a Plugin

How to Back Up WordPress Without a Plugin

Short answer

To back up WordPress without a plugin, export the database in phpMyAdmin with the Quick method and SQL format, then download the whole WordPress folder with your file manager or an FTP client. Put the .sql export and the files archive in one dated folder and move it off the server. Keep at least 3 to 5 recent backup sets in different places.

Key takeaways

  • A manual backup has two parts, files and database, and downloading the folder alone misses the database.
  • Back up the database first and the files second, then store both parts together as one backup set.
  • phpMyAdmin Quick export with SQL format is enough for most sites, but it cannot handle large databases.
  • wp db export writes a SQL dump using the login details in wp-config.php, with a dated file name by default.
  • Restore files first and import the database second, which is the reverse of the backup order.

What does a manual WordPress backup include?

A manual backup has two parts: a copy of your WordPress files and an export of your database, taken at about the same time.

The files are everything in your WordPress folder on the server: WordPress core, themes, plugins, uploads, wp-config.php and .htaccess, as listed in the WordPress backup handbook. The database holds your posts, pages, comments, users and settings, and it lives in a separate MySQL or MariaDB system.

Downloading the WordPress folder does not back up the database, because the database lives outside that folder. The WordPress backup handbook states this plainly, and it is the mistake most first-time manual backups make.

WordPress.org advises backing up the database first and then the files, so the two halves describe the same moment as closely as possible. Treat the pair as one backup set and store the two parts together.

PartWhat it holdsHow to copy it
FilesCore, themes, plugins, uploads, wp-config.phpFile manager, FTP or SSH
DatabasePosts, pages, comments, users, settingsphpMyAdmin, WP-CLI or mysqldump
Backup setBoth parts from the same timeOne dated folder, stored off the server

Our guide to how to back up WordPress covers the same two parts in more detail if you want the basics first.

How do you export the WordPress database with phpMyAdmin?

Open phpMyAdmin, select your database, click Export, choose the Quick method with SQL format, and click Go.

Find phpMyAdmin in your hosting control panel. In cPanel, look for the MySQL Databases page and click the phpMyAdmin link, as the WordPress backup handbook explains. If several databases are listed and you are unsure which one is yours, the database name and login sit in wp-config.php, since WP-CLI reads its database credentials from that file.

Once phpMyAdmin is open, click your WordPress database in the left column, then click the Export tab at the top. For most sites, the Quick method with the format set to SQL is enough. Click Go and save the .sql file to your computer.

For more control, choose the Custom method instead. Keep all tables selected, keep SQL as the format, pick zipped or gzipped compression for a large database, and tick Add DROP TABLE and IF NOT EXISTS, as the WordPress.org database backup guide describes. Then click Go at the bottom of the page.

One limit matters: phpMyAdmin cannot handle large databases, according to the same WordPress.org guide. If the export times out or the file comes back far smaller than you expect, switch to WP-CLI or mysqldump instead of retrying the same export.

How do you download your WordPress files without a plugin?

Download the whole WordPress folder with your host file manager or an FTP client, then zip the copy on your own computer.

The WordPress backup handbook notes that FTP clients let you copy the files to a folder on your computer, where you can compress them into a zip file to save space. If your file manager can compress the folder on the server first, use that option, since one archive downloads faster than thousands of small files.

At minimum, copy the wp-content folder, the wp-config.php file and the .htaccess file if your site has one. WordPress core itself can be downloaded again from WordPress.org, so those three items plus the database are the parts you cannot rebuild from scratch.

Do not leave the backup archive on the server when you finish. A file called backup.zip sitting in a public folder can be downloaded by anyone who guesses its name, and it holds your database password and your whole site. Download it to your own computer and delete the copy on the server.

How do you back up WordPress with WP-CLI?

Run wp db export from the WordPress folder over SSH, and WP-CLI will write a SQL dump using the login details in wp-config.php.

WP-CLI is the command line tool for WordPress. Its wp db export command runs the mysqldump utility with the DB_HOST, DB_NAME, DB_USER and DB_PASSWORD values from wp-config.php, and it accepts any valid mysqldump flag, according to the WP-CLI command documentation. If you give no file name, it writes {dbname}-{Y-m-d}-{random-hash}.sql in the current folder.

A typical export looks like this: wp db export --skip-opt --add-drop-table. The WP-CLI documentation shows this command ending with the message Success: Exported to 'wordpress_dbase-db72bb5.sql'. You can also export single tables with --tables=wp_options,wp_users, or skip tables with --exclude_tables.

For the files, archive the folder from the same SSH session, for example with tar -czf site-backup-2026-11-21.tar.gz public_html, then download the archive. WP-CLI only handles the database side, so the files still need a separate copy.

WP-CLI needs SSH access and WP-CLI installed on the server. If your host does not offer either, use the phpMyAdmin and file manager route above instead.

How do you back up WordPress with cPanel only?

Use cPanel Backup for the files and its MySQL download for the database, without installing anything on WordPress.

Open Backup in cPanel. Under Partial Backups, download a copy of your home directory to save all the files in your site folder. For the database, look for Download a MySQL Database Backup and click the name of your database.

WordPress.org notes that a .gz file will be downloaded to your local drive, and there is no need to unzip it to restore it.

Do not generate a full cPanel backup for this job. WordPress.org warns that full backups are strictly for archival purposes and cannot be restored through cPanel, so they are the wrong tool for a backup you plan to restore.

cPanel suits a one-off backup before an update or a move. If you want scheduled backups, a plugin or a host backup plan will serve you better. Our comparison of cPanel backup vs plugin backup weighs the two routes side by side.

How do you store and label a manual backup?

Put the files archive and the database export in one dated folder, move it off the server, and keep at least 3 to 5 recent sets.

WordPress.org recommends keeping at least 3 to 5 recent backups stored in different places, for example one on the hosting server, one in cloud storage and one on your own computer. A folder named example-com-2026-11-21 makes the site and the date clear at a glance, and it keeps each backup set separate from the rest.

Store copies in more than one place, since a backup on the same server as the site is lost in the same incident that takes the site down. Read where to store WordPress backups if you want help choosing the second location.

Before you trust a backup, check its size. A .sql file of 0 KB, or a zip far smaller than your uploads folder, usually means the export failed partway through. A quick look at the file list inside the archive catches that error before you need the backup.

How do you restore a manual backup?

Restore the files first, then import the database, which is the reverse of the backup order.

Upload the files back to the site folder with your file manager or FTP client, then open phpMyAdmin and import the database. WordPress.org describes the import steps: log in to phpMyAdmin, select the database, click the Import tab, browse to the backup file, make sure SQL is the format, and click Go.

If the database name or password changed during a move, update wp-config.php to match, as the WordPress backup handbook advises. The import replaces the current database, so it reverts the site to the state it was in when the backup was made.

Our guide to how to restore a WordPress site from backup walks through the full restore in order.

After the restore, run the checks in how to test a WordPress backup before you call the job done.

What can go wrong with a manual backup?

The most common manual backup mistakes are missing the database, mixing files and database from different times, and leaving the backup on the server.

A files-only copy looks complete until you try to restore it, and then you find no posts, no users and no settings. The WordPress backup handbook is blunt on this point: you need both parts to fully restore a typical site.

A long gap between the database export and the file download creates a mismatched set. New comments or orders can land in the database after the files were copied, or new uploads can arrive after the database was exported. Keep the two steps close together and store them as one set.

Large databases are the next trap. phpMyAdmin cannot handle them, so use mysqldump instead. MySQL describes mysqldump as a tool that performs logical backups, producing SQL statements that can rebuild the database, and it can dump one or more databases at once.

MySQL also warns that mysqldump is not built for very large amounts of data, since restoring replays the SQL statements one by one and can be slow. For a large site, a plugin with incremental backups or a host backup plan will usually be the better choice.

When should you use a backup plugin instead?

Use a plugin when backups must run on a schedule, when the site changes daily, or when manual steps keep getting skipped.

WordPress.org notes that several methods exist to automate backups, and it still advises backing up those automatic backups with a manual one once in a while to prove the process works. That check is worth keeping even after you switch to a plugin.

Plugins such as UpdraftPlus can schedule backups and send them straight to remote storage such as Google Drive or Amazon S3, according to TeamUpdraft. That removes the two weakest parts of the manual routine: remembering to run it, and moving the copy off the server.

Manual backups still have a place. They teach you where your files and database live, and they work on a site that is already broken, where a plugin may not run.

Learn the manual route once, then decide if a plugin should take over the daily work. Our guide to incremental vs full backups in WordPress explains how plugin backups differ from the full manual copy described here.

Frequently asked questions

Can I back up WordPress with only cPanel?

Yes. Use cPanel Backup to download your home directory for the files, and the Download a MySQL Database Backup link for a .gz copy of the database. Skip the full cPanel backup option, since WordPress.org warns it cannot be restored through cPanel.

Where do I find my database name?

Open wp-config.php in your file manager and look for the DB_NAME line. That value is the name of the database WordPress uses, and it tells you which database to pick in phpMyAdmin.

How do I back up a very large WordPress database?

Use WP-CLI with wp db export, or mysqldump from the command line, since phpMyAdmin cannot handle large databases. MySQL notes that restoring a large mysqldump file can be slow, so allow plenty of time for the import.

Do I need to back up WordPress core files?

Not strictly. WordPress core can be downloaded again, so the parts you must keep are wp-content, wp-config.php, .htaccess and the database export. Copying the whole folder is still simpler and leaves less room for error.

How often should I make a manual backup?

WordPress.org suggests once a week for small sites and daily for high-activity sites, with at least 3 to 5 recent backups kept. Make one before every update or move, and run a manual backup now and then even if a plugin handles the daily routine.

Sources

  1. Backups WordPress Developer Resources
  2. Backing Up Your Database WordPress.org
  3. wp db export WordPress Developer Resources
  4. mysqldump — A Database Backup Program MySQL
  5. How to Backup WordPress to Amazon S3 TeamUpdraft

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test