Compressing images for print vs web

Almost every rule reverses. The web wants the smallest sRGB file that looks right; print wants the most data you can supply, in a different colour space, compressed as little as possible.

Side by side

Web — resolution
Match the layout, doubled for high-density screens. 1600–2560 px.
Print — resolution
About 300 pixels per inch of final size. A4 needs ~2480 × 3508.
Web — colour
sRGB, always.
Print — colour
Adobe RGB or CMYK, as the printer specifies.
Web — format
WebP or JPEG, quality 75–85.
Print — format
TIFF, or JPEG at quality 92+. Never aggressive compression.
Web — metadata
Strip it. Saves bytes and removes GPS data.
Print — metadata
Keep the colour profile. It is doing real work.

Why the rules invert

Different constraints entirely

Web images are constrained by bandwidth and by a viewer looking at a backlit screen from arm's length, usually while scrolling. The goal is the fewest bytes that still look right in that context, and there is a great deal of headroom — the eye is forgiving of detail it never dwells on.

Print is constrained by ink on paper, examined at whatever distance the piece invites, permanently. There is no download to optimise and no second chance. The goal is to give the press as much correct information as possible and let it decide what to do with it.

Once you see it that way, every reversal below follows.

Resolution: layout size versus physical size

For the web you work backwards from the layout — the widest the image can be displayed, doubled for high-density screens. Beyond that, extra pixels cost bandwidth and show nobody anything.

For print you work forwards from the physical dimensions: roughly 300 pixels for every inch of final size. A 6 × 4 inch photo needs about 1800 × 1200; an A4 page about 2480 × 3508.

Large-format work is the exception — a poster viewed from three metres, or a billboard from fifty, needs far less than 300 PPI because the viewing distance does the work. Ask the printer rather than assuming.

Colour: sRGB versus everything else

Browsers work in sRGB and handle it universally. Anything wider is a gamble across the range of devices real visitors use, so the web answer is: convert to sRGB, embed it, done.

Print does not use RGB at all. Presses mix cyan, magenta, yellow and black subtractively, and the range of colours that produces overlaps with but differs from any screen's. Some vivid screen colours simply cannot be printed, and some printed colours cannot be shown on screen.

So print work is usually supplied in Adobe RGB — wider than sRGB, converted to CMYK by the printer — or in CMYK directly if they ask for it. Converting a print master to sRGB throws away gamut you were meant to use.

Compression: aggressive versus barely any

Quality 80 is right for the web because artefacts at that level are invisible on a screen at normal viewing size. On paper, examined closely, the same artefacts can be visible — and a press amplifies rather than hides them, particularly in smooth areas and skin tones.

For print: TIFF if the printer accepts it, or JPEG at quality 92 or above. The file will be large. That is correct, and it is not a problem to solve.

Never send a print shop an image you have optimised for the web. It has been downscaled, converted to sRGB, and had detail discarded that the press would have used.

Keep two masters

The workflow that avoids every problem here is simple: keep one high-resolution master in a wide colour space, and generate everything else from it.

Web copies are downscaled, converted to sRGB, stripped of metadata and compressed. Print copies are supplied at full resolution with the colour profile intact. Neither is derived from the other, because each conversion is lossy in a direction the other one needs.

The failure mode to avoid is round-tripping: compressing for the web, then later trying to prepare that file for print. The pixels and the gamut are already gone.

Try it yourself

Everything below runs in your browser, so you can test any of this on your own files without uploading them.

  • Compress JPEG

    Shrink JPG and JPEG photographs with a quality slider or an exact target size.

    Open the tool
  • Resize image

    By pixels or percentage, aspect ratio locked, across a whole batch.

    Open the tool
  • JPG to WebP

    Typically 25–35% smaller at matched quality. The standard web win.

    Open the tool
  • Bulk compressor

    One setting across a whole folder, processed in parallel, downloaded as a ZIP.

    Open the tool

Questions

Frequently asked questions

Every answer below is present in the page source, expanded, so it can be read without opening anything.

Can I use a web image for printing?

Rarely well. A web image has been downscaled to its display size, converted to sRGB and compressed with detail discarded. Printing it usually looks soft, and none of that can be recovered. Go back to the original.

What resolution do I need for print?

About 300 pixels for every inch of final printed size — roughly 2480 × 3508 for A4, or 1800 × 1200 for a 6 × 4 photo. Large-format work viewed from a distance needs considerably less; ask the printer.

Should print images be CMYK?

Only if the printer asks for it. Many prefer to receive Adobe RGB and handle the conversion themselves with a profile matched to their press and paper. Converting badly yourself is worse than not converting at all.

What quality should I use for print JPEGs?

92 or above, or TIFF if the printer accepts it. Compression artefacts that are invisible on a backlit screen can show on paper under close inspection, particularly in skin tones and smooth gradients.

Can I compress print images at all?

Lightly. Quality 92–95 JPEG is usually indistinguishable from lossless in print and considerably smaller than TIFF. What you must not do is apply web settings — quality 80 and a downscale — to something headed for paper.

Should I use these tools for print work?

For web copies, yes. For print masters, no — these tools re-encode through a browser canvas, which converts to sRGB and so discards the wider gamut a print workflow needs. Prepare print files in software that preserves the colour space.

From the blog

Related reading

Longer, more practical guides from the blog.

  • Practical Guides

    How to Compress Images for a Website Without Wrecking Them

    Resize before you compress. Measured on one photograph: half the width at quality 80 produced a 16.4 KB file, while full width at quality 40 produced 20.6 KB and looked far worse. The order of operations matters more than the settings.

    8 min read

  • Image Compression

    JPEG Quality Settings Explained: What the Number Actually Means

    Quality 80 is not 80% of anything. It is an index into a quantisation table. Measured on one photograph: dropping from 100 to 90 removes 77% of the file and 4.2 dB of fidelity; dropping from 40 to 30 removes 17% and costs almost as much.

    8 min read

  • Image Formats

    PNG vs JPEG: When to Use Each, With the File Sizes to Prove It

    PNG stored the same photograph in 1274.1 KB where JPEG needed 67.5 KB — nineteen times larger. On a flat graphic PNG won. On a smooth gradient PNG lost to JPEG by a factor of two, which surprises most people.

    9 min read