Skip to content

Guides · September 21, 2026 · PiccTools Team

How to Compress Images Without Losing Quality

Image compression has an unfair reputation. Done carelessly, it turns crisp photos into mush. Done properly, it can cut a file to a quarter of its size while remaining visually identical to the original — and that difference comes down to understanding a handful of concepts rather than owning expensive software. This guide walks through the whole craft: what “quality” actually means, which settings matter, and a workflow you can reuse for every image you publish.

Lossy vs. lossless: the only distinction that really matters

Every compression method is one of two kinds. Lossless compression (PNG, lossless WebP, GIF) reorganizes data more efficiently without throwing anything away — decompress it and you get back the exact original pixels. It is perfect for screenshots, logos and graphics with sharp edges and flat colors, but it can only shrink a photograph so far, usually 10–30%.

Lossy compression (JPEG, lossy WebP, AVIF) deliberately discards information your eyes are bad at noticing: fine color detail, gentle gradients in busy textures, tiny high-frequency noise. The “quality” slider controls how aggressive that discarding is. This is where the big wins live — a quality-80 JPEG is routinely 70–90% smaller than the source photo.

The crucial insight: “losing quality” in the technical sense is not the same as “losing quality” in the perceptual sense. Information is lost at every quality setting below 100; visible damage only appears when you push too far. The goal is to stop just before that point.

Step 1: Resize first, compress second

The most common compression mistake has nothing to do with codecs. People upload a 6000×4000 photo from their camera, compress it carefully — and serve it on a page that displays it at 900 pixels wide. All that careful quality tuning is wasted because 97% of the pixels are discarded by the browser anyway.

So before touching the quality slider, resize the image to the largest size it will actually be displayed at. For a blog image, 1200–1600 pixels wide is generous. For a thumbnail, 400. Resizing first routinely saves more bytes than any encoder setting, and it costs zero visible quality because the extra resolution was never shown. Our Image Resizer does this with multi-step halving, which keeps downscaled images sharp.

Step 2: Pick the right format for the content

  • Photographs: WebP at quality 75–85, or JPEG at 80–85 if you need maximum compatibility. AVIF goes smaller still where supported.
  • Screenshots, UI, text, logos: PNG (lossless) or lossless WebP. Lossy codecs smear sharp edges and make text look dirty at any setting.
  • Graphics needing transparency: PNG or WebP — JPEG has no alpha channel at all.

Choosing wrong here swamps every other optimization. A screenshot saved as JPEG either looks terrible (low quality) or weighs more than the PNG would have (high quality).

Step 3: Find your quality floor with a before/after view

Quality settings are not portable wisdom — the right number depends on the image. A smooth studio portrait survives quality 60; a detailed landscape full of grass and foliage shows artifacts at 75. The only reliable method is to look.

Drop the image into our Compressor, set quality to 80, and drag the comparison handle across the areas most likely to degrade: skin, skies, text, sharp diagonal edges. Then lower the slider five points at a time. The moment you can see blockiness or “mosquito noise” around edges, step back up five. That is your floor for this image. For most photographs you will land between 70 and 85 and save 60–85% of the file size.

Step 4: Mind the hidden extras

A surprising amount of image weight is not pixels at all. EXIF metadata, embedded thumbnail previews, color profiles and editing-software XMP blocks can add tens or hundreds of kilobytes. Stripping metadata — which happens automatically when an image is re-encoded through a canvas, as all PiccTools utilities do — removes this dead weight. It is also good privacy hygiene.

Three compression myths worth unlearning

“PNG is always higher quality.” PNG is pixel-perfect, but for a photograph that perfection is invisible at normal viewing sizes while costing five to ten times the bandwidth. Quality you cannot see is quality you are overpaying for. “Quality 100 is the safe choice.” JPEG quality 100 disables most of the compression and still is not lossless — it produces huge files with no meaningful benefit over 90. “You can compress repeatedly.” Each lossy save discards a little more, so always keep an untouched original and compress from it, never from a previously compressed copy. Treat compression as the last step of the pipeline, done once, from the best source you have.

A repeatable checklist

  1. Resize to the real display dimensions (never bigger).
  2. Choose the format that matches the content: lossy for photos, lossless for graphics.
  3. Start at quality 80 and walk down with a side-by-side comparison.
  4. Strip metadata and thumbnails.
  5. Spot-check the final file on the actual page, at the actual size.

Follow those five steps and “compression without losing quality” stops being a contradiction: your files shrink by two-thirds or more, and nobody looking at the result will ever know.