The "Incorrect format parameter" error in phpMyAdmin usually appears when importing a database file that is too large, in an unsupported format, or when the upload timed out during transfer. This guide covers all the common causes and how to work around them.
If the file is larger than 128MB, skip phpMyAdmin entirely and import via SSH: mysql -u dbuser -p dbname < backup.sql. This has no size limit and is significantly faster for large databases.
01. Common Causes
File too large - phpMyAdmin is limited by PHP's upload_max_filesize setting (typically 128MB on our servers). Files larger than this will fail silently or show the "Incorrect format parameter" error.
Wrong file format - phpMyAdmin expects a valid SQL dump file (.sql) or a compressed SQL dump (.sql.gz or .sql.zip). If you're trying to import a CSV, you need to select "CSV" from the format dropdown on the import page instead of leaving it on "SQL."
Upload timeout - Large files on slower connections may time out during the upload phase. The file arrives incomplete and phpMyAdmin can't parse it.
Corrupted export file - If the original export was interrupted, the .sql file may be truncated or contain incomplete statements.
02. Fixing Upload Size Limits
If the file is under 256MB and you want to use phpMyAdmin, increase the PHP upload limit:
- Log in to cPanel and go to "MultiPHP INI Editor"
- Select your domain from the dropdown
- Find
upload_max_filesizeand set it to256M - Also set
post_max_sizeto256M(must be equal to or greater than upload_max_filesize) - Save and retry the import in phpMyAdmin
For more details, see Changing Maximum Upload Size.
03. Importing via SSH (No Size Limit)
For files over 128MB or when phpMyAdmin keeps timing out, SSH import is the most reliable method:
# Upload the .sql file to your home directory via FTP first, then:
# Import an uncompressed .sql file
mysql -u cpaneluser_dbuser -p cpaneluser_dbname < backup.sql
# Import a gzipped file without extracting first
gunzip < backup.sql.gz | mysql -u cpaneluser_dbuser -p cpaneluser_dbname
You'll be prompted for the database password. Replace the username and database name with your actual cPanel-prefixed values. See our SSH access guide if you need help connecting.
SSH imports are 10-50x faster than phpMyAdmin for large databases because there's no web server overhead, no upload size limit, and no timeout. A 500MB database that fails in phpMyAdmin will import in seconds via SSH.
04. Checking File Format
phpMyAdmin's import page supports these formats:
SQL (.sql, .sql.gz, .sql.zip) - Standard database dump from mysqldump, phpMyAdmin export, or another MySQL tool. This is the default and most common format.
CSV (.csv) - Imports data into a single table. You must select "CSV" from the Format dropdown and specify the target table.
If you're importing a file exported from another tool (like a WordPress plugin export, a .json file, or an Excel spreadsheet), it needs to be converted to SQL or CSV first. For proper export format guidelines, see Proper Import/Export Format.
Import Still Failing?
If you've tried increasing the limits and the import still fails, open a support ticket with the file size and error message. We can import it server-side.
Open a Support TicketQuick Recap: phpMyAdmin Import Errors
- Check file size against phpMyAdmin's upload limit
- Use SSH for large imports - no size limit, much faster
- File must be .sql or .sql.gz - other formats need the correct dropdown selection
- Increase upload_max_filesize and post_max_size in MultiPHP INI Editor
- Contact support if we need to import it server-side
Last updated March 2026 · Browse all PHP/MySQL articles
