
Compress large PDFs for email and client portals. Practical size targets, quality checks, and mistakes to avoid.
A 28 MB phone-scan packet bounces from email and stalls a portal progress bar. Compress PDF is the controlled shrink: one pass, legibility check, then send—not endless recompress until ink melts.
The clip below shows reducing PDF file size in the browser.
Corporate mail often sits near 10 MB. Older portals sit near 5 MB. Drive links allow more but still choke mobile downloads. Measure first. Barely over the limit → mild compress. Five times over → fewer pages or better capture upstream.
Example target: a 22 MB three-page signed rider that must clear a 10 MB portal. Write the target in the ticket before you click.
Sideways pages waste quality budget—use Rotate PDF before compress. Unused photo appendices should leave via Split PDF. Build the final stack with Merge PDF only when parts are final, then compress that one file.
Category path: PDF tools. 10 trial usages a day on file tools means plan the pass with targets written first.
packet-full.pdf and packet-portal-8mb.pdf both in archive.22 MB → 9.4 MB after one sensible pass. Signatures remain clear. Portal accepts. Six months later a dispute still has the full-quality original on file.
Another case: 48 MB board pack with photo appendices. Split appendices, compress the narrative pack to 9 MB, leave photos as a separate 15 MB file on an approved drive link. Email carries the narrative; the link carries photos. Compress alone was never going to make 48 MB pleasant in an inbox.
Already optimized exports barely move. Vector text PDFs may already be small—attachments or embedded media may be the real weight. Giant cover photos dominate; crop or reshoot. Locked files need unlock handling first.
Some gateways reject certain encodings even under the stated MB limit. Ask IT if a "small" file still bounces with a vague error.
Ten recompress cycles until ink melts. Compressing before rotating. Deleting the only uncompressed original. Chasing "as small as possible" instead of "under the real limit." Sending a soft signature that looked fine on a bright laptop and fails on a phone.
Compression re-encodes. It cannot refocus a blurry capture. FreeDailyPro offers this among 200+ professional tools for browser-based file work.
Is smaller always better? No—readable under the cap wins.
Does compress remove secrets? No—use redaction for that.
When to split? When one unused appendix is most of the weight.
Can I compress password-protected files? Unlock or work on an authorized copy first per policy.
Signatures and notary stamps need higher quality than a background photo of an office plant. If a packet mixes both, compress less aggressively or split photo pages out. One soft signature can invalidate a practical review even when the file is small enough.
Text-heavy born-digital PDFs often shrink less than scan-heavy ones. If size barely moves, the file was already efficient—look for embedded attachments or huge unused pages instead.
Email wants small. Archive wants faithful. Portal wants whatever its validator coded years ago. Keep two outputs when those goals conflict, and say which is which in the send note. Label files so a colleague never emails the archive original by mistake.
Closing days create ten heavy scans. Compress in a queue: measure, target, compress, zoom-check, rename, upload. Do not interleave with unrelated work; that is how unchecked soft files ship.
File tools list 10 trial usages a day—queue the ten packets with targets written first so each run is intentional.
Hold the phone level. Avoid glare. Capture one page per shot when possible. A cleaner capture at 4 MB beats a crushed 1 MB blur. Compress is not a substitute for photography basics.
You open full screen. Then a colleague on a different OS. Then, if possible, a phone. Only then the client. Internal eyes are cheaper than support tickets.
A file that looks fine on a bright laptop may fail when printed on a weak office printer. For signature packets that might be printed, inspect a print preview or a test page after compress. Adjust targets if toner makes soft antialiasing worse.
If a portal allows multiple uploads, send the agreement first at high quality and the image appendix second. Compress strategy differs per file instead of crushing everything into one blob.
A notary packet must clear a 5 MB county portal. Original is 11 MB of mixed scans. Rotate two sideways pages, split a decorative cover photo, compress once to 4.6 MB, zoom the stamp and signature, then upload. Keep the 11 MB original offline for the paper file. The portal never sees the soft-stamp version because you stopped after one good pass.
When a packet mixes born-digital text pages and phone photos, compress once at a mild setting, then decide. If text is fine and photos still dominate size, split photo pages out and compress photos harder as a separate file. Do not apply one aggressive setting to every page type.
Document the two outputs in the send note so the recipient knows which file is for signature review and which is image reference.
Use matter-portal-under10mb-DATE.pdf for the small file and matter-archive-full-DATE.pdf for the large one. Avoid compressed.pdf as a name. Future you will not remember which limit it was built for.
Open Compress PDF, run one pass, zoom a signature, confirm MB under the written target, rename, upload. If any step fails, stop and fix source quality instead of looping. That five-minute definition of done prevents evening recompress marathons.
Run one pass on Compress PDF for your next over-limit file and zoom signatures before you send.
What size limit keeps blocking your uploads? Send the limit and file type on the contact page.