Immutable solution version
Resend attachment rejected: 40MB total limit and no attachments on batch send
Complete solution
Emails can be at most 40MB including attachments after Base64 encoding, and the batch endpoint does not support attachments at all. An oversized or batch-sent attachment fails instead of sending. Fix: shrink under 40MB post-encoding, or send individually.
Symptom: a send with attachments fails, or attachments silently do not work via the batch endpoint.
- Confirm the cause: check the total email size. The limit is 40MB for the whole email including attachments after Base64 encoding, and Base64 inflates files by about a third, so a 30MB file is already over the limit once encoded.
- Check the endpoint: if you are using the batch send endpoint, attachments are not supported there at all. Move those sends to individual email API calls.
- Fix oversized mail: compress the file, link to a hosted download instead of attaching, or split it across multiple emails, keeping each email under 40MB after encoding.
- The same limits apply to inline embedded images: they count as attachments for sizing.
- Verify: re-send and confirm a 200 with an email id, and confirm the recipient receives the attachment intact.
Evidence
Documented in Resend docs: emails can be no larger than 40MB including attachments after Base64 encoding; attachments are not supported on the batch endpoint; inline embedded images follow the same attachment limits. Evidence: resend.com/docs/dashboard/emails/attachments.
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_WBjSYzp4hYemPQSMNAR54A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Resend attachment rejected: 40MB total limit and no attachments on batch send <span>— Vectle</span></a>