PDF Too Large to Email? Compress It Under 5MB in 3 Steps

Bottom line: when a PDF is too large to email, the file size has exceeded the mailbox's attachment limit. The solution is to compress the PDF under the limit (WeCom and Outlook 20MB, QQ Mail 50MB), prioritizing the two biggest contributors: embedded images and fonts. This article starts with mailbox limits, then walks through a 3-step method to compress under 5MB, and finishes with a real case study of compressing an 80MB scanned contract.

1. Why Email Attachments Have Size Limits

Almost every mailbox and office collaboration tool imposes a cap on the size of a single email attachment. This is not to make life difficult — it is constrained by the SMTP email transmission protocol, server storage cost, and anti-spam policies. The table below summarizes the attachment size limits of mainstream email platforms used in China.

Email Platform	Single Attachment Cap	Total Attachments per Email	Behavior When Exceeded
QQ Mail	50MB	50MB	Prompts "attachment too large", cannot send
NetEase 163 Mail	50MB	50MB	Prompts over limit, suggests using large attachment
WeCom (Enterprise WeChat)	20MB	20MB	Directly blocked, prompts cannot send
DingTalk (Enterprise Platform)	20MB	20MB	Prompts file too large, suggests saving to DingPan
Outlook Web	20MB	20MB	Prompts attachment over limit, cannot attach
Gmail	25MB	25MB	Automatically converts to Google Drive link
Outlook Client (Exchange)	10–25MB	Configurable by admin	Send fails, bounce-back notice over limit

As you can see, the most generous QQ Mail only allows 50MB, while WeCom, DingTalk, and Outlook all cap office scenarios at 20MB. A scanned contract easily runs into dozens or even hundreds of MB — far over the limit. Rather than scrambling for a cloud-drive workaround, just compress the PDF under 5MB — that size sails through every mainstream mailbox, with room left over for the email body and other attachments.

2. The 3-Step Method to Compress a PDF Under 5MB

A PDF's volume comes mainly from three kinds of objects: embedded images, embedded fonts, and redundant structures. Scanned documents are image-dominated, while text documents are font-dominated. The 3-step method's core is to first diagnose where the size is going, then choose the matching compression strategy, and finally execute. For scanned contracts up to 80MB, this method reliably compresses to under 5MB.

Step 1: Examine the PDF Structure and Locate the Size Source

Before compressing, first figure out where the size is going. Open the file with a compression tool or PDF analyzer to see the proportion of volume from each of the three object types: embedded images, embedded fonts, and document structure (including redundant objects). This step determines what to focus on compressing next.

Common indicators: for scanned documents, over 90% of the volume is in images — typical signs are a single page over 1MB, FlateDecode encoding, and DPI in the 300–600 range; for text-only documents, the bulk is in fonts — a complete Chinese font alone can run 10–20MB; old files that have been edited repeatedly often contain redundant objects, which can be trimmed by 5%–15%. Diagnose first, act second — otherwise you may spend time compressing the wrong thing and see no benefit.

Step 2: Choose the Compression Strategy

Based on the diagnosis in Step 1, choose the matching strategy from the table below. The compression gains differ greatly by size source — image resampling has the largest payoff, while font subsetting is particularly effective for Chinese documents.

Size Source	Compression Strategy	Key Parameters	Expected Reduction
High-DPI scanned images	Image resampling (lower DPI)	600DPI → 150DPI, Lanczos	80%–90%
FlateDecode-encoded images	Format conversion (to JPEG)	Quality 72, B&W to grayscale	70%–85%
Fully embedded Chinese fonts	Font subsetting	Keep only used characters	90%–95%
Redundant objects from repeated edits	Remove redundancy + rebuild cross-reference table	Clean up unreferenced resources	5%–15%
Need fast web preview	Linearization (Fast Web View)	Enable Object Stream	1%–3%

For a scanned contract, the first three rows of Step 2 are usually all needed: resampling takes the biggest cut, format conversion takes another chunk, and font subsetting wraps it up. Combine all three and an 80MB file lands under 5MB.

Step 3: Execute the Compression and Verify

Once you have selected the strategy, run the compression and output the new file. After compression, always run two checks: first, whether the file size meets the target (≤ target limit); second, whether the content is complete and readable (open it and inspect each page for text clarity, signature legibility, table border integrity, no misalignment). We recommend comparing key pages against the original after compression to confirm that signatures and seals are intact.

One commonly overlooked point: do not compress right up to the limit. For example, WeCom's limit is 20MB — pushing to 18MB is safer, because the email body, other attachments, and encoding overhead (base64 encoding inflates size by about 33%) all take space. Setting the target at under 60% of the limit (e.g., under 12MB for a 20MB limit) almost eliminates send failures.

3. Case Study: Compressing an 80MB Scanned Contract to 4.8MB

This is a 32-page Chinese sales contract scan, original size 80.4MB, that needs to be sent through WeCom (20MB limit). We processed it with the 3-step method.

Document characteristics: 32 A4 pages, 600DPI black-and-white scan, 32 embedded images all FlateDecode-encoded (averaging 2.4MB per page), embedded Source Han Serif Regular+Bold totaling 28MB, with 3 incremental saves leaving redundant objects.

Execution parameters and size changes:

Step	Operation	Key Parameters	Size Change
1	Image resampling	600DPI → 150DPI, Lanczos	80.4 → 15.2MB
2	Format conversion	FlateDecode → JPEG, quality 72, to grayscale	15.2 → 6.1MB
3	Font subsetting	Keep 1,287 used characters	6.1 → 4.9MB
Wrap-up	Remove redundancy + linearize	Rebuild cross-reference table	4.9 → 4.8MB

Result: 4.8MB, compression ratio approximately 16.8:1, well below the WeCom 20MB limit. Text is crisp and readable, signature strokes are intact, tables have no broken borders, and the recipient opened the file without issue. The entire process was completed locally — the contract never touched any third-party server, meeting the confidentiality requirements of business documents.

4. Compression Recommendations by Email Scenario

Different delivery channels and document types call for different target sizes and strategy priorities. The table below gives recommendations for common scenarios.

Sending Scenario	Target Size	Document Type	Recommended Strategy
WeCom / DingTalk: send a contract	≤15MB	Scanned contract	150DPI + grayscale JPEG + font subsetting
QQ Mail: send a report	≤40MB	Mixed image-text report	200DPI + JPEG quality 80 + subsetting
Outlook: send a bid document	≤15MB	Bid document with charts	200DPI + JPEG quality 85, keep color
Government OA upload	≤5MB	Approval material scan	150DPI + grayscale JPEG + subsetting + redundancy cleanup
Email: plain text notice	≤2MB	Text-only PDF	Font subsetting mainly, images can be ignored
Cross-border email: send drawings	≤20MB	CAD-exported PDF	Vector optimization + remove redundancy, be cautious with DPI reduction

A general rule: for scanned documents, lower DPI first, then convert to JPEG; for text documents, do font subsetting first; for old files, clean up redundancy first. Set the target size at under 60% of the limit for the safest results.

5. FAQ

Q1: How do I send a PDF that exceeds the email attachment size limit?

First use a compression tool to shrink the PDF to under the target mailbox's limit (QQ Mail 50MB, WeCom 20MB, Outlook 20MB), then attach it to your email. For scanned contracts, resample images to 150DPI, convert to JPEG encoding, and subset fonts — these three steps reliably compress an 80MB file to under 5MB. For very large files (e.g., multi-hundred-MB drawing sets) that resist compression, split them into multiple PDFs and send in batches, or use local compression to produce an encrypted archive and send that.

Q2: Will compressing a PDF to 5MB affect clarity?

For on-screen reading and email transmission, resampling a scanned document to 150DPI and converting to grayscale JPEG (quality 72) keeps text crisp and legible, with virtually no perceptible difference to the eye. 150DPI is the standard DPI for screen reading of document content, and the human eye can no longer distinguish it from higher DPIs. If you need to print and archive, raise JPEG quality to 85 or keep a separate 300DPI high-fidelity copy for printing — and send the compressed version by email.

Q3: I do not have compression software — how can I send a large PDF temporarily?

You can use cloud drive share links (Baidu Netdisk, Alibaba Cloud Drive) or file transfer stations (QQ Mail's file transfer station supports 2GB with a 30-day validity) to send download links, but these are only temporary solutions. Please note: sensitive files like contracts and bid documents are not recommended for upload to third-party cloud drives, as there is a risk of leakage; links also expire, and the recipient may not be able to open them after the deadline, which can delay your work. The more reliable approach is to use local compression software to process the file and then send it by email — safer and independent of any third party.

Q4: Why can WeCom only send 20MB attachments?

WeCom sets the single-attachment cap at 20MB due to server storage cost and transmission stability considerations. Exceeding this limit causes the system to block the message and prompt that it cannot be sent, so the file must be compressed or split first. The Outlook web version is also 20MB, and QQ Mail is more lenient at 50MB, but in all cases we do not recommend sending right at the limit — base64 email encoding inflates attachments by about 33%, and the email body and other attachments take up additional space, so the actual usable room is smaller, and leaving compression headroom is safer.

Summary

PDF too large to email — the root cause is the file size exceeding the mailbox attachment limit, and the fix is targeted compression. The 3-step method is straightforward in logic: first inspect the PDF structure to locate the size source, then choose the compression strategy (lower DPI and convert to JPEG for scanned documents, font subsetting for text documents, redundancy cleanup for old files), and finally execute and verify. An 80MB scanned contract processed through this pipeline reliably compresses to under 5MB and sails through every mainstream mailbox.

Keep three points in mind: first, diagnose before compressing — do not act blindly; second, set the target size at under 60% of the limit, leaving headroom for encoding overhead and the email body; third, use local compression for sensitive files — do not take the easy route of uploading to a cloud drive. With these three points, sending a PDF by email will never be a problem again.