phpMyAdmin is the tool almost every host gives you for managing your MySQL database through your browser, and exporting your database with it is the first move in getting your content off the old host — as well as being an essential backup skill in its own right. The export produces a single .sql file that is a complete, portable copy of your database. Doing it is genuinely quick, and knowing the couple of options that matter means you get a clean, complete export every time.

This guide walks through exporting a database with phpMyAdmin: opening phpMyAdmin and finding your database, the Quick versus Custom export methods, choosing the SQL format, running the export and getting your file, options for a large database, and what to do with the exported file. By the end you will be able to export any database cleanly, whether for a migration or a backup.

Opening phpMyAdmin and finding your database

phpMyAdmin is accessed through your hosting control panel — most panels have a phpMyAdmin icon or link, often in a ‘Databases’ section. Clicking it opens phpMyAdmin in your browser, showing a list of your databases down the left-hand side. If your host uses a different database tool, the export concept is the same, but phpMyAdmin is by far the most common.

Your first task is to select the correct database from that left-hand list. If you have only one, it is obvious; if you have several, you need to know which one belongs to the site you are exporting. The database name is recorded in your site’s configuration file — for WordPress, the DB_NAME value in wp-config.php — so if you are unsure, check there first to identify the right database.

So opening phpMyAdmin is a click from your control panel, and finding your database is selecting the right one from the list on the left (checking your config file for the name if you have multiple). Clicking the database name shows its tables, confirming you have the right one. With the correct database selected, you are ready to export it — which is where phpMyAdmin’s Export tab comes in.

Quick versus Custom export

With your database selected, you click the Export tab at the top of phpMyAdmin, and you are offered two export methods: Quick and Custom. Quick is the simple, one-choice option that exports the entire database with sensible default settings; Custom opens up detailed options for exactly which tables to include, how to format the output, compression, and more.

For the vast majority of cases — a standard migration or backup of a whole site — Quick is exactly what you want. It exports the complete database with the defaults that suit almost any WordPress or standard site, requiring no configuration and no risk of misconfiguring an option. You choose Quick, confirm the format is SQL, and you are done.

Custom is only needed for specific situations: exporting only certain tables, adding compression for a large database, or adjusting technical options for a particular requirement. Unless you have a reason to use Custom, choose Quick — it produces the complete, correct export you need with the least chance of error. So the default recommendation is Quick, and you reach for Custom only when a specific need (like compression or partial export) arises.

Choosing the SQL format

phpMyAdmin can export in various formats, but for a migration or a portable backup you want the SQL format, which is the default and the correct choice. The SQL format produces the .sql file — the text file of instructions that recreate your database — which is exactly what you import into a new database to rebuild it elsewhere. It is the universal, portable format for moving a database.

Other formats phpMyAdmin offers (like CSV, or various data-only formats) serve different purposes — CSV for spreadsheet-style data extraction, for instance — and are not what you want for migrating or backing up a whole database, because they do not capture the complete structure-and-data needed to rebuild it. For moving or backing up a site’s database, SQL is the format that carries everything.

So confirm the format is SQL (it is the default with Quick export), and you have the right output type. This is a simple point but worth being deliberate about: the SQL format is what makes the export a true, restorable copy of your database that you can import elsewhere. With Quick method and SQL format selected, all the important choices are made, and you are ready to run the export.

Running the export and getting your file

With Quick export and SQL format selected, you run the export by clicking the Go (or Export) button. phpMyAdmin generates the .sql file from your database and your browser downloads it — a single file containing your complete database. For a typical site, this takes only moments, and you now have your entire database as a portable file on your computer.

• Click Go: phpMyAdmin generates the export and your browser downloads the .sql file.
• Check the file: confirm it downloaded fully and is a reasonable size (not zero bytes, which would indicate a failure).
• Keep it safe: this file is your database — store it somewhere safe, especially if it is a backup.
• Note the database name: useful for identifying the file later and for recreating the database on import.

That downloaded .sql file is the whole point of the export — a complete, portable copy of your database that you can import into a new database (to migrate) or keep as a restore point (to back up). Confirm it downloaded completely; a zero-byte or tiny file when your site has substantial content signals a failed or interrupted export to retry. With a good .sql file in hand, the export is done — you have successfully lifted your database off the server into a movable file.

Options for a large database

For a large database, the standard Quick export can run into phpMyAdmin’s limits — a script execution time limit that a big export can exceed, causing it to time out or produce an incomplete file. If your database is large and the export fails, stalls, or gives you a truncated file, you need one of a few approaches for size.

Within phpMyAdmin, the Custom export lets you add compression (exporting as a gzip-compressed file), which produces a much smaller download and can help the export complete — and a compressed .sql can usually be imported directly too. Beyond phpMyAdmin, the more robust route for a genuinely large database is command-line export with mysqldump if you have SSH access, which has no web-interface time limit and reliably handles databases of any size.

So for a large database, either use Custom export with compression within phpMyAdmin, or step up to command-line mysqldump over SSH for full reliability. The phpMyAdmin web interface is perfect for normal-sized databases but has size limits that a large one can hit, and knowing the compression option and the command-line alternative means a big database does not stop you. For most sites, though, the straightforward Quick SQL export completes cleanly, and these size options only matter when your data genuinely outgrows the web interface.

What to do with the exported file

Once you have your .sql file, what you do with it depends on your purpose. For a migration, this file is the database half of your move: you take it to the new host, create a new empty database there, and import the .sql file into it (via phpMyAdmin on the new host), then reconnect your site to that new database. The export is the first step of moving your database; the import is its mirror on the other side.

For a backup, the .sql file is your database restore point: you store it safely (on independent storage, not just the server), ideally alongside a copy of your files, so that together they form a complete backup you could rebuild the site from. A database export on its own is only half a website backup — pair it with a files backup for a full one.

So the exported .sql file is a versatile, complete copy of your database, ready either to import into a new host (migration) or to keep as a restore point (backup). Either way, treat it with care as the valuable copy of your content and settings that it is. Knowing how to export a database with phpMyAdmin is thus a dual-purpose skill: it is the first move of any manual database migration, and it is the core of backing up your database — both resting on the same quick, three-click Quick-SQL-Go export.

FAQs

How do I export a database with phpMyAdmin?

Open phpMyAdmin from your control panel, select your database from the left-hand list (check your config file, like wp-config.php’s DB_NAME, if unsure which), click the Export tab, choose the Quick method and SQL format (both defaults), and click Go. Your browser downloads a single .sql file — a complete, portable copy of your database, ready to import elsewhere or keep as a backup.

What’s the difference between Quick and Custom export?

Quick exports the entire database with sensible defaults in one choice — right for almost any migration or backup. Custom opens detailed options: which tables to include, output format, compression, and more. Use Quick unless you have a specific need like exporting only certain tables or adding compression for a large database. Quick is complete, correct, and has the least chance of error.

Which format should I export in?

SQL — it’s the default and the correct choice for a migration or portable backup. The SQL format produces the .sql file of instructions that recreate your whole database (structure and data), which is exactly what you import into a new database to rebuild it. Other formats like CSV serve different purposes (spreadsheet extraction) and don’t capture what’s needed to rebuild the database.

How do I export a large database with phpMyAdmin?

A large export can hit phpMyAdmin’s execution-time limit and time out or truncate. Use Custom export with gzip compression for a smaller file that’s more likely to complete (and can usually be imported compressed), or — more reliably — use command-line mysqldump over SSH, which has no web-interface time limit and handles any size. For normal databases, the standard Quick export works fine.

How do I know my database exported correctly?

Check the downloaded .sql file isn’t zero bytes or tiny when your site has substantial content — that would signal a failed or interrupted export to retry. A complete export is a reasonable size for your data. The fuller confirmation comes on import: if it recreates all your tables and content on the new database, the export was good. Always verify a big export especially, since those are likeliest to truncate.

What do I do with the exported .sql file?

For a migration, take it to the new host, create a new empty database there, and import the .sql into it, then reconnect your site to that database. For a backup, store it safely on independent storage (not just the server), ideally alongside a files backup — a database export alone is only half a website backup. Either way, it’s a complete, portable copy of your content and settings.

The bottom line

Exporting a database with phpMyAdmin is a quick, three-click skill that serves double duty — it is the first move of any manual database migration and the core of a database backup. You open phpMyAdmin from your control panel, select the correct database from the left-hand list (checking your config file’s database name if you have several), click the Export tab, and make just two choices: the Quick method (which exports the whole database with sensible defaults, right for almost every case) and the SQL format (the default, and the one that produces the portable .sql file of instructions to rebuild your database). Click Go, and your browser downloads a single .sql file that is a complete, portable copy of all your content and settings. Confirm it downloaded fully — a zero-byte or tiny file when your site has real content signals a failed export to retry.

Two refinements cover the edges. For a large database that hits phpMyAdmin’s execution-time limit, use Custom export with gzip compression for a smaller, more reliable file, or step up to command-line mysqldump over SSH, which has no such limit and handles any size — while for normal databases the straightforward Quick SQL export completes cleanly. And what you do with the resulting file depends on your purpose: for a migration it is the database half of your move, to be imported into a new empty database on the new host and reconnected to your site; for a backup it is your restore point, to be stored safely on independent storage alongside a files backup, since a database export alone is only half a full website backup. Pick your database, choose Quick and SQL, and hit Go — and you have lifted your entire database into a movable file, ready to migrate or to keep safe.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Export a database with phpMyAdmin: open it from your control panel, select your database (check wp-config.php’s DB_NAME if unsure), click Export, choose Quick method + SQL format (both defaults), and hit Go to download the .sql file — a complete, portable copy. For a large database, use Custom export with gzip compression or command-line mysqldump over SSH. The file is your migration source or backup restore point; pair it with a files backup for a full one.