Skip to content
TryImager

How to reduce image size in KB without losing quality

Most oversized images are oversized for one boring reason: the dimensions are far larger than anywhere they're displayed. Fix that first, then compress.

By Ranjith R, Creator & Developer of TryImagerPublished Last updated: 8 min read

A 4.2 MB image on a page that displays it 800 pixels wide is not a compression problem. It is a dimensions problem. Phone cameras produce 4000-pixel-wide files; websites, email clients and chat apps almost never show them at more than 1600. Before you touch a quality slider, ask what size the image is actually seen at.

Step 1 — Resize to the size it's displayed at

File size scales with pixel count, which scales with the square of the dimensions. Halving width and height removes 75% of the pixels — and scaling a 4000 × 3000 phone photo (12 MP, 48 MB raw RGBA) down to 1200 × 900 (1.08 MP, 4.32 MB raw RGBA) removes 91% of the pixel grid before any lossy compression runs, with zero visible loss on a layout that never displayed the extra pixels. Practical targets: 1600 × 900 or 1600px wide for a full-width web image, 1200px for a blog body image, 800px for a card or thumbnail, and 2x those numbers only if you're serving retina explicitly.

Step 2 — Pick the format that fits the content

ContentFormat to compareWhat to check
PhotographWEBP, JPG as fallbackMeasured bytes and visible detail
Logo or flat graphicPNG, or WEBP if transparency plus size matterCrisp edges; small icons may not shrink
Screenshot with textPNG (WEBP lossless if supported end to end)Readability at the destination size
Transparent product cut-outWEBPAlpha edges and actual savings

Step 3 — Set quality, and look at the result

For JPG and WEBP, quality 75–85 is the working range for almost everything. Below 70 you begin to see artefacts in flat areas and around sharp edges; above 90 you're paying a lot of bytes for detail nobody perceives. Change the slider, look at the output at full size, and check the byte count — all three, every time. A number that looks reasonable is not evidence.

Hitting a specific KB limit

Upload forms often impose hard caps: 2 MB, 500 KB, sometimes 200 KB or 50 KB. Guessing at quality values to land under a cap is tedious, so our Image Compressor and Resize Image tools take the target size directly and search for it — encoding, measuring the real output bytes, adjusting quality, and stepping pixel dimensions down only if quality alone cannot reach the limit.

Image size reducer vs image resizer: which method to use

What you need to reduceBest tool to useWhat changes in the output file
Reduce file size in KB while keeping width × height unchangedImage Compressor (Quality mode)Encoded bytes drop; pixel dimensions stay identical
Reduce picture size to fit under 20 KB, 50 KB, 100 KB or 200 KBImage Compressor (Target size in KB mode)Binary search lowers encoder quality first, then steps dimensions down if needed
Change width and height to exact pixels (e.g. 1200 × 800 px)Resize ImagePixel grid scales proportionally with Keep aspect ratio locked
Meet passport, signature or Indian exam portal rulesPassport Photo Resizer, Signature Resizer or Indian Exam Photo ResizerApplies preset aspect ratio/pixel frame and checks the resulting KB range

Five things that quietly waste quality

  • Compressing first and resizing after. You throw away detail, then throw away the pixels holding it. Always resize first.
  • Re-saving the same JPG over and over. Each cycle adds permanent damage; go back to the original instead.
  • Upscaling a small image to 'improve' it. Nothing is added — you get a bigger, softer file.
  • Using PNG for photographs. It cannot compress photographic noise and produces files several times larger than needed.
  • Judging quality on a zoomed-out preview. Artefacts only become obvious at 100%.

A recipe for the common case

  • Crop away anything the image doesn't need.
  • Resize the long edge to 1600px for a full-width image, 1200px for body content.
  • Convert to WEBP at quality 80, and keep a JPG at 85 if you need broad compatibility.
  • Check the reported saving. If it says 'Larger', your source was already well optimised — keep it.

Every step above runs entirely in your browser on TryImager. Your files never leave your device, so you can do this with client photos, ID documents or unreleased product shots without thinking about it.

Tools for this