Compress a JPG to an exact 100 KB

WebP would deliver 25–35% better quality at the same file size — that gap is real. The reason to pick JPG is that the upload destination demands it. Government recruitment forms, employer ATS systems, older CMSes, print pipelines, and several social-media APIs hardcode JPG and reject WebP at the file-type check. The destination dictates the format; Sukat just makes sure the JPG hits the cap.

For a typical 1080p–1500p photo, Sukat usually converges around JPEG quality 75–85 at full original dimensions — visually clean, no obvious artefacts on faces or product shots. Busy landscapes, foliage, or crowd shots may dip into the 60–70 range and can show mild blocking on flat areas. For most identity photos and profile shots, 100 KB is comfortably above the “visible degradation” threshold.

JPG is the right choice for photos. PNG is a lossless format optimised for line art, screenshots, and transparency — for a photo, a 100 KB PNG ends up much smaller in pixel dimensions than the equivalent JPG because PNG can’t throw away perceptual detail the way JPEG can. Use PNG only when you need transparency or pixel-exact output. For everything else photographic, JPG at 100 KB wins.

Yes — drop any supported input format (JPG, PNG, WebP, HEIC, AVIF, GIF) and pick JPEG as the output. Sukat decodes the source in-browser, re-encodes to JPEG, and downloads a file with the .jpg extension. HEIC is handled natively; you don’t need a separate “HEIC to JPG” step first.

Yes. Drop multiple images onto the drop zone, set 100 KB as the maximum file size, and pick JPEG. Sukat processes each image independently — the binary search runs per file because optimal quality depends on the image — and you can download them as individual files or as a single ZIP.

After the page loads, switch your device to airplane mode and try a compression. The page keeps working because everything runs locally through the Canvas and JPEG encoders bundled with the page. No network round-trip, no server, no logged file.