My module upload fails with "file too large". What do I do?

This is usually a PHP upload limit, not a problem with the module ZIP. PrestaShop receives the ZIP through PHP's normal uploaded-file flow; if PHP rejects the file first, the back office can only show a "file too large" or incomplete-upload error.

Ask your host to raise upload_max_filesize and post_max_size. Set post_max_size higher than upload_max_filesize, because the whole HTTP POST has overhead. For bigger modules or slow shared hosting, also raise max_execution_time so PHP has time to copy and extract the archive.

; php.ini or .user.ini example
upload_max_filesize = 64M
post_max_size = 80M
max_execution_time = 300
memory_limit = 256M

# Apache + mod_php only, not PHP-FPM
php_value upload_max_filesize 64M
php_value post_max_size 80M
php_value max_execution_time 300

After changing PHP settings, restart PHP-FPM or Apache if your host requires it, then reload the PrestaShop back office and try again. If you cannot change those values, upload by FTP/SFTP instead: unzip the module locally, copy the module folder into /modules/, then install it from Modules > Module Manager. The installed result is the same as a successful ZIP upload.

Still stuck? Contact our support team with the ZIP name, file size, PrestaShop version, PHP version and the exact upload error.

When you use FTP/SFTP, make sure you upload the folder that contains the module's main PHP file. For example, a module whose source declares $this->name = 'mprinternallinking' must live as /modules/mprinternallinking/, with mprinternallinking.php and its vendor/, controllers/, views/ or src/ files inside that same folder. An extra wrapper folder is a common reason the module does not appear in Module Manager.

After the files are in place, do not stop there. The install routine is what creates module tables, registers hooks and adds admin controllers. In the inspected modules, install code can also reset opcache, install shared admin config storage and seed defaults. If you only copy files and never click Install, those database tables and hooks are missing.

If a previous failed upload left a half-created folder, remove only that incomplete module folder before retrying, then upload a clean copy. Do not delete unrelated PrestaShop cache or module folders just because the upload failed; the failure usually happened before the module install code even ran.