How to import table in phpmyadmin? I got error of file size

How to import table in phpmyadmin? I got error of file size

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Diagnosing and Resolving the "No Data Was Received" Import Error in phpMyAdmin

Encountering the error message No data was received to import. Either no file name was submitted, or the file size exceeded the maximum size permitted by your PHP configuration is a frequent stumbling block when migrating databases via phpMyAdmin. When you have a 4.8 MB SQL dump file and receive this specific warning, it rarely indicates that your file is actually too large for modern servers. Instead, it points to a configuration bottleneck within the PHP environment running your web server.

The error message itself provides a direct clue: file size exceeded the maximum size permitted by your PHP configuration. By default, many shared hosting environments or fresh installations restrict the upload_max_filesize and post_max_size directives. While phpMyAdmin runs on PHP, the import process relies on reading the uploaded file into memory or processing it via a form submission. If your server is configured to accept only 2 MB uploads (a common default), a 4.8 MB file will be rejected before the import logic even begins executing.

To resolve this, you must inspect and modify your PHP configuration. Locate the php.ini file used by your specific server instance. You need to find and update the following directives:

upload_max_filesize = 128M
post_max_size = 128M
memory_limit = 256M

Setting upload_max_filesize higher ensures the web server accepts the file upload in the first place. Crucially, post_max_size must be equal to or larger than upload_max_filesize. If you set the upload limit to 128 MB but leave post_max_size at its default, any POST request containing a file larger than that second threshold will fail silently or trigger errors. Increasing memory_limit is also advisable during import operations, as phpMyAdmin needs sufficient RAM to hold the parsed SQL statements in memory before executing them against the database engine.

After editing php.ini, you must restart the web server (Apache, Nginx with PHP-FPM, etc.) for changes to take effect. Once the service is restarted, attempt the import again directly through the phpMyAdmin interface. The file should now process without triggering the size error.

However, there is a significant trade-off depending on your hosting setup. If you are using shared hosting, you may not have access to php.ini. In that scenario, you must look for .user.ini in your home or public_html directory, or modify settings via your control panel (cPanel/Plesk) under "Select PHP Version" or "Software Settings." Many modern panels allow you to set these limits per-directory without root access.

If modifying the server configuration remains impossible, bypassing phpMyAdmin entirely is often the most robust solution for larger datasets. Command-line tools like mysql or mariadb do not suffer from the same form submission limitations. You can simply run:

mysql -u username -p database_name < path/to/your/file.sql

This approach streamlines the import by sending data directly to the SQL client without involving the HTTP layer, effectively sidestepping PHP's upload_max_filesize restrictions. This method is particularly useful if you are on a server where SSH access is enabled but phpMyAdmin web interface limitations persist.

Our network