Algolia Record Is Too Big Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Reduce the record size

   Copy steps
   1. Remove attributes you do not search, filter or display
   2. Truncate long text or strip HTML before sending
   Did this fix it? Yes No

2. 2. Split big content into several records

   Copy steps
   1. Break long documents into chunks with a shared parent attribute and use distinct to group them
   2. The Crawler offers helpers.splitContentIntoRecords
   Did this fix it? Yes No

3. 3. Filter before sending

   Copy steps
   1. Measure the serialized JSON size per record and skip or fix records over the limit
   2. If a batch failed, read the error for the failing objectIDs, remove them and retry
   Did this fix it? Yes No

4. 4. Check your plan limit

   1. Compare your largest record with the limit for your plan; higher limits come with higher plans
   Did this fix it? Yes No

Symptoms

Indexing fails with an error like "Record at the position N objectID=X is too big size=..." and the whole batch is rejected.

Why it happens

• A record exceeds your plan's maximum record size
• Long text fields (full article bodies, HTML) stored in one record
• Duplicated or unneeded attributes
• The whole payload is rejected when any record is over the limit

This guide also covers

• algolia record too big
• algolia record size limit
• algolia objectID is too big

The same problem in other apps

All not loading, error messages & connection guides →

• Meilisearch Primary Key Error (Meilisearch)
• Typesense 503 Not Ready or Lagging Error (Typesense)

Other Algolia errors

• Algolia Search Returns No Results
• Algolia Search Results Irrelevant or Wrong Order
• Algolia 429 Too Many Requests Error
• Algolia Record Quota Exceeded or Limit Reached
• Algolia Invalid Application ID or API Key (403)
• Algolia Updates Not Showing in Search Results
• Algolia Search Slow or High Latency
• Algolia Crawler Not Indexing Records