phpMyAdmin is the web tool every Ultra Web Hosting account uses to look inside its databases, and once you know your way around it, most database chores take a couple of minutes instead of a support ticket. This guide covers opening phpMyAdmin from cPanel, finding your way around the interface, browsing and editing rows without breaking anything, running SQL safely, and taking a proper backup before you make bulk changes.
- What phpMyAdmin Is and When to Use It
- Opening phpMyAdmin from cPanel
- A Tour of the Interface
- Browsing and Editing Rows Safely
- Running SQL from the SQL Tab
- Exporting a Database as a Backup
- Importing or Restoring a SQL File
- Search and Find-and-Replace
- Repairing and Optimizing Tables
- Privileges and Safety Tips
Look, Edit, Back Up, Import
phpMyAdmin gives you a point-and-click window into the MariaDB databases behind your site. You mostly use it for four things, and each one is quick once you know where the button is.
- Inspect and edit individual rows without writing any SQL
- Export a full database to a .sql file as a backup
- Import or restore a .sql file into an existing database
- Run one-off SQL queries for quick fixes and lookups
Export Before Any Bulk Change
The one habit that will save you a bad afternoon: export the database before you run any UPDATE, DELETE, or import. A phpMyAdmin export takes ten seconds and gives you a file you can restore from if a query goes sideways. There is no undo button in a database.
- Export > Quick > SQL format before every bulk edit
- Keep the .sql file until you have confirmed the change worked
- See How to Back Up Your Website for a full-account backup
01. What phpMyAdmin Is and When to Use It
phpMyAdmin is a web-based front end for MariaDB and MySQL databases. Instead of connecting a database client or typing commands at a shell, you point, click, and browse your data in the browser. Every Ultra Web Hosting plan includes it in cPanel, and it talks to the same databases your website (WordPress, Joomla, a custom app) reads and writes.
Reach for phpMyAdmin when you want to:
- Inspect or edit data - change a WordPress admin email, flip a plugin setting stored in a table, or fix a typo in a record.
- Back up a database - export the whole thing to a .sql file before an upgrade or migration.
- Import a database - restore a backup, or load a database from another host into your new account.
- Run a quick SQL query - a one-off SELECT to check a value, or a targeted UPDATE with a proper WHERE clause.
Point and Click
The right tool for occasional, interactive database work on shared hosting.
- No SSH, no client software to install
- Visual browse and edit for individual rows
- Built-in export and import with a progress bar
The mysql Client
Faster for very large databases and scripting, but you need SSH access and comfort at a shell.
- Best for imports too big for the browser upload limit
- Scriptable for automation and repeated jobs
- Requires SSH; not enabled by default on every plan
For anything you do a handful of times, phpMyAdmin is the answer. The one place the command line wins is importing a database larger than the browser upload limit, which we cover in Section 07. Everything else in this guide is faster in phpMyAdmin.
02. Opening phpMyAdmin from cPanel
phpMyAdmin lives in cPanel and logs you in automatically using your cPanel account, so there is no separate password to remember.
- Log in to cPanel for your account.
- Scroll to the Databases section.
- Click phpMyAdmin. It opens in a new tab, already logged in.
phpMyAdmin only lists databases your cPanel user owns. If the left panel is empty or you do not see the database you expect, it has not been created yet, or the current user has no privileges on it. Create the database and a user first in cPanel > MySQL Databases, then grant that user access. The full walkthrough is in How to Add a User to a Database. Until a user is assigned to the database, phpMyAdmin cannot see it.
If you have several databases, they all appear in the left panel once their owning user has privileges. A brand-new account with no databases yet will show an almost empty phpMyAdmin, which is normal.
03. A Tour of the Interface
phpMyAdmin is split into two areas. Spend a minute learning them and everything else falls into place.
- The left panel lists your databases. Click a database name to expand it and see the tables inside. Click a table to select it and load its contents in the main area.
- The main area shows a row of tabs across the top. Which tabs appear depends on whether you have a database or a single table selected. The ones you use most are:
- Browse - view the rows in the selected table.
- Structure - the columns, types, indexes, and keys that define the table.
- SQL - a box where you type and run SQL statements.
- Search - find rows by column value without writing SQL.
- Export - dump the database or table to a file.
- Import - load a .sql file into the database.
The tabs are context-sensitive. Select a database in the left panel and the tabs act on the whole database (Export dumps every table). Select a single table and the same tabs act on just that table. If a query or export is affecting more than you meant, check what is selected on the left first.
04. Browsing and Editing Rows Safely
The safest way to change a single value is not SQL at all, it is the Browse tab. You see exactly the row you are changing, and you only touch one record.
- Click the database in the left panel, then click the table you want.
- The Browse tab loads automatically, showing the rows.
- To change a row, click the Edit (pencil) link at the start of that row. A form opens with every column, where you change the value and click Go to save.
- For a fast one-value change, double-click a cell to inline edit it, type the new value, and click away to save.
- To remove a row, tick its checkbox on the left and click Delete, then confirm. Deleting one clearly identified row this way is far safer than a DELETE query.
If a table has thousands of rows, use the Search tab (Section 08) to narrow down to the row you want before editing, rather than paging through by hand. It is quicker and you are less likely to edit the wrong record.
05. Running SQL from the SQL Tab
When point-and-click is not enough, the SQL tab lets you run statements directly. Select a database in the left panel first so the query runs against the right one, then click SQL and type into the box.
Read-only SELECT queries are safe to run any time. A couple of harmless examples:
SELECT * FROM wp_options WHERE option_name = 'siteurl';
SELECT ID, user_login, user_email FROM wp_users;These only read data, so run them freely to check values before you change anything.
An UPDATE or DELETE with no WHERE clause hits every row in the table. DELETE FROM wp_posts; empties the entire table in one shot, with no undo. Always include a WHERE that pins the statement to the exact rows you mean, and always export the database first (Section 06). Run the matching SELECT version first to confirm it returns only the rows you expect, then change SELECT to UPDATE or DELETE.
A targeted, WHERE-scoped update looks like this. Note how the WHERE clause limits it to one row:
UPDATE wp_options SET option_value = 'https://example.com'
WHERE option_name = 'siteurl';Even with a WHERE clause, take the export first. It costs nothing and it is the difference between a two-minute fix and a restore from an older backup.
06. Exporting a Database as a Backup
Exporting writes the whole database (structure plus data) to a single .sql file you can keep or restore later. Do this before any upgrade, migration, or bulk edit.
- Click the database name in the left panel so the whole database is selected.
- Click the Export tab.
- Leave the method on Quick for a standard full backup. Choose Custom only if you need to pick specific tables or add options.
- Leave the format as SQL.
- Click Go. Your browser downloads a
.sqlfile named after the database.
For a large database, use Custom export and set Compression to gzip. You get a smaller .sql.gz file that downloads faster and, just as importantly, is small enough to upload back through the Import tab later without hitting the size limit. For a small site the plain SQL export is fine.
A phpMyAdmin export covers one database. For a full account backup that also includes your files and email, see How to Back Up Your Website. The two together are your complete safety net.
07. Importing or Restoring a SQL File
Import loads a .sql file into a database, which is how you restore a backup or move a site in from another host. The target database has to exist first, so create it in cPanel > MySQL Databases if it is not there yet.
- In the left panel, click the database you want to import into. Make sure it is the right one, since import writes into whatever is selected.
- Click the Import tab.
- Under File to import, click Choose File and pick your
.sqlor.sql.gzfile. - Leave the format on SQL and click Go.
- Wait for the success message. Large imports take a minute or two, so do not close the tab.
phpMyAdmin caps the upload size (commonly around 50 MB on shared hosting). If your file is bigger, you have two options. First, re-export it as gzip, which often shrinks a database enough to fit. If it is still too large, import it over SSH from the command line, which has no such limit:
mysql -u db_user -p db_name < backup.sqlRun that from the directory holding the file, replacing db_user and db_name with your database user and database name. It prompts for the password. SSH is not enabled on every plan by default, so open a ticket if you need it turned on and we will help with a large import. For connection details, see How to Test Your MySQL Connection.
08. Search and Find-and-Replace
The Search tab finds rows by value without any SQL, which is handy for locating the exact record you need. A common ask is updating a WordPress site URL after a domain change, and it is worth being careful about how you do it.
- Select the table (for WordPress, the
wp_optionstable for the site URL), then click the Search tab. - Enter the value you are looking for and run the search to find the matching rows.
- For a single, plainly non-serialized value like the
siteurlandhomeoptions, a targeted edit or WHERE-scoped UPDATE (Section 05) is fine.
Do not run a blanket find-and-replace across an entire WordPress database with raw SQL. WordPress stores many settings as PHP serialized data, where each string is stored with its length. A raw replace changes the text but not the stored length, which corrupts the value and can break widgets, theme options, and plugins. For a site-wide URL change, use a proper search-replace tool that understands serialization (WP-CLI's search-replace command, or a trusted plugin such as Better Search Replace) rather than a raw UPDATE. Reserve the manual edit for the two or three unserialized wp_options rows only.
09. Repairing and Optimizing Tables
If a table reports itself as crashed or corrupt (you might see a "table marked as crashed" error on the site), phpMyAdmin can repair it, and it can reclaim space from tables with a lot of churn.
- Click the database in the left panel to see its list of tables in the main area.
- Tick the checkbox next to the affected table (or use Check all for the whole database).
- From the With selected dropdown at the bottom, choose Repair table to fix a corrupted table, or Optimize table to defragment and reclaim space.
- You can also do this per table from that table's Operations tab, under Table maintenance.
Repair fixes most MyISAM corruption. InnoDB tables (the modern default) rarely corrupt and are not repaired the same way, so if an InnoDB table is throwing errors, or repair does not clear the problem, open a ticket and we will look at it from the server side.
10. Privileges and Safety Tips
You will notice phpMyAdmin has a Privileges tab and a Users area. On shared hosting you almost never use them. Database users and their permissions are managed for you in cPanel > MySQL Databases, which is where you create a user, set its password, and attach it to a database. Doing it there keeps cPanel and the database in sync. Managing users directly in phpMyAdmin can leave cPanel out of step and is usually blocked anyway. See How to Add a User to a Database for the correct place to do this.
A few habits keep database work uneventful:
- Back up first. Export the database (Section 06) before any UPDATE, DELETE, or import. Every time.
- One statement at a time. Run and check statements individually rather than pasting a wall of SQL and hoping.
- Always use a WHERE clause on UPDATE and DELETE, and confirm it with a SELECT first.
- Never run DROP (which deletes tables or databases outright) unless you are certain and you have a current export in hand.
If your site itself cannot reach the database (rather than a query failing inside phpMyAdmin), that is a connection problem, not a phpMyAdmin one. Start with Cannot Connect to MySQL, and if it is specifically the port, Cannot Connect on Port 3306 and What Port Is MariaDB or MySQL On.
Stuck on a Database Task?
Facing a large import, a corrupted table, or a query you would rather not run without a second pair of eyes, send us the details and we will handle it or walk you through it. We can also enable SSH for command-line imports and take a server-side backup before any risky change.
Open a Support TicketQuick Recap: phpMyAdmin in Six Steps
If you remember only six things from this guide, remember these:
- Open it from cPanel under Databases > phpMyAdmin, and note it only shows databases your user owns.
- Learn the layout: left panel for databases and tables, top tabs for Browse, SQL, Export, and Import.
- Edit single rows with Browse and the Edit pencil rather than SQL whenever you can.
- Export before every bulk change from Export > Quick > SQL, and gzip large databases.
- Never run UPDATE or DELETE without a WHERE clause, and confirm with a SELECT first.
- Use a serialization-aware tool for WordPress URL changes, and manage database users in cPanel, not phpMyAdmin.
Last updated July 2026 · Browse all PHP, MariaDB, and MySQL articles
