How to Fix: “SQLSTATE[42000]: Specified key was too long; max key length is 1000 bytes” in Laravel Migration (MySQL)

If you’ve ever encountered the following error during Laravel migrations, especially when working with MySQL or MariaDB, you’re not alone: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes This error is common, but the good news is — it’s easily fixable. Let’s explore why this […]

If you’ve ever encountered the following error during Laravel migrations, especially when working with MySQL or MariaDB, you’re not alone:

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes

This error is common, but the good news is — it’s easily fixable. Let's explore why this happens, how to resolve it, and what settings you should check to avoid it in the future.

🧠 Why This Laravel Migration Error Happens

This issue originates from MySQL, not Laravel itself.

By default, Laravel uses the InnoDB storage engine and the utf8mb4 character set for better Unicode support (like emojis). But older MySQL/MariaDB versions and misconfigured MySQL setups may still use:

• The MyISAM engine (which has a lower max key length limit of 1000 bytes)
• A row format of Compact, instead of Dynamic
• An incompatible charset or collation

All of these can trigger the 1071 error when indexing long string columns.

🛠️ Fix 1: Change Default Storage Engine to InnoDB

If your MySQL is still using MyISAM as the default engine, switch to InnoDB. Here's how:

✅ Step-by-Step via my.ini or my.cnf

1. Open your MySQL configuration file:

   • On Linux/macOS: /etc/mysql/my.cnf or /etc/mysql/mysql.conf.d/mysqld.cnf
   • On Windows: C:\ProgramData\MySQL\MySQL Server x.x\my.ini

2. Under the [mysqld] section, add or update:

   default-storage-engine = InnoDB

3. Save and restart your MySQL server.

🛠️ Fix 2: Update Laravel's Database Config

You can explicitly define the storage engine in your Laravel project inside config/database.php:

'mysql' => [
    // other config...
    'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',
],

This helps Laravel apply the correct row format and engine when creating tables.

🛠️ Fix 3: Row Format — Set to Dynamic

Older MySQL setups default to ROW_FORMAT=Compact, which can conflict with long index keys.

To set the row format to dynamic, do one of the following:

Option 1: MySQL Global Setting

Add this in your my.cnf or my.ini:

innodb_default_row_format = dynamic

Option 2: Laravel Config (as shown above)

'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

🛠️ Fix 4: Use Schema::defaultStringLength(191) (Fallback Option)

In some cases, when none of the above work (usually on MySQL < 5.7.7 or MariaDB < 10.2.2), you can fall back to:

use Illuminate\Database\Schema\Builder;

public function boot(): void
{
    Builder::defaultStringLength(191);
}

But remember — this is a workaround, not a real fix. Laravel includes this to support legacy systems, but ideally, your MySQL settings should be compatible with Laravel's default behavior.

❓ So, Is This a Laravel Bug?

No. This issue is entirely on the MySQL configuration side. Laravel expects a modern database setup (InnoDB, utf8mb4, dynamic row format). If your MySQL isn’t configured accordingly, you might face this error.

That’s why Laravel doesn’t "fix" this by default in each new project. It’s your environment’s responsibility to meet modern standards.

✅ Summary – Fixing Laravel's Key Length Error

📌 Final Thoughts

Fixing the "Specified key was too long" error in Laravel is mostly about setting up your MySQL environment correctly. Once you've updated the default engine and row format, you’ll rarely see this issue again.

Happy coding! 🚀
Feel free to bookmark this guide for the next time you hit a migration error!