How to Increase phpMyAdmin Upload File Size Limit in cPanel & Linux VPS

Why Does phpMyAdmin Default to a 2MB Upload Limit?

By default, vanilla PHP installations restrict file uploads to 2MB (upload_max_filesize = 2M) to prevent unauthorized users from exhausting server memory buffers during HTTP POST requests. However, modern WordPress databases with years of blog posts, WooCommerce transactions, and page builder data routinely exceed 50MB to 500MB, triggering the frustrating “No data was received to import” or “File exceeds maximum allowed size” errors in phpMyAdmin.

Method 1: Increasing Upload Limits in cPanel (Shared Hosting)

1. Log in to your CpanelFree dashboard and scroll to the Software section.
2. Click on MultiPHP INI Editor (or Select PHP Version > Options).
3. Select your home directory or specific domain from the dropdown menu.
4. Locate and update the following four values:
   • upload_max_filesize: 512M
   • post_max_size: 512M (Must always be equal to or greater than upload_max_filesize)
   • memory_limit: 512M
   • max_execution_time: 300 (Seconds)
5. Click Apply. Re-open phpMyAdmin, and the import screen will now display “(Max: 512MiB)”.

Method 2: Increasing Limits in Linux VPS (Ubuntu / Debian / Nginx / Apache)

On dedicated or cloud VPS instances, edit the master PHP-FPM configuration file using your preferred terminal editor:

sudo nano /etc/php/8.3/fpm/php.ini

Search for and update the directives:

upload_max_filesize = 512M
post_max_size = 512M
memory_limit = 512M
max_execution_time = 300
max_input_time = 300

Updating Nginx Client Body Buffer Limit (client_max_body_size)

If your VPS runs Nginx reverse proxy, Nginx enforces its own independent upload restriction (default 1MB). Add this line inside the http { ... } or server { ... } block in /etc/nginx/nginx.conf:

client_max_body_size 512M;

Restart PHP-FPM and Nginx to load the changes:

sudo systemctl restart php8.3-fpm
sudo systemctl restart nginx

Method 3: Increasing Limits via .htaccess or .user.ini

On Apache servers running PHP as an Apache module or via FastCGI, add these rules to your root .htaccess file:

php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 512M
php_value max_execution_time 300
php_value max_input_time 300

Understanding max_input_vars and Memory Fragmentation in phpMyAdmin

In addition to file size directives, importing complex multi-table SQL backups containing thousands of WooCommerce attributes or translated taxonomy terms can trigger truncated input errors. In your php.ini, increase the max_input_vars limit from the default 1000 to 5000:

max_input_vars = 5000
max_input_time = 600

Bypassing Browser Timeouts with Gzip Compressed Imports

Instead of uploading raw uncompressed .sql files (which waste upload bandwidth and trigger HTTP socket timeouts), always compress your SQL dumps into .sql.gz or .sql.zip format prior to uploading. phpMyAdmin automatically detects compressed archives, decompresses them in memory on the fly, and reduces initial network upload payload by up to 85%.

Diagnostic Checklist for phpMyAdmin Upload Errors

• ✅ Verify upload_tmp_dir: Ensure the Linux temporary upload directory (/tmp) has free disk space and write permissions (chmod 1777 /tmp).
• ✅ Check Post Max Size Alignment: Confirm post_max_size is set strictly equal to or larger than upload_max_filesize.
• ✅ Restart Web Daemons: Always reload PHP-FPM and Nginx/Apache after editing configuration files.

Comparing Upload Limits Across Common Web Control Panels

By properly scaling your upload limits across PHP, web server daemons, and database buffers, you ensure smooth database migrations and uninterrupted site administration.

Frequently Asked Questions

Troubleshooting phpMyAdmin Session Expired Errors

If phpMyAdmin logs you out during long database imports, increase the session expiration timeout in php.ini: session.gc_maxlifetime = 3600. This keeps your administrative session active for up to 60 minutes continuously.