Gmail increases size limits for inbound attachments to 50MB but keeps 25MB send size limit
Email really isn't designed to handle massive files being sent along with messages... but then, since the standard has been in use for decades, it's been modified in a lot of ways that weren't originally intended.
Context & Ripple Effects
This lands mid-way through a burst of Gmail attachment work in March 2017: within weeks, desktop users gained the ability to stream video attachments instead of downloading them, so the platform was being reworked around heavier media payloads rather than plain messages.
The asymmetry is the story — Gmail will accept what it won't send — and it foreshadows where the product went: by the time Gmail turned 20, storage had become central to its identity, and Google has since run a storage policy test trimming free allotments for new accounts.
First-order effects
- Recipients can now take inbound attachments up to 50MB directly in Gmail, while anyone replying with a similarly sized file still hits the 25MB send cap and must route around it via Google Drive or another channel.
Second-order effects
- Bigger accepted attachments mean fuller mailboxes, which raises the stakes on Google's storage economics — the same quota system later tightened in the 2026 free-storage test — making storage management and paid upgrades more consequential for heavy users.
- The pairing with video streaming turns large inbound media into something consumed inside Gmail rather than downloaded, keeping engagement and file handling on Google's infrastructure instead of third-party transfer services.
Third-order effects
- If the pattern holds, attachment limits stop being protocol constraints and become storage-policy levers: Google controls how much lands in your mailbox and then prices the space it occupies, edging email toward a metered storage product.
The trend: Gmail is shifting from a message-transport standard into a storage-governed media platform, where size limits are set by quota economics rather than email protocol limits.