Compress Image

Shrink a photo's file size with a quality slider and a live before/after preview — nothing ever uploads.

Your files are processed locally in your browser and are never uploaded to our servers.

Drop in an image, drag the quality slider, and watch the file size drop in real time. The comparison preview shows exactly what you're trading away before you download anything.

How it works

  1. Add your image

    Drag and drop a JPG, PNG, or WebP file, paste from your clipboard, or click to browse. Nothing is sent anywhere — the file stays in your browser's memory.

  2. Adjust the quality slider

    Move the slider and the tool re-encodes the image on the fly, updating the preview and the projected file size instantly.

  3. Compare before and after

    Use the side-by-side or slider preview to check for visible artifacts around edges, text, and gradients before committing to a quality level.

  4. Download the result

    Save the compressed file directly to your device. Batch mode lets you compress several images at the same settings in one pass.

Lossy vs. lossless compression, in plain terms

Every image compressor makes a choice between two strategies. Lossless compression (PNG, and technically WebP has a lossless mode too) rearranges and packs image data more efficiently without discarding anything — decompress it and you get back pixel-for-pixel the same image. Lossy compression (JPG, and WebP/AVIF in their normal modes) throws away information the algorithm predicts you won’t notice — subtle color gradations, high-frequency detail in busy textures — in exchange for much smaller files. This tool’s quality slider controls exactly that trade-off for lossy formats: at 100% almost nothing is discarded, at 10% the encoder is aggressive about which detail it keeps.

The reason this matters practically: a lossless format can never beat a well-tuned lossy format on file size for photographic content. If your source image is a photo and file size matters, converting to JPG or WebP before compressing will almost always beat compressing a PNG.

What actually happens when you move the slider

JPG-family compression works by splitting the image into small blocks (typically 8×8 pixels), converting each block’s color information into frequency components, and then rounding those components more or less aggressively depending on the quality setting. Fine detail and sharp edges live in the higher-frequency components, so as quality drops, the encoder rounds those away first — this is why compressed images get “blocky” or lose crisp edges before they lose overall color accuracy. Flat, low-detail areas like a clear sky or a plain wall compress extremely well at any quality level; busy areas like foliage, fabric patterns, or small text degrade first and are the best place to check when judging whether a quality setting is too aggressive.

WebP and AVIF use more modern, more efficient versions of the same general idea, along with better prediction between neighboring blocks, which is why they typically produce 25-50% smaller files than JPG at equivalent visual quality.

Reading the before/after preview correctly

Don’t judge compression quality by zooming to 400% and hunting for artifacts — nobody will view your image that way. Judge it at the size it will actually be displayed: full-screen for a hero image, thumbnail-size for a gallery grid. A quality level that shows visible blocking at high zoom is often completely invisible at normal viewing distance and size. The live preview in this tool is deliberately shown at a realistic scale for this reason.

Pay closest attention to three things: skin tones (banding shows up fastest here), text or fine line art embedded in the image (JPG is particularly bad at compressing sharp text edges — if your image contains a lot of text, consider PNG or WebP lossless instead), and large smooth gradients like sky or studio backdrops, where low-quality settings introduce visible “stepping.”

Why file size matters beyond just storage

Image weight is one of the largest and most controllable contributors to page load time. A web page’s Largest Contentful Paint (LCP) — a core Google ranking signal — is frequently the hero image itself. Shaving a 2MB photo down to 200KB without visible quality loss can cut multiple seconds off load time on a mobile connection, which affects both user experience and search ranking. It also matters for anything with an upload limit: many CMS platforms, email providers, and form tools cap attachment sizes, and getting under that ceiling without visibly degrading the image is the whole point of a quality slider rather than a blunt “resize until it fits” approach.

Compressing responsibly

Every time you re-compress an already-compressed JPG, you lose a little more information, because the rounding errors from each pass compound. If you plan to edit an image further (crop, color-correct, combine with others), do that work first from the highest-quality source you have, and compress only as the final export step. Keep your original file if storage allows — compression is one-directional, and there’s no way to recover detail that’s already been discarded.

Frequently asked questions

Will compressing my image reduce its resolution?

No. Quality-based compression (what this tool does) keeps the pixel dimensions identical — it only reduces the amount of data used to describe color and detail within each pixel block. If you also want smaller dimensions, use the Resize tool before or after compressing.

Why does my PNG barely shrink compared to my JPG?

PNG uses lossless compression, so a PNG of a photograph is often much larger than a JPG at any quality setting because it can't discard information the way JPG does. For photos, converting to JPG or WebP first will usually get you a much smaller file than compressing the PNG alone. PNG compression here mainly helps images with flat colors, like screenshots or logos.

What quality setting should I use?

For photos shared online, 70-80% quality is usually visually indistinguishable from the original at normal viewing sizes and cuts file size by 60-80%. Go lower (40-60%) for thumbnails or background images where fine detail doesn't matter. Stay above 85% for images you plan to print or crop further later, since repeated compression compounds quality loss.

Does this tool support batch compression?

Yes. Drop multiple files at once and the same quality setting is applied to all of them, with individual before/after sizes shown per file and a single download for each.

Is there a file size limit?

The practical limit is your device's memory, not an artificial cap. Because processing happens with your browser's own graphics engine, very large images (50 megapixels and up) are handled on a background thread so the page doesn't freeze, though extremely large batches will take longer on lower-powered devices.