Skip to main content

How to Compress PDF Files for Email

Updated 10 min read

By Utilavo Editorial · Reviewed

Try the tool: Compress PDF, Split PDF

Getting a PDF under an email limit means giving up one of three things: visual fidelity, page count, or delivery channel. Email systems force this trade-off because attachment limits are enforced on the MIME-encoded size, not the raw file size you see on disk. Gmail allows 25 MB of attachments when sending and 50 MB when receiving, but Base64 MIME encoding expands attachments by roughly a third in transit, so a file well under 25 MB on disk can still be rejected. Exchange Online (Microsoft 365) defaults to a 35 MB send and 36 MB receive limit per message, measured after encoding, and administrators frequently lower it.

Most users reach for compression as a first response, but compression is only one of three meaningful levers (image downsampling, structural cleanup, and content removal), and the right lever depends on what is consuming the bytes. This guide shows how to diagnose where weight lives in a PDF, understand what common compression presets change, and fall back to splitting or rasterization when compression caps out.

Email attachment limits by provider

Start with the limit you have to hit. These are the default per-message limits; a company mail server can set a lower one, and any limit measured after encoding leaves less room than the headline number suggests.

Default email attachment limits by provider
ProviderSending limitNotes
Gmail25 MBReceives up to 50 MB; larger files are offered as a Google Drive link (Google)
Outlook.com20 MBLarger files are offered as a OneDrive link
Yahoo Mail25 MBApplies to all attachments in one message combined
Microsoft 365 (Exchange Online)35 MB36 MB to receive; measured after encoding, and administrators often lower it (Microsoft)

How to compress a PDF for email in four steps

The Compress PDF tool runs on our server and handles files up to 50 MB:

  1. Open Compress PDF and upload your file.
  2. Keep the Recommended level. It re-encodes embedded images as JPEG at quality 75 and caps their longest side at 2400 pixels, leaving text and vector graphics untouched.
  3. Click Compress PDF and compare the new size with the original. If the file is still too large, run it again with Extreme Compression, which drops JPEG quality to 50 and caps images at 1200 pixels; if even that is not enough, use one of the alternative strategies below.
  4. Download the result, open it to check that text and images still look right, then attach it to a draft email to confirm it fits under your provider's limit before sending.

Diagnose where the bytes actually live

Before compressing, identify the dominant byte source. In most over-sized PDFs, a single category accounts for 70-90% of the file: embedded raster images, embedded font subsets, or incremental save history. Compressing the wrong category wastes time and quality. Open the file in any PDF inspector (Acrobat's Save As Optimized > Audit Space Usage, or mutool info -X file.pdf from the command line), and the breakdown is usually obvious within seconds.

Embedded images are the most common offender. PDFs store images at their native resolution regardless of the page size they appear at, so a 4000x3000 photo placed into a 600-pixel-wide column still carries the full 12-megapixel payload. The fix is downsampling: re-encoding images at a target DPI matched to viewing context. Ghostscript's pdfwrite device exposes this directly through -dColorImageResolution=150 and the matching -dGrayImageResolution and -dMonoImageResolution parameters documented in the Ghostscript pdfwrite reference.

Font embedding adds bulk only when subsetting is disabled or when the document references many typefaces. A fully-embedded font family with regular, bold, italic, and bold-italic faces typically adds 800 KB to 1.5 MB. Subsetting cuts this to 50-150 KB by embedding only the glyphs actually used. Word's PDF export subsets by default, but PDF generators built on legacy printer drivers often do not; re-saving through a modern engine usually fixes this without any visible change.

Scanned PDFs are a different problem class entirely. Each page is a full-page raster image, typically 3-8 MB at 300 DPI in 24-bit color. A 20-page scanned contract weighing 60-160 MB is unfortunate but expected. For these documents, the leverage point is choosing scan resolution at capture time and converting to JBIG2 or CCITT Group 4 for monochrome text pages, both natively supported by pdfwrite. Once a scan has been embedded at high DPI, recovering quality is impossible; you can only re-downsample.

What compression presets actually do

The four presets exposed by most online compressors (Screen, Ebook, Printer, Prepress) are not subjective quality tiers. They are named values for -dPDFSETTINGS in pdfwrite, each binding a specific set of resolution caps and image filters. The most important number behind each preset is the image resolution cap: /screen downsamples color and grayscale images to 72 DPI, /ebook to 150 DPI, and /printer and /prepress to 300 DPI, with /prepress also preserving color information for commercial print. The full parameter table is documented in the Ghostscript pdfwrite reference. Utilavo's own Compress PDF tool does not use Ghostscript; its three levels are described in the four-step section above.

For email-bound documents that will be read on screen and occasionally printed in draft mode, /ebook is the correct default. Its 150 DPI cap produces images that look close to the originals at typical viewing distances on a laptop or phone, while removing most of the excess resolution that bloats illustrated reports. /screen is genuinely aggressive: at 72 DPI a printed page shows visible blur, and fine text rasterized inside images can become unreadable. Use /screen only when the recipient explicitly does not need to print.

Lossless restructuring is a separate axis. Ghostscript and qpdf both perform object stream compression, duplicate-object detection, and content-stream Flate recompression, operations that produce identical visual output and can still trim a noticeable amount from bloated files. A PDF that has been edited, signed, and re-saved several times often carries an incremental save history (the trailing %%EOF markers reveal it) that linearization or qpdf --object-streams=generate --linearize will collapse. Try a lossless pass first; you may not need lossy compression at all.

Expected compression varies wildly by content. Image-heavy reports shrink substantially once their images are downsampled. Text-and-vector PDFs (think LaTeX-generated papers) often shrink very little because their content streams are already compact; the bytes are mostly typeset glyph references. If your text-heavy 30 MB PDF refuses to shrink, the bloat is likely fonts or embedded files, not images.

Alternative strategies for large PDFs

When compression alone cannot bring a PDF below the email size limit, splitting the document into smaller parts is the most straightforward alternative; our guide on how to split a PDF and extract pages covers the options in detail. The Split PDF tool lets you divide a document by page range, so you can send a 40-page report as two 20-page attachments in separate emails or in the same email if each part fits within the limit. Label the parts clearly in the filename, such as "Report-Part1.pdf" and "Report-Part2.pdf," so the recipient can reassemble them easily.

For documents where the recipient only needs a visual reference rather than editable content, converting to images can reduce the file size substantially. The PDF to Image tool exports each page as a JPEG or PNG. JPEG images of PDF pages are often much smaller than the equivalent PDF page, especially for scanned documents, because you can control the image quality and resolution independently. You can then attach the images directly or zip them into a single archive.

Another approach is to remove unnecessary pages before sending. Many PDFs contain cover pages, blank pages, appendices, or sections that are not relevant to the recipient. The Organize PDF tool lets you delete, reorder, and select specific pages, producing a trimmed document that may fit within the email limit without any compression at all. This is especially effective for long reports where you only need to share a specific section.

For files above 20 MB, a Google Drive, Dropbox, or OneDrive share link is often more reliable than an attachment: the recipient gets the full-quality file, and nothing bounces or trips spam filters that flag large attachments.

Tips for preventing large PDFs

The most effective way to keep PDF sizes manageable is to control the input quality before the document is created. When scanning physical documents, choose a resolution appropriate for the final use. For documents that will only be viewed on screen or sent by email, 150 DPI is sufficient and produces files roughly one-quarter the size of 300 DPI scans. Reserve 300 DPI for documents that will be printed at high quality. If your scanner offers a grayscale mode for text-only documents, use it instead of color to cut file size by another 50 to 70 percent.

In digital workflows, avoid embedding full-resolution photographs when the document does not require them. Resize and compress images in an image editor before placing them into your document. A 1200-pixel-wide image is more than sufficient for a full-page illustration in a PDF destined for email. If you are using Word, PowerPoint, or another office application, look for a "Reduce file size" or "Compress pictures" option before exporting to PDF. These features strip metadata and downsample images automatically.

Replace scanned signature pages with digital signatures whenever possible. A scanned page adds several megabytes as a raster image, while a digital signature adds virtually nothing to the file size. Similarly, avoid pasting screenshots of tables or text into PDFs; keep that content as native text and vector graphics for dramatically smaller files.

Key takeaways

  • Email services typically limit attachments to 25 MB (Gmail, Yahoo) or 20 MB (Outlook), and many corporate servers set even lower thresholds.
  • For documents sent by email, moderate image recompression (the Recommended level in Utilavo's tool) is usually the right balance between file size and visual quality.
  • Image-heavy and scanned PDFs compress far more than text-heavy ones, because nearly all of the recoverable bytes are in embedded images.
  • Split large PDFs into parts using the Split PDF tool if compression alone cannot bring the file below the email limit.
  • Scan documents at 150 DPI for email-destined files to prevent bloat at the source.
  • Always open and review the compressed file before sending to confirm that text remains legible and images are acceptable.

Frequently asked questions

Why does my 24 MB PDF still bounce from Gmail when the limit is 25 MB?

Email attachments are MIME-encoded, and Base64 encoding expands binary content by approximately 33%. A 24 MB file on disk becomes roughly 32 MB on the wire, which exceeds Gmail's 25 MB sending cap. The practical headroom is around 18-19 MB raw for a 25 MB MIME limit. If a file refuses to send, check the encoded size, not the on-disk size.

I compressed a scanned PDF and the file size barely changed. Why?

Scanned pages are stored as full-page raster images. If the original scanner output was already JPEG-compressed at high quality, re-running JPEG compression at a similar quality gives only marginal additional savings. The leverage on scans is downsampling the resolution (300 DPI to 150 DPI cuts payload by ~75%) or converting monochrome text pages to JBIG2 / CCITT Group 4. In the Compress PDF tool, Extreme Compression is the level that also reduces image resolution, capping each image at 1200 pixels on its longest side.

Will compression break my form fields, signatures, or hyperlinks?

Form fields and hyperlinks survive compression because they are stored as separate annotation objects, not embedded in image streams. Digital signatures are different: any modification invalidates the signature, including lossless restructuring. If a PDF carries a cryptographic signature, compression will break it. Sign after compressing, never before.

Can I compress a password-protected PDF without removing the password first?

No. Compression engines need to read content streams to re-encode them, and encrypted streams cannot be read without the decryption key. Use the Unlock PDF tool to remove the password, compress the result, and re-apply protection with Protect PDF. The owner password is removable on most files; the user password requires the actual password.

Why does the compressed PDF look fine on my screen but pixelated when printed?

Aggressive presets cap image resolution, for example 72 DPI for Ghostscript's /screen and 150 DPI for /ebook; Utilavo's Extreme Compression caps each image at 1200 pixels on its longest side, about 110 DPI across a letter-size page. On screen that looks acceptable, but office printers run at 300-600 DPI, so the printer has to upsample the image, which produces visible blur and stairstepping. For documents that may be printed, use the Recommended or Less Compression level, or send the original.

Where can I read more about how Utilavo handles uploaded files?

See our processing model for transport encryption, retention windows, and logging policy. For PDF/A archival conversions specifically, the PDF/A archival matrix documents conformance levels and validation tooling.