Free tool · no signup

Email Attachment Size Limit Checker

Gmail's attachment limit is 25 MB, Outlook.com's is 20 MB, and both are measured after encoding — which inflates every attachment by about a third, so a 19 MB file already exceeds a 25 MB limit once it is packaged. This checker does that maths for any file size and every major provider, and lists the daily sending limits too.

Runs entirely in your browser. Nothing you paste is uploaded, logged or stored.

Several files? Add them up — the limit applies to the whole message.

On the wire, after encoding

24.0 MB

Base64 adds about 33%. Your 18.0 MB file travels as 24.0 MB — 5 of 8 providers will send it.

ProviderSendsSend limitReceive limitLargest file that fitsOver the limit
Gmail / Google Workspace2,000 recipients/day (Workspace); 500 for a free accountfits25.0 MB50.0 MB18.7 MBFiles over the limit are swapped for a Google Drive link automatically.Source: Google Workspace Admin Help
Outlook.com300 recipients/day for a new account, rising with account agetoo big20.0 MB150.0 MB15.0 MBPrompts you to upload to OneDrive and send a link instead.Source: Microsoft Support
Microsoft 365 (Exchange Online)10,000 recipients/day per mailboxfits25.0 MB25.0 MB18.7 MBThe message is rejected with a 552 error. The tenant default can be raised to 150 MB by an admin.Source: Microsoft Exchange Online limits
Apple iCloud Mail1,000 messages/day, 500 recipients per messagetoo big20.0 MB20.0 MB15.0 MBMail Drop takes over for attachments up to 5 GB, sending a link valid for 30 days.Source: Apple Support
Yahoo Mailfits25.0 MB25.0 MB18.7 MBRejected outright — no automatic link fallback.Source: Yahoo Help
Proton MailVaries by plan; free accounts are limited to 150 messages/dayfits25.0 MB25.0 MB18.7 MBRejected. Proton Drive sharing is the workaround.Source: Proton support
Zoho Mailtoo big20.0 MB40.0 MB15.0 MBRejected above the plan limit; larger allowances exist on higher tiers.Source: Zoho Mail help
Fastmailfits70.0 MB70.0 MB52.5 MBOne of the highest limits available — but the receiving server's limit still applies.Source: Fastmail help

Both limits apply: yours on the way out, the recipient’s on the way in, and the lower one wins. Figures checked September 2026 — providers change them, so confirm before sending something critical.

  • Enter a file size and see which providers will accept it
  • Applies the base64 overhead that trips up every borderline attachment
  • Send limits and receive limits shown separately — they differ
  • Daily sending limits per provider, for bulk and cold-mail planning
  • What each provider does when you go over: link, or hard rejection
  • The largest file that fits each limit, worked out for you

How to use it

Four steps, about thirty seconds

  1. 01

    Enter your file size

    In MB, as your operating system reports it. Several files? Add them up first — the limit applies to the whole message.

  2. 02

    Read the verdict per provider

    Green means it fits after encoding. The table shows both the sending limit and the recipient's receiving limit.

  3. 03

    Check the recipient's side too

    Your provider's send limit is only half of it. Microsoft 365 defaults to 25 MB on receive, which is where most 'but it sent fine' failures happen.

  4. 04

    Go around it if needed

    Over the limit, a link beats a fight: Drive, OneDrive, Mail Drop or a signed URL. The page explains which each provider does automatically.

The encoding

Why a 24 MB file fails a 25 MB limit

Email is a text protocol. It has been since 1982, and it cannot carry raw binary data — so every attachment is base64-encoded, which represents three bytes using four characters. The result is about 33% larger than the file on your disk, and the encoded size is the one the provider checks.

So the working rule is: your real ceiling is roughly three-quarters of the stated limit. An 18 MB file fits comfortably under Gmail’s 25 MB. A 20 MB file is borderline once the headers and MIME framing are added. A 24 MB file — under the limit by every number your file manager shows you — is rejected.

Base64 overhead against a 25 MB limitAn 18 MB file encodes to about 24 MB and fits under a 25 MB limit. A 24 MB file encodes to about 32 MB and is rejected, even though the file itself is smaller than the stated limit.25 MB limit18 MB fileon the wire24 MB — sends24 MB fileon the wire32 MB — rejectedRule of thumb: your real ceiling is about three-quarters of the stated limit.
Both files look like they fit. Only one of them does.

Two limits

Yours on the way out, theirs on the way in

The second most common failure has nothing to do with encoding: the message left fine and the recipient’s server refused it. Every hop can enforce its own ceiling, and the lowest one decides.

This is why a 25 MB attachment sent from Gmail bounces into a Microsoft 365 tenant that never raised its 25 MB default — the encoding pushed it past the line on the receiving side. It is also why “it worked when I sent it to myself” proves nothing at all.

The bounce, when it comes, is usually a 552 (message too large) or 5.3.4 (message size exceeds fixed maximum). Both name the limit that was hit; the header analyzer will show you which server said it.

Going around it

What to do when the file is too big

Ranked by how well each option actually works, rather than by how obvious it is.

OptionHow it goesWatch out for
A cloud linkBest by a distance. Gmail swaps in a Drive link automatically over 25 MB; Outlook.com offers OneDrive; Apple Mail uses Mail Drop for up to 5 GB.Check the sharing permissions. A link the recipient cannot open is worse than a bounce, because nobody finds out for a day.
Compress itUseful for documents and uncompressed formats. A folder of Word files can shrink dramatically.Nothing on a photo, video or PDF — those are already compressed. And many providers block .zip files containing executables outright.
Shrink the originalOften the real answer. A PDF exported at print resolution is frequently ten times larger than it needs to be.Re-exporting at screen resolution can lose detail someone needs. Ask before flattening a document.
Split across emailsWorks, technically.The worst option. It irritates the recipient, multi-part archives fail if one message lands in spam, and a burst of near-identical attachments is itself a spam pattern.

Sending limits

The other limit: how many, not how big

Daily sending caps are anti-abuse ceilings, not targets. Google Workspace allows 2,000 recipients a day (500 on a free Gmail account), Microsoft 365 allows 10,000 per mailbox, Outlook.com starts a new account near 300 and raises it with age, and iCloud allows 1,000 messages.

Two things people get wrong here. First, recipients, not messages — one email to fifty people spends fifty of your allowance. Second, hitting the cap is not the real risk; approaching it from a new domain is. A brand-new sending domain going from zero to a thousand messages a day looks exactly like a compromised account, and the response is usually a quiet routing of your mail to spam rather than a visible block.

If you are planning volume, the outbound calculator works out how many sends your reply rate actually requires — which is often far fewer than the cap, and the useful number to plan against.

Questions

Frequently asked

Short answers, including the ones where the honest answer is “this tool can’t do that”.

25 MB for a message you send, and 50 MB for one you receive. Files above 25 MB are replaced automatically with a Google Drive link rather than rejected.

The product behind the tool

AI Emaily does the part this tool can’t: the reply.

A free tool cleans up a list or builds a link. AI Emaily reads the thread, drafts the answer in the voice you set, and waits for one click — across Gmail, Outlook, iCloud and any IMAP mailbox. You approve every send.

Ready when you are

Email, finally worthy of your attention.

Start your 7-day free trial. Cancel anytime.

  • 7-day free trial
  • Cancel anytime
  • Every provider