How to fix ERROR 1064: Packet too large in MySQL

MySQLINTERMEDIATEHIGH

MySQL received a network packet larger than the max_allowed_packet limit. Increase max_allowed_packet in your MySQL configuration to handle larger queries, database imports, or BLOB data uploads.

What this error means

MySQL enforces a maximum size limit on network packets transmitted between the client and server to prevent resource exhaustion and network overload. The max_allowed_packet system variable controls this limit (default 4MB, maximum 1GB). When a packet exceeds this limit, MySQL sends ERROR 1064 and terminates the connection. This error occurs during large SQL dumps, bulk INSERT/UPDATE statements with substantial data, BLOB/TEXT field uploads, or API payloads containing large binary content.

How to fix "ERROR 1064: Packet too large"

1Check the current max_allowed_packet setting

Log into your MySQL server and run:

sql

SHOW VARIABLES LIKE "max_allowed_packet";

The result shows the current limit in bytes. For example:
- 4194304 = 4MB (default)
- 16777216 = 16MB
- 67108864 = 64MB

Note this value to compare against your actual packet needs.

2Determine the required packet size

Measure your largest SQL dump or payload:

bash

# Check file size
ls -lh your_dump.sql

# Get exact byte count
wc -c your_dump.sql

# For application data, check logs or estimate:
# Large WooCommerce exports: 100-500MB
# Media-rich applications: 256MB+
# Standard business apps: 50-100MB

A practical recommendation: set max_allowed_packet to 256MB for most production systems.

3Apply a temporary fix (for immediate testing)

Connect to MySQL and run:

sql

SET GLOBAL max_allowed_packet = 256 * 1024 * 1024;  -- 256MB
SET SESSION max_allowed_packet = 256 * 1024 * 1024;

Verify it took effect:

sql

SHOW VARIABLES LIKE "max_allowed_packet";

Warning: This change resets when MySQL restarts. Use only for testing or one-time operations.

4Make a permanent fix via my.cnf configuration

Edit your MySQL configuration file:

bash

# Linux/macOS
sudo nano /etc/mysql/my.cnf

# Or
sudo nano /etc/mysql/mysql.conf.d/mysqld.cnf

# Windows
notepad "C:\ProgramData\MySQL\MySQL Server 8.0\my.ini"

Locate the [mysqld] section and add (or update):

ini

[mysqld]
max_allowed_packet = 256M
net_buffer_length = 16M

[mysql]
max_allowed_packet = 256M

Save the file and restart MySQL:

bash

# Linux/macOS
sudo systemctl restart mysql
# or
brew services restart mysql

# Windows (PowerShell as Admin)
net stop MySQL80
net start MySQL80

5For one-off imports, use command-line options

If you only need to import a large dump once, pass max_allowed_packet to the client tool:

bash

mysql --max_allowed_packet=256M -u root -p database_name < huge_dump.sql

# Or with mysqldump
mysqldump --max_allowed_packet=256M -u root -p database_name > backup.sql
mysql --max_allowed_packet=256M -u root -p database_name < backup.sql

This avoids permanent configuration changes for temporary needs.

6Verify the fix resolves the error

Re-run your import or operation:

bash

mysql --max_allowed_packet=256M -u root -p database_name < dump.sql

If it succeeds, the error is resolved. If the error persists:
- Increase to 512MB: --max_allowed_packet=512M
- Check if your file or query is genuinely larger than expected
- Review application logs to confirm packet sizes being sent

For application-level errors, update your connection string or database driver settings if they support max_allowed_packet configuration.

How to fix ERROR 1064: Packet too large in MySQL

What this error means

Typical symptoms

Common causes

How to fix "ERROR 1064: Packet too large"

Advanced notes

Related errors

Official resources & further reading