Processed entirely on your device — nothing is uploaded
How to use the compress image to 150 kb
- 1Drop the photo or signature in — this page has 150 KB preset as the target.
- 2Keep JPG as the output format for portal uploads; choose WebP only for your own site.
- 3The tool searches quality (and dimensions when needed) until the file fits 150 KB.
- 4Read the size and dimensions on the result line, then download.
What actually fits in 150 KB
The useful way to read 150 KB is as a pixel allowance. Mid-quality JPEG needs about 1.8 bits per pixel, which makes the allowance roughly 697,500 pixels — a 4:3 frame of around 960 × 720, or about 960 × 720 pixels of photo, which fills a phone screen cleanly.
Prints well at snapshot size. The limiting factor becomes the pixel count, not the compression.
Those figures assume photographic content. Plain-background material — a signature, a form, a diagram — beats the 960 × 720 estimate handily at 150 KB, while dense textures like foliage or fabric undershoot it.
Where the 150 KB limit comes from
This page exists because upload forms reject files, and they reject them at round numbers. The situations that bring people here: a scholarship or certificate portal with a 150 KB limit, a classified-ad photo, or a forum or community upload with a per-file cap.
150 KB caps show up on portals that accept full photographs but still run on constrained storage — scholarship sites and regional boards among them.
What makes a 150 KB rejection so irritating is the feedback loop — export, upload, get refused, guess again. A tool that takes 150 KB as an input and searches for the best encode under it removes the loop entirely.
How this tool reaches 150 KB exactly
The compressor binary-searches JPEG quality: encode, measure against 150 KB, halve the range, repeat. Eight rounds land within about one quality point of the largest encode that still fits, and since it all happens in this tab's memory, the search takes well under a second per image.
When the pixel count is too high for 150 KB at any quality — a 4,000 × 3,000 phone original against a 697,500-pixel budget, say — the tool shrinks the dimensions toward about 964 × 723 and searches again, repeating until the encode fits. The final dimensions are reported next to the size.
On format: WebP reaches 150 KB at higher quality than JPG, and upload portals reject it anyway. Keep the default JPG output for anything with a size cap; save WebP for your own website.
And the privacy point, which matters when the file is your signature or your face: reaching 150 KB happens entirely on your device. The tool uploads nothing, queues nothing server-side, and keeps nothing.
Getting the best result at 150 KB
Make the subject the frame. The 960 × 720 that 150 KB affords is ample for a face or a page, and wasted on a wide shot where the subject is a small patch — crop first, compress second.
Documents behave differently from faces at 150 KB: a scan compresses best when it is straight, evenly lit and pure black-on-white, because shadows and grey cast are pure cost to the encoder. Re-scanning flat or photographing in daylight buys more legibility than any slider.
If the destination limits dimensions as well as size, do the resize first and the 150 KB compression second — quality survives that order far better than the reverse.
At 150 KB you can afford to be choosy about what degrades: portraits keep skin tones smooth well past this budget, while screenshots with fine text suffer first. If a screenshot must fit 150 KB and the destination is your own site, the WebP output preserves its edges far better than JPG.
Frequently asked questions
How do I compress an image to exactly 150 KB?
Drop the image above — the target is preset to 150 KB on this page. The tool searches out the highest quality that fits under the cap, shrinking dimensions automatically if it must, and reports the final size before you download. No upload, no watermark, no sign-up.
Will my image still look good at 150 KB?
Usually, yes. 150 KB holds a clearly recognisable 960 × 720 photograph; softness appears at full zoom but not at normal viewing size, and cropping to the subject first improves it further.
Why did the dimensions of my image change?
The pixel count exceeded what 150 KB can hold — about 697,500 pixels of ordinary photo. Below that point no quality slider helps, so the tool shrank the dimensions by its estimate and re-ran the search. Nothing changes silently: the output line shows the new size and dimensions.
Is my photo or signature uploaded anywhere?
No. Decoding, resizing, the quality search and the encode all run in your browser with the canvas API; nothing is transmitted. For a 150 KB task that is usually a signature or an ID photo, that matters more than usual.
The portal wants specific pixel dimensions as well as 150 KB. What order do I do that in?
Resize to the required dimensions first (the Image Resizer linked below does that), then compress the resized file to 150 KB here. In that order the compressor is not fighting excess pixels, so more of the budget goes to quality.
Does this work with PNG and WebP files too?
Yes — PNG, WebP and AVIF are all accepted and re-encoded toward 150 KB. PNGs convert to JPG by default, since lossless PNG cannot hit small byte targets on photographs, and JPG is what upload portals expect anyway.