Skip to content

How to reduce image file size without ruining the picture

Format choice beats quality sliders: how JPG, WebP and PNG compress, and how to hit an exact KB target.

Updated September 2, 2026 · 6 min read · by the InfyTool team

Upload forms with 100 KB limits, emails that bounce over 10 MB, pages that load slowly because a hero image weighs 4 MB — file size is the most common image problem there is. The fix is a sequence, and the order matters, because the first two steps are free and the last one costs quality.

Step 1 — resize to the size it will be seen (free)

A 4000×3000 photo shown at 800 px wide carries 18 megapixels where 1 is needed. Resizing to the display size is the single biggest saving available — routinely 80–95% — and costs nothing visually. If you do not know the display size, the resizing guide has targets for the common destinations.

Step 2 — pick the right format (free)

ContentRight formatWhy
PhotoWebP (or JPG for maximum compatibility)lossy codecs built for photos; WebP ~30% smaller than JPG
Screenshot, UI, textPNG or WebP-losslesslossy formats smear text edges
Logo / iconSVG if available, else PNGvector is tiny and infinitely sharp
Photo needing transparencyWebPalpha channel at a fraction of PNG’s size

Converting is one drop in the image converter — it batches, and shows the size change per file so you can see what the format switch bought you.

Step 3 — compress (the only step that costs quality)

Only after size and format are right, lower the quality setting. For JPG and WebP, quality 80–85 is visually indistinguishable from 100 for most photos at a third of the bytes; 60–70 shows mild softness under scrutiny; below 50 is visible. The image compressor previews the result live so you can stop exactly where your eyes tell you to.

Compress images now

Live preview, batch, before/after sizes. Or use the resizer’s “Max file size” field to hit an exact KB target automatically.

Hitting an exact limit (100 KB, 200 KB, 1 MB…)

Guessing quality values until a file squeaks under a limit is miserable. The image resizer has a Max file size field: set “100 KB” and it binary-searches the quality that lands just under the limit while keeping your chosen dimensions. If even quality 20 cannot fit, the honest fix is fewer pixels — drop the dimensions 20–30% and try again.

Special cases

  • SVGs that are somehow huge: exported SVGs carry editor junk — hidden layers, absurd precision, embedded rasters. The SVG optimizer typically cuts 40–70% losslessly.
  • Animated GIFs: GIF is an ancient format; the same clip as MP4/WebM is 10× smaller. If it must stay an image, reduce dimensions and frame count.
  • Documents full of images: compress the images before inserting them; office suites re-encode poorly and PDFs balloon.

Frequently asked questions

How do I get an image under exactly 100 KB (or any limit)?

Use a tool with a target-size mode. The InfyTool resizer has a “Max file size” field: enter 100 KB and it searches for the highest JPG/WebP quality that fits under the limit, instead of you guessing quality numbers repeatedly.

Which is smaller, JPG or WebP or PNG?

For photos: WebP is usually 25–35% smaller than JPG at the same visible quality; PNG is by far the largest and the wrong choice. For graphics with few colours: PNG (or better, SVG if it exists) beats JPG, and WebP-lossless often beats PNG. Format choice makes a bigger difference than any quality slider.

Does reducing file size reduce quality?

Below a point, yes — that is the trade. But the first big savings are free: resizing to the display size and picking the right format often cuts 80–90% with no visible change. Only after that does the quality slider start costing anything you can see.

Why is my PNG so huge?

PNG is lossless, so a photographic PNG stores every pixel’s noise faithfully — megabytes of it. Photos belong in JPG or WebP. Keep PNG for screenshots, logos, UI graphics and anything needing transparency or crisp text.

Tools used in this guide