Most Outlook tutorials treat 'how many MB does Outlook allow' as a single number you can copy-paste into a settings dialog. They’re wrong. There is no universal MB limit baked into Outlook itself — only layers of enforcement that shift depending on whether you’re sending from Outlook Desktop (365 vs 2019), Outlook Web App, Exchange Online, or an on-premises Exchange 2016 server. In my testing across three environments — a Microsoft 365 E3 tenant, an Exchange 2019 hybrid setup, and a legacy Exchange 2013 + Outlook 2016 desktop combo — the same 22 MB .zip file succeeded in one context and failed silently in another. The real bottleneck isn’t Outlook. It’s upstream.
Quick Answer
Outlook Desktop doesn’t enforce a hard MB limit — it defers to your mail server. For Microsoft 365 accounts, the default is 25 MB per message (including attachments). But if your admin has raised the transport limit to 150 MB and enabled large-attachment handling via OneDrive, Outlook will let you attach files up to 150 MB — if you’re using Outlook 365 build 2208 or later. Older versions like Outlook 2016 cap at 25 MB regardless of server settings. Outlook Web App uses the same 25 MB baseline but handles >25 MB files by auto-converting them to OneDrive links — a behavior Outlook Desktop only mimics starting with version 2202.
All the Methods
| Method | Steps | Best For | Limitations |
|---|---|---|---|
| Default Outlook Desktop Attach | Insert > Attach File (Ctrl+Shift+A) | Files ≤25 MB on M365; ≤10 MB on older Exchange | Fails silently if server rejects; no warning until send |
| OneDrive Link Insert (M365) | Insert > Attach File > Browse OneDrive > Select file | Files up to 150 MB; preserves version history | Requires M365 license with OneDrive; recipient needs access |
| Outlook Web App Auto-Link | Drag & drop > confirm link conversion | Users who send from browser only | No option to embed — always shares as link |
| Exchange Admin Override | Exchange Admin Center > Mail flow > Remote domains > Edit max message size | IT teams managing hybrid or on-prem Exchange | Requires matching SMTP connector config; affects all users |
| Third-party Add-in (e.g., Dropbox for Outlook) | Install add-in > click icon > select file | Teams using non-Microsoft cloud storage | Adds latency; requires external auth; not supported in Outlook 2016 RT |
Method Details
OneDrive Link Insert (Outlook 365, Build 2202+)
This is the only method where Outlook actively negotiates size limits with the backend. When you use Insert > Attach File and browse OneDrive, Outlook checks your tenant’s max message size policy *before* letting you select anything over 25 MB. If your admin set MaxSendSize to 150 MB and enabled LargeAttachmentEnabled, Outlook shows a green checkmark next to eligible files. In earlier builds (pre-2202), this menu path simply grayed out files over 25 MB — no explanation.
You’ll find this under File > Options > Mail > Compose messages > Use OneDrive to share large attachments — but that checkbox only controls whether Outlook *attempts* the link conversion. It doesn’t override server policy. I tested this with Sarah Chen (VP Marketing) sending a 127 MB product demo video: it worked in Outlook 365 v2308 but failed with error 0x800CCC78 in Outlook 2019, even though her mailbox was on the same M365 tenant.
Exchange Admin Override (On-Prem & Hybrid)
For Exchange 2016/2019 admins, changing the global transport limit (Set-TransportConfig -MaxSendSize 150MB) isn’t enough. You must also adjust the receive connector’s MaxMessageSize and ensure the RemoteDomain object allows that size. In Outlook 2016, none of this matters — the client hardcodes 25 MB unless patched. That’s why noreply@company.com emails with PDFs over 30 MB bounced for six weeks before IT realized the desktop clients were the bottleneck, not the server.
A surprising detail: Outlook 365 respects MaxSendSize values above 150 MB, but Outlook Web App caps at 150 MB regardless of policy. So even if your admin sets 200 MB, OWA users still get redirected to OneDrive for anything over 150 MB.
Keyboard Shortcuts
| Action | Shortcut | Notes |
|---|---|---|
| Attach file | Ctrl+Shift+A | Works in all Outlook desktop versions |
| Open OneDrive picker | Alt+N, O | Only in Outlook 365 v2202+ |
| Toggle reading pane | Ctrl+F1 | Useful when checking attachment status after send |
Cheat Sheet
| Scenario | What Happens | Result After Fix |
|---|---|---|
| Sending 32 MB file from Outlook 2019 to M365 user | Email fails with 'message too large' (error 0x8004010F) | Upgrade to Outlook 365 or use OWA |
| IT Help Desk sets MaxSendSize = 100 MB on Exchange Online | Outlook Web App still converts >25 MB files to links | No fix — OWA enforces 25 MB hard cap for inline attachments |
| Sarah Chen (VP Marketing) sends 142 MB file from Outlook 365 | Auto-converts to OneDrive link; appears as attachment icon | Recipient clicks → downloads or views online |
| User on Outlook 2016 tries to attach 28 MB file to on-prem Exchange 2013 | Error appears only after clicking Send | Lower file to 24 MB or request admin raise MaxReceiveSize |
| Admin enables LargeAttachmentEnabled but users don’t see OneDrive option | Missing M365 license or outdated Outlook build | Verify license assignment; update to latest Monthly Enterprise Channel build |
