Shrink a PDF and keep it looking sharp

The portfolio that must still impress

Elena, an interior photographer, is sending portfolio-spring.pdf, eighteen pages of room shots at 24 MB, to a studio that caps attachments at 5 MB. The file has to lose four fifths of its weight, yet the whole point of the file is how it looks. Squeezing blindly would be worse than sending nothing: a portfolio of mushy photos costs her the job faster than an oversized attachment.

Her situation has an honest answer, and it is twofold. Some of the weight in any PDF comes off for free, with every pixel and character untouched. The rest comes off by re-encoding pictures, and that always costs something. The trick is knowing which kind of weight your file carries, and stopping before the visible kind costs more than the job allows.

That is also why the target matters more than any setting. A roomy target lets the free savings finish the job alone; a brutal one drags the lossy methods in. Before anything else, read what the recipient actually allows and ask for all of it: a 5 MB cap deserves a 5 MB target, not a cautious 1 MB chosen out of fear.

What shrinks for free

Two of the four techniques in the quality-first tool never touch a pixel. The structural pass rebuilds the document into a fresh file and leaves behind the clutter that past edits piled up: dead objects, duplicated data, abandoned revisions. The font pass trims each embedded font down to the characters the pages actually draw, so a typeface that shipped with thousands of glyphs stops carrying the ones your document never uses.

On some files these two finish the job alone, and the pages come back looking byte-identical to the eye. Elena's portfolio is not such a file: eighteen pages of full-resolution room shots carry their weight in image data, and no amount of plumbing fixes that. But a forty-page project report with three charts and a corporate font pack? That one often folds to half its size without a single visible change. The size breakdown tool tells you which kind of file you hold before you compress.

Where shrinking starts to show

When the free savings cannot reach the target, the engine turns to pictures. Knowing the fixed numbers below helps you predict what your file will look like afterwards.

Two things deserve emphasis. First, resolution does most of the visible damage, not the quality figure: a photo placed at 600 dpi and re-encoded at 150 keeps one pixel in sixteen, and no quality number brings the rest back. Second, text itself is never part of the trade. Even the raster redraw writes the page's own words back as an invisible layer first, so selection, search, copying and screen readers keep working, and every candidate is read back against the original with anything missing over 2% of its characters refused.

Judge the result with your own eyes

1. Open the quality-first tool and drop your PDF onto the page.
2. Type the largest size the recipient accepts, in KB or MB, or leave the box for the 500 KB fallback.
3. Press Compress and read the verdict: final size, distance to target, and the technique that won.
4. Study the side-by-side preview at your usual zoom, then download only when the look satisfies you.

The verdict's winning technique is the whole diagnosis in one word. When a free method won, the pages are visually untouched and you can send with confidence. When an image method won, compare the preview crops closely: faces, fine print and thin lines show damage first. When the raster redraw won on a file full of line art or tiny type, consider dropping pages the recipient never needed and running again with a roomier target.

Quality mistakes and their fixes

Aiming far lower than the cap. A 5 MB ceiling with a 500 KB target throws away detail for nothing. The fix takes ten seconds: type the full cap the recipient allows.

Zooming to 400% to judge. Nobody reads your file at postage-stamp magnification. Compare the preview at the zoom you actually use, usually 100 to 150%, and judge that.

Forgetting the source. The downloaded file replaces nothing until you say so. Keep the original until the recipient confirms the file arrived and opens; recompressing the squeezed copy later only compounds the damage.

Shrinking a file meant for press. A printer measuring resolution and color spaces wants the original, full stop. A 150 dpi page will fail preflight or print soft, and no setting on a shrinking page fixes that. Run preflight on the original instead.

Blaming quality for an encrypted file. A bank statement that barely shrinks is rarely a quality problem; it is usually encrypted, which blocks the rebuild tricks. Unlock your own copy first, then judge the quality trade.

When shrinking is the wrong call

Three destinations deserve the untouched original. The first is professional print, as above: press workflows and shrinking workflows want opposite things from the same bytes. The second is long-term archiving. An archive copy should carry the most detail you have, since nobody knows what resolution a future reader will want; shrink a viewing copy for sharing and file the original.

The third is any recipient who asked for full quality in so many words. A magazine picture desk requesting print-resolution photos will reject a 150 dpi PDF no matter how nicely it fits the attachment limit. Ask whether a shared folder link works instead, or split the document so a light preview PDF travels separately from full-resolution images.

Everything else is a judgment call your eyes get to make. Run the tool, read the verdict, compare the preview, and let the look of the pages decide rather than a promise on a guide page.