Back Up a MySQL Database with phpMyAdmin

Use phpMyAdmin to export a selected MySQL database when you have authorized access through your hosting control panel. The resulting SQL file is a database backup, not a complete website or cPanel account backup.

Choose the correct database

1. Sign in to your control panel over HTTPS and open phpMyAdmin. The provider’s menu location depends on its panel theme.
2. Identify the database name from the application configuration. Do not guess from similarly named databases; a hosting account can contain several independent sites.
3. Select that database in the navigation tree, then check that the expected tables are listed. Starting an export from a single table produces a table export, not the complete database.

Export structure and data as SQL

Open Export and choose SQL. Quick export may be sufficient for a straightforward small database. Use Custom when you need to inspect the selected tables, structure/data choices and optional database objects. Ensure every required table and its data are included; do not accidentally select a structure-only export.

Save the generated file to a private location. Depending on phpMyAdmin’s configuration, the export may be compressed. Record the database name and export time. Preserve the downloaded SQL or compressed file as delivered rather than editing it casually or placing it on a public website.

Check what the export does not establish

• Live changes: a busy application can change while an export is running. Arrange a consistent backup strategy with your administrator; an Export button is not a universal transactional snapshot guarantee.
• Additional components: website files, mailbox data, application secrets, scheduled jobs and database-user grants are separate from this SQL export.
• Large databases: browser downloads and imports can fail because of PHP execution, memory or upload limits. Use an approved command-line or provider backup route instead of retrying until a partial file looks plausible. See the command-line MySQL guide.

Test an import without risking production

Create a separate empty test database and select it before opening Import. Check file-format support and size limits for the installed phpMyAdmin release, then import the saved export. SQL can drop or replace existing objects, so do not test against the only live copy.

Review errors, compare expected tables and representative records, and test an isolated application copy if appropriate. Prevent test copies from sending real mail or taking payments. Keep a verified private copy before making production changes; a successful download alone does not prove the database is recoverable.

Reference: phpMyAdmin import and export documentation. Reviewed October 14, 2026. Labels and available options vary by installed release and hosting configuration; no customer-panel export was executed in this editorial review.