Best Free PDF Compressor Under 5MB for Email Attachments (2026)

A consultant has just finished a 60-page proposal: 18MB of polished PDF with embedded photos, charts, and the company's standard cover page. They hit "send," and Outlook bounces it back: "The attachment exceeds the maximum allowed size of 5 MB." This is a corporate-IT email-server limit, much stricter than Gmail's 25MB consumer cap. The proposal is due in 90 minutes. The fast move is to drop the PDF into a free compressor and ship a 4.2MB version that still looks acceptable. The slow move is to call IT, get a one-time exception, and wait two hours. After helping hundreds of users hit corporate email size limits without sacrificing the document, the practical workflow that consistently works is browser-based PDF compression with explicit DPI and JPEG-quality controls — and knowing which knob to turn for which kind of input.

You can compress a PDF under 5MB through the free PDF compressor directly in your browser, or use the aggressive PDF compressor when standard compression isn't enough. Both run locally without uploading anywhere.

Why Email Servers Cap Attachments (and Where the 5MB Limit Comes From)

The 5MB attachment limit is a holdover from the original SMTP standard. RFC 5321 (the SMTP specification published by the IETF) doesn't mandate any size limit, but most early MTAs (mail transfer agents) imposed 10MB or smaller defaults to prevent server overload. Modern mail servers can technically handle gigabyte attachments, but corporate IT typically keeps the limit low for three reasons: storage cost (each attachment is stored in every recipient's mailbox), MIME-encoding overhead (base64 encoding inflates binary attachments by ~37%, so a 5MB attachment becomes ~6.85MB on the wire), and security (large attachments are slower to scan with antivirus and DLP tools).

Common 2026 attachment limits in the wild:

• Gmail (consumer): 25MB outgoing; receives up to 50MB (Google Workspace Help)
• Outlook.com (consumer): 33MB attachment limit
• Microsoft 365 (default): 35MB but admin-configurable down to 10MB
• Exchange Server (corporate): typically 10MB, sometimes 5MB
• Yahoo Mail: 25MB
• Many corporate Exchange installs: 5-10MB enforced
• Some gov agencies and law firms: 4-5MB enforced

For a sender, the safe target is under 5MB — that hits virtually every corporate inbox. Under 4MB is even safer because base64 encoding adds 33-37%, so a 4MB local file becomes ~5.4MB in transit and could still trigger a 5MB-on-the-wire limit on a strict server.

How PDF Compression Actually Works (DPI, JPEG Quality, Object Streams)

PDFs aren't images, but they often contain images — and the images are usually what makes a PDF large. A typical 60-page proposal with photos and charts is ~95% image data and ~5% everything else (text, vector graphics, fonts). Compressing the PDF means compressing those images.

The two levers that matter:

DPI (dots per inch) of embedded images. A photo embedded at 300dpi at 6"×4" is 1800×1200 pixels = 6.5 megapixels of image data. Downsampling to 150dpi keeps the same physical print size but halves the pixel count to 1.6 megapixels — typically a 4× reduction in encoded size. For screen viewing (which is how 95% of PDFs are consumed in 2026), 150dpi is visually indistinguishable from 300dpi. For print, 300dpi is the gold standard but 200dpi is acceptable for everything except glossy magazines. The International Color Consortium documentation on print resolution covers the perceptual thresholds in detail.

JPEG quality factor. JPEG compression is lossy: lower quality means smaller files but visible artifacts. Quality 90 is "near-original," quality 75 is "good," quality 60 is "acceptable for body text + photos," quality 40 is "noticeable artifacting." For email-bound proposals, quality 70-75 is the typical sweet spot. The Joint Photographic Experts Group (JPEG) ITU recommendation T.81 documents the standard if you want to go deep on the math.

A third lever is object stream compression: rewriting the PDF's internal object structure to use compressed object streams (introduced in PDF 1.5). Most modern PDFs already use this; older PDFs (saved from legacy software) often don't. The PDF Association's compression guidance covers this comprehensively. A "compress" pass that doesn't touch images at all can still recover 5-15% on legacy PDFs by switching to PDF 1.5+ object streams.

How to Compress a PDF Under 5MB Step by Step

Using the PDF compressor tool:

1. Drop your PDF into the upload area. The file is read into your browser; nothing uploads.
2. Choose a compression level. "Light" targets ~30% reduction, "Standard" ~50%, "Aggressive" ~70%. For most email attachments, Standard is right.
3. Click compress. The compression runs locally; processing takes 2-15 seconds depending on file size and image count.
4. Check the output size. If it's under 5MB, download. If it's still over, switch to the aggressive compressor and increase compression.
5. Spot-check a few pages. Open the compressed PDF and look at any photos, charts, or fine-text sections. If quality is acceptable, send. If not, redo at a lighter setting and accept that the email might bounce — you'll need to send a download link instead.

For batch jobs (compressing 30 invoices at once for a monthly archive), the batch PDF compressor handles dozens of files in one pass with consistent settings.

Worked Examples

Example 1 — 18MB consulting proposal to 4.2MB. Original PDF: 60 pages, embedded photos at 300dpi quality 95, two PowerPoint-exported chart pages. Compression target: under 5MB for the client's corporate inbox. Settings used: 150dpi downsample, quality 75 JPEG. Result: 4.2MB, visually fine on a laptop screen. Sent in 90 seconds; client received it without a bounce. The original 18MB file is still on the consultant's drive for higher-quality print exports if needed.

Example 2 — 30MB scanned-receipts batch to 2.8MB. A small-business owner has a year of scanned receipts saved to one PDF (180 pages from a flatbed scanner at 300dpi color). The original is 30MB, far too large to email. Compression strategy: convert color scans to grayscale (most receipts are essentially black on white anyway), downsample to 200dpi, JPEG quality 65. The aggressive compressor reduces 30MB to 2.8MB in one pass. Receipts remain readable, account numbers are clear. The compressed PDF goes to the CPA via email. Detail loss is real but irrelevant for the use case.

Example 3 — 8MB proposal compresses poorly. A proposal contains many embedded vector charts, dense tables, and minimal photos. Standard compression yields 7.2MB — only 10% reduction because the file is mostly text and vectors, not images. The right move: don't compress further (you'll start seeing JPEG artifacts in screenshot inserts) and instead use the PDF organize tool to remove the appendix (28 pages, mostly back-matter the client doesn't strictly need). Result: a 4.1MB main document plus a separate 4MB appendix sent as two emails or via a shared link. Sometimes the right answer is "send less," not "compress harder."

Example 4 — 12MB legal contract to 4.8MB without quality loss. A 40-page contract is mostly text with a few signature-page scans and one inserted image. Aggressive compression would degrade the signature scans to the point of looking faked. The right approach: standard compression at 200dpi quality 80, applied selectively. Result: 4.8MB, signatures still crisp, body text identical in quality. The contract goes to opposing counsel without rejection.

Common Pitfalls

Compressing already-compressed PDFs. Running a PDF that's been through aggressive compression once through the aggressive compressor again rarely yields more reduction — the compressible bits have already been compressed. Worse, double-compression introduces visible JPEG artifacts in photos. If you can't hit your target on the first compression pass, the problem is the document, not the compressor.

Losing OCR text from scanned PDFs. If the original PDF is a scanned document with OCR text behind the images, aggressive compression that re-encodes images can sometimes corrupt the OCR text layer. Verify by trying to select text in the compressed output. If the OCR is broken, recompress with lighter settings or re-OCR the compressed output.

Compressing form-fillable PDFs incorrectly. Aggressive compression can flatten form fields (turning them into static images), making the form no longer fillable. If you need the form to remain interactive, use light compression only or compress before adding the form fields, not after.

Quality loss on legal/medical documents. Compression at very low quality settings can make small print (footnotes, addenda, fine-print disclaimers) hard to read, especially on mobile screens. For legal contracts and medical records, stay at quality 75+ minimum even if it means the file ends up at 6MB instead of 4MB and you need to share via a link.

Mistaking compression for security. Compressing a PDF doesn't password-protect it or hide content. To protect a sensitive PDF from unauthorized viewing, use the PDF protect tool to add encryption, then compress.

Frequently Asked Questions

Q: Will compressing a PDF make text harder to read? A: No, if you stay at standard compression (150-200dpi, quality 70-80). Text is rendered from vector glyph data, not raster images, so DPI changes don't affect text crispness. JPEG quality only affects embedded photos and screenshots. Aggressive compression at quality 50 or below can degrade screenshots to the point of unreadability.

Q: Can I compress a PDF below 1MB? A: For mostly-text PDFs under 30 pages, yes — sometimes to 200KB or less. For PDFs with photos or scanned content, hitting 1MB usually means visible quality loss. Below 500KB on a photo-heavy PDF, you'll see JPEG blocking artifacts.

Q: Why is my "compressed" PDF the same size as the original? A: Most likely the original is already well-compressed (fonts subsetted, images downsampled, object streams used). PDFs from modern sources (Microsoft Word's "Save as PDF," Adobe Acrobat's "Save Optimized") often have nothing left to compress. Try lossy image compression specifically, or accept that the file size is what it is.

Q: Does compression affect digital signatures? A: Yes. Any modification to a PDF — including compression — invalidates existing digital signatures. The cryptographic hash of the file changes after compression, breaking the signature. Compress before signing, never after.

Q: What's the difference between standard and aggressive compression? A: Standard targets 50% reduction with minimal quality loss (150dpi/quality 80). Aggressive targets 70-80% reduction with visible quality loss on photos (96dpi/quality 60). For email under 5MB, try standard first; only escalate to aggressive if standard isn't enough.

Q: Are my files uploaded when I use the compressor? A: No. The compression runs in JavaScript on your computer. You can verify by opening browser DevTools → Network tab — there are no upload requests during compression.

Q: What's the best alternative when I can't compress small enough? A: Send a download link instead of the attachment. Cloud storage (Google Drive, OneDrive, Dropbox) provides shareable links that bypass attachment limits entirely. For a temporary one-off transfer, services like WeTransfer or Smash work without recipient signup. Compression is only the right answer when the recipient explicitly needs the file as an attachment.

Wrapping Up

Hitting 5MB for an email attachment is one of those everyday papercuts that the right free tool fixes in 30 seconds. The PDF compressor handles standard compression for most cases, and the aggressive PDF compressor takes over when the file is photo-heavy and corporate IT enforces 5MB strictly. Both run locally without uploading anywhere — the file never leaves your machine. For broader PDF workflows including merging, splitting, signing, and OCR, see the scoutmytool PDF tools index for the full free toolkit.