scribase
Fix guide

Resend caps a whole email at 40 MB, measured after Base64 encoding

Resend's own docs put a 40 MB ceiling on a full email — subject, body and attachments combined, after Base64 encoding. Because Base64 inflates raw file size by roughly a third, the practical ceiling on the files you actually attach is closer to 28-30 MB, not 40 MB, which is why an attachment that looks well under the limit on disk can still get rejected.

Last checked November 19, 2026.

Where the limit actually sits

The 40 MB cap applies to the whole encoded email, not to the raw attachment file. Base64 encoding — the format email attachments are sent in — adds roughly 33% to a file's raw size, so a 30 MB PDF can already be close to the ceiling once encoded, well before it feels like a '40 MB file'.

A separate, unrelated limit: emails that include attachments cannot be sent through the batch-send endpoint at all — only the single-send endpoint supports them.

Sources: Resend: Attachments

What to do about it

  • Budget for roughly 28-30 MB of raw file as the practical safe ceiling, not 40 MB, once Base64 overhead is accounted for.
  • For anything larger, send a link to the file (object storage, a signed URL) in the email body instead of attaching it directly.
  • If sending with attachments, use the single-send endpoint — the batch endpoint does not support them.
  • Resend also maintains a list of unsupported file types regardless of size, so confirm the file type is allowed before debugging size alone.

Sources: Resend: Attachments

If large files are the real problem

A Scribase project includes file storage alongside email sending, so a large file can be uploaded once and linked from the email body instead of attached directly — sidestepping the encoded-size ceiling entirely rather than working around it per message.

Sources: Scribase pricing

FAQ

Questions people ask

Is the 40 MB limit on the raw file or the encoded email?

The encoded email. Base64 encoding inflates the raw file size by about a third, so the practical safe raw-file size is closer to 28-30 MB.

Can I send an attachment through the batch endpoint?

No — Resend's docs state that emails with attachments cannot be sent through the batch-send endpoint; use the single-send endpoint instead.

What should I do for a file bigger than 30 MB?

Upload it to object storage and link to it from the email body instead of attaching it directly — this avoids the encoded-size ceiling entirely.

Does file type matter too?

Yes. Resend's docs list specific unsupported file types independent of size, so a rejection is not always about size alone.