Outlook Attachment Size Limit Office 365: The 3 Ceilings
Ask about the outlook attachment size limit office 365 imposes and you will get the famous answer - 25 MB - which is true, incomplete, and responsible for most of the confusion around failed attachments. The 25 MB figure is one ceiling of three, it measures the whole message rather than the file, and it is adjustable in one direction by your admin while remaining entirely out of your hands in another: the recipient's server has its own opinion, and no setting on your side changes it.
This guide walks the three ceilings in the order a message meets them, explains the encoding overhead that makes a 20 MB file fail a 25 MB limit, and covers the admin controls and the link-based escape hatch.
Where the outlook attachment size limit office 365 enforces actually lives
Three separate systems each get a veto, and the smallest one wins:
| Ceiling | Default | Range | Who controls it |
|---|---|---|---|
| Mailbox message size limit (Exchange Online) | 25 MB send and receive | 1 MB to 150 MB | Your Microsoft 365 admin, per mailbox or tenant-wide |
| Outlook client cap | 20 MB for internet (POP/IMAP) accounts; Exchange accounts follow the server | Registry-adjustable on classic desktop Outlook | The device or its admin |
| Recipient's receiving limit | Whatever their provider or admin set | Not visible to you | Entirely theirs |
The practical consequence: an attachment must clear all three, and a bounce or an in-client refusal tells you which one it hit. A red banner in Outlook before you even press Send is the client cap or your mailbox's send limit; a bounce minutes later mentioning "message size exceeds" the remote server's limit is the recipient's ceiling, and resending changes nothing.
The 33 percent tax: why a 20 MB file fails a 25 MB limit
Email transports attachments as text. Binary files are encoded with Base64 for the trip, and Base64 inflates payloads by roughly a third - three bytes of file become four bytes of message. The limits above measure the encoded message: attachments after inflation, plus the body, headers, and any embedded images in your signature.
Run the arithmetic backwards and the honest capacity of a 25 MB limit is roughly 18 MB of actual files. A 20 MB PowerPoint therefore fails a 25 MB ceiling with room to spare on paper and none in practice. This single fact explains the majority of "but it's under the limit!" tickets, and it applies at every ceiling in the table - the recipient's 25 MB limit also measures your inflated message, not your original file.
Two smaller inflators stack on top: signatures with embedded logo images add real weight to every message, and forwarding a message re-wraps its existing attachments inside a new envelope, occasionally tipping a message that originally sent fine.
Ceiling one: the mailbox limit, and how admins move it
Exchange Online gives every mailbox a maximum send size and a maximum receive size, both defaulting to 25 MB. Admins can set either anywhere from 1 MB to 150 MB - in the Microsoft 365 admin center under the mailbox's mail flow settings, or in PowerShell with Set-Mailbox -MaxSendSize and -MaxReceiveSize. Tenant-wide defaults for new mailboxes are set separately, so raising the default does not touch mailboxes that already exist - a classic gap where half the company can send 100 MB and the other half cannot, depending on hire date.
Three things admins learn the hard way:
- 150 MB is a hard service maximum. No license, support ticket, or connector raises Exchange Online past it.
- The change is not instant. Mailbox settings take time to propagate; test after an hour, not after a minute.
- Send and receive are independent. A mailbox allowed to send 100 MB but receive 25 MB will bounce replies that quote its own outgoing attachments back at it - raise both or expect asymmetric mysteries.
Note also what this ceiling governs: messages in transit. It is unrelated to mailbox storage quotas, and lowering it is a legitimate policy tool - some organizations deliberately set 10 MB to push large files toward links.
Ceiling two: the Outlook client's own caps
Classic desktop Outlook adds a cap of its own: 20 MB for internet email accounts (POP and IMAP), enforced before the message ever leaves the machine, with the familiar "attachment size exceeds the allowable limit" refusal. For Exchange and Microsoft 365 accounts, desktop Outlook defers to the server's limit instead - which is why the same file can attach fine at the office and refuse at home where the personal account is IMAP.
On managed machines the 20 MB client cap can be adjusted through the MaximumAttachmentSize registry value, though raising the client past the server is pointless - the server still refuses - and the modern answer is usually to stop fighting it and share a link.
Outlook on the web enforces the mailbox's server-side limit directly at upload time and offers the upload-to-OneDrive path in the same dialog when a file is too big, which makes it the easiest place to confirm what your mailbox's real limit is: attach a large file and read the number in the refusal.
Ceiling three: the recipient's server
The ceiling you cannot see and cannot change. Your admin's generous 150 MB send limit gets your message out the door; the recipient's provider then applies its own receive limit, and consumer services commonly sit at 25 MB or lower while corporate tenants can be anywhere their admin chose. The failure arrives as a bounce - typically a 5.2.3 or 5.3.4-class "message size exceeds" rejection naming the remote server.
There is no fix on your side except sending less. For one-off large files to external recipients, this ceiling is the decisive argument for links over attachments: a link weighs a few hundred bytes regardless of file size, and it clears every receiving limit on Earth. For recurring workflows - contracts to the same client every week - it is worth one email asking what their limit actually is, because designing around an unknown ceiling wastes everyone's time.
When the file should be a link
Microsoft's own design pushes here: OneDrive and SharePoint accept individual files up to 250 GB, and Outlook integrates the share flow directly - attach from OneDrive, or accept the prompt to upload when a local file exceeds the limit. The recipient gets a permission-controlled link, you keep one canonical copy instead of a dozen diverging inbox copies, and the message itself stays tiny.
The trade-offs are real but manageable: external recipients need the link's sharing scope set correctly (the "People you specify" option avoids both open-to-anyone links and access-denied replies), and regulated industries sometimes require the attachment to be in the message for retention. Where policy allows links, they beat attachments at every size that ever hits a ceiling.
For automated mail - invoices, reports, exports generated by systems rather than people - the same logic applies with more force: bulk-generating multi-megabyte attachments multiplies every ceiling by your send volume, and transactional email platforms cap attachment sizes far below Exchange anyway. Generate the file to storage, send the link.
The fast diagnosis
Refused before sending: the client cap (internet accounts, 20 MB) or your mailbox's send limit - check which account type you're on, then ask your admin what MaxSendSize is. Sent but bounced with a size complaint naming your own organization: your send limit is lower than you think. Bounced naming the recipient's server: their ceiling, switch to a link. File under the limit but failing anyway: add a third to its size for encoding and recount. Three ceilings, one rule - the smallest number in the chain decides, and past roughly 18 real megabytes, the link is always the answer.
Frequently asked questions
What is the maximum attachment size in Office 365?
The default message size limit is 25 MB for sending and receiving, adjustable by an admin from 1 MB up to a hard maximum of 150 MB per mailbox. Because Base64 encoding inflates attachments by about a third, a 25 MB limit fits roughly 18 MB of actual files.
Why does my attachment fail when it is under the 25 MB limit?
Limits measure the encoded message, not the raw file. Base64 encoding adds roughly 33 percent, and the body, headers, and signature images add more - so a 20 MB file routinely exceeds a 25 MB ceiling.
Can an admin increase the attachment size limit in Office 365?
Yes - via the Microsoft 365 admin center or Set-Mailbox with MaxSendSize and MaxReceiveSize, up to 150 MB. Changes take time to propagate, only apply to the mailboxes actually modified, and cannot exceed 150 MB under any license.
How do I send a file larger than the Outlook limit?
Share it as a OneDrive or SharePoint link - individual files up to 250 GB are supported, the link clears every receiving server's limit, and Outlook offers the upload flow automatically when a file is too large to attach.