ERR_AIRTABLE_413 on Airtable: Airtable API Returns 413 Payload Too Large When Uploading Records. Root cause: The Airtable REST API enforces a 5MB maximum payload size per request and a limit of 10 records per batch create/update call. Sending large base64-encoded attachments inline, or batching more than 10 records, causes the API gateway to reject the request with a 413 error before it reaches Airtable servers. Step 1: Split Records into Batches of 10. Restructure your API calls to send a maximum of 10 records per request. If you are using a Zapier or Make.com integration, enable the "batch" option and set the batch size to 10. Step 2: Upload Attachments via URL Instead of Base64. Instead of embedding file content as base64 in the API payload, upload the file to a public URL first (e.g. S3, Cloudinary, or Dropbox public link) and pass the URL in the attachment field. Airtable will fetch the file server-side. Step 3: Compress Images Before Upload. If you must send file data directly, compress images to under 500KB each using a tool like Sharp or TinyPNG before encoding. Keep total payload under 4MB to leave a safety margin.