SqueezeKB

Compress an image to 50KB

50 KB is a tight budget. The tool finds the best quality that fits and, when needed, reduces the pixel dimensions — then tells you exactly what it did.

Drop an image here

or paste it (Ctrl/⌘ + V)

JPG or PNG

Target size

Your image is processed on this device. It is never uploaded.

Real example: a photo compressed to 50 KB

These are not mock-ups. The photos below were run through this exact tool, and the result is the file you would get. Switch photos to compare an easy case and a hard one.

Garden with a split-rail fence and white houses, compressed to 50 KB
Original
7.15 MB · 4032 × 3024 px
Result
49.1 KB · 544 × 408 px · quality 60%
Saved
99.3%

The tool kept JPG quality at 60% and reduced the pixel dimensions just enough to fit. Below about 60% quality, JPG shows blocky artefacts, so a slightly smaller, clean image is the better trade.

Zoomed in: same area, before and after

Detail of the original photo at full resolution: house, window and leaves
Original, 100% (crop)
The same detail cut from the compressed file and enlarged to the same size
50 KB file, same area enlarged ×7.4

Download this exact file (49.1 KB)

Photo: 89Traveler, CC0 1.0, via Wikimedia Commons. Made with this tool in Chromium 156.0.8078.4. Other browsers’ JPG encoders give slightly different results.

What fits in 50 KB

A modern phone photo is usually several megabytes, so getting under 50 KB almost always means making the image smaller in pixels as well as lowering JPG quality. How small depends on the picture: smooth backgrounds compress far better than foliage, text or grain.

The result panel shows the final dimensions and quality, so you can judge whether it still looks right before you download.

Tips for a sharper 50 KB image

  • Crop away empty space before compressing — fewer pixels means more quality per pixel.
  • Choose JPG output for photos; PNG at 50 KB will be very small in dimensions.
  • If the site allows 100 KB, use that instead — the difference in sharpness is visible.

How the target-size compression works

  1. Your browser decodes the image (EXIF orientation is applied, metadata is not carried over).
  2. For JPG output we search for the highest encoder quality between 60% and 95% that fits under your target.
  3. If even 60% quality is too large, we reduce the pixel dimensions just enough to fit at 60%. Below about 60%, JPG shows blocky artefacts, so a slightly smaller, clean image is the better trade. Only for very small targets does quality go lower, never below 30%.
  4. The search stops after a fixed number of attempts or about 20 seconds, so a phone never locks up. If the target was not reached, you get the closest result and an honest warning.

Frequently asked questions

Why did my image get smaller in width and height?

Below about 60% quality, JPG starts to show blocky artefacts. Instead of going lower, the tool reduces the pixel dimensions, which looks cleaner at 50 KB. In our real example, a 12-megapixel phone photo ends up 544 px wide at 60% quality.

Is my image uploaded to a server?

No. The image is read into your browser’s memory, compressed with the browser’s own canvas encoder, and handed back to you as a download. There is no upload endpoint at all. You can check this yourself in your browser’s developer tools (Network tab) — the privacy page shows how.

What if the image can’t get under the target?

You’ll see the closest size we managed and a clear message that the target was not reached. We never label a file as “done” when it is over the limit. Larger targets, JPG output or a smaller source image usually solve it.

Will the result be accepted by the site I’m uploading to?

This tool changes file size and pixel dimensions only. It does not check whether a photo meets any organisation’s or form’s content rules (background, framing, etc.). Always check the requirements of the site you are uploading to.