Meilisearch Payload Too Large Error
Quick answer
Requests above the server payload limit (default 100 MB) are rejected with payload_too_large. Split the file into batches or compress it.
Most likely fix: Split or compress
How to fix it
Try these in order — the most common fix is first.
1. Split or compress
- Split into batches of tens of thousands of documents (NDJSON works well)
- Compress with gzip, deflate or br and set Content-Encoding
- Self-hosted: raise the limit with --http-payload-size-limit
- Cloud: Enterprise accounts can request a higher limit
Did this fix it?
Symptoms
Adding documents returns payload_too_large or 413.
Why it happens
- Document file bigger than the default 100 MB limit
This guide also covers
- meilisearch payload too large
- meilisearch 413
- meilisearch http payload size limit
Still not working?
If Meilisearch keeps failing, you're not alone. See every Meilisearch problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Typesense 503 Not Ready or Lagging Error (Typesense)
Algolia 429 Too Many Requests Error (Algolia)
Other Meilisearch errors
- Meilisearch Tasks Stuck on Enqueued
- Meilisearch Indexing Slow
- Meilisearch Documents Not Showing Up
- Meilisearch Primary Key Error
- Meilisearch Filter Not Working (Attribute Not Filterable)
- Meilisearch Invalid API Key / Missing Authorization Header
- Meilisearch Database Version Incompatible After Upgrade
- Meilisearch Disk Usage Keeps Growing / No Space Left on Device