Welcome to phpMyAdmin’s documentation!



phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as a single database. To accomplish the latter you’ll need a properly set up MySQL user who can read/write only the desired database. It’s up to you to look up the appropriate part in the MySQL manual.

Supported features

Currently phpMyAdmin can:

  • browse and drop databases, tables, views, columns and indexes
  • display multiple results sets through stored procedures or queries
  • create, copy, drop, rename and alter databases, tables, columns and indexes
  • maintenance server, databases and tables, with proposals on server configuration
  • execute, edit and bookmark any SQL-statement, even batch-queries
  • load text files into tables
  • create [1] and read dumps of tables
  • export [1] data to various formats: CSV, XML, PDF, ISO/IEC 26300 - OpenDocument Text and Spreadsheet, Microsoft Word 2000, and LATEX formats
  • import data and MySQL structures from OpenDocument spreadsheets, as well as XML, CSV, and SQL files
  • administer multiple servers
  • manage MySQL users and privileges
  • check referential integrity in MyISAM tables
  • using Query-by-example (QBE), create complex queries automatically connecting required tables
  • create PDF graphics of your database layout
  • search globally in a database or a subset of it
  • transform stored data into any format using a set of predefined functions, like displaying BLOB-data as image or download-link
  • track changes on databases, tables and views
  • support InnoDB tables and foreign keys
  • support mysqli, the improved MySQL extension see 1.17 Which Database versions does phpMyAdmin support?
  • create, edit, call, export and drop stored procedures and functions
  • create, edit, export and drop events and triggers
  • communicate in 80 different languages

Shortcut keys

Currently phpMyAdmin supports following shortcuts:

  • k - Toggle console
  • h - Go to home page
  • s - Open settings
  • d + s - Go to database structure (Provided you are in database related page)
  • d + f - Search database (Provided you are in database related page)
  • t + s - Go to table structure (Provided you are in table related page)
  • t + f - Search table (Provided you are in table related page)
  • backspace - Takes you to older page.

A word about users

Many people have difficulty understanding the concept of user management with regards to phpMyAdmin. When a user logs in to phpMyAdmin, that username and password are passed directly to MySQL. phpMyAdmin does no account management on its own (other than allowing one to manipulate the MySQL user account information); all users must be valid MySQL users.


[1](1, 2) phpMyAdmin can compress (Zip, GZip or RFC 1952 formats) dumps and CSV exports if you use PHP with Zlib support (--with-zlib). Proper support may also need changes in php.ini.


Web server

Since phpMyAdmin’s interface is based entirely in your browser, you’ll need a web server (such as Apache, nginx, IIS) to install phpMyAdmin’s files into.


  • You need PHP 5.5.0 or newer, with session support, the Standard PHP Library (SPL) extension, JSON support, and the mbstring extension (see mbstring).
  • To support uploading of ZIP files, you need the PHP zip extension.
  • You need GD2 support in PHP to display inline thumbnails of JPEGs (“image/jpeg: inline”) with their original aspect ratio.
  • When using the cookie authentication (the default), the openssl extension is strongly suggested.
  • To support upload progress bars, see 2.9 Seeing an upload progress bar.
  • To support XML and Open Document Spreadsheet importing, you need the libxml extension.
  • To support reCAPTCHA on the login page, you need the openssl extension.
  • To support displaying phpMyAdmin’s latest version, you need to enable allow_url_open in your php.ini or to have the curl extension.


phpMyAdmin supports MySQL-compatible databases.

  • MySQL 5.5 or newer
  • MariaDB 5.5 or newer

Web browser

To access phpMyAdmin you need a web browser with cookies and JavaScript enabled.

You need browser which is supported by jQuery 2.0, see <https://jquery.com/browser-support/>.


phpMyAdmin does not apply any special security methods to the MySQL database server. It is still the system administrator’s job to grant permissions on the MySQL databases properly. phpMyAdmin’s Users page can be used for this.


Mac users should note that if you are on a version before Mac OS X, StuffIt unstuffs with Mac formats. So you’ll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts before uploading them to your server, as PHP seems not to like Mac-style end of lines character (“\r”).

Linux distributions

phpMyAdmin is included in most Linux distributions. It is recommended to use distribution packages when possible - they usually provide integration to your distribution and you will automatically get security updates from your distribution.


Debian’s package repositories include a phpMyAdmin package, but be aware that the configuration file is maintained in /etc/phpmyadmin and may differ in some ways from the official phpMyAdmin documentation. Specifically it does:

See also

More information can be found in README.Debian (it is installed as /usr/share/doc/phmyadmin/README.Debian with the package).


OpenSUSE already comes with phpMyAdmin package, just install packages from the openSUSE Build Service.


Ubuntu ships phpMyAdmin package, however if you want to use recent version, you can use packages from phpMyAdmin PPA.

See also

The packages are same as in Debian please check the documentation there for more details.


Gentoo ships the phpMyAdmin package, both in a near stock configuration as well as in a webapp-config configuration. Use emerge dev-db/phpmyadmin to install.


Mandriva ships the phpMyAdmin package in their contrib branch and can be installed via the usual Control Center.


Fedora ships the phpMyAdmin package, but be aware that the configuration file is maintained in /etc/phpMyAdmin/ and may differ in some ways from the official phpMyAdmin documentation.

Red Hat Enterprise Linux

Red Hat Enterprise Linux itself and thus derivatives like CentOS don’t ship phpMyAdmin, but the Fedora-driven repository Extra Packages for Enterprise Linux (EPEL) is doing so, if it’s enabled. But be aware that the configuration file is maintained in /etc/phpMyAdmin/ and may differ in some ways from the official phpMyAdmin documentation.

Installing on Windows

The easiest way to get phpMyAdmin on Windows is using third party products which include phpMyAdmin together with a database and web server such as XAMPP.

You can find more of such options at Wikipedia.

Installing from Git

You can clone current phpMyAdmin source from https://github.com/phpmyadmin/phpmyadmin.git:

git clone https://github.com/phpmyadmin/phpmyadmin.git

Additionally you need to install dependencies using the Composer tool:

composer update

If you do not intend to develop, you can skip the installation of developer tools by invoking:

composer update --no-dev

Installing using Composer

You can install phpMyAdmin using the Composer tool, since 4.7.0 the releases are automatically mirrored to the default Packagist repository.


The content of the Composer repository is automatically generated separately from the releases, so the content doesn’t have to be 100% same as when you download the tarball. There should be no functional differences though.

To install phpMyAdmin simply run:

composer create-project phpmyadmin/phpmyadmin

Alternatively you can use our own composer repository, which contains the release tarballs and is available at <https://www.phpmyadmin.net/packages.json>:

composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev

Installing using Docker

phpMyAdmin comes with a Docker image, which you can easily deploy. You can download it using:

docker pull phpmyadmin/phpmyadmin

The phpMyAdmin server will listen on port 80. It supports several ways of configuring the link to the database server, either by Docker’s link feature by linking your database container to db for phpMyAdmin (by specifying --link your_db_host:db) or by environment variables (in this case it’s up to you to set up networking in Docker to allow the phpMyAdmin container to access the database container over network).

Docker environment variables

You can configure several phpMyAdmin features using environment variables:


Allows you to enter a database server hostname on login form.


Host name or IP address of the database server to use.


Comma-separated host names or IP addresses of the database servers to use.


Used only if PMA_HOST is empty.


Verbose name of the database server.


Comma-separated verbose name of the database servers.


Used only if PMA_VERBOSE is empty.


User name to use for Config authentication mode.


Password to use for Config authentication mode.


Port of the database server to use.


Comma-separated ports of the database server to use.


Used only if PMA_PORT is empty.


The fully-qualified path (https://pma.example.net/) where the reverse proxy makes phpMyAdmin available.

By default, Cookie authentication mode is used, but if PMA_USER and PMA_PASSWORD are set, it is switched to Config authentication mode.


The credentials you need to log in are stored in the MySQL server, in case of Docker image there are various ways to set it (for example MYSQL_ROOT_PASSWORD when starting the MySQL container). Please check documentation for MariaDB container or MySQL container.

Customizing configuration

Additionally configuration can be tweaked by /etc/phpmyadmin/config.user.inc.php. If this file exists, it will be loaded after configuration is generated from above environment variables, so you can override any configuration variable. This configuration can be added as a volume when invoking docker using -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php parameters.

Note that the supplied configuration file is applied after Docker environment variables, but you can override any of the values.

For example to change default behaviour of CSV export you can use following configuration file:

$cfg['Export']['csv_columns'] = true;

See also

See Configuration for detailed description of configuration options.

Docker Volumes

You can use following volumes to customize image behavior:


Can be used for additional settings, see previous chapter for more details.


Directory where PHP sessions are stored. You might want to share this for example when using Signon authentication mode.

Docker Examples

To connect phpMyAdmin to a given server use:

docker run --name myadmin -d -e PMA_HOST=dbhost -p 8080:80 phpmyadmin/phpmyadmin

To connect phpMyAdmin to more servers use:

docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin

To use arbitrary server option:

docker run --name myadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin/phpmyadmin

You can also link the database container using Docker:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin/phpmyadmin

Running with additional configuration:

docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php phpmyadmin/phpmyadmin

Using docker-compose

Alternatively you can also use docker-compose with the docker-compose.yml from <https://github.com/phpmyadmin/docker>. This will run phpMyAdmin with an arbitrary server - allowing you to specify MySQL/MariaDB server on login page.

docker-compose up -d

Customizing configuration file using docker-compose

You can use an external file to customize phpMyAdmin configuration and pass it using the volumes directive:

    image: phpmyadmin/phpmyadmin
    container_name: phpmyadmin
    restart: always
     - 8080:80
     - /sessions
     - ~/docker/phpmyadmin/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php

Running behind haproxy in a subdirectory

When you want to expose phpMyAdmin running in a Docker container in a subdirectory, you need to rewrite the request path in the server proxying the requests. For example using haproxy it can be done as:

frontend http
    bind *:80
    option forwardfor
    option http-server-close

    ### NETWORK restriction
    acl LOCALNET  src

    # /phpmyadmin
    acl phpmyadmin  path_dir /phpmyadmin
    use_backend phpmyadmin if phpmyadmin LOCALNET

backend phpmyadmin
    mode http

    reqirep  ^(GET|POST|HEAD)\ /phpmyadmin/(.*)     \1\ /\2

    # phpMyAdmin container IP
    server localhost

You then should specify PMA_ABSOLUTE_URI in the docker-compose configuration:

version: '2'

    restart: always
    image: phpmyadmin/phpmyadmin
    container_name: phpmyadmin
    hostname: phpmyadmin
    domainname: example.com
      - 8000:80
      - PMA_HOSTS=,,,
      - PMA_VERBOSES=production-db1,production-db2,dev-db1,dev-db2
      - PMA_USER=root
      - PMA_ABSOLUTE_URI=http://example.com/phpmyadmin/

Quick Install

  1. Choose an appropriate distribution kit from the phpmyadmin.net Downloads page. Some kits contain only the English messages, others contain all languages. We’ll assume you chose a kit whose name looks like phpMyAdmin-x.x.x -all-languages.tar.gz.
  2. Ensure you have downloaded a genuine archive, see Verifying phpMyAdmin releases.
  3. Untar or unzip the distribution (be sure to unzip the subdirectories): tar -xzvf phpMyAdmin_x.x.x-all-languages.tar.gz in your webserver’s document root. If you don’t have direct access to your document root, put the files in a directory on your local machine, and, after step 4, transfer the directory on your web server using, for example, ftp.
  4. Ensure that all the scripts have the appropriate owner (if PHP is running in safe mode, having some scripts with an owner different from the owner of other scripts will be a problem). See 4.2 What’s the preferred way of making phpMyAdmin secure against evil access? and 1.26 I just installed phpMyAdmin in my document root of IIS but I get the error “No input file specified” when trying to run phpMyAdmin. for suggestions.
  5. Now you must configure your installation. There are two methods that can be used. Traditionally, users have hand-edited a copy of config.inc.php, but now a wizard-style setup script is provided for those who prefer a graphical installation. Creating a config.inc.php is still a quick way to get started and needed for some advanced features.

Manually creating the file

To manually create the file, simply use your text editor to create the file config.inc.php (you can copy config.sample.inc.php to get a minimal configuration file) in the main (top-level) phpMyAdmin directory (the one that contains index.php). phpMyAdmin first loads libraries/config.default.php and then overrides those values with anything found in config.inc.php. If the default value is okay for a particular setting, there is no need to include it in config.inc.php. You’ll probably need only a few directives to get going; a simple configuration may look like this:

// use here a value of your choice at least 32 chars long
$cfg['blowfish_secret'] = '1{dd0`<Q),5XP_:R9UK%%8\"EEcyH#{o';

$cfg['Servers'][$i]['auth_type']     = 'cookie';
// if you insist on "root" having no password:
// $cfg['Servers'][$i]['AllowNoPassword'] = true; `

Or, if you prefer to not be prompted every time you log in:


$cfg['Servers'][$i]['user']          = 'root';
$cfg['Servers'][$i]['password']      = 'cbb74bc'; // use here your password
$cfg['Servers'][$i]['auth_type']     = 'config';


Storing passwords in the configuration is insecure as anybody can then manipulate with your database.

For a full explanation of possible configuration values, see the Configuration of this document.

Using Setup script

Instead of manually editing config.inc.php, you can use phpMyAdmin’s setup feature. The file can be generated using the setup and you can download it for upload to the server.

Next, open your browser and visit the location where you installed phpMyAdmin, with the /setup suffix. The changes are not saved to the server, you need to use the Download button to save them to your computer and then upload to the server.

Now the file is ready to be used. You can choose to review or edit the file with your favorite editor, if you prefer to set some advanced options which the setup script does not provide.

  1. If you are using the auth_type “config”, it is suggested that you protect the phpMyAdmin installation directory because using config does not require a user to enter a password to access the phpMyAdmin installation. Use of an alternate authentication method is recommended, for example with HTTP–AUTH in a .htaccess file or switch to using auth_type cookie or http. See the ISPs, multi-user installations for additional information, especially 4.4 phpMyAdmin always gives “Access denied” when using HTTP authentication..
  2. Open the main phpMyAdmin directory in your browser. phpMyAdmin should now display a welcome screen and your databases, or a login dialog if using HTTP or cookie authentication mode.
Setup script on Debian, Ubuntu and derivatives

Debian and Ubuntu have changed way how setup is enabled and disabled, in a way that single command has to be executed for either of these.

To allow editing configuration invoke:


To block editing configuration invoke:

Setup script on openSUSE

Some openSUSE releases do not include setup script in the package. In case you want to generate configuration on these you can either download original package from <https://www.phpmyadmin.net/> or use setup script on our demo server: <https://demo.phpmyadmin.net/STABLE/setup/>.

Verifying phpMyAdmin releases

Since July 2015 all phpMyAdmin releases are cryptographically signed by the releasing developer, who through January 2016 was Marc Delisle. His key id is 0xFEFC65D181AF644A, his PGP fingerprint is:

436F F188 4B1A 0C3F DCBF 0D79 FEFC 65D1 81AF 644A

and you can get more identification information from <https://keybase.io/lem9>.

Beginning in January 2016, the release manager is Isaac Bennetch. His key id is 0xCE752F178259BD92, and his PGP fingerprint is:

3D06 A59E CE73 0EB7 1B51 1C17 CE75 2F17 8259 BD92

and you can get more identification information from <https://keybase.io/ibennetch>.

Some additional downloads (for example themes) might be signed by Michal Čihař. His key id is 0x9C27B31342B7511D, and his PGP fingerprint is:

63CB 1DF1 EF12 CF2A C0EE 5A32 9C27 B313 42B7 511D

and you can get more identification information from <https://keybase.io/nijel>.

You should verify that the signature matches the archive you have downloaded. This way you can be sure that you are using the same code that was released. You should also verify the date of the signature to make sure that you downloaded the latest version.

Each archive is accompanied with .asc files which contains the PGP signature for it. Once you have both of them in the same folder, you can verify the signature:

$ gpg --verify phpMyAdmin-
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Can't check signature: public key not found

As you can see gpg complains that it does not know the public key. At this point you should do one of the following steps:

$ gpg --import phpmyadmin.keyring
  • Download and import the key from one of the key servers:
$ gpg --keyserver hkp://pgp.mit.edu --recv-keys 3D06A59ECE730EB71B511C17CE752F178259BD92
gpg: requesting key 8259BD92 from hkp server pgp.mit.edu
gpg: key 8259BD92: public key "Isaac Bennetch <bennetch@gmail.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

This will improve the situation a bit - at this point you can verify that the signature from the given key is correct but you still can not trust the name used in the key:

$ gpg --verify phpMyAdmin-
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Good signature from "Isaac Bennetch <bennetch@gmail.com>"
gpg:                 aka "Isaac Bennetch <isaac@bennetch.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 3D06 A59E CE73 0EB7 1B51  1C17 CE75 2F17 8259 BD92

The problem here is that anybody could issue the key with this name. You need to ensure that the key is actually owned by the mentioned person. The GNU Privacy Handbook covers this topic in the chapter Validating other keys on your public keyring. The most reliable method is to meet the developer in person and exchange key fingerprints, however you can also rely on the web of trust. This way you can trust the key transitively though signatures of others, who have met the developer in person. For example you can see how Isaac’s key links to Linus’s key.

Once the key is trusted, the warning will not occur:

$ gpg --verify phpMyAdmin-
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: Good signature from "Isaac Bennetch <bennetch@gmail.com>" [full]

Should the signature be invalid (the archive has been changed), you would get a clear error regardless of the fact that the key is trusted or not:

$ gpg --verify phpMyAdmin-
gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92
gpg: BAD signature from "Isaac Bennetch <bennetch@gmail.com>" [unknown]

phpMyAdmin configuration storage

Changed in version 3.4.0: Prior to phpMyAdmin 3.4.0 this was called Linked Tables Infrastructure, but the name was changed due to extended scope of the storage.

For a whole set of additional features (Bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, Transformations, Relations etc.) you need to create a set of special tables. Those tables can be located in your own database, or in a central database for a multi-user installation (this database would then be accessed by the controluser, so no other user should have rights to it).

Zero configuration

In many cases, this database structure can be automatically created and configured. This is called “Zero Configuration” mode and can be particularly useful in shared hosting situations. “Zeroconf” mode is on by default, to disable set $cfg['ZeroConf'] to false.

The following three scenarios are covered by the Zero Configuration mode:

  • When entering a database where the configuration storage tables are not present, phpMyAdmin offers to create them from the Operations tab.
  • When entering a database where the tables do already exist, the software automatically detects this and begins using them. This is the most common situation; after the tables are initially created automatically they are continually used without disturbing the user; this is also most useful on shared hosting where the user is not able to edit config.inc.php and usually the user only has access to one database.
  • When having access to multiple databases, if the user first enters the database containing the configuration storage tables then switches to another database, phpMyAdmin continues to use the tables from the first database; the user is not prompted to create more tables in the new database.

Manual configuration

Please look at your ./sql/ directory, where you should find a file called create_tables.sql. (If you are using a Windows server, pay special attention to 1.23 I’m running MySQL on a Win32 machine. Each time I create a new table the table and column names are changed to lowercase!).

If you already had this infrastructure and:

  • upgraded to MySQL 4.1.2 or newer, please use sql/upgrade_tables_mysql_4_1_2+.sql.
  • upgraded to phpMyAdmin 4.3.0 or newer from 2.5.0 or newer (<= 4.2.x), please use sql/upgrade_column_info_4_3_0+.sql.
  • upgraded to phpMyAdmin 4.7.0 or newer from 4.3.0 or newer, please use sql/upgrade_tables_4_7_0+.sql.

and then create new tables by importing sql/create_tables.sql.

You can use your phpMyAdmin to create the tables for you. Please be aware that you may need special (administrator) privileges to create the database and tables, and that the script may need some tuning, depending on the database name.

After having imported the sql/create_tables.sql file, you should specify the table names in your config.inc.php file. The directives used for that can be found in the Configuration.

You will also need to have a controluser ($cfg['Servers'][$i]['controluser'] and $cfg['Servers'][$i]['controlpass'] settings) with the proper rights to those tables. For example you can create it using following statement:

GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost'  IDENTIFIED BY 'pmapass';

Upgrading from an older version


Never extract the new version over an existing installation of phpMyAdmin, always first remove the old files keeping just the configuration.

This way you will not leave old no longer working code in the directory, which can have severe security implications or can cause various breakages.

Simply copy config.inc.php from your previous installation into the newly unpacked one. Configuration files from old versions may require some tweaking as some options have been changed or removed. For compatibility with PHP 5.3 and later, remove a set_magic_quotes_runtime(0); statement that you might find near the end of your configuration file.

You should not copy libraries/config.default.php over config.inc.php because the default configuration file is version- specific.

The complete upgrade can be performed in few simple steps:

  1. Download the latest phpMyAdmin version from <https://www.phpmyadmin.net/downloads/>.
  2. Rename existing phpMyAdmin folder (for example to phpmyadmin-old).
  3. Unpack freshly donwloaded phpMyAdmin to desired location (for example phpmyadmin).
  4. Copy config.inc.php` from old location (phpmyadmin-old) to new one (phpmyadmin).
  5. Test that everything works properly.
  6. Remove backup of previous version (phpmyadmin-old).

If you have upgraded your MySQL server from a version previous to 4.1.2 to version 5.x or newer and if you use the phpMyAdmin configuration storage, you should run the SQL script found in sql/upgrade_tables_mysql_4_1_2+.sql.

If you have upgraded your phpMyAdmin to 4.3.0 or newer from 2.5.0 or newer (<= 4.2.x) and if you use the phpMyAdmin configuration storage, you should run the SQL script found in sql/upgrade_column_info_4_3_0+.sql.

Do not forget to clear the browser cache and to empty the old session by logging out and logging in again.

Using authentication modes

HTTP and cookie authentication modes are recommended in a multi-user environment where you want to give users access to their own database and don’t want them to play around with others. Nevertheless be aware that MS Internet Explorer seems to be really buggy about cookies, at least till version 6. Even in a single-user environment, you might prefer to use HTTP or cookie mode so that your user/password pair are not in clear in the configuration file.

HTTP and cookie authentication modes are more secure: the MySQL login information does not need to be set in the phpMyAdmin configuration file (except possibly for the $cfg['Servers'][$i]['controluser']). However, keep in mind that the password travels in plain text, unless you are using the HTTPS protocol. In cookie mode, the password is stored, encrypted with the AES algorithm, in a temporary cookie.

Then each of the true users should be granted a set of privileges on a set of particular databases. Normally you shouldn’t give global privileges to an ordinary user, unless you understand the impact of those privileges (for example, you are creating a superuser). For example, to grant the user real_user with all privileges on the database user_base:

GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';

What the user may now do is controlled entirely by the MySQL user management system. With HTTP or cookie authentication mode, you don’t need to fill the user/password fields inside the $cfg['Servers'].

HTTP authentication mode


There is no way to do proper logout in HTTP authentication, most browsers will remember credentials until there is no different successful authentication. Because of this this method has limitation that you can not login with same user after logout.

Signon authentication mode

The very basic example of saving credentials in a session is available as examples/signon.php:

/* vim: set expandtab sw=4 ts=4 sts=4: */
 * Single signon for phpMyAdmin
 * This is just example how to use session based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.
 * @package    PhpMyAdmin
 * @subpackage Example

/* Need to have cookie visible from parent directory */
session_set_cookie_params(0, '/', '', true, true);
/* Create signon session */
$session_name = 'SignonSession';
// Uncomment and change the following line to match your $cfg['SessionSavePath']

/* Was data posted? */
if (isset($_POST['user'])) {
    /* Store there credentials */
    $_SESSION['PMA_single_signon_user'] = $_POST['user'];
    $_SESSION['PMA_single_signon_password'] = $_POST['password'];
    $_SESSION['PMA_single_signon_host'] = $_POST['host'];
    $_SESSION['PMA_single_signon_port'] = $_POST['port'];
    /* Update another field of server configuration */
    $_SESSION['PMA_single_signon_cfgupdate'] = array('verbose' => 'Signon test');
    $id = session_id();
    /* Close that session */
    /* Redirect to phpMyAdmin (should use absolute URL here!) */
    header('Location: ../index.php');
} else {
    /* Show simple form */
    header('Content-Type: text/html; charset=utf-8');
    echo '<?xml version="1.0" encoding="utf-8"?>' , "\n";
    <html lang="en" dir="ltr">
    <link rel="icon" href="../favicon.ico" type="image/x-icon" />
    <link rel="shortcut icon" href="../favicon.ico" type="image/x-icon" />
    <meta charset="utf-8" />
    <title>phpMyAdmin single signon example</title>
    if (isset($_SESSION['PMA_single_signon_error_message'])) {
        echo '<p class="error">';
        echo $_SESSION['PMA_single_signon_error_message'];
        echo '</p>';
    <form action="signon.php" method="post">
    Username: <input type="text" name="user" /><br />
    Password: <input type="password" name="password" /><br />
    Host: (will use the one from config.inc.php by default)
    <input type="text" name="host" /><br />
    Port: (will use the one from config.inc.php by default)
    <input type="text" name="port" /><br />
    <input type="submit" />

Alternatively you can also use this way to integrate with OpenID as shown in examples/openid.php:

/* vim: set expandtab sw=4 ts=4 sts=4: */
 * Single signon for phpMyAdmin using OpenID
 * This is just example how to use single signon with phpMyAdmin, it is
 * not intended to be perfect code and look, only shows how you can
 * integrate this functionality in your application.
 * It uses OpenID pear package, see https://pear.php.net/package/OpenID
 * User first authenticates using OpenID and based on content of $AUTH_MAP
 * the login information is passed to phpMyAdmin in session data.
 * @package    PhpMyAdmin
 * @subpackage Example

if (false === @include_once 'OpenID/RelyingParty.php') {

 * Map of authenticated users to MySQL user/password pairs.
$AUTH_MAP = array(
    'https://launchpad.net/~username' => array(
        'user' => 'root',
        'password' => '',

 * Simple function to show HTML page with given content.
 * @param string $contents Content to include in page
 * @return void
function Show_page($contents)
    header('Content-Type: text/html; charset=utf-8');
    echo '<?xml version="1.0" encoding="utf-8"?>' , "\n";
    <html lang="en" dir="ltr">
    <link rel="icon" href="../favicon.ico" type="image/x-icon" />
    <link rel="shortcut icon" href="../favicon.ico" type="image/x-icon" />
    <meta charset="utf-8" />
    <title>phpMyAdmin OpenID signon example</title>
    if (isset($_SESSION) && isset($_SESSION['PMA_single_signon_error_message'])) {
        echo '<p class="error">' , $_SESSION['PMA_single_signon_message'] , '</p>';
    echo $contents;

function Die_error($e)
    $contents = "<div class='relyingparty_results'>\n";
    $contents .= "<pre>" . htmlspecialchars($e->getMessage()) . "</pre>\n";
    $contents .= "</div class='relyingparty_results'>";

/* Need to have cookie visible from parent directory */
session_set_cookie_params(0, '/', '', true, true);
/* Create signon session */
$session_name = 'SignonSession';

// Determine realm and return_to
$base = 'http';
if (isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] == 'on') {
    $base .= 's';
$base .= '://' . $_SERVER['SERVER_NAME'] . ':' . $_SERVER['SERVER_PORT'];

$realm = $base . '/';
$returnTo = $base . dirname($_SERVER['PHP_SELF']);
if ($returnTo[strlen($returnTo) - 1] != '/') {
    $returnTo .= '/';
$returnTo .= 'openid.php';

/* Display form */
if (!count($_GET) && !count($_POST) || isset($_GET['phpMyAdmin'])) {
    /* Show simple form */
    $content = '<form action="openid.php" method="post">
OpenID: <input type="text" name="identifier" /><br />
<input type="submit" name="start" />

/* Grab identifier */
if (isset($_POST['identifier']) && is_string($_POST['identifier'])) {
    $identifier = $_POST['identifier'];
} else if (isset($_SESSION['identifier']) && is_string($_SESSION['identifier'])) {
    $identifier = $_SESSION['identifier'];
} else {
    $identifier = null;

/* Create OpenID object */
try {
    $o = new OpenID_RelyingParty($returnTo, $realm, $identifier);
} catch (Exception $e) {

/* Redirect to OpenID provider */
if (isset($_POST['start'])) {
    try {
        $authRequest = $o->prepare();
    } catch (Exception $e) {

    $url = $authRequest->getAuthorizeURL();

    header("Location: $url");
} else {
    /* Grab query string */
    if (!count($_POST)) {
        list(, $queryString) = explode('?', $_SERVER['REQUEST_URI']);
    } else {
        // I hate php sometimes
        $queryString = file_get_contents('php://input');

    /* Check reply */
    try {
        $message = new OpenID_Message($queryString, OpenID_Message::FORMAT_HTTP);
    } catch (Exception $e) {

    $id = $message->get('openid.claimed_id');

    if (!empty($id) && isset($AUTH_MAP[$id])) {
        $_SESSION['PMA_single_signon_user'] = $AUTH_MAP[$id]['user'];
        $_SESSION['PMA_single_signon_password'] = $AUTH_MAP[$id]['password'];
        /* Redirect to phpMyAdmin (should use absolute URL here!) */
        header('Location: ../index.php');
    } else {
        Show_page('<p>User not allowed!</p>');

If you intend to pass the credentials using some other means than, you have to implement wrapper in PHP to get that data and set it to $cfg['Servers'][$i]['SignonScript']. There is very minimal example in examples/signon-script.php:

/* vim: set expandtab sw=4 ts=4 sts=4: */
 * Single signon for phpMyAdmin
 * This is just example how to use script based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.
 * @package    PhpMyAdmin
 * @subpackage Example

 * This function returns username and password.
 * It can optionally use configured username as parameter.
 * @param string $user User name
 * @return array
function get_login_credentials($user)
    /* Optionally we can use passed username */
    if (!empty($user)) {
        return array($user, 'password');

    /* Here we would retrieve the credentials */
    $credentials = array('root', '');

    return $credentials;

Config authentication mode

  • This mode is sometimes the less secure one because it requires you to fill the $cfg['Servers'][$i]['user'] and $cfg['Servers'][$i]['password'] fields (and as a result, anyone who can read your config.inc.php can discover your username and password).
  • In the ISPs, multi-user installations section, there is an entry explaining how to protect your configuration file.
  • For additional security in this mode, you may wish to consider the Host authentication $cfg['Servers'][$i]['AllowDeny']['order'] and $cfg['Servers'][$i]['AllowDeny']['rules'] configuration directives.
  • Unlike cookie and http, does not require a user to log in when first loading the phpMyAdmin site. This is by design but could allow any user to access your installation. Use of some restriction method is suggested, perhaps a .htaccess file with the HTTP-AUTH directive or disallowing incoming HTTP requests at one’s router or firewall will suffice (both of which are beyond the scope of this manual but easily searchable with Google).

Securing your phpMyAdmin installation

The phpMyAdmin team tries hard to make the application secure, however there are always ways to make your installation more secure:

  • Follow our Security announcements and upgrade phpMyAdmin whenever new vulnerability is published.

  • Serve phpMyAdmin on HTTPS only. Preferably, you should use HSTS as well, so that you’re protected from protocol downgrade attacks.

  • Ensure your PHP setup follows recommendations for production sites, for example display_errors should be disabled.

  • Remove the test directory from phpMyAdmin, unless you are developing and need test suite.

  • Remove the setup directory from phpMyAdmin, you will probably not use it after the initial setup.

  • Properly choose an authentication method - Cookie authentication mode is probably the best choice for shared hosting.

  • Deny access to auxiliary files in ./libraries/ or ./templates/ subfolders in your webserver configuration. Such configuration prevents from possible path exposure and cross side scripting vulnerabilities that might happen to be found in that code. For the Apache webserver, this is often accomplished with a .htaccess file in those directories.

  • It is generally a good idea to protect a public phpMyAdmin installation against access by robots as they usually can not do anything good there. You can do this using robots.txt file in root of your webserver or limit access by web server configuration, see 1.42 How can I prevent robots from accessing phpMyAdmin?.

  • In case you don’t want all MySQL users to be able to access phpMyAdmin, you can use $cfg['Servers'][$i]['AllowDeny']['rules'] to limit them or $cfg['Servers'][$i]['AllowRoot'] to deny root user access.

  • Consider hiding phpMyAdmin behind an authentication proxy, so that users need to authenticate prior to providing MySQL credentials to phpMyAdmin. You can achieve this by configuring your web server to request HTTP authentication. For example in Apache this can be done with:

    AuthType Basic
    AuthName "Restricted Access"
    AuthUserFile /usr/share/phpmyadmin/passwd
    Require valid-user

    Once you have changed the configuration, you need to create a list of users which can authenticate. This can be done using the htpasswd utility:

    htpasswd -c /usr/share/phpmyadmin/passwd username
  • If you are afraid of automated attacks, enabling Captcha by $cfg['CaptchaLoginPublicKey'] and $cfg['CaptchaLoginPrivateKey'] might be an option.

  • Failed login attemps are logged to syslog (if available). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or access log files.

Known issues

Users with column-specific privileges are unable to “Browse”

If a user has only column-specific privileges on some (but not all) columns in a table, “Browse” will fail with an error message.

As a workaround, a bookmarked query with the same name as the table can be created, this will run when using the “Browse” link instead. Issue 11922.

Trouble logging back in after logging out using ‘http’ authentication

When using the ‘http’ auth_type, it can be impossible to log back in (when the logout comes manually or after a period of inactivity). Issue 11898.


All configurable data is placed in config.inc.php in phpMyAdmin’s toplevel directory. If this file does not exist, please refer to the Installation section to create one. This file only needs to contain the parameters you want to change from their corresponding default value in libraries/config.default.php (this file is not inteded for changes).

See also

Examples for examples of configurations

If a directive is missing from your file, you can just add another line with the file. This file is for over-writing the defaults; if you wish to use the default value there’s no need to add a line here.

The parameters which relate to design (like colors) are placed in themes/themename/layout.inc.php. You might also want to create config.footer.inc.php and config.header.inc.php files to add your site specific code to be included on start and end of each page.


Some distributions (eg. Debian or Ubuntu) store config.inc.php in /etc/phpmyadmin instead of within phpMyAdmin sources.


Mac users should note that if you are on a version before Mac OS X, PHP does not seem to like Mac end of lines character (\r). So ensure you choose the option that allows to use the *nix end of line character (\n) in your text editor before saving a script you have modified.

Basic settings

Default value:''

Changed in version 4.6.5: This setting was not available in phpMyAdmin 4.6.0 - 4.6.4.

Sets here the complete URL (with full path) to your phpMyAdmin installation’s directory. E.g. https://www.example.net/path_to_your_phpMyAdmin_directory/. Note also that the URL on most of web servers are case sensitive (even on Windows). Don’t forget the trailing slash at the end.

Starting with version 2.3.0, it is advisable to try leaving this blank. In most cases phpMyAdmin automatically detects the proper setting. Users of port forwarding or complex reverse proxy setup might need to set this.

A good test is to browse a table, edit a row and save it. There should be an error message if phpMyAdmin is having trouble auto–detecting the correct value. If you get an error that this must be set or if the autodetect code fails to detect your path, please post a bug report on our bug tracker so we can improve the code.

Default value:false

Starting with version 2.3.0 phpMyAdmin offers a lot of features to work with master / foreign – tables (see $cfg['Servers'][$i]['pmadb']).

If you tried to set this up and it does not work for you, have a look on the Structure page of one database where you would like to use it. You will find a link that will analyze why those features have been disabled.

If you do not want to use those features set this variable to true to stop this message from appearing.

Default value:false

A warning is displayed on the main page if Suhosin is detected.

You can set this parameter to true to stop this message from appearing.

Default value:false

A warning is displayed on the main page if the PHP parameter session.gc_maxlifetime is lower than cookie validity configured in phpMyAdmin.

You can set this parameter to true to stop this message from appearing.

Default value:false

Deprecated since version 4.7.0: This setting was removed as the warning has been removed as well.

A warning is displayed on the main page if there is a difference between the MySQL library and server version.

You can set this parameter to true to stop this message from appearing.

Default value:false

This warning is displayed on the Structure page of a table if one or more column names match with words which are MySQL reserved.

If you want to turn off this warning, you can set it to true and warning will no longer be displayed.

Default value:80

Show warning about incomplete translations on certain threshold.

Default value:'ask'

Sets the default behavior for JavaScript error reporting.

Whenever an error is detected in the JavaScript execution, an error report may be sent to the phpMyAdmin team if the user agrees.

The default setting of 'ask' will ask the user everytime there is a new error report. However you can set this parameter to 'always' to send error reports without asking for confirmation or you can set it to 'never' to never send error reports.

This directive is available both in the configuration file and in users preferences. If the person in charge of a multi-user installation prefers to disable this feature for all users, a value of 'never' should be set, and the $cfg['UserprefsDisallow'] directive should contain 'SendErrorReports' in one of its array values.

Default value:false

Setting this to true allows the user to execute queries by pressing Enter instead of Ctrl+Enter. A new line can be inserted by pressing Shift + Enter.

The behaviour of the console can be temporarily changed using console’s settings interface.

Default value:false

Setting this to true allows phpMyAdmin to be included inside a frame, and is a potential security hole allowing cross-frame scripting attacks or clickjacking.

Server connection settings

Default value:one server array with settings listed below

Since version 1.4.2, phpMyAdmin supports the administration of multiple MySQL servers. Therefore, a $cfg['Servers']-array has been added which contains the login information for the different servers. The first $cfg['Servers'][$i]['host'] contains the hostname of the first server, the second $cfg['Servers'][$i]['host'] the hostname of the second server, etc. In libraries/config.default.php, there is only one section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change).


The $cfg['Servers'] array starts with $cfg[‘Servers’][1]. Do not use $cfg[‘Servers’][0]. If you want more than one server, just copy following section (including $i incrementation) serveral times. There is no need to define full server array, just define values you need to change.

Default value:'localhost'

The hostname or IP address of your $i-th MySQL-server. E.g. localhost.

Possible values are:

  • hostname, e.g., 'localhost' or 'mydb.example.org'
  • IP address, e.g., '' or ''
  • IPv6 address, e.g. 2001:cdba:0000:0000:0000:0000:3257:9652
  • dot - '.', i.e., use named pipes on windows systems
  • empty - '', disables this server


The hostname localhost is handled specially by MySQL and it uses the socket based connection protocol. To use TCP/IP networking, use an IP address or hostname such as or db.example.com. You can configure the path to the socket with $cfg['Servers'][$i]['socket'].

Default value:''

The port-number of your $i-th MySQL-server. Default is 3306 (leave blank).


If you use localhost as the hostname, MySQL ignores this port number and connects with the socket, so if you want to connect to a port different from the default port, use or the real hostname in $cfg['Servers'][$i]['host'].

Default value:''

The path to the socket to use. Leave blank for default. To determine the correct socket, check your MySQL configuration or, using the mysql command–line client, issue the status command. Among the resulting information displayed will be the socket used.


This takes effect only if $cfg['Servers'][$i]['host'] is set to localhost.

Default value:false

Whether to enable SSL for the connection between phpMyAdmin and the MySQL server to secure the connection.

When using the 'mysql' extension, none of the remaining 'ssl...' configuration options apply.

We strongly recommend the 'mysqli' extension when using this option.

Default value:NULL

Path to the key file when using SSL for connecting to the MySQL server.

For example:

$cfg['Servers'][$i]['ssl_key'] = '/etc/mysql/server-key.pem';
Default value:NULL

Path to the cert file when using SSL for connecting to the MySQL server.

Default value:NULL

Path to the CA file when using SSL for connecting to the MySQL server.

Default value:NULL

Directory containing trusted SSL CA certificates in PEM format.

Default value:NULL

List of allowable ciphers for SSL connections to the MySQL server.

Default value:true

New in version 4.6.0: This is supported since phpMyAdmin 4.6.0.

If your PHP install uses the MySQL Native Driver (mysqlnd), your MySQL server is 5.6 or later, and your SSL certificate is self-signed, there is a chance your SSL connection will fail due to validation. Setting this to false will disable the validation check.

Since PHP 5.6.0 it also verifies whether server name matches CN of its certificate. There is currently no way to disable just this check without disabling complete SSL verification.


Disabling the certificate verification defeats purpose of using SSL. This will make the connection vulnerable to man in the middle attacks.


This flag only works with PHP 5.6.16 or later.

Default value:'tcp'

Deprecated since version 4.7.0: This setting is no longer used as of 4.7.0, since MySQL decides the connection type based on host, so it could lead to unexpected results. Please set $cfg['Servers'][$i]['host'] accordingly instead.

What type connection to use with the MySQL server. Your options are 'socket' and 'tcp'. It defaults to tcp as that is nearly guaranteed to be available on all MySQL servers, while sockets are not supported on some platforms. To use the socket mode, your MySQL server must be on the same machine as the Web server.

Default value:false

Whether to use a compressed protocol for the MySQL server connection or not (experimental).

Default value:''

Permits to use an alternate host to hold the configuration storage data.

Default value:''

Permits to use an alternate port to connect to the host that holds the configuration storage.

Default value:''
Default value:''

This special account is used to access phpMyAdmin configuration storage. You don’t need it in single user case, but if phpMyAdmin is shared it is recommended to give access to phpMyAdmin configuration storage only to this user and configure phpMyAdmin to use it. All users will then be able to use the features without need to have direct access to phpMyAdmin configuration storage.

Changed in version 2.2.5: those were called stduser and stdpass


New in version 4.7.0.

You can change any MySQL connection setting for control link (used to access phpMyAdmin configuration storage) using configuration prefixed with control_.

This can be used to change any aspect of the control connection, which by default uses same parameters as the user one.

For example you can configure SSL for the control connection:

// Enable SSL
$cfg['Servers'][$i]['control_ssl'] = true;
// Client secret key
$cfg['Servers'][$i]['control_ssl_key'] = '../client-key.pem';
// Client certificate
$cfg['Servers'][$i]['control_ssl_cert'] = '../client-cert.pem';
// Server certification authority
$cfg['Servers'][$i]['control_ssl_ca'] = '../server-ca.pem';
Default value:'cookie'

Whether config or cookie or HTTP or signon authentication should be used for this server.

  • ‘config’ authentication ($auth_type = 'config') is the plain old way: username and password are stored in config.inc.php.
  • ‘cookie’ authentication mode ($auth_type = 'cookie') allows you to log in as any valid MySQL user with the help of cookies.
  • ‘http’ authentication allows you to log in as any valid MySQL user via HTTP-Auth.
  • ‘signon’ authentication mode ($auth_type = 'signon') allows you to log in from prepared PHP session data or using supplied PHP script.
Default value:''

When using auth_type = http, this field allows to define a custom HTTP Basic Auth Realm which will be displayed to the user. If not explicitly specified in your configuration, a string combined of “phpMyAdmin ” and either $cfg['Servers'][$i]['verbose'] or $cfg['Servers'][$i]['host'] will be used.

Default value:'root'
Default value:''

When using $cfg['Servers'][$i]['auth_type'] set to ‘config’, this is the user/password-pair which phpMyAdmin will use to connect to the MySQL server. This user/password pair is not needed when HTTP or cookie authentication is used and should be empty.

Default value:false

Deprecated since version 4.7.0: This setting was removed as it can produce unexpected results.

Allow attempt to log in without password when a login with password fails. This can be used together with http authentication, when authentication is done some other way and phpMyAdmin gets user name from auth and uses empty password for connecting to MySQL. Password login is still tried first, but as fallback, no password method is tried.

Type:string or array
Default value:''

If set to a (an array of) database name(s), only this (these) database(s) will be shown to the user. Since phpMyAdmin 2.2.1, this/these database(s) name(s) may contain MySQL wildcards characters (“_” and “%”): if you want to use literal instances of these characters, escape them (I.E. use 'my\_db' and not 'my_db').

This setting is an efficient way to lower the server load since the latter does not need to send MySQL requests to build the available database list. But it does not replace the privileges rules of the MySQL database server. If set, it just means only these databases will be displayed but not that all other databases can’t be used.

An example of using more that one database:

$cfg['Servers'][$i]['only_db'] = array('db1', 'db2');

Changed in version 4.0.0: Previous versions permitted to specify the display order of the database names via this directive.

Default value:''

Regular expression for hiding some databases from unprivileged users. This only hides them from listing, but a user is still able to access them (using, for example, the SQL query area). To limit access, use the MySQL privilege system. For example, to hide all databases starting with the letter “a”, use

$cfg['Servers'][$i]['hide_db'] = '^a';

and to hide both “db1” and “db2” use

$cfg['Servers'][$i]['hide_db'] = '^(db1|db2)$';

More information on regular expressions can be found in the PCRE pattern syntax portion of the PHP reference manual.

Default value:''

Only useful when using phpMyAdmin with multiple server entries. If set, this string will be displayed instead of the hostname in the pull-down menu on the main page. This can be useful if you want to show only certain databases on your system, for example. For HTTP auth, all non-US-ASCII characters will be stripped.

Default value:'mysqli'

The PHP MySQL extension to use (mysql or mysqli).

It is recommended to use mysqli in all installations.

Default value:''

The name of the database containing the phpMyAdmin configuration storage.

See the phpMyAdmin configuration storage section in this document to see the benefits of this feature, and for a quick way of creating this database and the needed tables.

If you are the only user of this phpMyAdmin installation, you can use your current database to store those special tables; in this case, just put your current database name in $cfg['Servers'][$i]['pmadb']. For a multi-user installation, set this parameter to the name of your central database containing the phpMyAdmin configuration storage.

Type:string or false
Default value:''

Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This can be useful for queries you often run. To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 2.2.4 you can describe, in a special ‘relation’ table, which column is a key in another table (a foreign key). phpMyAdmin currently uses this to:

The keys can be numeric or character.

To allow the usage of this functionality:

  • set up $cfg['Servers'][$i]['pmadb'] and the phpMyAdmin configuration storage
  • put the relation table name in $cfg['Servers'][$i]['relation']
  • now as normal user open phpMyAdmin and for each one of your tables where you want to use this feature, click Structure/Relation view/ and choose foreign columns.

This feature can be disabled by setting the configuration to false.


In the current version, master_db must be the same as foreign_db. Those columns have been put in future development of the cross-db relations.

Type:string or false
Default value:''

Since release 2.3.0 you can describe, in a special ‘table_info’ table, which column is to be displayed as a tool-tip when moving the cursor over the corresponding key. This configuration variable will hold the name of this special table. To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

The designer feature can save your page layout; by pressing the “Save page” or “Save page as” button in the expanding designer menu, you can customize the layout and have it loaded the next time you use the designer. That layout is stored in this table. Furthermore, this table is also required for using the PDF relation export feature, see $cfg['Servers'][$i]['pdf_pages'] for additional details.

Type:string or false
Default value:''

Since release 2.3.0 you can have phpMyAdmin create PDF pages showing the relations between your tables. Further, the designer interface permits visually managing the relations. To do this it needs two tables “pdf_pages” (storing information about the available PDF pages) and “table_coords” (storing coordinates where each table will be placed on a PDF schema output). You must be using the “relation” feature.

To allow the usage of this functionality:

This feature can be disabled by setting either of the configurations to false.

Type:string or false
Default value:''

This part requires a content update! Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the “printview”.

Starting with release 2.5.0, comments are consequently used on the table property pages and table browse view, showing up as tool-tips above the column name (properties page) or embedded within the header of table in browse view. They can also be shown in a table dump. Please see the relevant configuration directives later on.

Also new in release 2.5.0 is a MIME- transformation system which is also based on the following table structure. See Transformations for further information. To use the MIME- transformation system, your column_info table has to have the three new columns ‘mimetype’, ‘transformation’, ‘transformation_options’.

Starting with release 4.3.0, a new input-oriented transformation system has been introduced. Also, backward compatibility code used in the old transformations system was removed. As a result, an update to column_info table is necessary for previous transformations and the new input-oriented transformation system to work. phpMyAdmin will upgrade it automatically for you by analyzing your current column_info table structure. However, if something goes wrong with the auto-upgrade then you can use the SQL script found in ./sql/upgrade_column_info_4_3_0+.sql to upgrade it manually.

To allow the usage of this functionality:

  • set up $cfg['Servers'][$i]['pmadb'] and the phpMyAdmin configuration storage

  • put the table name in $cfg['Servers'][$i]['column_info'] (e.g. pma__column_info)

  • to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in config.inc.php has been renamed from $cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i]['column_info']

    ALTER TABLE `pma__column_comments`
    ADD `mimetype` VARCHAR( 255 ) NOT NULL,
    ADD `transformation` VARCHAR( 255 ) NOT NULL,
    ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
  • to update your PRE-4.3.0 Column_info table manually use this ./sql/upgrade_column_info_4_3_0+.sql SQL script.

This feature can be disabled by setting the configuration to false.


For auto-upgrade functionality to work, your $cfg['Servers'][$i]['controluser'] must have ALTER privilege on phpmyadmin database. See the MySQL documentation for GRANT on how to GRANT privileges to a user.

Type:string or false
Default value:''

Since release 2.5.0 you can store your SQL history, which means all queries you entered manually into the phpMyAdmin interface. If you don’t want to use a table-based history, you can use the JavaScript-based history.

Using that, all your history items are deleted when closing the window. Using $cfg['QueryHistoryMax'] you can specify an amount of history items you want to have on hold. On every login, this list gets cut to the maximum amount.

The query history is only available if JavaScript is enabled in your browser.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 3.5.0 you can show recently used tables in the navigation panel. It helps you to jump across table directly, without the need to select the database, and then select the table. Using $cfg['NumRecentTables'] you can configure the maximum number of recent tables shown. When you select a table from the list, it will jump to the page specified in $cfg['NavigationTreeDefaultTabTable'].

Without configuring the storage, you can still access the recently used tables, but it will disappear after you logout.

To allow the usage of this functionality persistently:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 4.2.0 you can show a list of selected tables in the navigation panel. It helps you to jump to the table directly, without the need to select the database, and then select the table. When you select a table from the list, it will jump to the page specified in $cfg['NavigationTreeDefaultTabTable'].

You can add tables to this list or remove tables from it in database structure page by clicking on the star icons next to table names. Using $cfg['NumFavoriteTables'] you can configure the maximum number of favorite tables shown.

Without configuring the storage, you can still access the favorite tables, but it will disappear after you logout.

To allow the usage of this functionality persistently:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 3.5.0 phpMyAdmin can be configured to remember several things (sorted column $cfg['RememberSorting'], column order, and column visibility from a database table) for browsing tables. Without configuring the storage, these features still can be used, but the values will disappear after you logout.

To allow the usage of these functionality persistently:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''
Type:string or false
Default value:''

Since release 4.1.0 you can create different user groups with menu items attached to them. Users can be assigned to these groups and the logged in user would only see menu items configured to the usergroup he is assigned to. To do this it needs two tables “usergroups” (storing allowed menu items for each user group) and “users” (storing users and their assignments to user groups).

To allow the usage of this functionality:

This feature can be disabled by setting either of the configurations to false.

Type:string or false
Default value:''

Since release 4.1.0 you can hide/show items in the navigation tree.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 4.3.0 you can have a central list of columns per database. You can add/remove columns to the list as per your requirement. These columns in the central list will be available to use while you create a new column for a table or create a table itself. You can select a column from central list while creating a new column, it will save you from writing the same column definition over again or from writing different names for similar column.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 4.5.0 your designer settings can be remembered. Your choice regarding ‘Angular/Direct Links’, ‘Snap to Grid’, ‘Toggle Relation Lines’, ‘Small/Big All’, ‘Move Menu’ and ‘Pin Text’ can be remembered persistently.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 4.2.0 you can save and load query-by-example searches from the Database > Query panel.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 4.5.0 you can save and load export templates.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Type:string or false
Default value:''

Since release 3.3.x a tracking mechanism is available. It helps you to track every SQL command which is executed by phpMyAdmin. The mechanism supports logging of data manipulation and data definition statements. After enabling it you can create versions of tables.

The creation of a version has two effects:

  • phpMyAdmin saves a snapshot of the table, including structure and indexes.
  • phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.

Of course you can view the tracked changes. On the Tracking page a complete report is available for every version. For the report you can use filters, for example you can get a list of statements within a date range. When you want to filter usernames you can enter * for all names or you enter a list of names separated by ‘,’. In addition you can export the (filtered) report to a file or to a temporary database.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Default value:false

Whether the tracking mechanism creates versions for tables and views automatically.

If this is set to true and you create a table or view with


and no version exists for it, the mechanism will create a version for you automatically.


Defines the list of statements the auto-creation uses for new versions.

Default value:true

Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view.

Default value:true

Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table.

Default value:true

Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database.

Type:string or false
Default value:''

Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves and store them in the database.

If you don’t allow for storing preferences in $cfg['Servers'][$i]['pmadb'], users can still personalize phpMyAdmin, but settings will be saved in browser’s local storage, or, it is is unavailable, until the end of session.

To allow the usage of this functionality:

This feature can be disabled by setting the configuration to false.

Default value:100

Maximum number of rows saved in $cfg['Servers'][$i]['table_uiprefs'] table.

When tables are dropped or renamed, $cfg['Servers'][$i]['table_uiprefs'] may contain invalid data (referring to tables which no longer exist). We only keep this number of newest rows in $cfg['Servers'][$i]['table_uiprefs'] and automatically delete older rows.

Default value:''

Sets the time zone used by phpMyAdmin. Leave blank to use the time zone of your database server. Possible values are explained at https://dev.mysql.com/doc/refman/5.7/en/time-zone-support.html

This is useful when your database server uses a time zone which is different from the time zone you want to use in phpMyAdmin.

Default value:true

Whether to allow root access. This is just a shortcut for the $cfg['Servers'][$i]['AllowDeny']['rules'] below.

Default value:false

Whether to allow logins without a password. The default value of false for this parameter prevents unintended access to a MySQL server with was left with an empty password for root or on which an anonymous (blank) user is defined.

Default value:''

If your rule order is empty, then IP authorization is disabled.

If your rule order is set to 'deny,allow' then the system applies all deny rules followed by allow rules. Access is allowed by default. Any client which does not match a Deny command or does match an Allow command will be allowed access to the server.

If your rule order is set to 'allow,deny' then the system applies all allow rules followed by deny rules. Access is denied by default. Any client which does not match an Allow directive or does match a Deny directive will be denied access to the server.

If your rule order is set to 'explicit', authorization is performed in a similar fashion to rule order ‘deny,allow’, with the added restriction that your host/username combination must be listed in the allow rules, and not listed in the deny rules. This is the most secure means of using Allow/Deny rules, and was available in Apache by specifying allow and deny rules without setting any order.

Please also see $cfg['TrustedProxies'] for detecting IP address behind proxies.

Type:array of strings
Default value:array()

The general format for the rules is as such:

<'allow' | 'deny'> <username> [from] <ipmask>

If you wish to match all users, it is possible to use a '%' as a wildcard in the username field.

There are a few shortcuts you can use in the ipmask field as well (please note that those containing SERVER_ADDRESS might not be available on all webservers):

'all' ->
'localhost' ->
'localnetA' -> SERVER_ADDRESS/8
'localnetB' -> SERVER_ADDRESS/16
'localnetC' -> SERVER_ADDRESS/24

Having an empty rule list is equivalent to either using 'allow % from all' if your rule order is set to 'deny,allow' or 'deny % from all' if your rule order is set to 'allow,deny' or 'explicit'.

For the IP address matching system, the following work:

  • xxx.xxx.xxx.xxx (an exact IP address)
  • xxx.xxx.xxx.[yyy-zzz] (an IP address range)
  • xxx.xxx.xxx.xxx/nn (CIDR, Classless Inter-Domain Routing type IP addresses)

But the following does not work:

  • xxx.xxx.xxx.xx[yyy-zzz] (partial IP address range)

For IPv6 addresses, the following work:

  • xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (an exact IPv6 address)
  • xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:[yyyy-zzzz] (an IPv6 address range)
  • xxxx:xxxx:xxxx:xxxx/nn (CIDR, Classless Inter-Domain Routing type IPv6 addresses)

But the following does not work:

  • xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xx[yyy-zzz] (partial IPv6 address range)
Default value:false

Disable using INFORMATION_SCHEMA to retrieve information (use SHOW commands instead), because of speed issues when many databases are present.


Enabling this option might give you big performance boost on older MySQL servers.

Default value:''

New in version 3.5.0.

Name of PHP script to be sourced and executed to obtain login credentials. This is alternative approach to session based single signon. The script has to provide a function called get_login_credentials which returns list of username and password, accepting single parameter of existing username (can be empty). See examples/signon-script.php for an example:

/* vim: set expandtab sw=4 ts=4 sts=4: */
 * Single signon for phpMyAdmin
 * This is just example how to use script based single signon with
 * phpMyAdmin, it is not intended to be perfect code and look, only
 * shows how you can integrate this functionality in your application.
 * @package    PhpMyAdmin
 * @subpackage Example

 * This function returns username and password.
 * It can optionally use configured username as parameter.
 * @param string $user User name
 * @return array
function get_login_credentials($user)
    /* Optionally we can use passed username */
    if (!empty($user)) {
        return array($user, 'password');

    /* Here we would retrieve the credentials */
    $credentials = array('root', '');

    return $credentials;
Default value:''

Name of session which will be used for signon authentication method. You should use something different than phpMyAdmin, because this is session which phpMyAdmin uses internally. Takes effect only if $cfg['Servers'][$i]['SignonScript'] is not configured.

Default value:array()

New in version 4.7.0.

An associative array of session cookie parameters of other authentication system. It is not needed if the other system doesn’t use session_set_cookie_params(). Keys should include ‘lifetime’, ‘path’, ‘domain’, ‘secure’ or ‘httponly’. Valid values are mentioned in session_get_cookie_params, they should be set to same values as the other application uses. Takes effect only if $cfg['Servers'][$i]['SignonScript'] is not configured.

Default value:''

URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.

Default value:''

URL where user will be redirected after logout (doesn’t affect config authentication method). Should be absolute including protocol.

Generic settings

Default value:false

You can disable phpMyAdmin shortcut keys by setting $cfg['DisableShortcutKeys'] to false.

Default value:1

If you have more than one server configured, you can set $cfg['ServerDefault'] to any one of them to autoconnect to that server when phpMyAdmin is started, or set it to 0 to be given a list of servers without logging in.

If you have only one server configured, $cfg['ServerDefault'] MUST be set to that server.

Default value:true

Enables check for latest versions using JavaScript on the main phpMyAdmin page or by directly accessing version_check.php.


This setting can be adjusted by your vendor.

Default value:“”

The url of the proxy to be used when phpmyadmin needs to access the outside internet such as when retrieving the latest version info or submitting error reports. You need this if the server where phpMyAdmin is installed does not have direct access to the internet. The format is: “hostname:portnumber”

Default value:“”

The username for authenticating with the proxy. By default, no authentication is performed. If a username is supplied, Basic Authentication will be performed. No other types of authentication are currently supported.

Default value:“”

The password for authenticating with the proxy.

Default value:100

The maximum number of database names to be displayed in the main panel’s database list.

Default value:250

The maximum number of table names to be displayed in the main panel’s list (except on the Export page).

Default value:true

Whether or not to show hints (for example, hints when hovering over table headers).

Default value:1000

The maximum number of characters when a SQL query is displayed. The default limit of 1000 should be correct to avoid the display of tons of hexadecimal codes that represent BLOBs, but some users have real SQL queries that are longer than 1000 characters. Also, if a query’s length exceeds this limit, this query is not saved in the history.

Default value:false

Whether persistent connections should be used or not. Works with following extensions:

Default value:false

Deprecated since version 4.6.0: This setting is no longer available since phpMyAdmin 4.6.0. Please adjust your webserver instead.

Whether to force using https while accessing phpMyAdmin. In a reverse proxy setup, setting this to true is not supported.


In some setups (like separate SSL proxy or load balancer) you might have to set $cfg['PmaAbsoluteUri'] for correct redirection.

Type:integer [number of seconds]
Default value:300

Set the number of seconds a script is allowed to run. If seconds is set to zero, no time limit is imposed. This setting is used while importing/exporting dump files but has no effect when PHP is running in safe mode.

Default value:''

Path for storing session data (session_save_path PHP parameter).

Type:string [number of bytes]
Default value:'-1'

Set the number of bytes a script is allowed to allocate. If set to '-1', no limit is imposed. If set to '0', no change of the memory limit is attempted and the php.ini memory_limit is used.

This setting is used while importing/exporting dump files so you definitely don’t want to put here a too low value. It has no effect when PHP is running in safe mode.

You can also use any string as in php.ini, eg. ‘16M’. Ensure you don’t omit the suffix (16 means 16 bytes!)

Default value:false

Mark used tables and make it possible to show databases with locked tables (since MySQL 3.23.30).

Default value:true

Defines whether SQL queries generated by phpMyAdmin should be displayed or not.

Default value:false

Defines whether the SQL query box should be kept displayed after its submission.

Default value:true

Defines whether to use a Javascript code editor for SQL query boxes. CodeMirror provides syntax highlighting and line numbers. However, middle-clicking for pasting the clipboard contents in some Linux distributions (such as Ubuntu) is not supported by all browsers.

Default value:'default'

Default value of the checkbox for foreign key checks, to disable/enable foreign key checks for certain queries. The possible values are 'default', 'enable' or 'disable'. If set to 'default', the value of the MySQL variable FOREIGN_KEY_CHECKS is used.

Default value:false


This is not a security measure as there will be always ways to circumvent this. If you want to prohibit users from dropping databases, revoke their corresponding DROP privilege.

Defines whether normal users (non-administrator) are allowed to delete their own database or not. If set as false, the link Drop Database will not be shown, and even a DROP DATABASE mydatabase will be rejected. Quite practical for ISP ‘s with many customers.

This limitation of SQL queries is not as strict as when using MySQL privileges. This is due to nature of SQL queries which might be quite complicated. So this choice should be viewed as help to avoid accidental dropping rather than strict privilege limitation.

Default value:true

Whether a warning (“Are your really sure...”) should be displayed when you’re about to lose data.

Default value:true

Define whether the “search string inside database” is enabled or not.

Default value:false

Define whether phpMyAdmin will continue executing a multi-query statement if one of the queries fails. Default is to abort execution.

Main panel

Default value:true

Defines whether or not to display space usage and statistics about databases and tables. Note that statistics requires at least MySQL 3.23.3 and that, at this date, MySQL doesn’t return such information for Berkeley DB tables.

Default value:true

Defines whether to display detailed server information on main page. You can additionally hide more information by using $cfg['Servers'][$i]['verbose'].

Default value:false

Defines whether to display the PHP information or not at the starting main (right) frame.

Please note that to block the usage of phpinfo() in scripts, you have to put this in your php.ini:

disable_functions = phpinfo()


Enabling phpinfo page will leak quite a lot of information about server setup. Is it not recommended to enable this on shared installations.

This might also make easier some remote attacks on your installations, so enable this only when needed.

Default value:true

Defines whether to display the Change password link or not at the starting main (right) frame. This setting does not check MySQL commands entered directly.

Please note that enabling the Change password link has no effect with config authentication mode: because of the hard coded password value in the configuration file, end users can’t be allowed to change their passwords.

Default value:true

Defines whether to display the form for creating database or not at the starting main (right) frame. This setting does not check MySQL commands entered directly.

Default value:true

Defines whether to display informations about the current Git revision (if applicable) on the main panel.


Defines the minimum supported MySQL version. The default is chosen by the phpMyAdmin team; however this directive was asked by a developer of the Plesk control panel to ease integration with older MySQL servers (where most of the phpMyAdmin features work).

Database structure

Default value:false

Defines whether the database structure page (tables list) has a “Creation” column that displays when each table was created.

Default value:false

Defines whether the database structure page (tables list) has a “Last update” column that displays when each table was last updated.

Default value:false

Defines whether the database structure page (tables list) has a “Last check” column that displays when each table was last checked.

Default value:true

Defines whether the table structure actions are hidden under a “More” drop-down.

Browse mode

Default value:'icons'

Defines whether the table navigation links contain 'icons', 'text' or 'both'.

Default value:'both'

If set to icons, will display icons instead of text for db and table properties links (like Browse, Select, Insert, ...). Can be set to 'both' if you want icons AND text. When set to text, will only show text.

Default value:'both'

Whether to display icons or text or both icons and text in table row action segment. Value can be either of 'icons', 'text' or 'both'.

Default value:false

Defines whether a user should be displayed a “Show all” button in browse mode or not in all cases. By default it is shown only on small tables (less than 500 rows) to avoid performance issues while getting too many rows.

Default value:25

Number of rows displayed when browsing a result set and no LIMIT clause is used. If the result set contains more rows, “Previous” and “Next” links will be shown. Possible values: 25,50,100,250,500.

Default value:'SMART'

Defines whether columns are displayed in ascending (ASC) order, in descending (DESC) order or in a “smart” (SMART) order - I.E. descending order for columns of type TIME, DATE, DATETIME and TIMESTAMP, ascending order else- by default.

Changed in version 3.4.0: Since phpMyAdmin 3.4.0 the default value is 'SMART'.

Default value:'double-click'

Defines which action (double-click or click) triggers grid editing. Can be deactivated with the disabled value.

Default value:'K'

Defines the initial behavior for Options > Relational. K, which is the default, displays the key while D shows the display column.

Default value:false

Defines whether or not to save all edited cells at once for grid editing.

Editing mode

Type:boolean or string
Default value:'blob'

Defines whether BLOB or BINARY columns are protected from editing when browsing a table’s content. Valid values are:

  • false to allow editing of all columns;
  • 'blob' to allow editing of all columns except BLOBS;
  • 'noblob' to disallow editing of all columns except BLOBS (the opposite of 'blob');
  • 'all' to disallow editing of all BINARY or BLOB columns.
Default value:true

Defines whether or not MySQL functions fields should be initially displayed in edit/insert mode. Since version 2.10, the user can toggle this setting from the interface.

Default value:true

Defines whether or not type fields should be initially displayed in edit/insert mode. The user can toggle this setting from the interface.

Default value:2

Defines the maximum number of concurrent entries for the Insert page.

Default value:100

If there are fewer items than this in the set of foreign keys, then a drop-down box of foreign keys is presented, in the style described by the $cfg['ForeignKeyDropdownOrder'] setting.

Default value:array(‘content-id’, ‘id-content’)

For the foreign key drop-down fields, there are several methods of display, offering both the key and value data. The contents of the array should be one or both of the following strings: content-id, id-content.

Export and import settings

Default value:true
Default value:true
Default value:true

Defines whether to allow the use of zip/GZip/BZip2 compression when creating a dump file

Default value:true

Defines whether to allow on the fly compression for GZip/BZip2 compressed exports. This doesn’t affect smaller dumps and allows users to create larger dumps that won’t otherwise fit in memory due to php memory limit. Produced files contain more GZip/BZip2 headers, but all normal programs handle this correctly.

Default value:array(...)

In this array are defined default parameters for export, names of items are similar to texts seen on export page, so you can easily identify what they mean.

Default value:'sql'

Default export format.

Default value:'quick'

Defines how the export form is displayed when it loads. Valid values are:

  • quick to display the minimum number of options to configure
  • custom to display every available option to configure
  • custom-no-form same as custom but does not display the option of using quick export
Default value:''

Defines charset for generated export. By default no charset conversion is done assuming UTF-8.

Default value:'@TABLE@'

Default filename template for table exports.

Default value:'@DATABASE@'

Default filename template for database exports.

Default value:'@SERVER@'

Default filename template for server exports.

Default value:array(...)

In this array are defined default parameters for import, names of items are similar to texts seen on import page, so you can easily identify what they mean.

Default value:''

Defines charset for import. By default no charset conversion is done assuming UTF-8.

Tabs display settings

Default value:'both'

Defines whether the menu tabs contain 'icons', 'text' or 'both'.

Default value:1

How many columns will be utilized to display the tables on the database property view? When setting this to a value larger than 1, the type of the database will be omitted for more display space.

Default value:'welcome'

Defines the tab displayed by default on server view. The possible values are the localized equivalent of:

  • welcome (recommended for multi-user setups)
  • databases,
  • status
  • variables
  • privileges
Default value:'structure'

Defines the tab displayed by default on database view. The possible values are the localized equivalent of:

  • structure
  • sql
  • search
  • operations
Default value:'browse'

Defines the tab displayed by default on table view. The possible values are the localized equivalent of:

  • structure
  • sql
  • search
  • insert
  • browse

PDF Options

Default value:array('A3', 'A4', 'A5', 'letter', 'legal')

Array of possible paper sizes for creating PDF pages.

You should never need to change this.

Default value:'A4'

Default page size to use when creating PDF pages. Valid values are any listed in $cfg['PDFPageSizes'].


Default value:'en'

Defines the default language to use, if not browser-defined or user- defined. The corresponding language file needs to be in locale/code/LC_MESSAGES/phpmyadmin.mo.

Default value:'utf8mb4_general_ci'

Defines the default connection collation to use, if not user-defined. See the MySQL documentation for charsets for list of possible values.

Default value:not set

Force language to use. The corresponding language file needs to be in locale/code/LC_MESSAGES/phpmyadmin.mo.

Default value:''

Limit list of available languages to those matching the given regular expression. For example if you want only Czech and English, you should set filter to '^(cs|en)'.

Default value:'auto'

You can select here which functions will be used for character set conversion. Possible values are:

  • auto - automatically use available one (first is tested iconv, then recode)
  • iconv - use iconv or libiconv functions
  • recode - use recode_string function
  • mb - use mbstring extension
  • none - disable encoding conversion

Enabled charset conversion activates a pull-down menu in the Export and Import pages, to choose the character set when exporting a file. The default value in this menu comes from $cfg['Export']['charset'] and $cfg['Import']['charset'].

Default value:'//TRANSLIT'

Specify some parameters for iconv used in charset conversion. See iconv documentation for details. By default //TRANSLIT is used, so that invalid characters will be transliterated.

Default value:array(...)

Available character sets for MySQL conversion. You can add your own (any of supported by recode/iconv) or remove these which you don’t use. Character sets will be shown in same order as here listed, so if you frequently use some of these move them to the top.

Web server settings

Default value:'auto'

Defines whether to use GZip output buffering for increased speed in HTTP transfers. Set to true/false for enabling/disabling. When set to ‘auto’ (string), phpMyAdmin tries to enable output buffering and will automatically disable it if your browser has some problems with buffering. IE6 with a certain patch is known to cause data corruption when having enabled buffering.

Default value:array()

Lists proxies and HTTP headers which are trusted for $cfg['Servers'][$i]['AllowDeny']['order']. This list is by default empty, you need to fill in some trusted proxy servers if you want to use rules for IP addresses behind proxy.

The following example specifies that phpMyAdmin should trust a HTTP_X_FORWARDED_FOR (X -Forwarded-For) header coming from the proxy

$cfg['TrustedProxies'] = array('' => 'HTTP_X_FORWARDED_FOR');

The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the client’s IP address as usual.

Default value:'auto'

Specifies whether GD >= 2 is available. If yes it can be used for MIME transformations. Possible values are:

  • auto - automatically detect
  • yes - GD 2 functions can be used
  • no - GD 2 function cannot be used
Default value:true

We normally check the permissions on the configuration file to ensure it’s not world writable. However, phpMyAdmin could be installed on a NTFS filesystem mounted on a non-Windows server, in which case the permissions seems wrong but in fact cannot be detected. In this case a sysadmin would set this parameter to false.

Default value:1000

Limit for length of URL in links. When length would be above this limit, it is replaced by form with button. This is required as some web servers (IIS) have problems with long URL .

Default value:''

Additional string to include in allowed script and image sources in Content Security Policy header.

This can be useful when you want to include some external JavaScript files in config.footer.inc.php or config.header.inc.php, which would be normally not allowed by Content Security Policy.

To allow some sites, just list them within the string:

$cfg['CSPAllow'] = 'example.com example.net';

New in version 4.0.4.

Default value:false

In the database Structure page, it’s possible to mark some tables then choose an operation like optimizing for many tables. This can slow down a server; therefore, setting this to true prevents this kind of multiple maintenance operation.

Theme settings

Please directly modify themes/themename/layout.inc.php, although your changes will be overwritten with the next update.

Design customization

Default value:true

When set to true, hovering over an item in the navigation panel causes that item to be marked (the background is highlighted).

Default value:true

When set to true, hovering over a row in the Browse page causes that row to be marked (the background is highlighted).

Default value:true

When set to true, a data row is marked (the background is highlighted) when the row is selected with the checkbox.

Default value:50

Maximum number of characters shown in any non-numeric field on browse view. Can be turned off by a toggle button on the browse page.

Default value:'left'

Defines the place where table row links (Edit, Copy, Delete) would be put when tables contents are displayed (you may have them displayed at the left side, right side, both sides or nowhere).

Default value:false

Defines whether to show row links (Edit, Copy, Delete) and checkboxes for multiple row operations even when the selection does not have a unique key. Using row actions in the absence of a unique key may result in different/more rows being affected since there is no guaranteed way to select the exact row(s).

Default value:true

If enabled, remember the sorting of each table when browsing them.

Default value:'NONE'

This defines the default sort order for the tables, having a primary key, when there is no sort order defines externally. Acceptable values : [‘NONE’, ‘ASC’, ‘DESC’]

Default value:true
Default value:true

By setting the corresponding variable to true you can enable the display of column comments in Browse or Property display. In browse mode, the comments are shown inside the header. In property mode, comments are displayed using a CSS-formatted dashed-line below the name of the column. The comment is shown as a tool-tip for that column.

Text fields

Default value:'input'

Defines which type of editing controls should be used for CHAR and VARCHAR columns. Applies to data editing and also to the default values in structure editing. Possible values are:

  • input - this allows to limit size of text to size of columns in MySQL, but has problems with newlines in columns
  • textarea - no problems with newlines in columns, but also no length limitations
Default value:4

Defines the minimum size for input fields generated for CHAR and VARCHAR columns.

Default value:60

Defines the maximum size for input fields generated for CHAR and VARCHAR columns.

Default value:40
Default value:15
Default value:40
Default value:2

Number of columns and rows for the textareas. This value will be emphasized (*2) for SQL query textareas and (*1.25) for SQL textareas inside the query window.

The Char* values are used for CHAR and VARCHAR editing (if configured via $cfg['CharEditing']).

Default value:true

Defines whether textarea for LONGTEXT columns should have double size.

Default value:false

Defines if the whole textarea of the query box will be selected on click.

Default value:true

Whether to enable autocomplete for table and column names in any SQL query box.

SQL query box settings

Default value:true

Whether to display an edit link to change a query in any SQL Query box.

Default value:true

Whether to display a link to explain a SELECT query in any SQL Query box.

Default value:true

Whether to display a link to wrap a query in PHP code in any SQL Query box.

Default value:true

Whether to display a link to refresh a query in any SQL Query box.

Web server upload/save/import directories

If PHP is running in safe mode, all directories must be owned by the same user as the owner of the phpMyAdmin scripts.

If the directory where phpMyAdmin is installed is subject to an open_basedir restriction, you need to create a temporary directory in some directory accessible by the PHP interpreter.

For security reasons, all directories should be outside the tree published by webserver. If you cannot avoid having this directory published by webserver, limit access to it either by web server configuration (for example using .htaccess or web.config files) or place at least an empty index.html file there, so that directory listing is not possible. However as long as the directory is accessible by web server, an attacker can guess filenames to download the files.

Default value:''

The name of the directory where SQL files have been uploaded by other means than phpMyAdmin (for example, ftp). Those files are available under a drop-down box when you click the database or table name, then the Import tab.

If you want different directory for each user, %u will be replaced with username.

Please note that the file names must have the suffix ”.sql” (or ”.sql.bz2” or ”.sql.gz” if support for compressed formats is enabled).

This feature is useful when your file is too big to be uploaded via HTTP, or when file uploads are disabled in PHP.


Please see top of this chapter (Web server upload/save/import directories) for instructions how to setup this directory and how to make its usage secure.

Default value:''

The name of the directory where dumps can be saved.

If you want different directory for each user, %u will be replaced with username.

Please note that the directory must exist and has to be writable for the user running webserver.


Please see top of this chapter (Web server upload/save/import directories) for instructions how to setup this directory and how to make its usage secure.

Default value:''

The name of the directory where temporary files can be stored.

This is needed for importing ESRI Shapefiles, see 6.30 Import: How can I import ESRI Shapefiles? and to work around limitations of open_basedir for uploaded files, see 1.11 I get an ‘open_basedir restriction’ while uploading a file from the import tab..

This directory should have as strict permissions as possible as the only user required to access this directory is the one who runs the webserver. If you have root privileges, simply make this user owner of this directory and make it accessible only by it:

chown www-data:www-data tmp
chmod 700 tmp

If you cannot change owner of the directory, you can achieve a similar setup using ACL:

chmod 700 tmp
setfacl -m "g:www-data:rwx" tmp
setfacl -d -m "g:www-data:rwx" tmp

If neither of above works for you, you can still make the directory chmod 777, but it might impose risk of other users on system reading and writing data in this directory.


Please see top of this chapter (Web server upload/save/import directories) for instructions how to setup this directory and how to make its usage secure.

Various display setting

Default value:100

Repeat the headers every X cells, or 0 to deactivate.

Default value:false
Default value:25

If $cfg['QueryHistoryDB'] is set to true, all your Queries are logged to a table, which has to be created by you (see $cfg['Servers'][$i]['history']). If set to false, all your queries will be appended to the form, but only as long as your window is opened they remain saved.

When using the JavaScript based query window, it will always get updated when you click on a new table/db to browse and will focus if you click on Edit SQL after using a query. You can suppress updating the query window by checking the box Do not overwrite this query from outside the window below the query textarea. Then you can browse tables/databases in the background without losing the contents of the textarea, so this is especially useful when composing a query with tables you first have to look in. The checkbox will get automatically checked whenever you change the contents of the textarea. Please uncheck the button whenever you definitely want the query window to get updated even though you have made alterations.

If $cfg['QueryHistoryDB'] is set to true you can specify the amount of saved history items using $cfg['QueryHistoryMax'].

Default value:true

Enable Transformations.

Default value:500000

For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT. If the approximate row count as returned by SHOW TABLE STATUS is smaller than this value, SELECT COUNT will be used, otherwise the approximate count will be used.

Default value:0

For VIEWs, since obtaining the exact count could have an impact on performance, this value is the maximum to be displayed, using a SELECT COUNT ... LIMIT. Setting this to 0 bypasses any row counting.

Default value:true

Sorts database and table names according to natural order (for example, t1, t2, t10). Currently implemented in the navigation panel and in Database view, for the table list.

Default value:'closed'

If set to 'closed', the visual sliders are initially in a closed state. A value of 'open' does the reverse. To completely disable all visual sliders, use 'disabled'.

Default value:array()

Contains names of configuration options (keys in $cfg array) that users can’t set through user preferences. For possible values, refer to libraries/config/user_preferences.forms.php.

Default value:false

Activates in the user preferences a tab containing options for developers of phpMyAdmin.

Page titles

Default value:'@HTTP_HOST@ / @VSERVER@ | @PHPMYADMIN@'
Default value:'@HTTP_HOST@ | @PHPMYADMIN@'

Allows you to specify window’s title bar. You can use 6.27 What format strings can I use?.

Theme manager settings

Default value:true

Enables user-selectable themes. See 2.7 Using and creating themes.

Default value:'pmahomme'

The default theme (a subdirectory under ./themes/).

Default value:false

Whether to allow different theme for each server.

Default queries

Default value:'SELECT * FROM @TABLE@ WHERE 1'
Default value:''

Default queries that will be displayed in query boxes when user didn’t specify any. You can use standard 6.27 What format strings can I use?.

MySQL settings

Default value:array(...)

Functions selected by default when inserting/changing row, Functions are defined for meta types as (FUNC_NUMBER, FUNC_DATE, FUNC_CHAR, FUNC_SPATIAL, FUNC_UUID) and for first_timestamp, which is used for first timestamp column in table.



These settings might have huge effect on performance or security.

Default value:array(...)
Default value:false

Enable logging queries and execution times to be displayed in the console’s Debug SQL tab.

Default value:false

Enable logging of queries and execution times to the syslog. Requires $cfg['DBG']['sql'] to be enabled.

Default value:false

Enable to let server present itself as demo server. This is used for phpMyAdmin demo server.

It currently changes following behavior:

  • There is welcome message on the main page.
  • There is footer information about demo server and used git revision.
  • The setup script is enabled even with existing configuration.
  • The setup does not try to connect to the MySQL server.


See following configuration snippets for typical setups of phpMyAdmin.

Basic example

Example configuration file, which can be copied to config.inc.php to get some core configuration layout; it is distributed with phpMyAdmin as config.sample.inc.php. Please note that it does not contain all configuration options, only the most frequently used ones.

/* vim: set expandtab sw=4 ts=4 sts=4: */
 * phpMyAdmin sample configuration, you can use it as base for
 * manual configuration. For easier setup you can use setup/
 * All directives are explained in documentation in the doc/ folder
 * or at <https://docs.phpmyadmin.net/>.
 * @package PhpMyAdmin

 * This is needed for cookie based authentication to encrypt password in
 * cookie. Needs to be 32 chars long.
$cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */

 * Servers configuration
$i = 0;

 * First server
/* Authentication type */
$cfg['Servers'][$i]['auth_type'] = 'cookie';
/* Server parameters */
$cfg['Servers'][$i]['host'] = 'localhost';
$cfg['Servers'][$i]['compress'] = false;
$cfg['Servers'][$i]['AllowNoPassword'] = false;

 * phpMyAdmin configuration storage settings.

/* User used to manipulate with storage */
// $cfg['Servers'][$i]['controlhost'] = '';
// $cfg['Servers'][$i]['controlport'] = '';
// $cfg['Servers'][$i]['controluser'] = 'pma';
// $cfg['Servers'][$i]['controlpass'] = 'pmapass';

/* Storage database and tables */
// $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin';
// $cfg['Servers'][$i]['bookmarktable'] = 'pma__bookmark';
// $cfg['Servers'][$i]['relation'] = 'pma__relation';
// $cfg['Servers'][$i]['table_info'] = 'pma__table_info';
// $cfg['Servers'][$i]['table_coords'] = 'pma__table_coords';
// $cfg['Servers'][$i]['pdf_pages'] = 'pma__pdf_pages';
// $cfg['Servers'][$i]['column_info'] = 'pma__column_info';
// $cfg['Servers'][$i]['history'] = 'pma__history';
// $cfg['Servers'][$i]['table_uiprefs'] = 'pma__table_uiprefs';
// $cfg['Servers'][$i]['tracking'] = 'pma__tracking';
// $cfg['Servers'][$i]['userconfig'] = 'pma__userconfig';
// $cfg['Servers'][$i]['recent'] = 'pma__recent';
// $cfg['Servers'][$i]['favorite'] = 'pma__favorite';
// $cfg['Servers'][$i]['users'] = 'pma__users';
// $cfg['Servers'][$i]['usergroups'] = 'pma__usergroups';
// $cfg['Servers'][$i]['navigationhiding'] = 'pma__navigationhiding';
// $cfg['Servers'][$i]['savedsearches'] = 'pma__savedsearches';
// $cfg['Servers'][$i]['central_columns'] = 'pma__central_columns';
// $cfg['Servers'][$i]['designer_settings'] = 'pma__designer_settings';
// $cfg['Servers'][$i]['export_templates'] = 'pma__export_templates';

 * End of servers configuration

 * Directories for saving/loading files from server
$cfg['UploadDir'] = '';
$cfg['SaveDir'] = '';

 * Whether to display icons or text or both icons and text in table row
 * action segment. Value can be either of 'icons', 'text' or 'both'.
 * default = 'both'
//$cfg['RowActionType'] = 'icons';

 * Defines whether a user should be displayed a "show all (records)"
 * button in browse mode or not.
 * default = false
//$cfg['ShowAll'] = true;

 * Number of rows displayed when browsing a result set. If the result
 * set contains more rows, "Previous" and "Next".
 * Possible values: 25, 50, 100, 250, 500
 * default = 25
//$cfg['MaxRows'] = 50;

 * Disallow editing of binary fields
 * valid values are:
 *   false    allow editing
 *   'blob'   allow editing except for BLOB fields
 *   'noblob' disallow editing except for BLOB fields
 *   'all'    disallow editing
 * default = 'blob'
//$cfg['ProtectBinary'] = false;

 * Default language to use, if not browser-defined or user-defined
 * (you find all languages in the locale folder)
 * uncomment the desired line:
 * default = 'en'
//$cfg['DefaultLang'] = 'en';
//$cfg['DefaultLang'] = 'de';

 * How many columns should be used for table display of a database?
 * (a value larger than 1 results in some information being hidden)
 * default = 1
//$cfg['PropertiesNumColumns'] = 2;

 * Set to true if you want DB-based query history.If false, this utilizes
 * JS-routines to display query history (lost by window close)
 * This requires configuration storage enabled, see above.
 * default = false
//$cfg['QueryHistoryDB'] = true;

 * When using DB-based query history, how many entries should be kept?
 * default = 25
//$cfg['QueryHistoryMax'] = 100;

 * Whether or not to query the user before sending the error report to
 * the phpMyAdmin team when a JavaScript error occurs
 * Available options
 * ('ask' | 'always' | 'never')
 * default = 'ask'
//$cfg['SendErrorReports'] = 'always';

 * You can find more configuration options in the documentation
 * in the doc/ folder or at <https://docs.phpmyadmin.net/>.


Don’t use the controluser ‘pma’ if it does not yet exist and don’t use ‘pmapass’ as password.

Example for signon authentication

This example uses examples/signon.php to demonstrate usage of Signon authentication mode:

$i = 0;
$cfg['Servers'][$i]['extension']     = 'mysqli';
$cfg['Servers'][$i]['auth_type']     = 'signon';
$cfg['Servers'][$i]['SignonSession'] = 'SignonSession';
$cfg['Servers'][$i]['SignonURL']     = 'examples/signon.php';

Example for IP address limited autologin

If you want to automatically login when accessing phpMyAdmin locally while asking for a password when accessing remotely, you can achieve it using following snippet:

if ($_SERVER["REMOTE_ADDR"] == "") {
    $cfg['Servers'][$i]['auth_type'] = 'config';
    $cfg['Servers'][$i]['user'] = 'root';
    $cfg['Servers'][$i]['password'] = 'yourpassword';
} else {
    $cfg['Servers'][$i]['auth_type'] = 'cookie';


Filtering based on IP addresses isn’t reliable over the internet, use it only for local address.

Example for using multiple MySQL servers

You can configure any number of servers using $cfg['Servers'], following example shows two of them:

//any string of your choice
$i = 0;

$i++; // server 1 :
$cfg['Servers'][$i]['auth_type'] = 'cookie';
$cfg['Servers'][$i]['verbose']   = 'no1';
$cfg['Servers'][$i]['host']      = 'localhost';
$cfg['Servers'][$i]['extension'] = 'mysqli';
// more options for #1 ...

$i++; // server 2 :
$cfg['Servers'][$i]['auth_type'] = 'cookie';
$cfg['Servers'][$i]['verbose']   = 'no2';
$cfg['Servers'][$i]['host']      = 'remote.host.addr';//or ip:''
// this server must allow remote clients, e.g., host 10.9.8.%
// not only in mysql.host but also in the startup configuration
$cfg['Servers'][$i]['extension'] = 'mysqli';
// more options for #2 ...

// end of server sections
$cfg['ServerDefault'] = 0; // to choose the server on startup

// further general options ...

Google Cloud SQL with SSL

To connect to Google Could SQL, you currently need to disable certificate verification. This is caused by the certficate being issued for CN matching your instance name, but you connect to an IP address and PHP tries to match these two. With verfication you end up with error message like:

Peer certificate CN=`api-project-851612429544:pmatest' did not match expected CN=`'


With disabled verification your traffic is encrypted, but you’re open to man in the middle attacks.

To connect phpMyAdmin to Google Cloud SQL using SSL download the client and server certificates and tell phpMyAdmin to use them:

// IP address of your instance
$cfg['Servers'][$i]['host'] = '';
// Use SSL for connection
$cfg['Servers'][$i]['ssl'] = true;
// Client secret key
$cfg['Servers'][$i]['ssl_key'] = '../client-key.pem';
// Client certificate
$cfg['Servers'][$i]['ssl_cert'] = '../client-cert.pem';
// Server certification authority
$cfg['Servers'][$i]['ssl_ca'] = '../server-ca.pem';
// Disable SSL verification (see above note)
$cfg['Servers'][$i]['ssl_verify'] = false;

User Guide

Configuring phpMyAdmin

phpMyAdmin has quite a lot of configuration settings, those are described in Configuration. There are several layers of the configuration.

The global settings can be configured in config.inc.php as described in Configuration. This is only way to configure connections to databases and other system wide settings.

On top of this there are user settings which can be persistently stored in phpMyAdmin configuration storage, possibly automatically configured through Zero configuration. If the phpMyAdmin configuration storage are not configured, the settings are temporarily stored in the session data, these are valid only until you logout.

You can also save the user configuration for further use, either download them as a file or to the browser local storage. You can find both those options in the Settings tab. The settings stored in browser local storage will be automatically offered for loading upon your login to phpMyAdmin.



You need to have configured the phpMyAdmin configuration storage for using transformations feature.


To enable transformations, you have to setup the column_info table and the proper directives. Please see the Configuration on how to do so.

You can apply different transformations to the contents of each column. The transformation will take the content of each column and transform it with certain rules defined in the selected transformation.

Say you have a column ‘filename’ which contains a filename. Normally you would see in phpMyAdmin only this filename. Using transformations you can transform that filename into a HTML link, so you can click inside of the phpMyAdmin structure on the column’s link and will see the file displayed in a new browser window. Using transformation options you can also specify strings to append/prepend to a string or the format you want the output stored in.

For a general overview of all available transformations and their options, you can consult your <www.your-host.com>/<your-install- dir>/transformation_overview.php installation.

For a tutorial on how to effectively use transformations, see our Link section on the official phpMyAdmin homepage.


Go to your tbl_structure.php page (i.e. reached through clicking on the ‘Structure’ link for a table). There click on “Change” (or change icon) and there you will see three new fields at the end of the line. They are called ‘MIME-type’, ‘Browser transformation’ and ‘Transformation options’.

  • The field ‘MIME-type’ is a drop-down field. Select the MIME-type that corresponds to the column’s contents. Please note that transformations are inactive as long as no MIME-type is selected.
  • The field ‘Browser transformation’ is a drop-down field. You can choose from a hopefully growing amount of pre-defined transformations. See below for information on how to build your own transformation. There are global transformations and mimetype-bound transformations. Global transformations can be used for any mimetype. They will take the mimetype, if necessary, into regard. Mimetype-bound transformations usually only operate on a certain mimetype. There are transformations which operate on the main mimetype (like ‘image’), which will most likely take the subtype into regard, and those who only operate on a specific subtype (like ‘image/jpeg’). You can use transformations on mimetypes for which the function was not defined for. There is no security check for you selected the right transformation, so take care of what the output will be like.
  • The field ‘Transformation options’ is a free-type textfield. You have to enter transform-function specific options here. Usually the transforms can operate with default options, but it is generally a good idea to look up the overview to see which options are necessary. Much like the ENUM/SET-Fields, you have to split up several options using the format ‘a’,’b’,’c’,...(NOTE THE MISSING BLANKS). This is because internally the options will be parsed as an array, leaving the first value the first element in the array, and so forth. If you want to specify a MIME character set you can define it in the transformation_options. You have to put that outside of the pre- defined options of the specific mime-transform, as the last value of the set. Use the format “’; charset=XXX’”. If you use a transform, for which you can specify 2 options and you want to append a character set, enter “‘first parameter’,’second parameter’,’charset=us-ascii’”. You can, however use the defaults for the parameters: “’‘,’‘,’charset =us-ascii’”.

File structure

All specific transformations for mimetypes are defined through class files in the directory ‘libraries/plugins/transformations/’. Each of them extends a certain transformation abstract class declared in libraries/plugins/transformations/abstract.

They are stored in files to ease up customization and easy adding of new transformations.

Because the user cannot enter own mimetypes, it is kept sure that transformations always work. It makes no sense to apply a transformation to a mimetype the transform-function doesn’t know to handle.

There is a file called ‘transformations.lib.php‘ that provides some basic functions which can be included by any other transform function.

The file name convention is [Mimetype]_[Subtype]_[Transformation Name].class.php, while the abtract class that it extends has the name [Transformation Name]TransformationsPlugin. All of the methods that have to be implemented by a transformations plug-in are:

  1. getMIMEType() and getMIMESubtype() in the main class;
  2. getName(), getInfo() and applyTransformation() in the abstract class it extends.

The getMIMEType(), getMIMESubtype() and getName() methods return the name of the MIME type, MIME Subtype and transformation accordingly. getInfo() returns the transformation’s description and possible options it may receive and applyTransformation() is the method that does the actual work of the transformation plug-in.

Please see the libraries/plugins/transformations/TEMPLATE and libraries/plugins/transformations/TEMPLATE_ABSTRACT files for adding your own transformation plug-in. You can also generate a new transformation plug-in (with or without the abstract transformation class), by using scripts/transformations_generator_plugin.sh or scripts/transformations_generator_main_class.sh.

The applyTransformation() method always gets passed three variables:

  1. $buffer - Contains the text inside of the column. This is the text, you want to transform.
  2. $options - Contains any user-passed options to a transform function as an array.
  3. $meta - Contains an object with information about your column. The data is drawn from the output of the mysql_fetch_field() function. This means, all object properties described on the manual page are available in this variable and can be used to transform a column accordingly to unsigned/zerofill/not_null/... properties. The $meta->mimetype variable contains the original MIME-type of the column (i.e. ‘text/plain’, ‘image/jpeg’ etc.)



You need to have configured the phpMyAdmin configuration storage for using bookmarks feature.

Storing bookmarks

Any query you have executed can be stored as a bookmark on the page where the results are displayed. You will find a button labeled Bookmark this query just at the end of the page. As soon as you have stored a bookmark, it is related to the database you run the query on. You can now access a bookmark dropdown on each page, the query box appears on for that database.

Variables inside bookmarks

You can also have, inside the query, placeholders for variables. This is done by inserting into the query SQL comments between /* and */. Inside the comments, the special strings [VARIABLE{variable-number}] is used. Be aware that the whole query minus the SQL comments must be valid by itself, otherwise you won’t be able to store it as a bookmark.

When you execute the bookmark, everything typed into the Variables input boxes on the query box page will replace the strings /*[VARIABLE{variable-number}]*/ in your stored query.

Also remember, that everything else inside the /*[VARIABLE{variable-number}]*/ string for your query will remain the way it is, but will be stripped of the /**/ chars. So you can use:

/*, [VARIABLE1] AS myname */

which will be expanded to

, VARIABLE1 as myname

in your query, where VARIABLE1 is the string you entered in the Variable 1 input box.

A more complex example. Say you have stored this query:

SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE1]%' */

Say, you now enter “phpMyAdmin” as the variable for the stored query, the full query will be:

SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%'

NOTE THE ABSENCE OF SPACES inside the /**/ construct. Any spaces inserted there will be later also inserted as spaces in your query and may lead to unexpected results especially when using the variable expansion inside of a “LIKE ‘’” expression.

User management

User management is the process of controlling which users are allowed to connect to the MySQL server and what permissions they have on each database. phpMyAdmin does not handle user management, rather it passes the username and password on to MySQL, which then determines whether a user is permitted to perform a particular action. Within phpMyAdmin, administrators have full control over creating users, viewing and editing privileges for existing users, and removing users.

Within phpMyAdmin, user management is controlled via the Users link from the main page. Users can be created, edited, and removed.

Creating a new user

To create a new user, click the Add a new user link near the bottom of the Users page (you must be a “superuser”, e.g., user “root”). Use the textboxes and drop-downs to configure the user to your particular needs. You can then select whether to create a database for that user and grant specific global privileges. Once you’ve created the user (by clicking Go), you can define that user’s permissions on a specific database (don’t grant global privileges in that case). In general, users do not need any global privileges (other than USAGE), only permissions for their specific database.

Editing an existing user

To edit an existing user, simply click the pencil icon to the right of that user in the Users page. You can then edit their global- and database-specific privileges, change their password, or even copy those privileges to a new user.

Deleting a user

From the Users page, check the checkbox for the user you wish to remove, select whether or not to also remove any databases of the same name (if they exist), and click Go.

Assigning privileges to user for a specific database

Users are assigned to databases by editing the user record (from the Users link on the home page) not from within the Users link under the table. If you are creating a user specifically for a given table you will have to create the user first (with no global privileges) and then go back and edit that user to add the table and privileges for the individual table.

Configurable menus and user groups

By enabling $cfg['Servers'][$i]['usergroups'] and $cfg['Servers'][$i]['usergroups'] you can customize what users will see in the phpMyAdmin navigation.


This feature only limits what a user sees, he is still able to use all the functions. So this can not be considered as a security limitation. Should you want to limit what users can do, use MySQL privileges to achieve that.

With this feature enabled, the User accounts management interface gains a second tab for managing User groups, where you can define what each group will view (see image below) and you can then assign each user to one of these groups. Users will be presented with a simplified user interface, which might be useful for inexperienced users who could be overwhelmed by all the features phpMyAdmin provides.



phpMyAdmin allows relationships (similar to foreign keys) using MySQL-native (InnoDB) methods when available and falling back on special phpMyAdmin-only features when needed. There are two ways of editing these relations, with the relation view and the drag-and-drop designer – both of which are explained on this page.


You need to have configured the phpMyAdmin configuration storage for using phpMyAdmin only relations.

Technical info

Currently the only MySQL table type that natively supports relationships is InnoDB. When using an InnoDB table, phpMyAdmin will create real InnoDB relations which will be enforced by MySQL no matter which application accesses the database. In the case of any other table type, phpMyAdmin enforces the relations internally and those relations are not applied to any other application.

Relation view

In order to get it working, you first have to properly create the [[pmadb|pmadb]]. Once that is setup, select a table’s “Structure” page. Below the table definition, a link called “Relation view” is shown. If you click that link, a page will be shown that offers you to create a link to another table for any (most) fields. Only PRIMARY KEYS are shown there, so if the field you are referring to is not shown, you most likely are doing something wrong. The drop-down at the bottom is the field which will be used as the name for a record.

Relation view example
_images/pma-relations-relation-view-link.png _images/pma-relations-relation-link.png

Let’s say you have categories and links and one category can contain several links. Your table structure would be something like this:

  • category.category_id (must be unique)
  • category.name
  • link.link_id
  • link.category_id
  • link.uri.

Open the relation view (below the table structure) page for the link table and for category_id field, you select category.category_id as master record.

If you now browse the link table, the category_id field will be a clickable hyperlink to the proper category record. But all you see is just the category_id, not the name of the category.


To fix this, open the relation view of the category table and in the drop down at the bottom, select “name”. If you now browse the link table again and hover the mouse over the category_id hyperlink, the value from the related category will be shown as tooltip.



The Designer feature is a graphical way of creating, editing, and displaying phpMyAdmin relations. These relations are compatible with those created in phpMyAdmin’s relation view.

To use this feature, you need a properly configured phpMyAdmin configuration storage and must have the $cfg['Servers'][$i]['table_coords'] configured.

To use the designer, select a database’s structure page, then look for the Designer tab.

To export the view into PDF, you have to create PDF pages first. The Designer creates the layout, how the tables shall be displayed. To finally export the view, you have to create this with a PDF page and select your layout, which you have created with the designer.


New in version 3.4.0.

Since phpMyAdmin version 3.4.0, you can easily generate charts from a SQL query by clicking the “Display chart” link in the “Query results operations” area.


A window layer “Display chart” is shown in which you can customize the chart with the following options.

  • Chart type: Allows you choose the type of the chart. Supported types are bar charts, column charts, line charts, spline charts, area charts, pie charts and timeline charts (only the chart types applicable for current series selection are offered).
  • X-axis: Allows to choose the field for the main axis.
  • Series: Allows to choose series for the chart. You can choose multiple series.
  • Title: Allows specifying a title for the chart which is displayed above the chart.
  • X-axis and Y-axis labels: Allows specifying labels for axes.
  • Start row and number of rows: Allows generating charts only for a specified number of rows of the results set.

Chart implementation

Charts in phpMyAdmin are drawn using jqPlot jQuery library.


Pie chart

Query results for a simple pie chart can be generated with:

SELECT 'Food' AS 'expense',
   1250 AS 'amount' UNION
SELECT 'Accommodation', 500 UNION
SELECT 'Travel', 720 UNION
SELECT 'Misc', 220

And the result of this query is:

expense anount
Food 1250
Accommodation 500
Travel 720
Misc 220

Choosing expense as the X-axis and amount in series:

Bar and column chart

Both bar charts and column chats support stacking. Upon selecting one of these types a checkbox is displayed to select stacking.

Query results for a simple bar or column chart can be generated with:

   0.99 AS 'rental_rate',
   20.99 AS 'replacement_cost' UNION
SELECT 'AFRICAN EGG', 2.99, 22.99

And the result of this query is:

title rental_rate replacement_cost
AFRICAN EGG 2.99 22.99

Choosing title as the X-axis and rental_rate and replacement_cost as series:

Scatter chart

Scatter charts are useful in identifying the movement of one or more variable(s) compared to another variable.

Using the same data set from bar and column charts section and choosing replacement_cost as the X-axis and rental_rate in series:

Line, spline and timeline charts

These charts can be used to illustrate trends in underlying data. Spline charts draw smooth lines while timeline charts draw X-axis taking the distances between the dates/time into consideration.

Query results for a simple line, spline or timeline chart can be generated with:

   DATE('2006-01-08') AS 'date',
   2056 AS 'revenue',
   1378 AS 'cost' UNION
SELECT DATE('2006-01-09'), 1898, 2301 UNION
SELECT DATE('2006-01-15'), 1560, 600 UNION
SELECT DATE('2006-01-17'), 3457, 1565

And the result of this query is:

date revenue cost
2016-01-08 2056 1378
2006-01-09 1898 2301
2006-01-15 1560 600
2006-01-17 3457 1565
_images/line_chart.png _images/spline_chart.png _images/timeline_chart.png

Import and export


To import data, go to the “Import” tab in phpMyAdmin. To import data into a specific database or table, open the database or table before going to the “Import” tab.

In addition to the standard Import and Export tab, you can also import an SQL file directly by dragging and dropping it from your local file manager to the phpMyAdmin interface in your web browser.

If you are having troubles importing big files, please consult 1.16 I cannot upload big dump files (memory, HTTP or timeout problems)..

You can import using following methods:

Form based upload

Can be used with any supported format, also (b|g)zipped files, e.g., mydump.sql.gz .

Form based SQL Query

Can be used with valid SQL dumps.

Using upload directory

You can specify an upload directory on your web server where phpMyAdmin is installed, after uploading your file into this directory you can select this file in the import dialog of phpMyAdmin, see $cfg['UploadDir'].

phpMyAdmin can import from several various commonly used formats.


Comma separated values format which is often used by spreadsheets or various other programs for export/import.


When importing data into a table from a CSV file where the table has an ‘auto_increment’ field, make the ‘auto_increment’ value for each record in the CSV field to be ‘0’ (zero). This allows the ‘auto_increment’ field to populate correctly.

It is now possible to import a CSV file at the server or database level. Instead of having to create a table to import the CSV file into, a best-fit structure will be determined for you and the data imported into it, instead. All other features, requirements, and limitations are as before.


Similar to CSV, only using the internal MySQL parser and not the phpMyAdmin one.

ESRI Shape File

The ESRI shapefile or simply a shapefile is a popular geospatial vector data format for geographic information systems software. It is developed and regulated by Esri as a (mostly) open specification for data interoperability among Esri and other software products.


MediaWiki files, which can be exported by phpMyAdmin (version 4.0 or later), can now also be imported. This is the format used by Wikipedia to display tables.

Open Document Spreadsheet (ODS)

OpenDocument workbooks containing one or more spreadsheets can now be directly imported.

When importing an ODS speadsheet, the spreadsheet must be named in a specific way in order to make the import as simple as possible.

Table name

During import, phpMyAdmin uses the sheet name as the table name; you should rename the sheet in your spreadsheet program in order to match your existing table name (or the table you wish to create, though this is less of a concern since you could quickly rename the new table from the Operations tab).

Column names

You should also make the first row of your spreadsheet a header with the names of the columns (this can be accomplished by inserting a new row at the top of your spreadsheet). When on the Import screen, select the checkbox for “The first line of the file contains the table column names;” this way your newly imported data will go to the proper columns.


Formulas and calculations will NOT be evaluated, rather, their value from the most recent save will be loaded. Please ensure that all values in the spreadsheet are as needed before importing it.


SQL can be used to make any manipulation on data, it is also useful for restoring backed up data.


XML files exported by phpMyAdmin (version 3.3.0 or later) can now be imported. Structures (databases, tables, views, triggers, etc.) and/or data will be created depending on the contents of the file.

The supported xml schemas are not yet documented in this wiki.


phpMyAdmin can export into text files (even compressed) on your local disk (or a special the webserver $cfg['SaveDir'] folder) in various commonly used formats:


NHibernate file format. Planned versions: Java, Hibernate, PHP PDO, JSON, etc. So the preliminary name is codegen.


Comma separated values format which is often used by spreadsheets or various other programs for export/import.

CSV for Microsoft Excel

This is just preconfigured version of CSV export which can be imported into most English versions of Microsoft Excel. Some localised versions (like “Danish”) are expecting ”;” instead of ”,” as field separator.

Microsoft Word 2000

If you’re using Microsoft Word 2000 or newer (or compatible such as OpenOffice.org), you can use this export.


JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write and it is easy for machines to parse and generate.

Changed in version 4.7.0: The generated JSON structure has been changed in phpMyAdmin 4.7.0 to produce valid JSON data.

The generated JSON is list of objects with following attributes:


Type of given object, can be one of:

Export header containing comment and phpMyAdmin version.
Start of a database marker, containing name of database.
Table data export.

Used in header type and indicates phpMyAdmin version.


Optional textual comment.


Object name - either table or database based on type.


Database name for table type.


Table content for table type.

Sample output:

        "comment": "Export to JSON plugin for PHPMyAdmin",
        "type": "header",
        "version": "4.7.0-dev"
        "name": "cars",
        "type": "database"
        "data": [
                "car_id": "1",
                "description": "Green Chrysler 300",
                "make_id": "5",
                "mileage": "113688",
                "price": "13545.00",
                "transmission": "automatic",
                "yearmade": "2007"
        "database": "cars",
        "name": "cars",
        "type": "table"
        "data": [
                "make": "Chrysler",
                "make_id": "5"
        "database": "cars",
        "name": "makes",
        "type": "table"

If you want to embed table data or structure in LaTeX, this is right choice for you.

LaTeX is a typesetting system that is very suitable for producing scientific and mathematical documents of high typographical quality. It is also suitable for producing all sorts of other documents, from simple letters to complete books. LaTeX uses TeX as its formatting engine. Learn more about TeX and LaTeX on the Comprehensive TeX Archive Network also see the short description od TeX.

The output needs to be embedded into a LaTeX document before it can be rendered, for example in following document:

\title{phpMyAdmin SQL output}
\pdfpagewidth 210mm
\pdfpageheight 297mm

% insert phpMyAdmin LaTeX Dump here


Both tables and databases can be exported in the MediaWiki format, which is used by Wikipedia to display tables. It can export structure, data or both, including table names or headers.

OpenDocument Spreadsheet

Open standard for spreadsheet data, which is being widely adopted. Many recent spreadsheet programs, such as LibreOffice, OpenOffice or Google Docs can handle this format. Additionally, some versions of Microsoft Excel can be adapted to use the OpenDocument Formats through helpers like <http://odf-converter.sourceforge.net/>.

OpenDocument Text

New standard for text data which is being widely addopted. Most recent word processors (such as OpenOffice.org, AbiWord or KWord) can handle this.


For presentation purposes, non editable PDF might be best choice for you.

PHP Array

You can generate a php file which will declare a multidimensional array with the contents of the selected table or database.


Export in SQL can be used to restore your database, thus it is useful for backing up.

The option ‘Maximal length of created query’ seems to be undocumented. But experiments has shown that it splits large extended INSERTS so each one is no bigger than the given number of bytes (or characters?). Thus when importing the file, for large tables you avoid the error “Got a packet bigger than ‘max_allowed_packet’ bytes”.

Data Options

Complete inserts adds the column names to the SQL dump. This parameter improves the readability and reliability of the dump. Adding the column names increases the size of the dump, but when combined with Extended inserts it’s negligible.

Extended inserts combines multiple rows of data into a single INSERT query. This will significantly decrease filesize for large SQL dumps, increases the INSERT speed when imported, and is generally recommended.


Texy! markup format. You can see example on Texy! demo.


Easily parsable export for use with custom scripts.

Changed in version 3.3.0: The XML schema used has changed as of version 3.3.0


YAML is a data serialization format which is both human readable and computationally powerful ( <http://www.yaml.org> ).

Other sources of information

Printed Book

The definitive guide to using phpMyAdmin is the book Mastering phpMyAdmin for Effective MySQL Management by Marc Delisle. You can get information on that book and other officially endorsed books at the phpMyAdmin site.


Third party tutorials and articles which you might find interesting:

Česky (Czech)
Русский (Russian)

FAQ - Frequently Asked Questions

Please have a look at our Link section on the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin’s features and or interface.


1.1 My server is crashing each time a specific action is required or phpMyAdmin sends a blank page or a page full of cryptic characters to my browser, what can I do?

Try to set the $cfg['OBGzip'] directive to false in your config.inc.php file and the zlib.output_compression directive to Off in your php configuration file.

1.2 My Apache server crashes when using phpMyAdmin.

You should first try the latest versions of Apache (and possibly MySQL). If your server keeps crashing, please ask for help in the various Apache support groups.

1.3 (withdrawn).

1.4 Using phpMyAdmin on IIS, I’m displayed the error message: “The specified CGI application misbehaved by not returning a complete set of HTTP headers ...”.

You just forgot to read the install.txt file from the PHP distribution. Have a look at the last message in this PHP bug report #12061 from the official PHP bug database.

1.5 Using phpMyAdmin on IIS, I’m facing crashes and/or many error messages with the HTTP.

This is a known problem with the PHP ISAPI filter: it’s not so stable. Please use instead the cookie authentication mode.

1.6 I can’t use phpMyAdmin on PWS: nothing is displayed!

This seems to be a PWS bug. Filippo Simoncini found a workaround (at this time there is no better fix): remove or comment the DOCTYPE declarations (2 lines) from the scripts libraries/Header.class.php and index.php.

1.7 How can I gzip a dump or a CSV export? It does not seem to work.

This feature is based on the gzencode() PHP function to be more independent of the platform (Unix/Windows, Safe Mode or not, and so on). So, you must have Zlib support (--with-zlib).

1.8 I cannot insert a text file in a table, and I get an error about safe mode being in effect.

Your uploaded file is saved by PHP in the “upload dir”, as defined in php.ini by the variable upload_tmp_dir (usually the system default is /tmp). We recommend the following setup for Apache servers running in safe mode, to enable uploads of files while being reasonably secure:

  • create a separate directory for uploads: mkdir /tmp/php
  • give ownership to the Apache server’s user.group: chown apache.apache /tmp/php
  • give proper permission: chmod 600 /tmp/php
  • put upload_tmp_dir = /tmp/php in php.ini
  • restart Apache

1.9 (withdrawn).

1.10 I’m having troubles when uploading files with phpMyAdmin running on a secure server. My browser is Internet Explorer and I’m using the Apache server.

As suggested by “Rob M” in the phpWizard forum, add this line to your httpd.conf:

SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown

It seems to clear up many problems between Internet Explorer and SSL.

1.11 I get an ‘open_basedir restriction’ while uploading a file from the import tab.

Since version 2.2.4, phpMyAdmin supports servers with open_basedir restrictions. However you need to create temporary directory and configure it as $cfg['TempDir']. The uploaded files will be moved there, and after execution of your SQL commands, removed.

1.12 I have lost my MySQL root password, what can I do?

phpMyAdmin does authenticate against MySQL server you’re using, so to recover from phpMyAdmin password loss, you need to recover at MySQL level.

The MySQL manual explains how to reset the permissions.

If you are using MySQL server installed by your hosting provider, please contact their support to recover the password for you.

1.13 (withdrawn).

1.14 (withdrawn).

1.15 I have problems with mysql.user column names.

In previous MySQL versions, the User and Password columns were named user and password. Please modify your column names to align with current standards.

1.16 I cannot upload big dump files (memory, HTTP or timeout problems).

Starting with version 2.7.0, the import engine has been re–written and these problems should not occur. If possible, upgrade your phpMyAdmin to the latest version to take advantage of the new import features.

The first things to check (or ask your host provider to check) are the values of max_execution_time, upload_max_filesize, memory_limit and post_max_size in the php.ini configuration file. All of these three settings limit the maximum size of data that can be submitted and handled by PHP. Please note that post_max_size needs to be larger than upload_max_filesize. There exist several workarounds if your upload is too big or your hosting provider is unwilling to change the settings:

  • Look at the $cfg['UploadDir'] feature. This allows one to upload a file to the server via scp, ftp, or your favorite file transfer method. PhpMyAdmin is then able to import the files from the temporary directory. More information is available in the Configuration of this document.

  • Using a utility (such as BigDump) to split the files before uploading. We cannot support this or any third party applications, but are aware of users having success with it.

  • If you have shell (command line) access, use MySQL to import the files directly. You can do this by issuing the “source” command from within MySQL:

    source filename.sql;

1.17 Which Database versions does phpMyAdmin support?

For MySQL, versions 5.5 and newer are supported. For older MySQL versions, our Downloads page offers older phpMyAdmin versions (which may have become unsupported).

For MariaDB, versions 5.5 and newer are supported.

1.17a I cannot connect to the MySQL server. It always returns the error message, “Client does not support authentication protocol requested by server; consider upgrading MySQL client”

You tried to access MySQL with an old MySQL client library. The version of your MySQL client library can be checked in your phpinfo() output. In general, it should have at least the same minor version as your server - as mentioned in 1.17 Which Database versions does phpMyAdmin support?. This problem is generally caused by using MySQL version 4.1 or newer. MySQL changed the authentication hash and your PHP is trying to use the old method. The proper solution is to use the mysqli extension with the proper client library to match your MySQL installation. More information (and several workarounds) are located in the MySQL Documentation.

1.18 (withdrawn).

1.19 I can’t run the “display relations” feature because the script seems not to know the font face I’m using!

The TCPDF library we’re using for this feature requires some special files to use font faces. Please refers to the TCPDF manual to build these files.

1.20 I receive an error about missing mysqli and mysql extensions.

To connect to a MySQL server, PHP needs a set of MySQL functions called “MySQL extension”. This extension may be part of the PHP distribution (compiled-in), otherwise it needs to be loaded dynamically. Its name is probably mysqli.so or php_mysqli.dll. phpMyAdmin tried to load the extension but failed. Usually, the problem is solved by installing a software package called “PHP-MySQL” or something similar.

There are currently two interfaces PHP provides as MySQL extensions - mysql and mysqli. The mysqli is tried first, because it’s the best one.

This problem can be also caused by wrong paths in the php.ini or using wrong php.ini.

Make sure that the extension files do exist in the folder which the extension_dir points to and that the corresponding lines in your php.ini are not commented out (you can use phpinfo() to check current setup):


; Directory in which the loadable extensions (modules) reside.
extension_dir = "C:/Apache2/modules/php/ext"

The php.ini can be loaded from several locations (especially on Windows), so please check you’re updating the correct one. If using Apache, you can tell it to use specific path for this file using PHPIniDir directive:

LoadFile "C:/php/php5ts.dll"
LoadModule php5_module "C:/php/php5apache2_2.dll"
<IfModule php5_module>
    PHPIniDir "C:/PHP"
       AddType text/html .php
       AddHandler application/x-httpd-php .php

In some rare cases this problem can be also caused by other extensions loaded in PHP which prevent MySQL extensions to be loaded. If anything else fails, you can try commenting out extensions for other databses from php.ini.

1.22 I don’t see the “Location of text file” field, so I cannot upload.

This is most likely because in php.ini, your file_uploads parameter is not set to “on”.

1.23 I’m running MySQL on a Win32 machine. Each time I create a new table the table and column names are changed to lowercase!

This happens because the MySQL directive lower_case_table_names defaults to 1 (ON) in the Win32 version of MySQL. You can change this behavior by simply changing the directive to 0 (OFF): Just edit your my.ini file that should be located in your Windows directory and add the following line to the group [mysqld]:

set-variable = lower_case_table_names=0


Forcing this variable to 0 with –lower-case-table-names=0 on a case-insensitive filesystem and access MyISAM tablenames using different lettercases, index corruption may result.

Next, save the file and restart the MySQL service. You can always check the value of this directive using the query

SHOW VARIABLES LIKE 'lower_case_table_names';

1.24 (withdrawn).

1.25 I am running Apache with mod_gzip- on Windows XP, and I get problems, such as undefined variables when I run a SQL query.

A tip from Jose Fandos: put a comment on the following two lines in httpd.conf, like this:

# mod_gzip_item_include file \.php$
# mod_gzip_item_include mime "application/x-httpd-php.*"

as this version of mod_gzip on Apache (Windows) has problems handling PHP scripts. Of course you have to restart Apache.

1.26 I just installed phpMyAdmin in my document root of IIS but I get the error “No input file specified” when trying to run phpMyAdmin.

This is a permission problem. Right-click on the phpmyadmin folder and choose properties. Under the tab Security, click on “Add” and select the user “IUSR_machine” from the list. Now set his permissions and it should work.

1.27 I get empty page when I want to view huge page (eg. db_structure.php with plenty of tables).

This was caused by a PHP bug that occur when GZIP output buffering is enabled. If you turn off it (by $cfg['OBGzip'] in config.inc.php), it should work. This bug will has been fixed in PHP 5.0.0.

1.28 My MySQL server sometimes refuses queries and returns the message ‘Errorcode: 13’. What does this mean?

This can happen due to a MySQL bug when having database / table names with upper case characters although lower_case_table_names is set to 1. To fix this, turn off this directive, convert all database and table names to lower case and turn it on again. Alternatively, there’s a bug-fix available starting with MySQL 3.23.56 / 4.0.11-gamma.

1.29 When I create a table or modify a column, I get an error and the columns are duplicated.

It is possible to configure Apache in such a way that PHP has problems interpreting .php files.

The problems occur when two different (and conflicting) set of directives are used:

SetOutputFilter PHP
SetInputFilter PHP


AddType application/x-httpd-php .php

In the case we saw, one set of directives was in /etc/httpd/conf/httpd.conf, while the other set was in /etc/httpd/conf/addon-modules/php.conf. The recommended way is with AddType, so just comment out the first set of lines and restart Apache:

#SetOutputFilter PHP
#SetInputFilter PHP

1.30 I get the error “navigation.php: Missing hash”.

This problem is known to happen when the server is running Turck MMCache but upgrading MMCache to version 2.3.21 solves the problem.

1.31 Which PHP versions does phpMyAdmin support?

Since release 4.5, phpMyAdmin supports only PHP 5.5 and newer. Since release 4.1 phpMyAdmin supports only PHP 5.3 and newer. For PHP 5.2 you can use 4.0.x releases.

PHP 7 is supported since phpMyAdmin 4.6, PHP 7.1 is supported since 4.6.5.

phpMyAdmin also works fine with HHVM.

1.32 Can I use HTTP authentication with IIS?

Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in ISAPI mode under IIS 5.1.

  1. In your php.ini file, set cgi.rfc2616_headers = 0
  2. In Web Site Properties -> File/Directory Security -> Anonymous Access dialog box, check the Anonymous access checkbox and uncheck any other checkboxes (i.e. uncheck Basic authentication, Integrated Windows authentication, and Digest if it’s enabled.) Click OK.
  3. In Custom Errors, select the range of 401;1 through 401;5 and click the Set to Default button.

See also

RFC 2616

1.33 (withdrawn).

1.34 Can I access directly to database or table pages?

Yes. Out of the box, you can use URL like http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For server you use the server number which refers to the order of the server paragraph in config.inc.php. Table and script parts are optional. If you want http://server/phpMyAdmin/database[/table][/script] URL, you need to do some configuration. Following lines apply only for Apache web server. First make sure, that you have enabled some features within global configuration. You need Options SymLinksIfOwnerMatch and AllowOverride FileInfo enabled for directory where phpMyAdmin is installed and you need mod_rewrite to be enabled. Then you just need to create following .htaccess file in root folder of phpMyAdmin installation (don’t forget to change directory name inside of it):

RewriteEngine On
RewriteBase /path_to_phpMyAdmin
RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]

1.35 Can I use HTTP authentication with Apache CGI?

Yes. However you need to pass authentication variable to CGI using following rewrite rule:

RewriteEngine On
RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]

1.36 I get an error “500 Internal Server Error”.

There can be many explanations to this and a look at your server’s error log file might give a clue.

1.38 Can I use phpMyAdmin on a server on which Suhosin is enabled?

Yes but the default configuration values of Suhosin are known to cause problems with some operations, for example editing a table with many columns and no primary key or with textual primary key.

Suhosin configuration might lead to malfunction in some cases and it can not be fully avoided as phpMyAdmin is kind of application which needs to transfer big amounts of columns in single HTTP request, what is something what Suhosin tries to prevent. Generally all suhosin.request.*, suhosin.post.* and suhosin.get.* directives can have negative effect on phpMyAdmin usability. You can always find in your error logs which limit did cause dropping of variable, so you can diagnose the problem and adjust matching configuration variable.

The default values for most Suhosin configuration options will work in most scenarios, however you might want to adjust at least following parameters:

To further improve security, we also recommend these modifications:

You can also disable the warning using the $cfg['SuhosinDisableWarning'].

1.39 When I try to connect via https, I can log in, but then my connection is redirected back to http. What can cause this behavior?

This is caused by the fact that PHP scripts have no knowledge that the site is using https. Depending on used webserver, you should configure it to let PHP know about URL and scheme used to access it.

For example in Apache ensure that you have enabled SSLOptions and StdEnvVars in the configuration.

1.41 When I view a database and ask to see its privileges, I get an error about an unknown column.

The MySQL server’s privilege tables are not up to date, you need to run the mysql_upgrade command on the server.

1.42 How can I prevent robots from accessing phpMyAdmin?

You can add various rules to .htaccess to filter access based on user agent field. This is quite easy to circumvent, but could prevent at least some robots accessing your installation.

RewriteEngine on

# Allow only GET and POST verbs

# Ban Typical Vulnerability Scanners and others
# Kick out Script Kiddies
RewriteCond %{HTTP_USER_AGENT} ^(java|curl|wget).* [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^.*(libwww-perl|curl|wget|python|nikto|wkito|pikto|scan|acunetix).* [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^.*(winhttp|HTTrack|clshttp|archiver|loader|email|harvest|extract|grab|miner).* [NC,OR]

# Ban Search Engines, Crawlers to your administrative panel
# No reasons to access from bots
# Ultimately Better than the useless robots.txt
# Did google respect robots.txt?
# Try google: intitle:phpMyAdmin intext:"Welcome to phpMyAdmin *.*.*" intext:"Log in" -wiki -forum -forums -questions intext:"Cookies must be enabled"
RewriteCond %{HTTP_USER_AGENT} ^.*(AdsBot-Google|ia_archiver|Scooter|Ask.Jeeves|Baiduspider|Exabot|FAST.Enterprise.Crawler|FAST-WebCrawler|www\.neomo\.de|Gigabot|Mediapartners-Google|Google.Desktop|Feedfetcher-Google|Googlebot|heise-IT-Markt-Crawler|heritrix|ibm.com\cs/crawler|ICCrawler|ichiro|MJ12bot|MetagerBot|msnbot-NewsBlogs|msnbot|msnbot-media|NG-Search|lucene.apache.org|NutchCVS|OmniExplorer_Bot|online.link.validator|psbot0|Seekbot|Sensis.Web.Crawler|SEO.search.Crawler|Seoma.\[SEO.Crawler\]|SEOsearch|Snappy|www.urltrends.com|www.tkl.iis.u-tokyo.ac.jp/~crawler|SynooBot|crawleradmin.t-info@telekom.de|TurnitinBot|voyager|W3.SiteSearch.Crawler|W3C-checklink|W3C_Validator|www.WISEnutbot.com|yacybot|Yahoo-MMCrawler|Yahoo\!.DE.Slurp|Yahoo\!.Slurp|YahooSeeker).* [NC]
RewriteRule .* - [F]

1.43 Why can’t I display the structure of my table containing hundreds of columns?

Because your PHP’s memory_limit is too low; adjust it in php.ini.

1.44 How can I reduce the installed size of phpMyAdmin on disk?

Some users have requested to be able to reduce the size of the phpMyAdmin installation. This is not recommended and could lead to confusion over missing features, but can be done. A list of files and corresponding functionality which degrade gracefully when removed include:

  • ./vendor/tecnickcom/tcpdf folder (exporting to PDF)
  • ./locale/ folder, or unused subfolders (interface translations)
  • Any unused themes in ./themes/
  • ./js/jquery/src/ (included for licensing reasons)
  • ./js/line_counts.php
  • ./doc/ (documentation)
  • ./setup/ (setup script)
  • ./examples/
  • ./sql/ (SQL scripts to configure advanced functionality)
  • ./js/openlayers/ (GIS visualization)


2.1 The error message “Warning: Cannot add header information - headers already sent by ...” is displayed, what’s the problem?

Edit your config.inc.php file and ensure there is nothing (I.E. no blank lines, no spaces, no characters...) neither before the <?php tag at the beginning, neither after the ?> tag at the end. We also got a report from a user under IIS, that used a zipped distribution kit: the file libraries/Config.php contained an end-of-line character (hex 0A) at the end; removing this character cleared his errors.

2.2 phpMyAdmin can’t connect to MySQL. What’s wrong?

Either there is an error with your PHP setup or your username/password is wrong. Try to make a small script which uses mysql_connect and see if it works. If it doesn’t, it may be you haven’t even compiled MySQL support into PHP.

2.3 The error message “Warning: MySQL Connection Failed: Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (111) ...” is displayed. What can I do?

The error message can also be: Error #2002 - The server is not responding (or the local MySQL server’s socket is not correctly configured).

First, you need to determine what socket is being used by MySQL. To do this, connect to your server and go to the MySQL bin directory. In this directory there should be a file named mysqladmin. Type ./mysqladmin variables, and this should give you a bunch of info about your MySQL server, including the socket (/tmp/mysql.sock, for example). You can also ask your ISP for the connection info or, if you’re hosting your own, connect from the ‘mysql’ command-line client and type ‘status’ to get the connection type and socket or port number.

Then, you need to tell PHP to use this socket. You can do this for all PHP in the php.ini or for phpMyAdmin only in the config.inc.php. For example: $cfg['Servers'][$i]['socket'] Please also make sure that the permissions of this file allow to be readable by your webserver.

On my RedHat-Box the socket of MySQL is /var/lib/mysql/mysql.sock. In your php.ini you will find a line

mysql.default_socket = /tmp/mysql.sock

change it to

mysql.default_socket = /var/lib/mysql/mysql.sock

Then restart apache and it will work.

Have also a look at the corresponding section of the MySQL documentation.

2.4 Nothing is displayed by my browser when I try to run phpMyAdmin, what can I do?

Try to set the $cfg['OBGzip'] directive to false in the phpMyAdmin configuration file. It helps sometime. Also have a look at your PHP version number: if it contains “b” or “alpha” it means you’re running a testing version of PHP. That’s not a so good idea, please upgrade to a plain revision.

2.6 I get an “Access denied for user: 'root@localhost‘ (Using password: YES)”-error when trying to access a MySQL-Server on a host which is port-forwarded for my localhost.

When you are using a port on your localhost, which you redirect via port-forwarding to another host, MySQL is not resolving the localhost as expected. Erik Wasser explains: The solution is: if your host is “localhost” MySQL (the command line tool mysql as well) always tries to use the socket connection for speeding up things. And that doesn’t work in this configuration with port forwarding. If you enter “” as hostname, everything is right and MySQL uses the TCP connection.

2.7 Using and creating themes

Themes are configured with $cfg['ThemeManager'] and $cfg['ThemeDefault']. Under ./themes/, you should not delete the directory pmahomme or its underlying structure, because this is the system theme used by phpMyAdmin. pmahomme contains all images and styles, for backwards compatibility and for all themes that would not include images or css-files. If $cfg['ThemeManager'] is enabled, you can select your favorite theme on the main page. Your selected theme will be stored in a cookie.

To create a theme:

  • make a new subdirectory (for example “your_theme_name”) under ./themes/.
  • copy the files and directories from pmahomme to “your_theme_name”
  • edit the css-files in “your_theme_name/css”
  • put your new images in “your_theme_name/img”
  • edit layout.inc.php in “your_theme_name”
  • edit info.inc.php in “your_theme_name” to contain your chosen theme name, that will be visible in user interface
  • make a new screenshot of your theme and save it under “your_theme_name/screen.png”

In theme directory there is file info.inc.php which contains theme verbose name, theme generation and theme version. These versions and generations are enumerated from 1 and do not have any direct dependence on phpMyAdmin version. Themes within same generation should be backwards compatible - theme with version 2 should work in phpMyAdmin requiring version 1. Themes with different generation are incompatible.

If you do not want to use your own symbols and buttons, remove the directory “img” in “your_theme_name”. phpMyAdmin will use the default icons and buttons (from the system-theme pmahomme).

2.8 I get “Missing parameters” errors, what can I do?

Here are a few points to check:

  • In config.inc.php, try to leave the $cfg['PmaAbsoluteUri'] directive empty. See also 4.7 Authentication window is displayed more than once, why?.
  • Maybe you have a broken PHP installation or you need to upgrade your Zend Optimizer. See <https://bugs.php.net/bug.php?id=31134>.
  • If you are using Hardened PHP with the ini directive varfilter.max_request_variables set to the default (200) or another low value, you could get this error if your table has a high number of columns. Adjust this setting accordingly. (Thanks to Klaus Dorninger for the hint).
  • In the php.ini directive arg_separator.input, a value of ”;” will cause this error. Replace it with “&;”.
  • If you are using Suhosin, you might want to increase request limits.
  • The directory specified in the php.ini directive session.save_path does not exist or is read-only (this can be caused by bug in the PHP installer).

2.9 Seeing an upload progress bar

To be able to see a progress bar during your uploads, your server must have the APC extension, the uploadprogress one, or you must be running PHP 5.4.0 or higher. Moreover, the JSON extension has to be enabled in your PHP.

If using APC, you must set apc.rfc1867 to on in your php.ini.

If using PHP 5.4.0 or higher, you must set session.upload_progress.enabled to 1 in your php.ini. However, starting from phpMyAdmin version 4.0.4, session-based upload progress has been temporarily deactivated due to its problematic behavior.

See also

RFC 1867

Known limitations

3.1 When using HTTP authentication, a user who logged out can not log in again in with the same nick.

This is related to the authentication mechanism (protocol) used by phpMyAdmin. To bypass this problem: just close all the opened browser windows and then go back to phpMyAdmin. You should be able to log in again.

3.2 When dumping a large table in compressed mode, I get a memory limit error or a time limit error.

Compressed dumps are built in memory and because of this are limited to php’s memory limit. For gzip/bzip2 exports this can be overcome since 2.5.4 using $cfg['CompressOnFly'] (enabled by default). zip exports can not be handled this way, so if you need zip files for larger dump, you have to use another way.

3.3 With InnoDB tables, I lose foreign key relationships when I rename a table or a column.

This is an InnoDB bug, see <https://bugs.mysql.com/bug.php?id=21704>.

3.4 I am unable to import dumps I created with the mysqldump tool bundled with the MySQL server distribution.

The problem is that older versions of mysqldump created invalid comments like this:

-- MySQL dump 8.22
-- Host: localhost Database: database
-- Server version 3.23.54

The invalid part of the code is the horizontal line made of dashes that appears once in every dump created with mysqldump. If you want to run your dump you have to turn it into valid MySQL. This means, you have to add a whitespace after the first two dashes of the line or add a # before it: -- ------------------------------------------------------- or #---------------------------------------------------------

3.5 When using nested folders, multiple hierarchies are displayed in a wrong manner.

Please note that you should not use the separating string multiple times without any characters between them, or at the beginning/end of your table name. If you have to, think about using another TableSeparator or disabling that feature.

3.6 (withdrawn).

3.7 I have table with many (100+) columns and when I try to browse table I get series of errors like “Warning: unable to parse url”. How can this be fixed?

Your table neither have a primary key nor an unique key, so we must use a long expression to identify this row. This causes problems to parse_url function. The workaround is to create a primary key or unique key.

3.8 I cannot use (clickable) HTML-forms in columns where I put a MIME-Transformation onto!

Due to a surrounding form-container (for multi-row delete checkboxes), no nested forms can be put inside the table where phpMyAdmin displays the results. You can, however, use any form inside of a table if keep the parent form-container with the target to tbl_row_delete.php and just put your own input-elements inside. If you use a custom submit input field, the form will submit itself to the displaying page again, where you can validate the $HTTP_POST_VARS in a transformation. For a tutorial on how to effectively use transformations, see our Link section on the official phpMyAdmin-homepage.

3.9 I get error messages when using “–sql_mode=ANSI” for the MySQL server.

When MySQL is running in ANSI-compatibility mode, there are some major differences in how SQL is structured (see <https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html>). Most important of all, the quote-character (”) is interpreted as an identifier quote character and not as a string quote character, which makes many internal phpMyAdmin operations into invalid SQL statements. There is no workaround to this behaviour. News to this item will be posted in issue #7383.

3.10 Homonyms and no primary key: When the results of a SELECT display more that one column with the same value (for example SELECT lastname from employees where firstname like 'A%' and two “Smith” values are displayed), if I click Edit I cannot be sure that I am editing the intended row.

Please make sure that your table has a primary key, so that phpMyAdmin can use it for the Edit and Delete links.

3.11 The number of rows for InnoDB tables is not correct.

phpMyAdmin uses a quick method to get the row count, and this method only returns an approximate count in the case of InnoDB tables. See $cfg['MaxExactCount'] for a way to modify those results, but this could have a serious impact on performance. However, one can easily replace the approximate row count with exact count by simply clicking on the approximate count. This can also be done for all tables at once by clicking on the rows sum displayed at the bottom.

3.12 (withdrawn).

3.13 I get an error when entering USE followed by a db name containing an hyphen.

The tests I have made with MySQL 5.1.49 shows that the API does not accept this syntax for the USE command.

3.14 I am not able to browse a table when I don’t have the right to SELECT one of the columns.

This has been a known limitation of phpMyAdmin since the beginning and it’s not likely to be solved in the future.

3.15 (withdrawn).

3.16 (withdrawn).

3.17 (withdrawn).

3.18 When I import a CSV file that contains multiple tables, they are lumped together into a single table.

There is no reliable way to differentiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.

3.19 When I import a file and have phpMyAdmin determine the appropriate data structure it only uses int, decimal, and varchar types.

Currently, the import type-detection system can only assign these MySQL types to columns. In future, more will likely be added but for the time being you will have to edit the structure to your liking post-import. Also, you should note the fact that phpMyAdmin will use the size of the largest item in any given column as the column size for the appropriate type. If you know you will be adding larger items to that column then you should manually adjust the column sizes accordingly. This is done for the sake of efficiency.

3.20 After upgrading, some bookmarks are gone or their content cannot be shown.

At some point, the character set used to store bookmark content has changed. It’s better to recreate your bookmark from the newer phpMyAdmin version.

3.21 I am unable to log in with a username containing unicode characters such as á.

This can happen if MySQL server is not configured to use utf-8 as default charset. This is a limitation of how PHP and the MySQL server interact; there is no way for PHP to set the charset before authenticating.

ISPs, multi-user installations

4.1 I’m an ISP. Can I setup one central copy of phpMyAdmin or do I need to install it for each customer?

Since version 2.0.3, you can setup a central copy of phpMyAdmin for all your users. The development of this feature was kindly sponsored by NetCologne GmbH. This requires a properly setup MySQL user management and phpMyAdmin HTTP or cookie authentication.

4.2 What’s the preferred way of making phpMyAdmin secure against evil access?

This depends on your system. If you’re running a server which cannot be accessed by other people, it’s sufficient to use the directory protection bundled with your webserver (with Apache you can use .htaccess files, for example). If other people have telnet access to your server, you should use phpMyAdmin’s HTTP or cookie authentication features.


  • Your config.inc.php file should be chmod 660.
  • All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy is a user whose password is only known to you, and apache is the group under which Apache runs.
  • Follow security recommendations for PHP and your webserver.

4.3 I get errors about not being able to include a file in /lang or in /libraries.

Check php.ini, or ask your sysadmin to check it. The include_path must contain ”.” somewhere in it, and open_basedir, if used, must contain ”.” and ”./lang” to allow normal operation of phpMyAdmin.

4.4 phpMyAdmin always gives “Access denied” when using HTTP authentication.

This could happen for several reasons:

4.5 Is it possible to let users create their own databases?

Starting with 2.2.5, in the user management page, you can enter a wildcard database name for a user (for example “joe%”), and put the privileges you want. For example, adding SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER would let a user create/manage his/her database(s).

4.6 How can I use the Host-based authentication additions?

If you have existing rules from an old .htaccess file, you can take them and add a username between the 'deny'/'allow' and 'from' strings. Using the username wildcard of '%' would be a major benefit here if your installation is suited to using it. Then you can just add those updated lines into the $cfg['Servers'][$i]['AllowDeny']['rules'] array.

If you want a pre-made sample, you can try this fragment. It stops the ‘root’ user from logging in from any networks other than the private network IP blocks.

//block root from logging in except from the private networks
$cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
$cfg['Servers'][$i]['AllowDeny']['rules'] = array(
    'deny root from all',
    'allow root from localhost',
    'allow root from',
    'allow root from',
    'allow root from',

4.7 Authentication window is displayed more than once, why?

This happens if you are using a URL to start phpMyAdmin which is different than the one set in your $cfg['PmaAbsoluteUri']. For example, a missing “www”, or entering with an IP address while a domain name is defined in the config file.

4.8 Which parameters can I use in the URL that starts phpMyAdmin?

When starting phpMyAdmin, you can use the db, pma_username, pma_password and server parameters. This last one can contain either the numeric host index (from $i of the configuration file) or one of the host names present in the configuration file. Using pma_username and pma_password has been tested along with the usage of ‘cookie’ auth_type.

For example direct login URL can be constructed as https://example.com/phpmyadmin/?pma_username=user&pma_password=password.

Browsers or client OS

5.1 I get an out of memory error, and my controls are non-functional, when trying to create a table with more than 14 columns.

We could reproduce this problem only under Win98/98SE. Testing under WinNT4 or Win2K, we could easily create more than 60 columns. A workaround is to create a smaller number of columns, then come back to your table properties and add the other columns.

5.2 With Xitami 2.5b4, phpMyAdmin won’t process form fields.

This is not a phpMyAdmin problem but a Xitami known bug: you’ll face it with each script/website that use forms. Upgrade or downgrade your Xitami server.

5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).

With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that the proposed file name for the dump is always ‘tbl_dump.php’. The bzip2 dumps don’t seem to work. With Konqueror 2.2.1: plain dumps work; zip dumps are placed into the user’s temporary directory, so they must be moved before closing Konqueror, or else they disappear. gzip dumps give an error message. Testing needs to be done for Konqueror 2.2.2.

5.5 (withdrawn).

5.6 (withdrawn).

5.7 I refresh (reload) my browser, and come back to the welcome page.

Some browsers support right-clicking into the frame you want to refresh, just do this in the right frame.

5.8 With Mozilla 0.9.7 I have problems sending a query modified in the query box.

Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future Mozilla versions.

5.9 With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can’t type a whitespace in the SQL-Query edit area: the page scrolls down.

This is a Mozilla bug (see bug #26882 at BugZilla).

5.10 (withdrawn).

5.11 Extended-ASCII characters like German umlauts are displayed wrong.

Please ensure that you have set your browser’s character set to the one of the language file you have selected on phpMyAdmin’s start page. Alternatively, you can try the auto detection mode that is supported by the recent versions of the most browsers.

5.12 Mac OS X Safari browser changes special characters to ”?”.

This issue has been reported by a Mac OS X user, who adds that Chimera, Netscape and Mozilla do not have this problem.

5.13 (withdrawn)

5.14 (withdrawn)

5.15 (withdrawn)

5.16 With Internet Explorer, I get “Access is denied” Javascript errors. Or I cannot make phpMyAdmin work under Windows.

Please check the following points:

  • Maybe you have defined your $cfg['PmaAbsoluteUri'] setting in config.inc.php to an IP address and you are starting phpMyAdmin with a URL containing a domain name, or the reverse situation.
  • Security settings in IE and/or Microsoft Security Center are too high, thus blocking scripts execution.
  • The Windows Firewall is blocking Apache and MySQL. You must allow HTTP ports (80 or 443) and MySQL port (usually 3306) in the “in” and “out” directions.

5.17 With Firefox, I cannot delete rows of data or drop a database.

Many users have confirmed that the Tabbrowser Extensions plugin they installed in their Firefox is causing the problem.

5.18 (withdrawn)

5.19 I get JavaScript errors in my browser.

Issues have been reported with some combinations of browser extensions. To troubleshoot, disable all extensions then clear your browser cache to see if the problem goes away.

5.20 I get errors about violating Content Security Policy.

If you see errors like:

Refused to apply inline style because it violates the following Content Security Policy directive

This is usually caused by some software, which wrongly rewrites Content Security Policy headers. Usually this is caused by antivirus proxy or browser addons which are causing such errors.

If you see these errors, try disabling the HTTP proxy in antivirus or disable the Content Security Policy rewriting in it. If that doesn’t help, try disabling browser extensions.

Alternatively it can be also server configuration issue (if the webserver is configured to emit Content Security Policy headers, they can override the ones from phpMyAdmin).

Programs known to cause these kind of errors:

  • Kaspersky Internet Security

5.21 I get errors about potentially unsafe operation when browsing table or executing SQL query.

If you see errors like:

A potentially unsafe operation has been detected in your request to this site.

This is usually caused by web application firewall doing requests filtering. It tries to prevent SQL injection, however phpMyAdmin is tool designed to execute SQL queries, thus it makes it unusable.

Please whitelist phpMyAdmin scripts from the web application firewall settings or disable it completely for phpMyAdmin path.

Programs known to cause these kind of errors:

  • Wordfence Web Application Firewall

Using phpMyAdmin

6.1 I can’t insert new rows into a table / I can’t create a table - MySQL brings up a SQL error.

Examine the SQL error with care. Often the problem is caused by specifying a wrong column-type. Common errors include:

  • Using VARCHAR without a size argument
  • Using TEXT or BLOB with a size argument

Also, look at the syntax chapter in the MySQL manual to confirm that your syntax is correct.

6.2 When I create a table, I set an index for two columns and phpMyAdmin generates only one index with those two columns.

This is the way to create a multi-columns index. If you want two indexes, create the first one when creating the table, save, then display the table properties and click the Index link to create the other index.

6.3 How can I insert a null value into my table?

Since version 2.2.3, you have a checkbox for each column that can be null. Before 2.2.3, you had to enter “null”, without the quotes, as the column’s value. Since version 2.5.5, you have to use the checkbox to get a real NULL value, so if you enter “NULL” this means you want a literal NULL in the column, and not a NULL value (this works in PHP4).

6.4 How can I backup my database or table?

Click on a database or table name in the navigation panel, the properties will be displayed. Then on the menu, click “Export”, you can dump the structure, the data, or both. This will generate standard SQL statements that can be used to recreate your database/table. You will need to choose “Save as file”, so that phpMyAdmin can transmit the resulting dump to your station. Depending on your PHP configuration, you will see options to compress the dump. See also the $cfg['ExecTimeLimit'] configuration variable. For additional help on this subject, look for the word “dump” in this document.

6.5 How can I restore (upload) my database or table using a dump? How can I run a ”.sql” file?

Click on a database name in the navigation panel, the properties will be displayed. Select “Import” from the list of tabs in the right–hand frame (or “SQL” if your phpMyAdmin version is previous to 2.7.0). In the “Location of the text file” section, type in the path to your dump filename, or use the Browse button. Then click Go. With version 2.7.0, the import engine has been re–written, if possible it is suggested that you upgrade to take advantage of the new features. For additional help on this subject, look for the word “upload” in this document.

Note: For errors while importing of dumps exported from older MySQL versions to newer MySQL versions, please check 6.41 I get import errors while importing the dumps exported from older MySQL versions (pre-5.7.6) into newer MySQL versions (5.7.7+), but they work fine when imported back on same older versions ?.

6.6 How can I use the relation table in Query-by-example?

Here is an example with the tables persons, towns and countries, all located in the database “mydb”. If you don’t have a pma__relation table, create it as explained in the configuration section. Then create the example tables:

CREATE TABLE REL_countries (
country_code char(1) NOT NULL default '',
description varchar(10) NOT NULL default '',
PRIMARY KEY (country_code)

INSERT INTO REL_countries VALUES ('C', 'Canada');

id tinyint(4) NOT NULL auto_increment,
person_name varchar(32) NOT NULL default '',
town_code varchar(5) default '0',
country_code char(1) NOT NULL default '',

INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');

town_code varchar(5) NOT NULL default '0',
description varchar(30) NOT NULL default '',
PRIMARY KEY (town_code)

INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
INSERT INTO REL_towns VALUES ('M', 'Montréal');

To setup appropriate links and display information:

  • on table “REL_persons” click Structure, then Relation view
  • for “town_code”, choose from dropdowns, “mydb”, “REL_towns”, “code” for foreign database, table and column respectively
  • for “country_code”, choose from dropdowns, “mydb”, “REL_countries”, “country_code” for foreign database, table and column respectively
  • on table “REL_towns” click Structure, then Relation view
  • in “Choose column to display”, choose “description”
  • repeat the two previous steps for table “REL_countries”

Then test like this:

  • Click on your db name in the navigation panel
  • Choose “Query”
  • Use tables: persons, towns, countries
  • Click “Update query”
  • In the columns row, choose persons.person_name and click the “Show” tickbox
  • Do the same for towns.description and countries.descriptions in the other 2 columns
  • Click “Update query” and you will see in the query box that the correct joins have been generated
  • Click “Submit query”

6.7 How can I use the “display column” feature?

Starting from the previous example, create the pma__table_info as explained in the configuration section, then browse your persons table, and move the mouse over a town code or country code. See also 6.21 In edit/insert mode, how can I see a list of possible values for a column, based on some foreign table? for an additional feature that “display column” enables: drop-down list of possible values.

6.8 How can I produce a PDF schema of my database?

First the configuration variables “relation”, “table_coords” and “pdf_pages” have to be filled in. Then you need to think about your schema layout. Which tables will go on which pages?

  • Select your database in the navigation panel.
  • Choose “Operations” in the navigation bar at the top.
  • Choose “Edit PDF Pages” near the bottom of the page.
  • Enter a name for the first PDF page and click Go. If you like, you can use the “automatic layout,” which will put all your linked tables onto the new page.
  • Select the name of the new page (making sure the Edit radio button is selected) and click Go.
  • Select a table from the list, enter its coordinates and click Save. Coordinates are relative; your diagram will be automatically scaled to fit the page. When initially placing tables on the page, just pick any coordinates – say, 50x50. After clicking Save, you can then use the 6.28 How can I easily edit relational schema for export? to position the element correctly.
  • When you’d like to look at your PDF, first be sure to click the Save button beneath the list of tables and coordinates, to save any changes you made there. Then scroll all the way down, select the PDF options you want, and click Go.
  • Internet Explorer for Windows may suggest an incorrect filename when you try to save a generated PDF. When saving a generated PDF, be sure that the filename ends in ”.pdf”, for example “schema.pdf”. Browsers on other operating systems, and other browsers on Windows, do not have this problem.

See also


6.9 phpMyAdmin is changing the type of one of my columns!

No, it’s MySQL that is doing silent column type changing.

6.10 When creating a privilege, what happens with underscores in the database name?

If you do not put a backslash before the underscore, this is a wildcard grant, and the underscore means “any character”. So, if the database name is “john_db”, the user would get rights to john1db, john2db ... If you put a backslash before the underscore, it means that the database name will have a real underscore.

6.11 What is the curious symbol ø in the statistics pages?

It means “average”.

6.12 I want to understand some Export options.


  • “Add DROP TABLE” will add a line telling MySQL to drop the table, if it already exists during the import. It does NOT drop the table after your export, it only affects the import file.
  • “If Not Exists” will only create the table if it doesn’t exist. Otherwise, you may get an error if the table name exists but has a different structure.
  • “Add AUTO_INCREMENT value” ensures that AUTO_INCREMENT value (if any) will be included in backup.
  • “Enclose table and column names with backquotes” ensures that column and table names formed with special characters are protected.
  • “Add into comments” includes column comments, relations, and MIME types set in the pmadb in the dump as SQL comments (/* xxx */).


  • “Complete inserts” adds the column names on every INSERT command, for better documentation (but resulting file is bigger).
  • “Extended inserts” provides a shorter dump file by using only once the INSERT verb and the table name.
  • “Delayed inserts” are best explained in the MySQL manual - INSERT DELAYED Syntax.
  • “Ignore inserts” treats errors as a warning instead. Again, more info is provided in the MySQL manual - INSERT Syntax, but basically with this selected, invalid values are adjusted and inserted rather than causing the entire statement to fail.

6.13 I would like to create a database with a dot in its name.

This is a bad idea, because in MySQL the syntax “database.table” is the normal way to reference a database and table name. Worse, MySQL will usually let you create a database with a dot, but then you cannot work with it, nor delete it.

6.14 (withdrawn).

6.15 I want to add a BLOB column and put an index on it, but MySQL says “BLOB column ‘...’ used in key specification without a key length”.

The right way to do this, is to create the column without any indexes, then display the table structure and use the “Create an index” dialog. On this page, you will be able to choose your BLOB column, and set a size to the index, which is the condition to create an index on a BLOB column.

6.16 How can I simply move in page with plenty editing fields?

You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages with many editing fields (table structure changes, row editing, etc.).

6.17 Transformations: I can’t enter my own mimetype! What is this feature then useful for?

Defining mimetypes is of no use if you can’t put transformations on them. Otherwise you could just put a comment on the column. Because entering your own mimetype will cause serious syntax checking issues and validation, this introduces a high-risk false- user-input situation. Instead you have to initialize mimetypes using functions or empty mimetype definitions.

Plus, you have a whole overview of available mimetypes. Who knows all those mimetypes by heart so he/she can enter it at will?

6.18 Bookmarks: Where can I store bookmarks? Why can’t I see any bookmarks below the query box? What are these variables for?

You need to have configured the phpMyAdmin configuration storage for using bookmarks feature. Once you have done that, you can use bookmarks in the SQL tab.

See also


6.19 How can I create simple LATEX document to include exported table?

You can simply include table in your LATEX documents, minimal sample document should look like following one (assuming you have table exported in file table.tex):

\documentclass{article} % or any class you want
\usepackage{longtable}  % for displaying table
\begin{document}        % start of document
\include{table}         % including exported table
\end{document}          % end of document

6.20 I see a lot of databases which are not mine, and cannot access them.

You have one of these global privileges: CREATE TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also enable users to see all the database names. So if your users do not need those privileges, you can remove them and their databases list will shorten.

6.21 In edit/insert mode, how can I see a list of possible values for a column, based on some foreign table?

You have to setup appropriate links between the tables, and also setup the “display column” in the foreign table. See 6.6 How can I use the relation table in Query-by-example? for an example. Then, if there are 100 values or less in the foreign table, a drop-down list of values will be available. You will see two lists of values, the first list containing the key and the display column, the second list containing the display column and the key. The reason for this is to be able to type the first letter of either the key or the display column. For 100 values or more, a distinct window will appear, to browse foreign key values and choose one. To change the default limit of 100, see $cfg['ForeignKeyMaxLimit'].

6.22 Bookmarks: Can I execute a default bookmark automatically when entering Browse mode for a table?

Yes. If a bookmark has the same label as a table name and it’s not a public bookmark, it will be executed.

See also


6.23 Export: I heard phpMyAdmin can export Microsoft Excel files?

You can use CSV for Microsoft Excel, which works out of the box.

Changed in version 3.4.5: Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel version 97 and newer was dropped.

6.24 Now that phpMyAdmin supports native MySQL 4.1.x column comments, what happens to my column comments stored in pmadb?

Automatic migration of a table’s pmadb-style column comments to the native ones is done whenever you enter Structure page for this table.

6.25 (withdrawn).

6.26 How can I select a range of rows?

Click the first row of the range, hold the shift key and click the last row of the range. This works everywhere you see rows, for example in Browse mode or on the Structure page.

6.27 What format strings can I use?

In all places where phpMyAdmin accepts format strings, you can use @VARIABLE@ expansion and strftime format strings. The expanded variables depend on a context (for example, if you haven’t chosen a table, you can not get the table name), but the following variables can be used:

HTTP host that runs phpMyAdmin
MySQL server name
Verbose MySQL server name as defined in $cfg['Servers'][$i]['verbose']
Verbose MySQL server name if set, otherwise normal
Currently opened database
Currently opened table
Columns of the currently opened table
phpMyAdmin with version

6.28 How can I easily edit relational schema for export?

By clicking on the button ‘toggle scratchboard’ on the page where you edit x/y coordinates of those elements you can activate a scratchboard where all your elements are placed. By clicking on an element, you can move them around in the pre-defined area and the x/y coordinates will get updated dynamically. Likewise, when entering a new position directly into the input field, the new position in the scratchboard changes after your cursor leaves the input field.

You have to click on the ‘OK’-button below the tables to save the new positions. If you want to place a new element, first add it to the table of elements and then you can drag the new element around.

By changing the paper size and the orientation you can change the size of the scratchboard as well. You can do so by just changing the dropdown field below, and the scratchboard will resize automatically, without interfering with the current placement of the elements.

If ever an element gets out of range you can either enlarge the paper size or click on the ‘reset’ button to place all elements below each other.

6.29 Why can’t I get a chart from my query result table?

Not every table can be put to the chart. Only tables with one, two or three columns can be visualised as a chart. Moreover the table must be in a special format for chart script to understand it. Currently supported formats can be found in Charts.

6.30 Import: How can I import ESRI Shapefiles?

An ESRI Shapefile is actually a set of several files, where .shp file contains geometry data and .dbf file contains data related to those geometry data. To read data from .dbf file you need to have PHP compiled with the dBase extension (–enable-dbase). Otherwise only geometry data will be imported.

To upload these set of files you can use either of the following methods:

Configure upload directory with $cfg['UploadDir'], upload both .shp and .dbf files with the same filename and chose the .shp file from the import page.

Create a zip archive with .shp and .dbf files and import it. For this to work, you need to set $cfg['TempDir'] to a place where the web server user can write (for example './tmp').

To create the temporary directory on a UNIX-based system, you can do:

cd phpMyAdmin
mkdir tmp
chmod o+rwx tmp

6.31 How do I create a relation in designer?

To select relation, click: The display column is shown in pink. To set/unset a column as the display column, click the “Choose column to display” icon, then click on the appropriate column name.

6.32 How can I use the zoom search feature?

The Zoom search feature is an alternative to table search feature. It allows you to explore a table by representing its data in a scatter plot. You can locate this feature by selecting a table and clicking the Search tab. One of the sub-tabs in the Table Search page is Zoom Search.

Consider the table REL_persons in 6.6 How can I use the relation table in Query-by-example? for an example. To use zoom search, two columns need to be selected, for example, id and town_code. The id values will be represented on one axis and town_code values on the other axis. Each row will be represented as a point in a scatter plot based on its id and town_code. You can include two additional search criteria apart from the two fields to display.

You can choose which field should be displayed as label for each point. If a display column has been set for the table (see 6.7 How can I use the “display column” feature?), it is taken as the label unless you specify otherwise. You can also select the maximum number of rows you want to be displayed in the plot by specifing it in the ‘Max rows to plot’ field. Once you have decided over your criteria, click ‘Go’ to display the plot.

After the plot is generated, you can use the mousewheel to zoom in and out of the plot. In addition, panning feature is enabled to navigate through the plot. You can zoom-in to a certain level of detail and use panning to locate your area of interest. Clicking on a point opens a dialogue box, displaying field values of the data row represented by the point. You can edit the values if required and click on submit to issue an update query. Basic instructions on how to use can be viewed by clicking the ‘How to use?’ link located just above the plot.

6.33 When browsing a table, how can I copy a column name?

Selecting the name of the column within the browse table header cell for copying is difficult, as the columns support reordering by dragging the header cells as well as sorting by clicking on the linked column name. To copy a column name, double-click on the empty area next to the column name, when the tooltip tells you to do so. This will show you an input box with the column name. You may right-click the column name within this input box to copy it to your clipboard.

6.34 How can I use the Favorite Tables feature?

Favorite Tables feature is very much similar to Recent Tables feature. It allows you to add a shortcut for the frequently used tables of any database in the navigation panel . You can easily navigate to any table in the list by simply choosing it from the list. These tables are stored in your browser’s local storage if you have not configured your phpMyAdmin Configuration Storage. Otherwise these entries are stored in phpMyAdmin Configuration Storage.

IMPORTANT: In absence of phpMyAdmin Configuration Storage, your Favorite tables may be different in different browsers based on your different selections in them.

To add a table to Favorite list simply click on the Gray star in front of a table name in the list of tables of a Database and wait until it turns to Yellow. To remove a table from list, simply click on the Yellow star and wait until it turns Gray again.

Using $cfg['NumFavoriteTables'] in your config.inc.php file, you can define the maximum number of favorite tables shown in the navigation panel. Its default value is 10.

6.35 How can I use the Range search feature?

With the help of range search feature, one can specify a range of values for particular column(s) while performing search operation on a table from the Search tab.

To use this feature simply click on the BETWEEN or NOT BETWEEN operators from the operator select list in front of the column name. On choosing one of the above options, a dialog box will show up asking for the Minimum and Maximum value for that column. Only the specified range of values will be included in case of BETWEEN and excluded in case of NOT BETWEEN from the final results.

Note: The Range search feature will work only Numeric and Date data type columns.

6.36 What is Central columns and how can I use this feature?

As the name suggests, the Central columns feature enables to maintain a central list of columns per database to avoid similar name for the same data element and bring consistency of data type for the same data element. You can use the central list of columns to add an element to any table structure in that database which will save from writing similar column name and column definition.

To add a column to central list, go to table structure page, check the columns you want to include and then simply click on “Add to central columns”. If you want to add all unique columns from more than one table from a database then go to database structure page, check the tables you want to include and then select “Add columns to central list”.

To remove a column from central list, go to Table structure page, check the columns you want to remove and then simply click on “Remove from central columns”. If you want to remove all columns from more than one tables from a database then go to database structure page, check the tables you want to include and then select “Remove columns from central list”.

To view and manage the central list, select the database you want to manage central columns for then from the top menu click on “Central columns”. You will be taken to a page where you will have options to edit, delete or add new columns to central list.

6.37 How can I use Improve Table structure feature?

Improve table structure feature helps to bring the table structure upto Third Normal Form. A wizard is presented to user which asks questions about the elements during the various steps for normalization and a new structure is proposed accordingly to bring the table into the First/Second/Third Normal form. On startup of the wizard, user gets to select upto what normal form they want to normalize the table structure.

Here is an example table which you can use to test all of the three First, Second and Third Normal Form.

CREATE TABLE `VetOffice` (
 `petName` varchar(64) NOT NULL,
 `petBreed` varchar(64) NOT NULL,
 `petType` varchar(64) NOT NULL,
 `petDOB` date NOT NULL,
 `ownerLastName` varchar(64) NOT NULL,
 `ownerFirstName` varchar(64) NOT NULL,
 `ownerPhone1` int(12) NOT NULL,
 `ownerPhone2` int(12) NOT NULL,
 `ownerEmail` varchar(64) NOT NULL,

The above table is not in First normal Form as no primary key exists. Primary key is supposed to be (petName,`ownerLastName`,`ownerFirstName`) . If the primary key is chosen as suggested the resultant table won’t be in Second as well as Third Normal form as the following dependencies exists.

(OwnerLastName, OwnerFirstName) -> OwnerEmail
(OwnerLastName, OwnerFirstName) -> OwnerPhone
PetBreed -> PetType

Which says, OwnerEmail depends on OwnerLastName and OwnerFirstName. OwnerPhone depends on OwnerLastName and OwnerFirstName. PetType depends on PetBreed.

6.38 How can I reassign auto-incremented values?

Some users prefer their AUTO_INCREMENT values to be consecutive; this is not always the case after row deletion.

Here are the steps to accomplish this. These are manual steps because they involve a manual verification at one point.

  • Ensure that you have exclusive access to the table to rearrange
  • On your primary key column (i.e. id), remove the AUTO_INCREMENT setting
  • Delete your primary key in Structure > indexes
  • Create a new column future_id as primary key, AUTO_INCREMENT
  • Browse your table and verify that the new increments correspond to what you’re expecting
  • Drop your old id column
  • Rename the future_id column to id
  • Move the new id column via Structure > Move columns

6.39 What is the “Adjust privileges” option when renaming, copying, or moving a database, table, column, or procedure?

When renaming/copying/moving a database/table/column/procedure, MySQL does not adjust the original privileges relating to these objects on its own. By selecting this option, phpMyAdmin will adjust the privilege table so that users have the same privileges on the new items.

For example: A user 'bob'@'localhost‘ has a ‘SELECT’ privilege on a column named ‘id’. Now, if this column is renamed to ‘id_new’, MySQL, on its own, would not adjust the column privileges to the new column name. phpMyAdmin can make this adjustment for you automatically.


  • While adjusting privileges for a database, the privileges of all database-related elements (tables, columns and procedures) are also adjusted to the database’s new name.
  • Similarly, while adjusting privileges for a table, the privileges of all the columns inside the new table are also adjusted.
  • While adjusting privileges, the user performing the operation must have the following privileges:
    • SELECT, INSERT, UPDATE, DELETE privileges on following tables: mysql.`db`, mysql.`columns_priv`, mysql.`tables_priv`, mysql.`procs_priv`
    • FLUSH privilege (GLOBAL)

Thus, if you want to replicate the database/table/column/procedure as it is while renaming/copying/moving these objects, make sure you have checked this option.

6.40 I see “Bind parameters” checkbox in the “SQL” page. How do I write parameterized SQL queries?

From version 4.5, phpMyAdmin allows users to execute parameterized queries in the “SQL” page. Parameters should be prefixed with a colon(:) and when the “Bind parameters” checkbox is checked these parameters will be identified and input fields for these parameters will be presented. Values entered in these field will be substituted in the query before being executed.

6.41 I get import errors while importing the dumps exported from older MySQL versions (pre-5.7.6) into newer MySQL versions (5.7.7+), but they work fine when imported back on same older versions ?

If you get errors like #1031 - Table storage engine for ‘table_name’ doesn’t have this option while importing the dumps exported from pre-5.7.7 MySQL servers into new MySQL server versions 5.7.7+, it might be because ROW_FORMAT=FIXED is not supported with InnoDB tables. Moreover, the value of innodb_strict_mode would define if this would be reported as a warning or as an error.

Since MySQL version 5.7.9, the default value for innodb_strict_mode is ON and thus would generate an error when such a CREATE TABLE or ALTER TABLE statement is encountered.

There are two ways of preventing such errors while importing:

  • Change the value of innodb_strict_mode to OFF before starting the import and turn it ON after the import is successfully completed.
  • This can be achieved in two ways:
    • Go to ‘Variables’ page and edit the value of innodb_strict_mode
    • Run the query : SET GLOBAL `innodb_strict_mode = ‘[value]’`

After the import is done, it is suggested that the value of innodb_strict_mode should be reset to the original value.

phpMyAdmin project

7.1 I have found a bug. How do I inform developers?

Our issues tracker is located at <https://github.com/phpmyadmin/phpmyadmin/issues>. For security issues, please refer to the instructions at <https://www.phpmyadmin.net/security> to email the developers directly.

7.2 I want to translate the messages to a new language or upgrade an existing language, where do I start?

Translations are very welcome and all you need to have are the language skills. The easiest way is to use our online translation service. You can check out all the possibilities to translate in the translate section on our website.

7.3 I would like to help out with the development of phpMyAdmin. How should I proceed?

We welcome every contribution to the development of phpMyAdmin. You can check out all the possibilities to contribute in the contribute section on our website.


8.1 Where can I get information about the security alerts issued for phpMyAdmin?

Please refer to <https://www.phpmyadmin.net/security/>.

8.2 How can I protect phpMyAdmin against brute force attacks?

If you use Apache web server, phpMyAdmin exports information about authentication to the Apache environment and it can be used in Apache logs. Currently there are two variables available:

User name of currently active user (he does not have to be logged in).
Status of currently active user, one of ok (user is logged in), mysql-denied (MySQL denied user login), allow-denied (user denied by allow/deny rules), root-denied (root is denied in configuration), empty-denied (empty password is denied).

LogFormat directive for Apache can look like following:

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %{userID}n %{userStatus}n"   pma_combined

You can then use any log analyzing tools to detect possible break-in attempts.

8.3 Why are there path disclosures when directly loading certain files?

This is a server configuration problem. Never enable display_errors on a production site.

8.4 CSV files exported from phpMyAdmin could allow a formula injection attack.

It is possible to generate a CSV file that, when imported to a spreadsheet program such as Microsoft Excel, could potentially allow the execution of arbitrary commands.

The CSV files generated by phpMyAdmin could potentially contain text that would be interpreted by a spreadsheet program as a formula, but we do not believe escaping those fields is the proper behavior. There is no means to properly escape and differentiate between a desired text output and a formula that should be escaped, and CSV is a text format where function definitions should not be interpreted anyway. We have discussed this at length and feel it is the responsibility of the spreadsheet program to properly parse and sanitize such data on input instead.

Google also has a similar view.


9.1 (withdrawn).

9.2 (withdrawn).

Developers Information

phpMyAdmin is Open Source, so you’re invited to contribute to it. Many great features have been written by other people and you too can help to make phpMyAdmin a useful tool.

You can check out all the possibilities to contribute in the contribute section on our website.

Distributing and packaging phpMyAdmin

This document is intended to give advices to people who want to redistribute phpMyAdmin inside other software package such as Linux distribution or some all in one package including web server and MySQL server.

Generally you can customize some basic aspects (paths to some files and behavior) in libraries/vendor_config.php.

For example if you want setup script to generate config file in var, change SETUP_CONFIG_FILE to /var/lib/phpmyadmin/config.inc.php and you will also probably want to skip directory writable check, so set SETUP_DIR_WRITABLE to false.

External libraries

phpMyAdmin includes several external libraries, you might want to replace them with system ones if they are available, but please note that you should test whether version you provide is compatible with the one we ship.

Currently known list of external libraries:

jQuery js framework and various jQuery based libraries.
The download kit includes various Composer packages as dependencies.


Credits, in chronological order

  • Tobias Ratschiller <tobias_at_ratschiller.com>
    • creator of the phpmyadmin project
    • maintainer from 1998 to summer 2000
  • Marc Delisle <marc_at_infomarc.info>
    • multi-language version in December 1998
    • various fixes and improvements
    • SQL analyser (most of it)
    • current project maintainer
    • maintains content on our website
  • Olivier Müller <om_at_omnis.ch>
    • started SourceForge phpMyAdmin project in March 2001
    • sync’ed different existing CVS trees with new features and bugfixes
    • multi-language improvements, dynamic language selection
    • many bugfixes and improvements
  • Loïc Chapeaux <lolo_at_phpheaven.net>
    • rewrote and optimized JavaScript, DHTML and DOM stuff
    • rewrote the scripts so they fit the PEAR coding standards and generate XHTML1.0 and CSS2 compliant codes
    • improved the language detection system
    • many bugfixes and improvements
  • Robin Johnson <robbat2_at_users.sourceforge.net>
    • database maintenance controls
    • table type code
    • Host authentication IP Allow/Deny
    • DB-based configuration (Not completed)
    • SQL parser and pretty-printer
    • SQL validator
    • many bugfixes and improvements
  • Armel Fauveau <armel.fauveau_at_globalis-ms.com>
    • bookmarks feature
    • multiple dump feature
    • gzip dump feature
    • zip dump feature
  • Geert Lund <glund_at_silversoft.dk>
    • various fixes
    • moderator of the phpMyAdmin former users forum at phpwizard.net
  • Korakot Chaovavanich <korakot_at_iname.com>
    • “insert as new row” feature
  • Pete Kelly <webmaster_at_trafficg.com>
    • rewrote and fix dump code
    • bugfixes
  • Steve Alberty <alberty_at_neptunlabs.de>
    • rewrote dump code for PHP4
    • mySQL table statistics
    • bugfixes
  • Benjamin Gandon <gandon_at_isia.cma.fr>
    • main author of the version
    • bugfixes
  • Alexander M. Turek <me_at_derrabus.de>
    • MySQL 4.0 / 4.1 / 5.0 compatibility
    • abstract database interface (PMA_DBI) with MySQLi support
    • privileges administration
    • XML exports
    • various features and fixes
    • German language file updates
  • Mike Beck <mike.beck_at_web.de>
    • automatic joins in QBE
    • links column in printview
    • Relation view
  • Michal Čihař <michal_at_cihar.com>
    • enhanced index creation/display feature
    • feature to use a different charset for HTML than for MySQL
    • improvements of export feature
    • various features and fixes
    • Czech language file updates
    • created current website for phpMyAdmin
  • Christophe Gesché from the “MySQL Form Generator for PHPMyAdmin” (https://sourceforge.net/projects/phpmysqlformgen/)
    • suggested the patch for multiple table printviews
  • Garvin Hicking <me_at_supergarv.de>
    • built the patch for vertical display of table rows
    • built the Javascript based Query window + SQL history
    • Improvement of column/db comments
    • (MIME)-Transformations for columns
    • Use custom alias names for Databases in left frame
    • hierarchical/nested table display
    • PDF-scratchboard for WYSIWYG- distribution of PDF relations
    • new icon sets
    • vertical display of column properties page
    • some bugfixes, features, support, German language additions
  • Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
    • japanese kanji encoding conversion feature
  • Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
    • the Cookie authentication mode
  • Axel Sander <n8falke_at_users.sourceforge.net>
    • table relation-links feature
  • Maxime Delorme <delorme.maxime_at_free.fr>
    • PDF schema output, thanks also to Olivier Plathey for the “FPDF” library (see <http://www.fpdf.org/>), Steven Wittens for the “UFPDF” library and Nicola Asuni for the “TCPDF” library (see <https://tcpdf.org/>).
  • Olof Edlund <olof.edlund_at_upright.se>
    • SQL validator server
  • Ivan R. Lanin <ivanlanin_at_users.sourceforge.net>
    • phpMyAdmin logo (until June 2004)
  • Mike Cochrane <mike_at_graftonhall.co.nz>
    • blowfish library from the Horde project (withdrawn in release 4.0)
  • Marcel Tschopp <ne0x_at_users.sourceforge.net>
    • mysqli support
    • many bugfixes and improvements
  • Nicola Asuni (Tecnick.com)
  • Michael Keck <mkkeck_at_users.sourceforge.net>
    • redesign for 2.6.0
    • phpMyAdmin sailboat logo (June 2004)
  • Mathias Landhäußer
    • Representation at conferences
  • Sebastian Mendel <cybot_tm_at_users.sourceforge.net>
    • interface improvements
    • various bugfixes
  • Ivan A Kirillov
    • new relations Designer
  • Raj Kissu Rajandran (Google Summer of Code 2008)
    • BLOBstreaming support (withdrawn in release 4.0)
  • Piotr Przybylski (Google Summer of Code 2008, 2010 and 2011)
    • improved setup script
    • user preferences
    • Drizzle support
  • Derek Schaefer (Google Summer of Code 2009)
    • Improved the import system
  • Alexander Rutkowski (Google Summer of Code 2009)
    • Tracking mechanism
  • Zahra Naeem (Google Summer of Code 2009)
    • Synchronization feature (removed in release 4.0)
  • Tomáš Srnka (Google Summer of Code 2009)
    • Replication support
  • Muhammad Adnan (Google Summer of Code 2010)
    • Relation schema export to multiple formats
  • Lori Lee (Google Summer of Code 2010)
    • User interface improvements
    • ENUM/SET editor
    • Simplified interface for export/import
  • Ninad Pundalik (Google Summer of Code 2010)
    • AJAXifying the interface
  • Martynas Mickevičius (Google Summer of Code 2010)
    • Charts
  • Barrie Leslie
    • BLOBstreaming support with PBMS PHP extension (withdrawn in release 4.0)
  • Ankit Gupta (Google Summer of Code 2010)
    • Visual query builder
  • Madhura Jayaratne (Google Summer of Code 2011)
    • OpenGIS support
  • Ammar Yasir (Google Summer of Code 2011)
    • Zoom search
  • Aris Feryanto (Google Summer of Code 2011)
    • Browse-mode improvements
  • Thilanka Kaushalya (Google Summer of Code 2011)
    • AJAXification
  • Tyron Madlener (Google Summer of Code 2011)
    • Query statistics and charts for the status page
  • Zarubin Stas (Google Summer of Code 2011)
    • Automated testing
  • Rouslan Placella (Google Summer of Code 2011 and 2012)
    • Improved support for Stored Routines, Triggers and Events
    • Italian translation updates
    • Removal of frames, new navigation
  • Dieter Adriaenssens
    • Various bugfixes
    • Dutch translation updates
  • Alex Marin (Google Summer of Code 2012)
    • New plugins and properties system
  • Thilina Buddika Abeyrathna (Google Summer of Code 2012)
    • Refactoring
  • Atul Pratap Singh (Google Summer of Code 2012)
    • Refactoring
  • Chanaka Indrajith (Google Summer of Code 2012)
    • Refactoring
  • Yasitha Pandithawatta (Google Summer of Code 2012)
    • Automated testing
  • Jim Wigginton (phpseclib.sourceforge.net)
    • phpseclib
  • Bin Zu (Google Summer of Code 2013)
    • Refactoring
  • Supun Nakandala (Google Summer of Code 2013)
    • Refactoring
  • Mohamed Ashraf (Google Summer of Code 2013)
    • AJAX error reporting
  • Adam Kang (Google Summer of Code 2013)
    • Automated testing
  • Ayush Chaudhary (Google Summer of Code 2013)
    • Automated testing
  • Kasun Chathuranga (Google Summer of Code 2013)
    • Interface improvements
  • Hugues Peccatte
    • Load/save query by example (database search bookmarks)
  • Smita Kumari (Google Summer of Code 2014)
    • Central list of columns
    • Improve table structure (normalization)
  • Ashutosh Dhundhara (Google Summer of Code 2014)
    • Interface improvements
  • Dhananjay Nakrani (Google Summer of Code 2014)
    • PHP error reporting
  • Edward Cheng (Google Summer of Code 2014)
    • SQL Query Console
  • Kankanamge Bimal Yashodha (Google Summer of Code 2014)
    • Refactoring: Designer/schema integration
  • Chirayu Chiripal (Google Summer of Code 2014)
    • Custom field handlers (Input based MIME transformations)
    • Export with table/column name changes
  • Dan Ungureanu (Google Summer of Code 2015)
    • New parser and analyzer
  • Nisarg Jhaveri (Google Summer of Code 2015)
    • Page-related settings
    • SQL debugging integration to the Console
    • Other UI improvements
  • Deven Bansod (Google Summer of Code 2015)
    • Print view using CSS
    • Other UI improvements and new features

And also to the following people who have contributed minor changes, enhancements, bugfixes or support for a new language since version 2.1.0:

Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita, Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow, Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger, Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley, Bernard M. Piller, Laurent Haas, “Sakamoto”, Yuval Sarna, www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky, Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee, Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai, Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas, “Manuzhai”.


Following people have contributed to translation of phpMyAdmin:

  • Albanian

    • Arben Çokaj <acokaj_at_shkoder.net>
  • Arabic

    • Ahmed Saleh Abd El-Raouf Ismae <a.saleh.ismael_at_gmail.com>
    • Ahmed Saad <egbrave_at_hotmail.com>
    • hassan mokhtari <persiste1_at_gmail.com>
  • Armenian

    • Andrey Aleksanyants <aaleksanyants_at_yahoo.com>
  • Azerbaijani

    • Mircəlal <01youknowme_at_gmail.com>
    • Huseyn <huseyn_esgerov_at_mail.ru>
    • Sevdimali İsa <sevdimaliisayev_at_mail.ru>
    • Jafar <sharifov_at_programmer.net>
  • Belarusian

    • Viktar Palstsiuk <vipals_at_gmail.com>
  • Bulgarian

    • Boyan Kehayov <bkehayov_at_gmail.com>
    • Valter Georgiev <blagynchy_at_gmail.com>
    • Valentin Mladenov <hudsonvsm_at_gmail.com>
    • P <plamen_mbx_at_yahoo.com>
    • krasimir <vip_at_krasio-valia.com>
  • Catalan

    • josep constanti <jconstanti_at_yahoo.es>
    • Xavier Navarro <xvnavarro_at_gmail.com>
  • Chinese (China)

    • Vincent Lau <3092849_at_qq.com>
    • Zheng Dan <clanboy_at_163.com>
    • disorderman <disorderman_at_qq.com>
    • Rex Lee <duguying2008_at_gmail.com>
    • <fundawang_at_gmail.com>
    • popcorner <memoword_at_163.com>
    • Yizhou Qiang <qyz.yswy_at_hotmail.com>
    • zz <tczzjin_at_gmail.com>
    • Terry Weng <wengshiyu_at_gmail.com>
    • whh <whhlcj_at_126.com>
  • Chinese (Taiwan)

    • Albert Song <albb0920_at_gmail.com>
    • Chien Wei Lin <cwlin0416_at_gmail.com>
    • Peter Dave Hello <xs910203_at_gmail.com>
  • Colognian

    • Purodha <publi_at_web.de>
  • Czech

    • Aleš Hakl <ales_at_hakl.net>
    • Dalibor Straka <dalibor.straka3_at_gmail.com>
    • Martin Vidner <martin_at_vidner.net>
    • Ondra Šimeček <ondrasek.simecek_at_gmail.com>
    • Jan Palider <palider_at_seznam.cz>
    • Petr Kateřiňák <petr.katerinak_at_gmail.com>
  • Danish

    • Aputsiaĸ Niels Janussen <aj_at_isit.gl>
    • Dennis Jakobsen <dennis.jakobsen_at_gmail.com>
    • Jonas <jonas.den.smarte_at_gmail.com>
    • Claus Svalekjaer <just.my.smtp.server_at_gmail.com>
  • Dutch

      1. Voogt <a.voogt_at_hccnet.nl>
    • dingo thirteen <dingo13_at_gmail.com>
    • Robin van der Vliet <info_at_robinvandervliet.nl>
    • Dieter Adriaenssens <ruleant_at_users.sourceforge.net>
    • Niko Strijbol <strijbol.niko_at_gmail.com>
  • English (United Kingdom)

    • Dries Verschuere <dries.verschuere_at_outlook.com>
    • Francisco Rocha <j.francisco.o.rocha_at_zoho.com>
    • Marc Delisle <marc_at_infomarc.info>
    • Marek Tomaštík <tomastik.m_at_gmail.com>
  • Esperanto

    • Eliovir <eliovir_at_gmail.com>
    • Robin van der Vliet <info_at_robinvandervliet.nl>
  • Estonian

    • Kristjan Räts <kristjanrats_at_gmail.com>
  • Finnish

    • Juha Remes <jremes_at_outlook.com>
    • Lari Oesch <lari_at_oesch.me>
  • French

    • Marc Delisle <marc_at_infomarc.info>
  • Frisian

    • Robin van der Vliet <info_at_robinvandervliet.nl>
  • Galician

    • Xosé Calvo <xosecalvo_at_gmail.com>
  • German

    • Julian Ladisch <github.com-t3if_at_ladisch.de>
    • Jan Erik Zassenhaus <jan.zassenhaus_at_jgerman.de>
    • Lasse Goericke <lasse_at_mydom.de>
    • Matthias Bluthardt <matthias_at_bluthardt.org>
    • Michael Koch <michael.koch_at_enough.de>
    • Ann + J.M. <phpMyAdmin_at_ZweiSteinSoft.de>
    • <pma_at_sebastianmendel.de>
    • Phillip Rohmberger <rohmberger_at_hotmail.de>
    • Hauke Henningsen <sqrt_at_entless.org>
  • Greek

    • Παναγιώτης Παπάζογλου <papaz_p_at_yahoo.com>
  • Hebrew

    • Moshe Harush <mmh15_at_windowslive.com>
    • Yaron Shahrabani <sh.yaron_at_gmail.com>
    • Eyal Visoker <visokereyal_at_gmail.com>
  • Hindi

    • Atul Pratap Singh <atulpratapsingh05_at_gmail.com>
    • Yogeshwar <charanyogeshwar_at_gmail.com>
    • Deven Bansod <devenbansod.bits_at_gmail.com>
    • Kushagra Pandey <kushagra4296_at_gmail.com>
    • Nisarg Jhaveri <nisargjhaveri_at_gmail.com>
    • Roohan Kazi <roohan_cena_at_yahoo.co.in>
    • Yugal Pantola <yug.scorpio_at_gmail.com>
  • Hungarian

    • Akos Eros <erosakos02_at_gmail.com>
    • Dániel Tóth <leedermeister_at_gmail.com>
    • Szász Attila <undernetangel_at_gmail.com>
    • Balázs Úr <urbalazs_at_gmail.com>
  • Indonesian

    • Deky Arifianto <Deky40_at_gmail.com>
    • Andika Triwidada <andika_at_gmail.com>
    • Dadan Setia <da2n_s_at_yahoo.co.id>
    • Dadan Setia <dadan.setia_at_gmail.com>
    • Yohanes Edwin <edwin_at_yohanesedwin.com>
    • Fadhiil Rachman <fadhiilrachman_at_gmail.com>
    • Benny <tarzq28_at_gmail.com>
    • Tommy Surbakti <tommy_at_surbakti.net>
    • Zufar Fathi Suhardi <zufar.bogor_at_gmail.com>
  • Interlingua

    • Giovanni Sora <g.sora_at_tiscali.it>
  • Italian

    • Francesco Saverio Giacobazzi <francesco.giacobazzi_at_ferrania.it>
    • Marco Pozzato <ironpotts_at_gmail.com>
    • Stefano Martinelli <stefano.ste.martinelli_at_gmail.com>
  • Japanese

    • k725 <alexalex.kobayashi_at_gmail.com>
    • Hiroshi Chiyokawa <hiroshi.chiyokawa_at_gmail.com>
    • Masahiko HISAKAWA <orzkun_at_ageage.jp>
    • worldwideskier <worldwideskier_at_yahoo.co.jp>
  • Kannada

    • Robin van der Vliet <info_at_robinvandervliet.nl>
    • Shameem Ahmed A Mulla <shameem.sam_at_gmail.com>
  • Korean

    • Bumsoo Kim <bskim45_at_gmail.com>
    • Kyeong Su Shin <cdac1234_at_gmail.com>
    • Dongyoung Kim <dckyoung_at_gmail.com>
    • Myung-han Yu <greatymh_at_gmail.com>
    • JongDeok <human.zion_at_gmail.com>
    • Yong Kim <kim_at_nhn.com>
    • 이경준 <kyungjun2_at_gmail.com>
    • Seongki Shin <skshin_at_gmail.com>
    • Yoon Bum-Jong <virusyoon_at_gmail.com>
    • Koo Youngmin <youngminz.kr_at_gmail.com>
  • Kurdish Sorani

    • Alan Hilal <alan.hilal94_at_gmail.com>
    • Aso Naderi <aso.naderi_at_gmail.com>
    • muhammad <esy_vb_at_yahoo.com>
    • Zrng Abdulla <zhyarabdulla94_at_gmail.com>
  • Latvian

    • Latvian TV <dnighttv_at_gmail.com>
    • Edgars Neimanis <edgarsneims5092_at_inbox.lv>
    • Ukko <perkontevs_at_gmail.com>
  • Limburgish

    • Robin van der Vliet <info_at_robinvandervliet.nl>
  • Lithuanian

    • Vytautas Motuzas <v.motuzas_at_gmail.com>
  • Malay

    • Amir Hamzah <amir.overlord666_at_gmail.com>
    • diprofinfiniti <anonynuine-999_at_yahoo.com>
  • Nepali

    • Nabin Ghimire <nnabinn_at_hotmail.com>
  • Norwegian Bokmål

    • Børge Holm-Wennberg <borge947_at_gmail.com>
    • Tor Stokkan <danorse_at_gmail.com>
    • Espen Frøyshov <efroys_at_gmail.com>
    • Kurt Eilertsen <kurt_at_kheds.com>
    • Christoffer Haugom <ph3n1x.nobody_at_gmail.com>
    • Sebastian <sebastian_at_sgundersen.com>
    • Tomas <tomas_at_tomasruud.com>
  • Persian

    • ashkan shirian <ashkan.shirian_at_gmail.com>
    • HM <goodlinuxuser_at_chmail.ir>
  • Polish

    • Andrzej <andrzej_at_kynu.pl>
    • Przemo <info_at_opsbielany.waw.pl>
    • Krystian Biesaga <krystian4842_at_gmail.com>
    • Maciej Gryniuk <maciejka45_at_gmail.com>
    • Michał VonFlynee <vonflynee_at_gmail.com>
  • Portuguese

    • Alexandre Badalo <alexandre.badalo_at_sapo.pt>
    • João Rodrigues <geral_at_jonilive.com>
    • Pedro Ribeiro <p.m42.ribeiro_at_gmail.com>
    • Sandro Amaral <sandro123iv_at_gmail.com>
  • Portuguese (Brazil)

    • Alex Rohleder <alexrohleder96_at_outlook.com>
    • bruno mendax <brunomendax_at_gmail.com>
    • Danilo GUia <danilo.eng_at_globomail.com>
    • Douglas Rafael Morais Kollar <douglas.kollar_at_pg.df.gov.br>
    • Douglas Eccker <douglaseccker_at_hotmail.com>
    • Ed Jr <edjacobjunior_at_gmail.com>
    • Guilherme Souza Silva <g.szsilva_at_gmail.com>
    • Guilherme Seibt <gui_at_webseibt.net>
    • Helder Santana <helder.bs.santana_at_gmail.com>
    • Junior Zancan <jrzancan_at_hotmail.com>
    • Luis <luis.eduardo.braschi_at_outlook.com>
    • Marcos Algeri <malgeri_at_gmail.com>
    • Marc Delisle <marc_at_infomarc.info>
    • Renato Rodrigues de Lima Júnio <renatomdd_at_yahoo.com.br>
    • Thiago Casotti <thiago.casotti_at_uol.com.br>
    • Victor Laureano <victor.laureano_at_gmail.com>
    • Vinícius Araújo <vinipitta_at_gmail.com>
    • Washington Bruno Rodrigues Cav <washingtonbruno_at_msn.com>
    • Yan Gabriel <yansilvagabriel_at_gmail.com>
  • Punjabi

    • Robin van der Vliet <info_at_robinvandervliet.nl>
  • Romanian

    • Alex <amihaita_at_yahoo.com>
    • Costel Cocerhan <costa1988sv_at_gmail.com>
    • Ion Adrian-Ionut <john_at_panevo.ro>
    • Raul Molnar <molnar.raul_at_wservices.eu>
    • Deleted User <noreply_at_weblate.org>
    • Stefan Murariu <stefan.murariu_at_yahoo.com>
  • Russian

    • Andrey Aleksanyants <aaleksanyants_at_yahoo.com>
    • <ddrmoscow_at_gmail.com>
    • Robin van der Vliet <info_at_robinvandervliet.nl>
    • Хомутов Иван Сергеевич <khomutov.ivan_at_mail.ru>
    • Alexey Rubinov <orion1979_at_yandex.ru>
    • Олег Карпов <salvadoporjc_at_gmail.com>
    • Egorov Artyom <unlucky_at_inbox.ru>
  • Serbian

    • Smart Kid <kidsmart33_at_gmail.com>
  • Sinhala

    • Madhura Jayaratne <madhura.cj_at_gmail.com>
  • Slovak

    • Martin Lacina <martin_at_whistler.sk>
    • Patrik Kollmann <parkourpotex_at_gmail.com>
    • Jozef Pistej <pistej2_at_gmail.com>
  • Slovenian

    • Domen <mitenem_at_outlook.com>
  • Spanish

    • Luis García Sevillano <floss.dev_at_gmail.com>
    • Franco <fulanodetal.github1_at_openaliasbox.org>
    • Luis Ruiz <luisan00_at_hotmail.com>
    • Macofe <macofe.languagetool_at_gmail.com>
    • Matías Bellone <matiasbellone+weblate_at_gmail.com>
    • Rodrigo A. <ra4_at_openmailbox.org>
    • FAMMA TV NOTICIAS MEDIOS DE CO <revistafammatvmusic.oficial_at_gmail.com>
    • Ronnie Simon <ronniesimonf_at_gmail.com>
  • Swedish

    • Anders Jonsson <anders.jonsson_at_norsjovallen.se>
  • Tamil

    • கணேஷ் குமார் <GANESHTHEONE_at_gmail.com>
    • Achchuthan Yogarajah <achch1990_at_gmail.com>
    • Rifthy Ahmed <rifthy456_at_gmail.com>
  • Thai

    • <nontawat39_at_gmail.com>
    • Somthanat W. <somthanat_at_gmail.com>
  • Turkish

    • Burak Yavuz <hitowerdigit_at_hotmail.com>
  • Ukrainian

    • Сергій Педько <nitrotoll_at_gmail.com>
    • Igor <vmta_at_yahoo.com>
    • Vitaliy Perekupka <vperekupka_at_gmail.com>
  • Vietnamese

    • Bao Phan <baophan94_at_icloud.com>
    • Xuan Hung <mr.hungdx_at_gmail.com>
    • Bao trinh minh <trinhminhbao_at_gmail.com>
  • West Flemish

    • Robin van der Vliet <info_at_robinvandervliet.nl>

Documentation translators

Following people have contributed to translation of phpMyAdmin documentation:

  • Albanian

    • Arben Çokaj <acokaj_at_shkoder.net>
  • Arabic

    • Ahmed El Azzabi <ahmedtek1993_at_gmail.com>
    • Omar Essam <omar_2412_at_live.com>
  • Armenian

    • Andrey Aleksanyants <aaleksanyants_at_yahoo.com>
  • Azerbaijani

    • Mircəlal <01youknowme_at_gmail.com>
    • Sevdimali İsa <sevdimaliisayev_at_mail.ru>
  • Catalan

    • josep constanti <jconstanti_at_yahoo.es>
    • Joan Montané <joan_at_montane.cat>
    • Xavier Navarro <xvnavarro_at_gmail.com>
  • Chinese (China)

    • Vincent Lau <3092849_at_qq.com>
    • 罗攀登 <6375lpd_at_gmail.com>
    • disorderman <disorderman_at_qq.com>
    • ITXiaoPang <djh1017555_at_126.com>
    • tunnel213 <tunnel213_at_aliyun.com>
    • Terry Weng <wengshiyu_at_gmail.com>
    • whh <whhlcj_at_126.com>
  • Chinese (Taiwan)

    • Chien Wei Lin <cwlin0416_at_gmail.com>
    • Peter Dave Hello <xs910203_at_gmail.com>
  • Czech

    • Aleš Hakl <ales_at_hakl.net>
    • Michal Čihař <michal_at_cihar.com>
    • Jan Palider <palider_at_seznam.cz>
    • Petr Kateřiňák <petr.katerinak_at_gmail.com>
  • Danish

    • Aputsiaĸ Niels Janussen <aj_at_isit.gl>
    • Claus Svalekjaer <just.my.smtp.server_at_gmail.com>
  • Dutch

      1. Voogt <a.voogt_at_hccnet.nl>
    • dingo thirteen <dingo13_at_gmail.com>
    • Dries Verschuere <dries.verschuere_at_outlook.com>
    • Robin van der Vliet <info_at_robinvandervliet.nl>
    • Stefan Koolen <nast3zz_at_gmail.com>
    • Ray Borggreve <ray_at_datahuis.net>
    • Dieter Adriaenssens <ruleant_at_users.sourceforge.net>
    • Tom Hofman <tom.hofman_at_gmail.com>
  • Estonian

    • Kristjan Räts <kristjanrats_at_gmail.com>
  • Finnish

    • Juha <jremes_at_outlook.com>
  • French

    • Cédric Corazza <cedric.corazza_at_wanadoo.fr>
    • Étienne Gilli <etienne.gilli_at_gmail.com>
    • Marc Delisle <marc_at_infomarc.info>
    • Donavan_Martin <mart.donavan_at_hotmail.com>
  • Frisian

    • Robin van der Vliet <info_at_robinvandervliet.nl>
  • Galician

    • Xosé Calvo <xosecalvo_at_gmail.com>
  • German

    • Daniel <d.gnauk89_at_googlemail.com>
    • JH M <janhenrikm_at_yahoo.de>
    • Lasse Goericke <lasse_at_mydom.de>
    • Michael Koch <michael.koch_at_enough.de>
    • Ann + J.M. <phpMyAdmin_at_ZweiSteinSoft.de>
    • Niemand Jedermann <predatorix_at_web.de>
    • Phillip Rohmberger <rohmberger_at_hotmail.de>
    • Hauke Henningsen <sqrt_at_entless.org>
  • Greek

    • Παναγιώτης Παπάζογλου <papaz_p_at_yahoo.com>
  • Hungarian

    • Balázs Úr <urbalazs_at_gmail.com>
  • Italian

    • Francesco Saverio Giacobazzi <francesco.giacobazzi_at_ferrania.it>
    • Marco Pozzato <ironpotts_at_gmail.com>
    • Stefano Martinelli <stefano.ste.martinelli_at_gmail.com>
    • TWS <tablettws_at_gmail.com>
  • Japanese

    • Eshin Kunishima <ek_at_luna.miko.im>
    • Hiroshi Chiyokawa <hiroshi.chiyokawa_at_gmail.com>
  • Lithuanian

    • Jur Kis <atvejis_at_gmail.com>
    • Dovydas <dovy.buz_at_gmail.com>
  • Norwegian Bokmål

    • Tor Stokkan <danorse_at_gmail.com>
    • Kurt Eilertsen <kurt_at_kheds.com>
  • Portuguese (Brazil)

    • Alexandre Moretti <alemoretti2010_at_hotmail.com>
    • Douglas Rafael Morais Kollar <douglas.kollar_at_pg.df.gov.br>
    • Guilherme Seibt <gui_at_webseibt.net>
    • Helder Santana <helder.bs.santana_at_gmail.com>
    • Michal Čihař <michal_at_cihar.com>
    • Michel Souza <michel.ekio_at_gmail.com>
    • Danilo Azevedo <mrdaniloazevedo_at_gmail.com>
    • Thiago Casotti <thiago.casotti_at_uol.com.br>
    • Vinícius Araújo <vinipitta_at_gmail.com>
    • Yan Gabriel <yansilvagabriel_at_gmail.com>
  • Slovak

    • Martin Lacina <martin_at_whistler.sk>
    • Michal Čihař <michal_at_cihar.com>
    • Jozef Pistej <pistej2_at_gmail.com>
  • Slovenian

    • Domen <mitenem_at_outlook.com>
  • Spanish

    • Luis García Sevillano <floss.dev_at_gmail.com>
    • Franco <fulanodetal.github1_at_openaliasbox.org>
    • Matías Bellone <matiasbellone+weblate_at_gmail.com>
    • Ronnie Simon <ronniesimonf_at_gmail.com>
  • Turkish

    • Burak Yavuz <hitowerdigit_at_hotmail.com>

Original Credits of Version 2.1.0

This work is based on Peter Kuppelwieser’s MySQL-Webadmin. It was his idea to create a web-based interface to MySQL using PHP3. Although I have not used any of his source-code, there are some concepts I’ve borrowed from him. phpMyAdmin was created because Peter told me he wasn’t going to further develop his (great) tool.

Thanks go to

  • Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the code for the check when dropping a table or database. He also suggested that you should be able to specify the primary key on tbl_create.php3. To version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as well as a bug-report. Plus many smaller improvements.
  • Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that were introduced in 1.3.0 (including quite significant ones like the authentication). For 1.4.1 he enhanced the table-dump feature. Plus bug-fixes and help.
  • Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin language-independent by outsourcing the strings to a separate file. He also contributed the French translation.
  • Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed tbl_select.php3, a feature to display only some columns from a table.
  • Chris Jackson <chrisj_at_ctel.net> added support for MySQL functions in tbl_change.php3. He also added the “Query by Example” feature in 2.0.
  • Dave Walton <walton_at_nordicdms.com> added support for multiple servers and is a regular contributor for bug-fixes.
  • Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access features for 2.0.6.

The following people have contributed minor changes, enhancements, bugfixes or support for a new language:

Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann, Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov, Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns, G. Wieggers.

And thanks to everyone else who sent me email with suggestions, bug- reports and or just some feedback.


From Wikipedia, the free encyclopedia


the default name of Apache’s directory-level configuration file.

Access Contol List

a keyed, symmetric block cipher, designed in 1993 by Bruce Schneier.


a software application that enables a user to display and interact with text, images, and other information typically located on a web page at a website on the World Wide Web.


a free software/open source data compression algorithm and program developed by Julian Seward.


Common Gateway Interface is an important World Wide Web technology that enables a client web browser to request data from a program executed on the Web server.


a log or record of changes made to a project.


a computer system that accesses a (remote) service on another computer by some kind of network.


a set of data values of a particular simple type, one for each row of the table.

a packet of information sent by a server to a World Wide Web browser and then sent back by the browser each time it accesses that server.


Comma- separated values

look at database

an organized collection of data.

look at storage engines

a PHP module that extends PHP with additional functionality.


Frequently Asked Questions is a list of commonly asked question and there answers.


one part of divided data/columns.

foreign key

a column or group of columns in a database row that point to a key column or group of columns forming a key of another database row in some (usually different) table.


Graphics Library by Thomas Boutell and others for dynamically manipulating images.

look at gd

gzip is short for GNU zip, a GNU free software file compression program.


any machine connected to a computer network, a node that has a hostname.


the unique name by which a network attached device is known on a network.


HyperText Transfer Protocol is the primary method used to transfer or convey information on the World Wide Web.


a HTTP-connection with additional security measures.

International Electrotechnical Commission

Internet Information Services is a set of Internet-based services for servers using Microsoft Windows.


a feature that allows quick access to the rows in a table.


Internet Protocol is a data-oriented protocol used by source and destination hosts for communicating data across a packet-switched internetwork.

IP Address

a unique number that devices use in order to identify and communicate with each other on a network utilizing the Internet Protocol standard.


IPv6 (Internet Protocol version 6) is the latest revision of the Internet Protocol (IP), designed to deal with the long-anticipated problem of its precedessor IPv4 running out of addresses.


Internet Server Application Programming Interface is the API of Internet Information Services (IIS).


Internet service provider is a business or organization that offers users access to the Internet and related services.

International Standards Organisation

a most commonly used standard method of lossy compression for photographic images.

look at jpeg
look at index

a document preparation system for the TEX typesetting program.


Apple Macintosh is line of personal computers is designed, developed, manufactured, and marketed by Apple Computer.

. seealso:: <https://en.wikipedia.org/wiki/Mac>

Mac OS X

the operating system which is included with all currently shipping Apple Macintosh computers in the consumer and professional markets.


The PHP mbstring functions provide support for languages represented by multi-byte character sets, most notably UTF-8.

If you have troubles installing this extension, please follow 1.20 I receive an error about missing mysqli and mysql extensions., it provides useful hints.


a cryptographic library.


the MCrypt PHP extension.


Multipurpose Internet Mail Extensions is an Internet Standard for the format of e-mail.


some sort of extension for the Apache Webserver.

an Apache module implmenting a Fast CGI interface; PHP can be run as a CGI module, FastCGI, or directly as an Apache module.

a multithreaded, multi-user, SQL (Structured Query Language) Database Management System (DBMS).


the improved MySQL client PHP extension.


the MySQL client PHP extension.


open standard for office documents.


look at Mac OS X.


Portable Document Format is a file format developed by Adobe Systems for representing two dimensional documents in a device independent and resolution independent format.


the PHP Extension and Application Repository.


Perl Compatible Regular Expressions is the perl-compatible regular expression functions for PHP


short for “PHP: Hypertext Preprocessor”, is an open-source, reflective programming language used mainly for developing server-side applications and dynamic web content, and more recently, a broader range of software applications.


a connection through which data is sent and received.

primary key

A primary key is an index over one or more fields in a table with unique values for each single row in this table. Every table should have a primary key for easier accessing/identifying data in this table. There can only be one primary key per table and it is named always PRIMARY. In fact a primary key is just an unique key with the name PRIMARY. If no primary key is defined MySQL will use first unique key as primary key if there is one.

You can create the primary key when creating the table (in phpMyAdmin just check the primary key radio buttons for each field you wish to be part of the primary key).

You can also add a primary key to an existing table with ALTER TABLE or CREATE INDEX (in phpMyAdmin you can just click on ‘add index’ on the table structure page below the listed fields).


Request for Comments (RFC) documents are a series of memoranda encompassing new research, innovations, and methodologies applicable to Internet technologies.

RFC 1952

GZIP file format specification version 4.3

See also

RFC 1952

Row (record, tuple)

represents a single, implicitly structured data item in a table.


a computer system that provides services to other computing systems over a network.

Storage Engines

MySQL can use several different formats for storing data on disk, these are called storage engines or table types. phpMyAdmin allows a user to change their storage engine for a particular table through the operations tab.

Common table types are InnoDB and MyISAM, though many others exist and may be desirable in some situations.


a form of inter-process communication.


Secure Sockets Layer is a cryptographic protocol which provides secure communication on the Internet.

Stored procedure

a subroutine available to applications accessing a relational database system


Structured Query Language


a set of data elements (cells) that is organized, defined and stored as horizontal rows and vertical columns where each item can be uniquely identified by a label or key or by it?s position in relation to other items.


a type of archive file format: the Tape ARchive format.


Transmission Control Protocol is one of the core protocols of the Internet protocol suite.


PHP library to generate PDF files.

See also



a procedural code that is automatically executed in response to certain events on a particular table or view in a database

unique key
An unique key is an index over one or more fields in a table which has a unique value for each row. The first unique key will be treated as primary key if there is no primary key defined.

Uniform Resource Locator is a sequence of characters, conforming to a standardized format, that is used for referring to resources, such as documents and images on the Internet, by their location.


A computer (program) that is responsible for accepting HTTP requests from clients and serving them Web pages.


Extensible Markup Language is a W3C-recommended general- purpose markup language for creating special-purpose markup languages, capable of describing many different kinds of data.


a popular data compression and archival format.


an open-source, cross- platform data compression library by Jean-loup Gailly and Mark Adler.

Indices and tables