How to Create MySQL Database in Hostinger & Access Phpmyadmin Easily 2026

Log in to Hostinger and select the website you're working on to land on its Dashboard. This overview page shows tiles for Domain, Hosting, Free Email, and Backups near the top, and a second row further down with PageSpeed Insights, File manager, and Databases. The Databases tile is your entry point for everything in this guide: creating a new database, managing existing ones, and launching phpMyAdmin.

Click into Databases and choose the option to create a new one. Hostinger attaches your account's numeric prefix automatically, so a database you name pmnonline becomes something like u276259427_pmnonline.

The name you type becomes a suffix, and that prefix cannot be removed or changed later. Pick a name that describes what the database is for, since you'll reference the full prefixed name in your site's configuration file.

Alongside the database, create a MySQL user with its own username and password, then assign that user full permissions on the new database. The password needs at least 8 characters, with an uppercase letter, a lowercase letter, and a number, or Hostinger will reject it.

Each database can only have one user on shared and cloud hosting; a project needing several separate credentials on the same database would need a VPS plan instead. Keep the password somewhere secure, since Hostinger typically shows it only once, at creation.

For WordPress, enter the database name, username, password, and host (usually localhost) into wp-config.php during setup, or let the WordPress installer handle it if you're using Hostinger's one-click install. For a custom app, use the same four credentials in whatever connection string or environment file your framework expects. Use the full prefixed name Hostinger generated (u276259427_pmnonline, not just pmnonline) everywhere a database name is expected; a connection failure after setup is often just the short name sitting where the full one belongs.

From the Databases section, launch phpMyAdmin, which opens to a Structure view of whatever database is currently selected. By default this often lands on the internal information_schema database, showing dozens of system tables like COLUMNS, ENGINES, and EVENTS with their row counts, types, and collations. That's normal; information_schema is MySQL's built-in metadata database, not something you created.

In phpMyAdmin's left sidebar, click your actual database. It appears with the same prefixed name Hostinger generated, such as u276259427_pmnonline, sitting below information_schema in the list. Selecting it switches the Structure view to your own tables instead of MySQL's internal ones, which is where the real work of browsing rows, editing structure, and running queries happens.

Once inside your own database, use the Browse and Structure links per table to view or edit rows and columns, the SQL tab to run raw queries directly, and Import or Export at the top to move data in or out as a .sql file. This covers the everyday database management most WordPress and custom-app workflows need without leaving the browser.