Compress image to 150 KB

Set the budget, and the encoder is searched for the best quality that fits under 150 KB. On your device — the image is never uploaded.

  • 0 uploads
  • No limits
  • No signup
  • Works offline

Where a 150 KB limit comes from

Nobody chooses 150 KB for fun. If you are here, a form told you to, and the form probably did not explain how. These are the places this particular number turns up:

  • Forms that specify a 100–200 KB range
  • Blog and CMS uploads with a per-image budget
  • Email signatures with an embedded logo or photo

A 1600-pixel photo at 150 KB is indistinguishable from the original at normal viewing size.

What 150 KB actually buys you

At 150 kilobytes the constraint has stopped being adversarial. A 1600-pixel photograph fits with the quality high enough that the difference from the original is not visible at any normal viewing distance, which means the interesting question is no longer whether you can hit the number but whether you should be sending that many pixels at all.

Forms that specify 100 to 200 KB are usually protecting a page-weight budget rather than a storage one. If the image will be displayed at 800 pixels wide, sending 1600 is paying twice — once in bytes and once in the browser's downscaling. Resize to the display size first and the compression barely has to work.

Effectively lossless for anything screen-sized. The search here spends the budget on dimensions before quality — a larger image at quality 55 beats a smaller one at 95, because the eye forgives artefacts more readily than missing resolution.

Getting a better result

Three things reliably help when the budget is tight:

  • Crop before compressing. Every pixel you keep costs bytes. A tightly framed portrait at 150 KB looks far better than a full-body shot squeezed into the same space. The cropper hands its result straight to this tool.
  • Start from the highest-quality original you have. Compressing an image that has already been through WhatsApp compounds the damage. Go back to the file straight off the camera.
  • Prefer WebP if the form allows it. At the same file size WebP holds noticeably more detail than JPEG. Most official forms still want JPG, but it costs nothing to check.

Other common targets

10 KB · 20 KB · 30 KB · 50 KB · 100 KB · 200 KB · 300 KB · 500 KB

How it works

  1. 01Add your imageDrop it on the page, click to browse, or paste from the clipboard.
  2. 02The 150 KB target is already setYou landed on this page, so the budget is filled in. Change it if you need something different.
  3. 03The search runsThe encoder is run repeatedly, binary-searching quality for the best result that still fits under 150 KB.
  4. 04Compare, then downloadDrag the before/after slider to see what the compression cost before you commit.

Questions people actually ask

Should I resize or compress to hit 150 KB?
Resize, if you know the display size. Halving the dimensions removes three quarters of the pixels and costs nothing visible when the image was oversized to begin with. Compression is the right lever only once the dimensions are already correct.
Will my photo still look acceptable at 150 KB?
A 1600-pixel photo at 150 KB is indistinguishable from the original at normal viewing size. Effectively lossless for anything screen-sized.
Is the result exactly 150 KB?
It lands within about 5% below 150 KB, and never above it. Going over would defeat the point — a form that says "maximum 150 KB" rejects a file of 151 KB without explanation.
Is my image uploaded to reach 150 KB?
No. Every encode in the search runs on your own device, in a background thread, using WebAssembly builds of MozJPEG and libwebp.