Fix "File Too Large" Error in Gmail & Outlook: The Complete Guide

You have just finished polishing a report, a design portfolio, or a set of high-resolution scans. You click "Attach," wait for the upload bar, and then—"Attachment failed: file too large." This is one of the most common and frustrating problems in modern digital communication. The root cause is simple: every email provider enforces a strict maximum attachment size to protect their infrastructure and prevent abuse. When your file exceeds this limit, the email server simply refuses to accept it. Understanding these limits is the first step to never seeing this error again.

Each email provider sets its own ceiling. Here is the definitive reference for the most popular services as of 2024:

Important: These limits apply to the total message size, which includes the email body, headers, and the Base64-encoded attachment. Because Base64 encoding increases file size by roughly 33%, a file that is 19 MB on your disk can actually exceed a 25 MB email limit after encoding. A safe rule of thumb is to keep your actual file size under 18 MB for maximum compatibility across all providers.

The fastest and most reliable fix is to simply make the file smaller. PDF compression is especially effective because most large PDFs contain unoptimized images, redundant metadata, and embedded font families that inflate the file far beyond what is necessary.

How to do it with FileSwift:

1. Go to the Compress PDF tool.
2. Upload your oversized file.
3. Select a compression level—"Standard" is ideal for email, typically reducing files by 60–80%.
4. Download the optimized file and attach it to your email.

This method preserves text sharpness and page layout while aggressively optimizing the embedded images and stripping hidden metadata. A 45 MB scanned contract can often be reduced to under 5 MB without any visible quality loss.

If compression alone is not enough, or if your document is genuinely hundreds of pages long, splitting it into smaller chunks is the next best approach. For example, a 120-page report can be split into three 40-page PDFs, each well under the 25 MB limit.

How to do it with FileSwift:

1. Use the Split PDF tool.
2. Specify page ranges (e.g., 1–40, 41–80, 81–120).
3. Download each part and attach them as separate files.

This approach is especially useful for academic submissions, legal filings, and financial reports where every page must be included.

For truly massive files (100 MB+), the professional approach is to upload the file to a cloud service and share a download link in your email body.

• Gmail: Files over 25 MB are automatically uploaded to Google Drive and inserted as a link.
• Outlook: Click "Attach" → "Upload and share" to save the file to OneDrive.
• Apple Mail: Enable "Mail Drop" in Preferences to send files up to 5 GB via a temporary iCloud link.

This method has no practical size limit, but the recipient needs an internet connection to download the file. For sensitive documents, make sure to set appropriate sharing permissions (e.g., "Only people with the link" or "Specific people").

If your email contains inline images rather than PDF attachments, oversized photos are usually the culprit. A single iPhone photo can be 5–8 MB, and embedding just four of them puts you over Gmail's limit.

How to fix it:

1. Use the Image Compressor tool to reduce each image to under 200 KB.
2. Resize images to the display dimensions they actually need (e.g., 800px wide for an email body).
3. Convert from PNG to JPG if the image doesn't require transparency—this alone can cut file size by 70%.

For the best email compatibility, aim for images under 150 KB each and total inline content under 10 MB.

A common but often misguided approach is to zip the file before attaching it. Here is why this rarely solves the problem:

• PDFs and JPGs are already compressed. ZIP compression works by finding redundant patterns in data. Since PDF images and JPEG photos are already compressed, zipping them typically saves less than 2–5%.
• Some email providers block .zip files. Gmail, in particular, will reject zip archives containing certain file types (like .exe or .js), and corporate Outlook servers frequently quarantine or strip zip attachments entirely.
• It adds friction for the recipient. The person on the other end has to download and extract the archive, which is an unnecessary extra step.

Instead of zipping, use proper format-aware compression (like FileSwift's Ghostscript engine for PDFs) that actually reduces the data density of images inside the file.