Outlook Attachment Size Limit: Why It Fails and What to Do

The Outlook attachment size limit is usually 25 MB for a personal Outlook.com account and 35 MB to send (36 MB to receive) on a default Microsoft 365 mailbox — though an admin can raise that as high as 150 MB, and Outlook on the web enforces roughly 25% less than whatever that number is, because encoding a file for transport inflates it by about a third. If you're staring at an error that a file is "too large," or a message that simply won't leave your outbox, you've hit one of three separate ceilings: your own account's setting, the recipient's mail server, or the file's real size once Outlook finishes encoding it.

None of these ceilings move because you asked nicely, and a bigger mailbox storage plan does nothing for them — attachment limits are transport limits, not storage limits, and Microsoft treats them as two entirely separate settings. What actually works is skipping the attachment: compress the file, split it if compression isn't enough, or send a link to a copy stored in OneDrive or SharePoint instead of the file itself. The rest of this guide walks through telling the three ceilings apart, the fastest legitimate way past each one, and what to check when even the workaround doesn't get through.

Which limit did you actually hit?#

Work out which ceiling stopped you before you try anything — the fix is different for each one, and troubleshooting the wrong one wastes a round trip with your recipient. Outlook's own error text is more specific than it looks, and matching it to the right row below saves you from compressing a file that was never too big for your account, but too big for theirs.

That third row is the one that trips people up. Email doesn't move raw binary — Outlook encodes every attachment, typically in Base64, before it goes out, and that adds roughly a third to the file's size on the wire. A 20 MB video is closer to 27 MB by the time it hits your actual send limit, which is why a file that "should" fit sometimes doesn't. It's also why two files that add up to comfortably under your stated limit can still get rejected together — Outlook checks the encoded total, not the total you see in File Explorer.

If you manage the mailbox yourself — a Microsoft 365 admin raising the ceiling for a whole organization, or for one person who regularly sends large files — that setting lives in the Exchange admin center's mail flow settings, or via the MaxSendSize and MaxReceiveSize parameters on Set-Mailbox and Set-TransportConfig in PowerShell. Raising it helps your own outbound limit; it does nothing for whatever the recipient's server enforces on the way in.

Once you know which ceiling you hit, the fix is one of three moves — and which one you reach for depends on how much bigger than the limit your file actually is.

How to send a file that's too big for Outlook#

All three routes below are the documented path Microsoft itself points to — none of them is a workaround in the shady sense, and none require IT to change a setting on your behalf.

1. 1

   Compress the file first

   Right-click the file, or a folder of files, and zip it. A Word document, spreadsheet, or set of scanned PDFs can shrink by half or more; a folder of photos or already-compressed video usually shrinks less, but it costs one click before you try anything more involved.

2. 2

   Check the size against the real limit

   Attach the compressed file and read Outlook's own size warning if one appears before you send. That number already reflects whatever your admin set the tenant limit to, not just Microsoft's default, so trust what Outlook tells you over what this guide says your org's ceiling "should" be.

3. 3

   Attach a OneDrive or SharePoint link instead of the file

   In the Attach File menu, choose your OneDrive or a recent SharePoint location instead of Browse This PC. Outlook uploads the file once and inserts a link, and you choose the permission before you send: anyone with the link, people in your organization only, or specific people by name. A single file shared this way can be up to 2 GB.

4. 4

   Split the file if a link genuinely isn't an option

   For a recipient on a locked-down corporate account that blocks cloud storage links outright, use a zip tool's "split archive" option to break the file into parts sized under the smaller of your limit and theirs, and send them across two or three messages with a note on how to reassemble them.

5. 5

   Use a dedicated transfer service for a one-off huge file

   A large single deliverable, like a video export or a full project backup, usually moves faster through a service built for large transfers than forced through email at all. Paste the download link into the message instead of the file, and treat it the same way you'd treat any other link from an unfamiliar sender if you're the one receiving it.

Attachment limits by platform#

The number you're fighting depends on which Outlook you're actually using, and it isn't the same everywhere. A file that sends fine from Outlook on your laptop can bounce from the same account on Outlook.com or your phone, because each surface adds its own layer on top of the same underlying account.

That last row is the one senders forget. Even a message your own account happily sends can bounce once it reaches a server on the other end with a tighter limit, and you won't know until the non-delivery report lands, often several minutes later.

One more wrinkle if you've switched to the New Outlook for Windows: treat its ceiling like Outlook on the web's rather than classic Outlook's. New Outlook is built on the same web technology as OWA rather than the older desktop mail engine, so a file that a colleague sends fine from classic Outlook can still get flagged in New Outlook on an identical account.

What to do when the workaround doesn't get through#

Sometimes the manual route still fails after you've compressed the file and switched to a link. Before assuming the fix itself doesn't work, check these first.

• The recipient's IT department may block links to consumer cloud storage entirely — ask whether their policy allows OneDrive or SharePoint links, or whether they need the file through their own portal instead.
• A file type can be blocked regardless of size. Many organizations strip executables, password-protected zips, or macro-enabled Office files at the mail gateway before the size is even checked.
• Read the actual bounce code in the non-delivery report, not just the headline. A 5.2.3 or 5.3.4 error points at a size limit; other 5.x codes point at something else, and compressing the file again won't fix a blocked attachment type or a rejected sender.
• Ask the recipient to check spam or quarantine before assuming the message never arrived. A link to an external file is exactly the kind of content some filters hold for review rather than reject outright, so it can be sitting there rather than actually bounced.
• If it's a recurring need, like sending the same client large files weekly, ask for a shared folder or a client portal instead of solving the size limit fresh every time.

A faster way to stop relearning this limit#

Every fix above works, and none of them get easier the tenth time — you still have to remember which account you're sending from, whether OneDrive is even turned on for that tenant, and whether this particular recipient's IT department blocks cloud links. AI Emaily is an AI email client that sits on top of whichever mailbox you're actually using, Gmail, Outlook, iCloud, or plain IMAP, so the composer you attach a file in doesn't change depending on which account happens to be open. When a big attachment comes back as a bounce, it lands in the same inbox the agent already triages on arrival, instead of sitting unread in a folder nobody checks until a client calls asking where their file went. It doesn't remove Outlook's limit — no client can — it just means you stop learning that limit separately for every account you own. We build AI Emaily.