Email gateways, client portals, and messaging apps still reject oversized PDFs. The usual fix people find first is an online compressor: upload the file, pick a quality slider, download a smaller copy. That works for a public brochure. It is a poor fit for bank statements, ID scans, or contracts that happen to be too large because they are full of high-DPI photos. Compression is exactly when the sensitive pixels are densest — which is when you least want a third-party copy.
LoveMyFile's Compress PDF tool shrinks files in the browser. Images are re-encoded via the Canvas API; work can run in a Web Worker so the UI stays responsive. This guide explains what local compression can and cannot do, how Light and Strong presets differ, and how to choose a setting without wrecking readability.
What PDF compression does — and when it matters
Most "heavy" PDFs are heavy because of embedded images: phone photos of documents, scanner output at 300+ DPI, or design exports with large bitmaps. Compression reduces those image payloads — lower resolution, stronger JPEG-style encoding, color-space cleanup — then writes a new PDF. Pure text-and-vector office files often shrink only modestly because there is little image mass to remove. Knowing that up front saves frustration: if your file is already lean text, expect smaller gains than with a photo-heavy scan pack.
Local compression matters for any file you would not casually email in the clear, and for workflows where the only reason you reached for a cloud tool was attachment size. Shrink on-device, then send the smaller copy through channels you already trust.
Upload compressors vs browser-only compression
| Factor | Typical online compressor | Browser-only (LoveMyFile) |
|---|---|---|
| Where files go | Vendor servers for re-encode | Canvas + worker in your tab |
| Retention risk | Minutes to hours (claimed) | No server copy of your PDF |
| How to verify | Privacy policy wording | Network tab: no PDF multipart upload |
| Quality control | Opaque server presets | You pick Light / Medium / Strong locally |
| Best for | Non-sensitive marketing PDFs | Statements, ID packs, client scans |
How compression works locally on LoveMyFile
LoveMyFile renders page imagery through the browser, then re-encodes images on a canvas. Heavy work can run in a Web Worker so the main thread does not freeze while large scans shrink. Color spaces such as CMYK are converted toward RGB for web-friendly output — a common source of both size savings and slight color shifts on print-oriented files.
Presets trade size for fidelity. Roughly: Light targets about 150 DPI for embedded imagery and aims to keep text selectable where the structure allows; Medium sits between Light and Strong for everyday email limits; Strongtargets about 72 DPI and may rasterize more aggressively, which can shrink dramatically but may reduce or eliminate selectable text on some pages. Treat Strong as "fit the attachment quota" rather than archival quality.
This tool is marked limited-browser in the catalog: browser engines are not Acrobat Distiller. Results vary by how the source was built (born-digital vs scan, font embedding, image filters). Always open the output and check a dense page before you send it.
Step overview and practical tips
- Open Compress PDF and drop your file into the dropzone.
- Start with Light or Medium if the document must stay readable and searchable.
- Run compression in the tab; wait for the local progress indicator to finish.
- Compare file size and open a sample page at 100% zoom before sharing.
- If Strong is still too large, split off unused pages with Split PDF first — fewer pages beat harsher DPI every time.
- For a deeper walkthrough of email-size tactics, read how to compress a PDF for email.
- Photo-only packs can also be rebuilt from optimized images via Images to PDF after compressing the images themselves.
Limits and caveats unique to compression
- Selectable text — Light and Medium are designed to keep text selectable when the source structure supports it. Strong may rasterize pages; do not assume copy-paste still works.
- CMYK and print profiles — conversion to RGB can change how brand colors look on screen and in inkjet proofs. Soft-proof critical print jobs elsewhere.
- Already-optimized files — a second pass on a tightly compressed PDF often yields little gain and more artifacts.
- Device memory — multi-hundred-page scan books can strain mobile browsers. Desktop Chrome or Edge handles typical office packs more comfortably.
- Encrypted PDFs — unlock first if you own the password, using Unlock PDF, then compress the clear copy.
Common mistakes
- Jumping straight to Strong for a text-critical contract — try Light first; only escalate if the size still fails the gateway.
- Uploading to a cloud compressor "just this once" for a passport scan — local canvas re-encode exists for exactly that case.
- Judging quality only by file size — always zoom a page with fine print or handwriting.
- Expecting compression to remove metadata or redact secrets — those are separate jobs. See the PDF compression guide for trade-offs, then use dedicated tools for privacy edits.
Related tools and bottom line
Pair compression with Merge PDF when a combined pack balloons past email limits, or with PDF to Images when you need per-page visual QA. Browser compression via canvas and a Web Worker will not match every Distiller preset, but it keeps sensitive scans on your machine while you chase attachment quotas. Start Light, escalate only as needed, and keep cloud compressors for files you would already post publicly.