Outlook 20 MB Attachment Limit: How to Send Anyway

You hit send on a 32 MB attachment in Outlook at 4:43 p.m. on a Tuesday, and Outlook hit you with a 451 server error. Your recipient runs Exchange, your IT department refuses to raise the corporate limit, and the file has to be on your client's desk by end of day. You are 90 minutes from the deadline, looking at three options that all feel wrong: ask IT (24-hour ticket queue), upload to a random web service (against corporate policy), or break the file into chunks (recipient will never reassemble it). What you actually need is one of three legitimate workarounds that take less than 5 minutes each and do not require asking permission.

This article walks through those three workarounds in detail, with the specific tooling decisions, file-format choices, and security considerations that make each one viable in a corporate context. Pick the right workaround for the situation, hit send, and the workday keeps moving. The bonus: once you have built the muscle for these three moves, attachment failures stop being a recurring crisis and start being a 90-second routine.

Background: why Outlook says no

Microsoft's default attachment limit is 20 MB for Outlook.com and 35 MB for many Office 365 tenants. Corporate Exchange administrators routinely set it lower — 10 MB is common, 5 MB still happens at organizations with old infrastructure. Even if your outbound limit is 35 MB, the recipient's inbound limit may be 10. Email-server-to-email-server hops add MIME encoding overhead, so a 24 MB file on disk arrives as roughly 32 MB on the wire — which means a 25 MB outbound limit fails for any file actually approaching it.

The fix is not "ask IT to raise the limit." IT will say no, and even if they say yes, the recipient's IT will still say no on their end. The fix is shipping the same content as a smaller payload — and there are three reliable ways to do that, each appropriate for different content types.

Background: the three workarounds at a glance

• Workaround 1: Compress JPGs. Best for photos. Cuts attachment size 50 to 70 percent in 45 seconds.
• Workaround 2: Bundle into a PDF. Best for multi-page document scans. Often 30 to 50 percent smaller than the JPGs separately and more polite to the recipient.
• Workaround 3: Cloud-shared link. Best for genuinely large files over 100 MB. OneDrive, SharePoint, Dropbox, or your tenant's sanctioned service.

Choosing the right one is a 5-second decision once you understand the content type. The rest of this article explains the trade-offs and the specific steps for each.

Step-by-step walkthrough: Workaround 1, compress JPGs

If the attachment is photos, the answer is almost always recompression. A folder of 12 iPhone photos at original quality is 50 to 70 MB. The same folder, recompressed at quality 85, lands around 12 MB — well under any reasonable email limit.

Step 1: Save attachments to a folder

In your Outlook draft, save the attached files to a temporary folder on your desktop. Right-click each attachment, "Save As," to a folder named email_attachments_temp.

Step 2: Convert any non-JPG photos

If some of the photos are HEIC (from a phone), PNG (from a screenshot), or WebP (from a website), normalize them to JPG first. Use the HEIC to JPG converter, the PNG to JPG converter, or the WebP to JPG converter as appropriate. The universal image converter handles mixed-format batches in one drag-and-drop.

Step 3: Compress the JPGs

Drag the folder into the JPG compressor. Choose the email-friendly preset (quality 85). Download the compressed ZIP.

Step 4: Re-attach

Extract the compressed ZIP, attach the compressed files to your Outlook draft. Confirm the size meter shows under your recipient's limit.

Step 5: Send and verify

Hit send. Watch for a delivery receipt or a bounce notice. If it lands, you are done.

Step-by-step walkthrough: Workaround 2, bundle into a PDF

If you are sending multiple JPGs together — a scanned contract, a series of receipts, a portfolio of photos — bundling them into a single PDF is smaller than the JPGs separately and far more polite to the recipient. PDFs deduplicate metadata, share a single set of file overhead, and apply their own internal image compression.

Step 1: Save the JPGs to a folder

Same as before. Get the source files out of the Outlook draft into a working folder.

Step 2: Sort them in send order

If the order matters (page 1, page 2, page 3 of a scanned contract), rename them 01-cover.jpg, 02-page1.jpg, 03-page2.jpg. Most JPG-to-PDF tools respect filename order.

Step 3: Bundle into PDF

Use the JPG to PDF converter to combine 5 to 50 JPGs into one PDF document. Choose the "Smaller file" or "Medium quality" preset, not the highest-quality preset, unless the recipient specifically needs print-quality output.

Step 4: Verify the PDF

Open the resulting PDF. Confirm all pages are present, in order, and right-side-up. Check file size — typically 40 to 60 percent smaller than the loose JPG folder.

Step 5: Attach and send

Attach the single PDF to your Outlook draft. The recipient gets a single tidy attachment they can scroll through in their email preview pane without downloading individual files.

Step-by-step walkthrough: Workaround 3, OneDrive link

For genuinely large files — 100 MB design comps, video B-roll, a folder of RAW photos, a marketing-asset library — no amount of compression gets you under 20 MB without sacrificing what makes the file useful. Use OneDrive, SharePoint, Dropbox, or whatever your company sanctions.

Step 1: Use the built-in OneDrive button

Microsoft's "Share with OneDrive" button is built into the Outlook attach dialog. When you attach a file from your local drive, Outlook offers to "upload to OneDrive and share as link." Click it. The file uploads to your OneDrive automatically, and the attachment is replaced with a link.

Step 2: Set the right permission scope

The default link permission is often "anyone with the link can view." For sensitive content, restrict to "specific people in my organization" or "people I specify." This matters; default permissions on shared links have caused real data leaks.

Step 3: Send the email

Hit send. The recipient gets an email with a link instead of an attachment. They click the link, view or download the file from OneDrive.

Step 4: Manage the link after sending

Bonus: if you find an error after sending, you can replace the file at the OneDrive location and the recipient's link still works. With email attachments, every recipient has a frozen copy and you cannot update.

Decision matrix

Situation	Best workaround	Time to send
5 to 30 photos, total 20 to 80 MB	Compress JPGs with JPG compressor	2 minutes
Scanned multi-page document	Bundle as PDF with JPG to PDF	3 minutes
Anything over 100 MB	OneDrive or SharePoint link	5 to 15 minutes (upload time)
Confidential file	OneDrive link with permission scope, not email	5 to 15 minutes
External recipient, no shared cloud	Compress + zip, or WeTransfer	3 to 10 minutes
Mixed format payload (HEIC, PNG, WebP)	Normalize with universal image converter then compress	3 minutes

Common mistakes and how to avoid them

Renaming .jpg to .txt to bypass scanners. Diagnosis: doesn't work; server scanners read the file header, not the extension. The attachment is still flagged at its real size and type. Fix: use the legitimate workarounds.

Zipping a folder of JPGs. Diagnosis: JPGs are already compressed. A zip file of JPGs is typically 1 to 3 percent smaller than the loose folder. Fix: use zip only when you need to preserve folder structure, not for size reduction.

Splitting one image across multiple emails. Diagnosis: recipients cannot stitch the parts back together easily. Fix: compress, don't split.

Using a personal Dropbox for corporate files. Diagnosis: your company's DLP policy flags the upload, and your security team gets a notification. Fix: use the company-sanctioned OneDrive or SharePoint instead.

Defaulting OneDrive links to "anyone with the link." Diagnosis: sensitive content is now searchable via guessable URLs. Fix: scope to specific recipients before sending.

Skipping the compression step on a PDF. Diagnosis: a PDF from 30 raw JPGs is still 25 MB. Fix: compress the source JPGs first, then bundle. The PDF inherits the smaller image payload.

Real-world examples

Diana, paralegal at a boutique law firm. Diana sends scanned exhibits to opposing counsel weekly. The exhibits are typically 40 to 80 pages of scanned documents at 300 DPI, totaling 60 to 120 MB. Bundling with the JPG to PDF converter at medium quality cuts the payload to 15 to 25 MB while preserving every word's legibility. Opposing counsel gets a single browsable PDF instead of a 40-attachment email.

Hassan, marketing manager at a mid-size manufacturer. Hassan ships campaign assets to external agencies — videos, design files, photo libraries. He used to email zipped folders and hit Outlook's wall constantly. After switching to OneDrive sharing inside the Outlook attach dialog, his weekly attachment-fail incidents dropped to zero, and the agencies can re-download from the same link when they misplace files.

Carla, regional sales manager. Carla sends product photos to retail buyers. Her files come in as a mix of JPG, HEIC, PNG, and the occasional WebP from a supplier's site. She runs everything through the universal image converter to normalize to JPG, then through the JPG compressor for size. A typical 50 MB attachment payload arrives as 12 MB, well under every buyer's email limit.

Advanced tips

Build an Outlook quick-step. Outlook supports custom quick-steps. Create one called "Compress and send" that opens a file picker, lets you drag in the source folder, and pre-fills the recipient list. Saves 10 seconds per send.

Set up a "send to OneDrive" right-click action on Windows. Power Automate or a simple PowerShell script can register a right-click action on any file. One click uploads to OneDrive and copies the share link to your clipboard.

Use Outlook's "Reduce attachment size" prompt. Outlook 365 will offer to compress attachments if it detects they are too large. Accept the offer for casual sends; use the explicit pipeline for sends where you control the quality.

Build a habit of exporting at email-friendly size from the start. Lightroom export preset called "Email" outputs at 1,800 px, quality 80, sRGB. Used for photos that you know will be emailed, this preset bypasses the compression step entirely.

For recurring recipients, set up a shared SharePoint folder. Instead of emailing files, drop them into a shared folder. Recipients get notified, files stay updated, and version history is preserved.

Verify delivery for time-sensitive sends. Outlook supports delivery receipts. Enable them for sends where confirmation matters.

Compress PDFs separately when needed. If a bundled PDF is still too large, re-export the source JPGs through the JPG compressor first, then re-bundle into the PDF. The PDF inherits the smaller image payload.

Security considerations

Many corporate policies forbid uploading certain types of files to third-party services. If you are sending HR documents, customer PII, or anything covered by a compliance regime (HIPAA, GDPR, SOX), stay inside your company's approved tooling — OneDrive and SharePoint sit inside the same tenant as your Exchange server, so they inherit the same security boundary. Public WeTransfer-style services should be reserved for non-sensitive content like marketing assets or product photos.

The image-conversion and compression tools used in this article process files in-browser without uploading to a server — meaning even sensitive image content stays on your local machine during the conversion step. Verify this property of any tool you use for confidential content; the privacy-by-design tools clearly state in-browser processing.

FAQ

Does the corporate Exchange limit apply to both incoming and outgoing?

Usually yes, but the values may differ. Check Outlook's File > Info > Mailbox Settings for your specific tenant limits.

What's the difference between OneDrive and SharePoint sharing?

OneDrive is your personal cloud storage. SharePoint is shared team/department storage. For files multiple colleagues need to access, SharePoint. For files only you originate, OneDrive.

Can I attach OneDrive links to non-Microsoft recipients?

Yes. The recipient gets a link they can open in any browser. They don't need a Microsoft account if you set the link permission to "anyone with the link."

How long do OneDrive shared links last?

By default, indefinitely. You can set expiration dates on links for sensitive content — common settings are 7, 30, or 90 days.

What if my recipient still can't receive it?

Their email server may be the constraint, not yours. Send the OneDrive link instead; the recipient pulls the file rather than receiving it through email.

Is there a way to send video?

Video almost always exceeds email limits. Use OneDrive for internal recipients or YouTube/Vimeo for external recipients with privacy settings enabled.

How do I handle a recipient whose IT blocks OneDrive links?

WeTransfer or your tenant's sanctioned external-share service. Some industries (financial services, legal) have approved third-party file-share platforms specifically for this case.

Why your file gets bigger when emailed

A file that shows up as 24 MB on disk often arrives at the email server as 32 MB on the wire. The reason is MIME encoding — email attachments are encoded using base64, which expands binary data by roughly 33 percent. So Outlook's 25 MB cap effectively means your file should be under 19 MB on disk to clear the limit safely after encoding.

This is why compression matters even when you're "under" the limit. A file at 18 MB on disk is right at the edge; a single MIME header change or a forwarded thread that adds metadata can push it over. Building a margin into your file size — aim for 50 to 70 percent of the stated limit — gives you headroom for the encoding expansion plus future forwarding.

The recurring-recipient workflow

If you send large files to the same recipient regularly — a client, a vendor, a contractor — the fastest long-term solution is setting up a shared cloud folder rather than emailing files one at a time. SharePoint, Dropbox Business, and OneDrive for Business all support shared folders with notification rules, so the recipient gets an email when new content drops without needing to manage attachments. The first-time setup takes 10 minutes and saves cumulative hours over the next year.

For external partners outside your corporate tenant, a dedicated client portal often makes sense. Many industries have specialized portals (Box for legal, ShareFile for healthcare, Hightail for creative) that handle the security, version control, and notification logic better than email-plus-attachment ever can. The marginal cost is small once the relationship is ongoing.

Build the muscle once

Most attachment failures happen because the sender exported original-quality files when web-quality would have served the purpose. Set your phone's photo-sharing preset to "Medium" or "Most Compatible" before you attach. Build a Lightroom export preset called "Email" that outputs at 1,800 px, quality 80, sRGB. The compressor becomes a cleanup tool for edge cases rather than your only line of defense. Bookmark the JPG compressor, the JPG to PDF converter, and the universal image converter in your browser. The next time Outlook says no, you have three options that work — pick the one that fits the file, hit send, and the workday keeps moving. Pair these with the HEIC to JPG converter for phone photo inputs and the PNG to JPG converter for screenshots, and the entire attachment-failure category disappears from your work life.