← Back to blog

Email Attachment Size Limit: Gmail, Outlook and Beyond

November 12, 2026
Email Attachment Size Limit: Gmail, Outlook and Beyond

Most mainstream email services cap a message at roughly 20 to 25 MB, and Base64 encoding means the file you can actually attach is smaller still, around 18 MB under a 25 MB cap. If your file is bigger, stop fighting the limit and send a download link instead.

Below you will find the limits for the major providers, the arithmetic that explains why "25 MB" really means about 18 MB, what to do when a file is too big, and how one-time and signed download links work.

Pingfloat
Share large files beyond email limits
Pingfloat includes file sharing tools for developers and IT professionals who need an alternative to oversized email attachments.
Visit

TL;DR

  • Gmail and Yahoo cap sending at 25 MB, Outlook at 20 MB for internet accounts, and iCloud Mail at 20 MB.
  • Encoding adds about 37% to a file, so a 25 MB limit leaves roughly 18 MB for the raw attachment.
  • The recipient's server has its own limit, and it can reject a message your server accepted.
  • Above roughly 15 to 18 MB, send a secure download link instead of an attachment.
  • Expiring, single-use or signed links let you control who downloads and for how long.

Table of Contents

Attachment size limits by provider

The numbers below are the ones you will hit most often. They describe the whole message, not just one file, and they change over time, so treat them as a guide and confirm with your provider's help page if a send is borderline.

ProviderTypical send limitNotes
Gmail25 MBLarger files are offered as a Google Drive link
Yahoo Mail25 MBSame ceiling as Gmail
Outlook (internet accounts)20 MBOversized files can be shared via OneDrive
iCloud Mail20 MBLeaves about 14 to 15 MB of raw file
Proton Mail25 MB send, 50 MB receiveUp to 100 files per message
Office 365 (one university's setup)35 MBAdministrators can change it
Amazon SES (SMTP, v2 API)40 MBThe v1 API allows only 10 MB

Sources for each row are linked in the sections that follow. One pattern matters more than any single number: limits vary by provider and organization, and the receiving server's limit counts as much as yours.

Gmail attachment limit

Gmail sends up to 25 MB per message. When you attach something larger, Gmail uploads the file to Google Drive and inserts a share link in its place. That is convenient, but the recipient now depends on Drive permissions, and a link that you leave open to anyone stays open until you change it.

Outlook attachment limit

The question of how big an Outlook attachment can be has two answers. For internet accounts such as Gmail or Yahoo added to Outlook, the cap is 20 MB combined. Exchange-based accounts follow whatever the administrator configured. Microsoft 365 administrators can set limits from 1 MB to 150 MB, so a colleague's inbox may accept far more than your personal one. Outlook can also offer to upload an oversized file to OneDrive and send a link, which handles a file up to 2 GB.

Outlook attachment limit

Yahoo, iCloud, Proton and business hosting

Yahoo Mail matches Gmail at 25 MB, and Fivetran's documentation lists 25 MB for Gmail and Yahoo, 20 MB for Outlook and 40 MB for Amazon SES v2. iCloud Mail sits at 20 MB. Proton Mail allows 25 MB to send and 50 MB to receive, with up to 100 attached files per message.

Email attachment limits across five providers

Business and self-hosted systems differ. One hosting provider documents a 40 MB maximum per message including the body and attachments, yet warns that messages around 30 MB or larger may fail. So the answer to "is 40 MB too big for an email?" is: sometimes it is accepted, but it is a gamble you do not need to take.

Why a 25 MB limit really means about 18 MB

Email was designed for text. To carry a binary file such as a PDF or a photo, the message converts it into plain ASCII text using Base64. That conversion turns every 3 bytes into 4 characters, which adds about 33% overhead, and MIME line wrapping at 76 characters brings the total to about 37%.

The consequence is simple division:

The message body, signature images and headers also take a share of the envelope. A practical rule: keep the raw file under about 70% of the stated cap. For a 25 MB limit, aim for 15 to 17 MB at most.

If you handle encoding in code, our guide to Base64 overhead for developers explains where the extra bytes come from, and the Base64 encoder and decoder lets you check an encoded size yourself.

Why email limits exist at all

The cap is not arbitrary. Every attachment is stored on the sender's server, relayed to the recipient's server, and stored again, often with copies in sent folders, backups and spam scanning. A mailbox full of 100 MB messages becomes expensive to host and slow to search. Large messages also tie up delivery queues and give malware a bigger place to hide, so providers scan and constrain them.

The limit also protects the weakest link in the chain. Your server may accept 50 MB, but the recipient's server decides whether the message arrives. A mismatch produces a bounce, or in the worst case a silent failure. If you send from an application, message and attachment limits in email delivery services and APIs are worth knowing before you build a feature that emails reports or invoices.

What to do when your file is too big

Work through these options in order, from least effort to most control.

  1. Compress the file. Zip documents, export PDFs at a lower quality setting, and resize images. Zipping already-compressed formats such as JPEG or MP4 saves little.
  2. Split the send. Several smaller emails each stay under the cap. This works, but it is clumsy for the recipient and fills inboxes.
  3. Use your provider's built-in link feature. Drive or OneDrive links work well inside one ecosystem. Check the sharing setting so you are not leaving the file open to anyone with the URL.
  4. Send a secure download link. Upload the file once, paste a link in the email, and control access. This is the approach we recommend for anything above roughly 15 MB, for sensitive files, and whenever you want to know the file arrived.

Fivetran's own advice for oversized email data follows the same logic: compress, split into separate emails, or use another route.

A download link replaces the attachment with a URL. The file lives on a file-sharing service, and the email stays tiny, so no mail server limit applies. The security comes from the controls around the link.

An expiring link stops working after a set time. Cloud storage platforms offer this through signed URLs. An S3 presigned URL, for example, embeds a signature and an expiry in the link itself, so anyone holding it can download until the time runs out, and nobody can after. Our comparison of expiring download links across AWS, GCS and Pingfloat walks through the different lifetimes and when each fits.

A one-time link works for a single download and is then dead. It suits contracts, credentials exports and anything that should not sit on the internet after the recipient has it. When you evaluate any one-time sharing option, check these settings:

  • Is the link truly invalidated after the first completed download, or only after the first click?
  • Can you set an expiry as a backstop in case nobody opens it?
  • Can you revoke the link manually at any time?
  • Is the transfer encrypted in transit?
  • Can you see whether the file was downloaded?

Many link-based tools handle revocation and expiry together; our piece on expiring links and instant revocation for dev teams covers how that looks in practice.

Tracking downloads

With a link, you can usually see whether a file was opened, which an attachment never tells you. That matters for proposals, invoices and press kits. For marketers, a share page can also capture the recipient's details before the download, which turns a file send into a lead.

Signed URLs for developers

If you build your own delivery, a signed URL (the S3 presigned pattern) is the standard way to hand out time-limited access to private objects without making the bucket public. Generate the URL server-side, set the shortest expiry that works, and never log the full URL where others can read it. Our guide to securing files in transit covers the wider checklist.

Our perspective

We built Pingfloat around a simple observation: the email attachment limit is a rule about mail servers, not about your file. The moment a file crosses roughly 15 MB, the question stops being how to squeeze it in and becomes how to deliver it well.

Delivering it well means three things. The recipient can download it without a login or an installer. You decide how long the link lives. And you are not paying for it with the privacy of the file. That is why our file sharing tool is built for secure transfer, with optional sign-up for expanded storage rather than a wall in front of the basics.

For teams, the same logic scales: a link in an email is lighter, safer and easier to audit than a dozen copies of an attachment scattered across inboxes. We would rather you send one link you can control than one file you can never take back.

Andreas

Send the file without the size limit

When an attachment is too big, Pingfloat's file sharing and secure transfer tool lets you upload the file and send the recipient a link instead. Core use needs no installation and no account. Signing up adds options such as expanded storage, and the share flow supports lead capture if you are sending to prospects.

Pingfloat

Developers who want to automate this can look at the Pingfloat Public API, and the full toolset also covers Base64, JSON, SSL and uptime checks. For a longer walkthrough of the process, read our guide to sending large files securely without servers.

A quick checklist before you hit send

  • Check the total size, including every attachment and any inline images.
  • Subtract about 30% to estimate the real room under the cap.
  • Find out what the recipient's provider allows, especially for corporate inboxes.
  • For anything sensitive, choose a link with an expiry over an attachment that lives forever in two mailboxes.
  • Tell the recipient in the email body how long the link works.

FAQ

What is the file limit for Outlook?

Outlook caps attachments at 20 MB combined for internet accounts. Exchange and Microsoft 365 accounts follow the administrator's setting, which can range from 1 MB to 150 MB. Oversized files can be uploaded to OneDrive and shared as a link.

Is 40 MB too big for an email?

For Gmail, Yahoo, Outlook and iCloud, yes. Some business hosting accepts messages up to 40 MB, but encoding adds about a third, and messages near 30 MB or more may still fail. A download link is the safer route.

Why are email attachments limited to 25 MB?

Every attachment is stored and relayed by several servers, and large messages strain storage, delivery queues and security scanning. Providers set a cap to keep mail fast and affordable. Encoding overhead also means a 25 MB cap fits only about 18 MB of raw file.

An expiring link works for any number of downloads until a deadline. A one-time link stops after the first download, whatever the time. The strongest setup combines both, so an unopened link still dies on schedule.

Can I see whether someone downloaded my file?

Usually yes, if you use a link-based tool that logs downloads. A plain attachment gives you no such signal. Check that your chosen tool reports downloads before relying on it.

Sources