What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To download a WordPress database, open your host’s phpMyAdmin, select the database named by DB_NAME in wp-config.php, choose Export, keep SQL as the format, and save the generated file. Use Quick when that database belongs only to the WordPress site; use Custom when other applications share it or you need to select tables, compression, or restore-related options.
This creates a database dump, not a complete copy of the site. A recoverable full-site backup also needs the WordPress files, including core files, themes, plugins, uploads, and other server-side content.
As an Amazon Associate I earn from qualifying purchases.
What a phpMyAdmin WordPress download contains
A phpMyAdmin export is a text-based database dump. In SQL format it contains commands that recreate tables and insert the database records used by WordPress. Those records commonly include posts, pages, comments, users, settings, menus, and plugin data stored in MySQL.
Recommended Free Tools
The dump does not include the WordPress directory. It therefore omits WordPress core files, themes, plugins, media in wp-content/uploads, server configuration, and any other files outside the database. WordPress documentation treats the database and the files as separate parts of a site backup. Keep the SQL export with a matching file backup if your goal is disaster recovery.
Before you start
Have hosting access to phpMyAdmin
phpMyAdmin is normally supplied through your hosting control panel. The exact menu name and login route depend on the host. Look for a database section, a phpMyAdmin link, or a database-management button. If you cannot find it, ask the host where its phpMyAdmin login is located; you do not need to install a second copy merely to perform this export.
Locate the WordPress database name
Open the WordPress installation’s wp-config.php and find the line defining DB_NAME. The value is the database you must select in phpMyAdmin. Do not guess from a hosting account label: hosts often prepend an account or user name to the actual database name.
define( 'DB_NAME', 'example_database' );Also note the configured $table_prefix, especially if the database contains more than one application or more than one WordPress installation.
$table_prefix = 'wp_';The prefix is part of each WordPress table name, such as wp_posts or wp_options. A site may use a custom prefix, so never assume that every installation starts with wp_.
Choose a protected storage location
Decide where the downloaded file will be stored before you begin. Database dumps can contain personal information, email addresses, user records, comments, site settings, and sometimes secrets saved by plugins. Use a location with access controls, avoid leaving the file in a publicly served web directory, and retain an additional protected copy if the export is part of your backup plan.
How to download the database with Quick export
Quick export is the shortest path when the selected database is dedicated to this WordPress installation and you want all of its tables.
- Open phpMyAdmin from your host. Sign in through the hosting provider’s control panel or the provider’s documented phpMyAdmin address.
- Select the database. In the left navigation pane, click the database whose name matches
DB_NAMEinwp-config.php. Its tables should appear in the main pane. Do not start from only the server-level view when your goal is one site’s database. - Open Export. Use the Export tab or export command shown for your phpMyAdmin version.
- Choose Quick. This mode is intended to export all tables in the selected database with minimal decisions.
- Keep SQL as the format. SQL is the restorable database-dump format described in WordPress’s database-backup guidance.
- Run the export. Submit the export form. Your browser should offer a file download rather than displaying a normal WordPress page.
- Save the file. Put it in the protected location you chose. Depending on the options and phpMyAdmin configuration, the filename may end in
.sql,.gz, or.bz2.
After the download completes, check that the file exists locally and that its size is plausible for your site. A very small file can be legitimate for a new site, but it can also indicate that you selected the wrong database or that an export failed before completion.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWhen to use Custom export
Choose Custom when the database is shared with another application, when you need to select a subset of tables, or when you want compression and other export controls. Custom gives you more control but also creates more opportunities to omit a required table.
Select only this site’s tables in a shared database
- Select the database named by
DB_NAME, then open Export. - Choose Custom rather than Quick.
- In the table list, select the tables that begin with the WordPress
$table_prefixfromwp-config.php. For a prefix ofsite7_, for example, select tables such assite7_posts,site7_options, andsite7_users. - Review the selection carefully. Plugins can create additional tables with the same prefix, and those tables may be essential to the site. Excluding them can remove plugin settings or data from a later restore.
- Choose SQL as the output format and start the export.
If you are uncertain which tables belong to WordPress, compare the table names with the configured prefix and with the tables visible in the database. Do not delete or alter unselected tables; Custom export only controls what is included in the downloaded file.
Compression options
Custom export can package SQL output with compression. WordPress documentation gives zipped and gzipped output as examples. Compression reduces download size and storage space; it does not change the fact that the content is a database dump. A compressed file must be decompressed, or handled by a compatible import process, before a conventional SQL restore.
| Output | What it is | Use it when |
|---|---|---|
.sql |
Uncompressed SQL commands | You want the most directly readable and widely compatible dump. |
.gz |
Gzip-compressed export | You want a smaller file and your storage or restore workflow supports gzip. |
.bz2 |
Bzip2-compressed export | You want compressed storage and your workflow supports bzip2. |
The exact compression choices and labels depend on the phpMyAdmin version and host configuration. Keep the original extension so you know how the file is packaged.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →DROP statements and restore behavior
Some Custom export configurations can add DROP TABLE statements. A dump containing these commands can be useful when restoring over an existing database because a restore process can remove a table before recreating it. It also increases the consequences of importing the file into the wrong database: existing tables with matching names may be dropped.
Do not enable destructive restore-related options merely because they are visible. Use them only when you understand the target database and have a separate backup. For a routine download whose purpose is archival, the essential decisions are the correct tables and SQL format; restore behavior should be chosen for the later import scenario.
Quick versus Custom: which path fits?
| Choice | Best fit | What you decide | Main risk |
|---|---|---|---|
| Quick | A database dedicated to one WordPress site and an all-table dump | Usually only the SQL format and download location | You may export unrelated application tables if the database is shared. |
| Custom | A shared database, a need for table selection, compression, or restore-specific options | Tables, SQL format, compression, and optional SQL behaviors | Accidentally omitting a WordPress or plugin table can make a later restore incomplete. |
When in doubt, identify the database and prefix first. If the database contains only this site, Quick minimizes selection errors. If it contains other applications, Custom is safer because it lets you limit the dump to the WordPress-prefixed tables.
How to verify the downloaded file
Confirm the filename and extension
Make sure the browser saved a file rather than an HTML error page. The expected extension is usually .sql, .gz, or .bz2. If your browser appended an extra extension or saved the response as a web page, repeat the export and inspect the download details.
Free tools Windows power users keep installed
One-click scans. No signup required.
Inspect an uncompressed SQL file safely
An uncompressed .sql file can be opened as text. It should contain SQL statements and table definitions, not a WordPress login screen or an error message. Avoid editing the file unless you understand SQL syntax; a small change can make an import fail.
Record what the file represents
Use a filename that identifies the site and date, for example example-site-database-2026-10-18.sql. Record whether the export was Quick or Custom, which prefix was selected, and whether compression was used. This note prevents confusion when several sites or backup dates are stored together.
Protect the backup
Store the dump where unauthorized visitors cannot fetch it. Do not place it in a public uploads folder or leave it in the web root. Encrypting an off-site or removable copy is sensible when the file contains personal or administrative data. WordPress guidance allows the database export to be kept with the matching file backup; a portable external drive is one possible storage category, but it is optional rather than a requirement.
What this download is not
It is not a copy of the WordPress directory
Downloading files through a hosting file manager, SFTP, or another file-copy method does not include the database automatically. The database is stored separately from the typical WordPress file tree, so a file-only copy cannot recreate posts, users, settings, or other database records.
It is not WordPress Tools → Export
The Tools → Export screen in the WordPress dashboard creates a WXR XML content export. That format is designed for moving selected WordPress content between installations. It is different from a phpMyAdmin SQL dump, which represents the database structure and records and is the appropriate format for a database-level backup.
It is not necessarily a complete migration package
A database dump alone cannot restore media files, themes, plugins, or WordPress core. For a migration or full recovery, pair it with a compatible copy of the site files and document the PHP, WordPress, and plugin environment separately if your recovery process requires those details.
Rank #4
Common mistakes and fixes
The wrong database was exported
Symptom: The dump contains unfamiliar tables, is unexpectedly tiny, or lacks the site’s recent content.
Fix: Reopen wp-config.php, verify DB_NAME character for character, and select that database in phpMyAdmin before opening Export. Hosting accounts may contain several similarly named databases.
You exported from the server-level view
Symptom: The export screen offers a broad set of databases or produces a dump larger than expected.
Fix: Click the actual WordPress database in the left pane first. Then confirm that its table list includes the configured prefix before exporting.
Shared-database tables were included or omitted
Symptom: The file includes tables belonging to another application, or a later WordPress restore lacks plugin data.
Fix: Use Custom export. Select every table using the WordPress prefix, including plugin-created tables, and exclude unrelated prefixes. If you cannot establish ownership confidently, ask the host or site developer before importing or deleting anything.
The download is an HTML page
Symptom: The saved file opens as a login page, an error page, or another HTML document.
Fix: Sign in to phpMyAdmin again, select the database, and repeat the export. Check that the browser completed the file download and that no session timeout interrupted the request.
The file is too large for the browser export
Symptom: The export times out or never finishes.
Fix: Try Custom export with compression if available, and make sure you are exporting only the required WordPress tables in a shared database. If the host still cannot complete the operation, ask the host what database-backup method it supports; do not assume that a partial file is usable.
You enabled destructive options without meaning to
Symptom: The dump contains DROP TABLE commands and you are unsure whether it is safe to import.
Fix: Keep the file as an archive, but do not import it into a live database until you understand the target and have a separate backup. Those commands can remove matching tables during an overwrite-style restore.
Version and interface differences
phpMyAdmin’s tabs, option names, and screen arrangement vary by host and version. WordPress’s database guide describes a procedure tested with phpMyAdmin 4.4.13 connected to MySQL 5.6.28 on Linux; those figures identify the documented test environment, not a requirement for your current site. The reliable sequence is still: select the database, open Export, choose Quick or Custom, keep SQL, and download the result.
If your interface uses a slightly different label, look for the equivalent database-level Export action rather than relying on an exact screenshot. Confirm the selected database and table scope before submitting the form.
A safe repeatable checklist
- Open the correct WordPress installation’s
wp-config.php. - Record
DB_NAMEand$table_prefix. - Open phpMyAdmin through the hosting provider.
- Select the database whose name matches
DB_NAME. - Verify the visible tables use the expected prefix.
- Choose Quick for a WordPress-only database or Custom for shared databases and extra controls.
- Use SQL as the format.
- If using Custom, include every WordPress and plugin table with the correct prefix.
- Enable compression only if your storage or restore process supports it.
- Treat
DROP TABLEoptions as restore-specific and potentially destructive. - Download the file and confirm its extension and contents.
- Store the dump securely with the matching WordPress file backup.
Using the dump later
A SQL dump is intended to be imported into a MySQL-compatible database through a tool such as phpMyAdmin or another database utility. The target database must be chosen deliberately, particularly when the file contains DROP TABLE statements. A compressed dump may need to be decompressed or imported through a tool that understands its compression format.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →For a site move or recovery, the database is only one component. Restore the corresponding WordPress files as well, then verify the database credentials and table prefix in wp-config.php. The downloaded file cannot supply missing uploads, themes, plugins, or core files.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
