Drop an image in and PixSqueeze will squeeze it to 100KB or under while keeping it as sharp as that budget allows. The target is already set below — press Compress and you are done. Nothing is uploaded; the whole thing runs on your device.
Target size is preset to 100 KB. Change it below if you need a different budget.
100KB is the limit that turns up again and again in forms that were designed years ago and never revisited — government portals, university applications, job boards, exam registrations, older CMS uploaders. The number is arbitrary, but the rejection is not: go one byte over and the form bounces you.
It is also a sensible ceiling for a photograph on a web page. An image under 100KB will load on a weak mobile connection without the visitor noticing it arrive, which is more than can be said for the 4MB straight-from-the-camera JPEG it replaced.
Most tools give you a quality slider and leave you to guess. Guessing means exporting, checking the file size, adjusting, exporting again.
PixSqueeze works backwards from the number instead. It encodes the image, measures the result, and narrows in on the quality setting that lands just under your budget — a handful of passes, all in the browser, taking under a second on a normal photo. You get the highest quality that still fits, not simply the first setting that happened to be small enough.
A very large or very detailed image sometimes cannot reach a small budget without falling apart. When that happens PixSqueeze tells you plainly rather than handing back something over the limit or something unusable.
The fix is almost always dimensions rather than quality. A 6000 × 4000 photo does not need to stay 6000 × 4000 to sit in a form field. Set Resize to 1920px or smaller and try again — halving the width cuts the pixel count to a quarter, and the target becomes easy.
It depends entirely on the picture. A portrait against a plain wall, or a screenshot with flat colour, will look essentially untouched at 100KB. A dense landscape — foliage, gravel, crowds, fine texture everywhere — has far more detail to preserve and will show some softening.
If the result looks over-compressed, resize first and compress second. Fewer pixels at high quality nearly always beats more pixels at low quality for the same file size.
PixSqueeze targets 100KB or just under, never over. Landing exactly on the byte is not possible with image compression — you set a ceiling and the encoder gets as close beneath it as it can while keeping quality as high as possible.
For most photographs at normal web dimensions, no. Quality only suffers noticeably when the image is very large or extremely detailed. In that case, resize the image first — reducing the dimensions preserves far more apparent quality than compressing harder.
No. All compression happens in your browser using local APIs. Your files never leave your device, so there is no upload wait, no queue, and no copy of your image on anyone's server.
Yes. Drop in as many as you like and each one is compressed to the same target independently, then downloaded individually or all together.