Need a dependable WordPress backup before updating a plugin, redesigning your site, moving hosts, or fixing an unexpected error? If you’re searching for how to manually backup your WordPress site, you’re in the right place.
A manual backup gives you direct control over your site’s files and database. It’s especially useful when you don’t want to rely solely on a plugin or hosting provider, your site is experiencing problems, or you need an independent copy stored safely off the server.
This guide will show you how to create matching copies of your complete WordPress files and database, store them together, and check that both are usable if you ever need to restore your site. These steps are for self-hosted WordPress.org sites. WordPress.com users should use the export or backup options available with their plan.
The most reliable way to backup WordPress is with a robust, reputable backup plugin that captures every site file and the matching database while reducing the risk of human error. If you backup manually, copy all WordPress files and export the database from the same point in time. One without the other is incomplete. Store both copies off-site, then open and verify them before relying on the backup.
What a complete WordPress backup contains
A full backup has two parts:
- The complete site folder: This includes WordPress core files, which run WordPress; wp-content, which contains uploads, plugins, and themes; wp-config.php, which contains site and database settings; .htaccess, when present; and other files in the main WordPress folder.
- The database export: The database stores posts, pages, comments, users, menus, settings, orders, and other saved site data. Export it as SQL, a text format that can be imported into a database later.
Downloading the site folder does not include the database. Exporting the database does not include uploads, themes, plugins, or the files that run the site. Copying only wp-content is useful for a targeted file change, but it is not a complete backup.
Keep both parts close in time. New orders, comments, registrations, or edits between the two exports can make them describe different versions of the site.
Prepare the backup session
Gather these items before you begin:
- Confirm your hosting access: Have your hosting control panel, file manager, or SFTP access ready. SFTP is a secure file-transfer method that encrypts your login details and the files sent between your computer and the host.
- Locate the database tool: Your host may provide phpMyAdmin, a browser-based database manager, through cPanel, Plesk, or another hosting panel.
- Reserve enough storage: A compressed copy of a large site can still be large. Check the available space if you plan to save a backup WordPress site to computer or private cloud storage first.
- Create a private dated folder: Use a name such as example-site-backup-2026-08-07. Keep the destination outside the live hosting account.
- Choose a low-change time: If the site takes orders or accepts registrations, avoid exporting during a busy period. When possible, export the database first, then copy the files, and finish both without a long delay.
Copy all WordPress files
Start with the folder that contains the WordPress installation. Do not assume its name. Use the hosting file manager Find the WordPress installation folder: Look for wp-admin, wp-content, and wp-includes together.
Use the hosting file manager
- Find the WordPress installation folder: Look for wp-admin, wp-content, and wp-includes together. The folder containing all three is the correct main folder.
- Select the complete folder contents: Include the files directly inside that folder, including hidden files such as .htaccess when it exists. Do not select only wp-content.
- Create a complete compressed archive: Choose Compress, Archive, or a similar option, then select ZIP if the panel offers it. A compressed archive is one file containing the folder structure and its contents.
- Download and open the archive: Save it in the dated backup folder, wait for the download to finish, and open it on your computer. Confirm that it contains the expected WordPress folders and files.
If the archive is unexpectedly small, the panel shows an error, or the download stops, do not delete the server copy. Create the archive again or use SFTP.
Use SFTP when the file manager is not enough
- Request the correct connection details: Ask your host for the SFTP address, username, port, and sign-in method. These details are separate from your WordPress dashboard login.
- Choose SFTP in your transfer app: Open a file-transfer app such as FileZilla or Cyberduck and confirm that the connection type is SFTP, not plain FTP. FTP may send login details and file transfers without encryption.
- Open the same WordPress folder: Locate the folder containing wp-admin, wp-content, and wp-includes.
- Show hidden files before copying: This helps include .htaccess and other hidden files when they are part of the installation.
- Download the whole folder and review the result: Wait for the transfer queue to finish, then check for failed or skipped files. A transfer can look complete while still missing files.
Export the WordPress database
Use wp-config.php to identify the correct database. Open the file through your protected hosting or SFTP connection and find DB_NAME. Then follow standard steps to backup your WordPress database.
wp-config.php can also contain database passwords and other private settings. Do not paste it into a public document or leave a downloaded copy in a public web folder.
Export through phpMyAdmin
- Open the database manager from your host: The link may appear in cPanel, Plesk, or a custom hosting dashboard. Menu names differ by provider.
- Select the database from DB_NAME: If several databases are listed, match the full name from wp-config.php.
- Choose the complete export: Select Export, keep the full database selected, and choose SQL as the format. A compressed SQL file can reduce download size for a large database.
- Save the export beside the file archive: Use a name such as example-site-database-2026-08-07.sql or the compressed version provided by the tool.
- Check the downloaded export: Confirm that the file exists, has a non-zero size, and opens or decompresses without an error.
Export the complete database instead of selecting only familiar sections. Plugins, stores, memberships, and custom features can save important data there.
Use SSH and WP-CLI only if you already know them
SSH is secure terminal access to your hosting account. WP-CLI is a command-line tool for managing WordPress. If you already use both, you can run the database export command wp db export example-site-database-2026-08-07.sql, then transfer the result through SFTP.
This route exports the database only. Copy the complete WordPress files separately. If SSH or WP-CLI is new to you, use the hosting file manager and database tool instead.
Store and verify the backup set
Keep the two files together in one dated folder, for example:
- example-site-files-2026-08-07.zip
- example-site-database-2026-08-07.sql
Then apply these checks:
- Keep the first copy away from the live host: A server outage, account lockout, accidental deletion, or compromised site could affect a backup stored beside the site.
- Protect access to the folder: Backups can contain configuration details, user records, comments, orders, and other private data. Use restricted access and encryption when possible.
- Keep another protected copy: A second location reduces the chance that one storage failure removes your only recovery copy.
- Open both exported files: Check the archive folders, confirm the SQL file is present and non-empty, and review the SFTP transfer list for failures.
- Plan a safe restore test: A staging site is a private copy used for testing. Restore the set there when the backup matters, and do not experiment with the live site.
Understand what each part can restore
- Missing or changed files: Restore the affected files.
- Lost posts, settings, users, or other saved data: Restore the database.
- A failed server or site move: You will usually need both parts from a compatible time.
A complete restore may also depend on the new host, the PHP version used to run WordPress, the database service, the domain settings, and other host configuration. Restoring the files and then importing the database is a common order; a guide to restoring WordPress from a backup can help you understand what the process will replace. Do not restore over the live site until you know what the process will replace.
When manual backups stop being practical
Manual backups suit a one-off copy before a WordPress, theme, plugin, or PHP update, a migration, or when learning how to archive a WordPress site for long-term storage. They are easy to miss on sites that publish often or receive orders, comments, registrations, or other frequent changes.
A backup service can schedule the work and keep copies away from the live server. Before choosing one, confirm that it covers both files and the database, stores copies in a location you control, and provides a practical restore process. If you want automated WordPress backups with BlogVault, review its current backup and restore options before relying on it.
FAQs
Can I backup only the wp-content folder?
Not for a complete site backup. wp-content contains uploads, plugins, and themes, but it leaves out WordPress core files and other files in the main folder. Use it alone only when you need a selective file copy.
Does copying the WordPress files include the database?
No. The database is stored separately, so export it as SQL and keep it with the file archive.
Can you manually backup your WordPress site without opening the WordPress dashboard?
Yes. You need access to the hosting files and database, not necessarily the WordPress dashboard. Use the host’s file manager or SFTP for the files and the host’s database tool for the export.
Should I backup before updating WordPress?
Yes. Create a fresh matched backup before updating WordPress, a plugin, a theme, PHP, or major site settings. Keep the backup until you confirm that the change works.
How often should I make a manual backup?
Match the timing to how quickly your site changes. While implementing a 3-2-1 WordPress backup rule is ideal for defining your overall routine, low-change brochure sites need far fewer manual copies than e-commerce stores or high-traffic blogs. Always create a fresh backup before making major changes.
Conclusion
To manually backup your WordPress site, copy the complete WordPress folder and export the matching database. Save both in a dated folder outside the live host, protect the folder, and check the archive and SQL file before you rely on them. For a one-off change, this process gives you a clear recovery point. If your site changes often, use a backup system that runs on a schedule.
That system should store copies away from the live server and let you test a restore before an emergency.
Shivani enjoys crafting guides that make every aspect of using WordPress simple and easy to follow. When she's not glued to her laptop, you can find her buried in a good book or occasionally, painting.
