How to Access Your WordPress Database With phpMyAdmin (Safely)

To access a WordPress database with phpMyAdmin, sign in to your hosting control panel, open its phpMyAdmin link, identify the database name in wp-config.php, and select that database in phpMyAdmin. Export a backup before editing anything. The database contains your posts, pages, comments, users, and settings, but it does not contain your themes, plugins, media uploads, or other WordPress files.

Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.

What you need before opening phpMyAdmin

phpMyAdmin is a browser-based administration tool for MySQL and MariaDB databases. Your hosting company may expose it through a control panel, restrict it to administrators, or disable it completely. You need an active hosting-panel account and permission to manage the WordPress installation’s database.

#	Preview	Product	Price
1		Mastering phpMyAdmin for Effective MySQL Management	$40.98	Buy on Amazon
2		phpMyAdmin Starter	$25.99	Buy on Amazon
3		Learn phpMyAdmin Documentation: Database	$1.99	Buy on Amazon
4		Mastering phpMyAdmin 3.1 for Effective MySQL Management	$10.56	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

• The site should be accessed through HTTPS. Never enter database credentials over ordinary, non-secure HTTP.
• Know where the WordPress files are stored, normally in a document root such as /home/username/public_html on a cPanel account.
• Have access to the file manager or SFTP so you can read wp-config.php.
• Prepare a backup location outside the public web root. A SQL export should not be left where a visitor could download it.

phpMyAdmin is an administrative surface, not a WordPress dashboard feature. Make only a change you can explain and reverse, and keep the original export until the site has been tested.

Open phpMyAdmin from your hosting panel

cPanel

1. Sign in to cPanel.
2. Open Home » Databases » phpMyAdmin.
3. Wait for phpMyAdmin to open in the hosting account’s administrative session.

The cPanel documentation describes phpMyAdmin as a third-party tool for manipulating MySQL or MariaDB databases. The exact icon, wording, or location can vary by host, and a host can remove the interface from the account.

#1 Best Overall

Mastering phpMyAdmin for Effective MySQL Management

• Used Book in Good Condition

$40.98

Buy on Amazon

Plesk, DirectAdmin, and other panels

Look for a database section, then a database-management or phpMyAdmin link. Common labels include Databases, Database Management, MySQL Databases, or Manage. Some providers open phpMyAdmin from a specific database’s action menu rather than from a global menu.

If there is no phpMyAdmin link, do not install a copy in the public web directory as a workaround. Ask the host for its supported database-access method, such as a protected administrative URL, an SSH connection, or a temporary support session.

Find the correct database name in wp-config.php

Opening the wrong database is the most common cause of an apparently missing WordPress site. The authoritative value is in the configuration file used by that installation.

1. Open the hosting file manager or connect with SFTP.
2. Go to the WordPress installation directory. A document-root installation on cPanel commonly uses /home/username/public_html; a subdirectory or additional site will have a different path.
3. Open wp-config.php in a text viewer. Do not paste its contents into a public ticket or chat.
4. Record the values assigned to DB_NAME, DB_USER, DB_PASSWORD, and, when present, DB_HOST.

define( 'DB_NAME', 'account_wordpress' );
define( 'DB_USER', 'account_wpuser' );
define( 'DB_PASSWORD', 'use-the-current-password' );
define( 'DB_HOST', 'localhost' );
$table_prefix = 'wp_';

In the example, account_wordpress is the database to select. The prefix is wp_, but that is only a convention. A security-conscious or migrated installation might use a value such as site7_. The prefix determines the table names you should expect; it does not change the database name.

Use the file that the live site actually loads. A staging copy, an old backup, or a second WordPress installation can have a different DB_NAME. If the file contains environment-variable expressions instead of literal values, use the host’s deployment documentation or ask its administrator rather than guessing.

Select the WordPress database in phpMyAdmin

1. In phpMyAdmin, use the left navigation pane or the Databases page.
2. Find the name that exactly matches DB_NAME, including any hosting-account prefix, underscores, and capitalization shown by the panel.
3. Click the database name. Its tables will appear in the navigation pane and in the main area.
4. Confirm that the table names match the $table_prefix from wp-config.php. For a default prefix, you might see wp_posts, wp_options, and wp_users.

Do not select a database merely because its name contains “WordPress.” Shared hosting accounts often contain several databases for different sites, staging copies, applications, or abandoned installations. If the expected tables are absent, return to wp-config.php and verify both the database name and prefix.

Rank #2

phpMyAdmin Starter

$25.99

Buy on Amazon

Export a backup before editing

WordPress recommends regular database backups and one before every upgrade. WordPress.org Developer Resources recommended keeping three to five recent backups in 2023. Keep those copies in separate locations so a failed import, account problem, or damaged file does not destroy every copy.

What a database export includes

A database-only backup cannot restore a missing uploads directory or a deleted theme. A complete site backup therefore needs a separate copy of the WordPress files and, where relevant, server-level configuration.

Export through phpMyAdmin

1. Select the verified WordPress database.
2. Open the Export tab.
3. Use the quick export option when you need a complete export with the panel’s standard SQL settings. Use custom export only when you understand the table, format, and compression choices.
4. Start the export and save the resulting SQL or compressed SQL file outside the public web root.
5. Record the date, site, database name, and whether the export completed without an error.
6. Keep the original file until the site has been checked after the change. Remove temporary copies when the backup workflow is complete.

Large databases can exceed a browser upload or download limit imposed by the host, PHP, or the panel. Do not repeatedly retry a partial file. Ask the host for its documented large-database method, such as command-line export, a panel migration tool, or a temporary limit increase.

Make a targeted change without damaging the site

After the export, select only the table or row relevant to the task. Read the row before changing it, note the original value in a private change record, and avoid editing serialized option data as ordinary text. Serialized values contain length information; changing their text without a serialization-aware tool can make settings unreadable.

Example: locate a user for a password reset

WordPress’s official phpMyAdmin password-reset procedure demonstrates the navigation pattern:

1. Log in to phpMyAdmin.
2. Click Databases and select the WordPress database identified from wp-config.php.
3. Open the users table, normally wp_users or the same name with your installation’s custom prefix.
4. Choose Browse and locate the account by its login or email address.
5. Choose Edit for that row and change only the field required by the documented procedure.
6. Save the row, then test the login and the site’s normal front end.

Use this procedure only when you have legitimate administrator access. phpMyAdmin’s own interface can execute destructive operations immediately, so never use Drop, Empty, or a broad delete query as a shortcut for finding an account.

Rank #3

Learn phpMyAdmin Documentation: Database

$1.99

Buy on Amazon

Editing URLs, permissions, and options

URL changes and permission edits can affect every request or every user. Export immediately before the change, change the smallest possible set of rows, and test redirects, login, media, and the administration area. If a plugin stores structured or serialized values, use that plugin’s supported migration or command-line procedure instead of manually replacing text in the database.

Migrate a WordPress database

A migration uses phpMyAdmin twice: export from the source and import into a destination database. The database and its user should be created with the hosting panel’s MySQL Databases, Manage My Databases, or Database Wizard feature. cPanel specifically warns against creating databases or users in phpMyAdmin because the panel’s account mapping can then fail during backups and restorations.

Source database

1. Open the source database identified in its source wp-config.php.
2. Choose Export and save a complete SQL export.
3. Keep the source site available until the destination has been verified.

Destination database

1. Use the host’s database wizard to create the destination database and database user.
2. Grant the user the permissions required by WordPress, using the panel’s normal workflow.
3. Open phpMyAdmin for the destination account and select the empty destination database.
4. Choose Import, select the SQL file, confirm its format, and run the import.
5. Update the destination wp-config.php with the destination database name, user, password, and host.
6. If the domain or path changed, update the site’s URL using a migration-safe method and test every redirect, login, image, and administrative screen.

Import limits vary by host and database size. A browser error does not prove that an import completed; check for the panel’s success message and inspect the destination tables. For a large file, use the provider’s supported command-line or migration workflow instead of splitting SQL casually.

Keep credentials consistent

The values in wp-config.php must match the database account configured by the host. If you change a database user’s password in the hosting panel, immediately update the corresponding DB_PASSWORD value in wp-config.php. Otherwise WordPress may display a database connection error.

cPanel documents a basic command-line credential check:

mysql -u db_user -p

Run it only in a protected shell, replace db_user with the actual database user, and enter the password at the prompt rather than putting it in the command history. A successful login confirms that the credentials are accepted by the database service; it does not confirm that the WordPress file references the same database name or host.

Rank #4

Mastering phpMyAdmin 3.1 for Effective MySQL Management

• Used Book in Good Condition

$10.56

Buy on Amazon

Secure phpMyAdmin after use

• Use HTTPS for the control panel and phpMyAdmin session. WordPress documentation warns that non-secure HTTP logins can expose credentials to theft.
• Use the hosting panel’s access controls, administrator-only network rules, or VPN where the provider supports them. Do not leave a public, unauthenticated phpMyAdmin installation on the site.
• Follow phpMyAdmin security announcements and upgrade when a vulnerability affects the version supplied by your host.
• Log out of phpMyAdmin and the hosting panel when finished.
• Store SQL exports outside the public web root, protect their file permissions, and delete temporary copies after a verified backup process.
• Never publish wp-config.php, database passwords, exported users, or SQL files in a support forum or repository.

Troubleshoot common access problems

There is no phpMyAdmin menu

The host may have disabled it, your account may lack database permissions, or the service may be available only through a separate administrator URL. Check the panel’s database section and contact the host for its supported access route. Do not upload an unprotected phpMyAdmin package yourself.

The database name is unclear

Read DB_NAME from the active installation’s wp-config.php. If several WordPress directories exist, compare each file with the domain’s document root and the hosting panel’s database list. Confirm the prefix by checking $table_prefix and the table names after selection.

phpMyAdmin rejects the login

Use the host-provided phpMyAdmin link rather than a bookmarked session that has expired. Verify the database user, password, and host in wp-config.php. If the database password was recently changed, synchronize the file and the panel account. The shell test documented by cPanel can help distinguish invalid credentials from a WordPress configuration error.

The tables look empty or belong to another site

Stop before editing. You probably selected a different database or a staging copy. Recheck DB_NAME, the installation path, and the table prefix. Do not delete unfamiliar tables to “clean up” the list.

An export or import stops partway through

Check the file size and the panel’s reported error. Browser, PHP, and host limits commonly affect large SQL files. Retain the source export, remove any incomplete destination tables only when the host’s procedure says it is safe, and use the provider’s command-line or migration method for large databases.

The site fails after an edit

Stop making additional changes. Restore the affected rows or import the pre-edit backup into a test or recovery database according to the host’s procedure. If a database password changed, restore matching credentials in wp-config.php. For URL or serialized-option problems, use a WordPress-aware recovery tool or qualified administrator rather than broad search-and-replace operations.

Database access checklist

• Sign in through a secure hosting-panel session.
• Open the provider’s supported phpMyAdmin link.
• Read DB_NAME, DB_USER, DB_PASSWORD, DB_HOST, and $table_prefix from the active wp-config.php.
• Select the exact matching database and confirm its table prefix.
• Export before every edit, upgrade, or migration.
• Keep three to five recent database copies in separate, protected locations.
• Use the hosting database wizard to create databases and users.
• Import only into the verified destination database.
• Test the site after the change and retain the original backup until verification is complete.
• Log out, remove temporary SQL files, and keep phpMyAdmin patched and restricted.

How phpMyAdmin fits into a complete WordPress backup

phpMyAdmin solves the database part of recovery and migration. It does not replace a full-site backup. Pair the SQL export with a protected copy of the WordPress files, including themes, plugins, uploads, and wp-config.php handled according to your security policy. This separation explains why a database restore can bring back posts and settings while leaving media or a custom theme unavailable.

For routine maintenance, the safest sequence is consistent: identify the active configuration, export the database, make one narrowly defined change, test the site, and preserve the verified backup. That process lets you access the correct WordPress database without confusing a database task with a file restore or a hosting-account configuration change.

Quick Recap

Bestseller No. 1

Mastering phpMyAdmin for Effective MySQL Management

Used Book in Good Condition

$40.98

Bestseller No. 2

phpMyAdmin Starter

$25.99

Bestseller No. 3

Learn phpMyAdmin Documentation: Database

$1.99

Bestseller No. 4

Mastering phpMyAdmin 3.1 for Effective MySQL Management

Used Book in Good Condition

$10.56

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.