Why 50KB?
A 50KB limit is tight — common for small avatars, thumbnails, and some exam or ID portals that want a tiny, predictable file. A multi-megabyte iPhone HEIC has to come down 40–80×, which a quality slider can’t do precisely. Enter 50, get a JPEG at or under 50KB.
How it works
- Your HEIC is decoded in your browser by a WebAssembly module — no server round-trip.
- The encoder searches JPEG quality levels to find the highest quality that fits under 50KB.
- If 50KB can’t be reached at the quality floor, the image is resized with a Lanczos filter until it fits.
- You get a JPEG to download, with a before/after preview.
Privacy
ID photos and exam portraits are sensitive. These files never leave your device — all decoding and compression happens locally in your browser, with no uploads, no cloud storage, no analytics. When you close the tab, the data is gone.
Frequently asked questions
Can it compress HEIC to exactly 50KB?
Yes. It searches JPEG quality levels to land at or just under 50KB, resizing only if 50KB can't be reached at the quality floor — so you always get 50KB or less.
Is my photo uploaded to a server?
No. Everything runs in your browser via WebAssembly. Your HEIC never leaves your device, and nothing is stored — close the tab and it's gone.
Will 50KB look bad?
Quality is protected by a floor, so the result stays clear rather than blocky. At 50KB the image is usually resized smaller, which is expected for a thumbnail-size target.
How is this different from a quality slider?
A slider makes you guess and re-check. You enter 50KB and it hits that target directly — which is what tight limits actually require.
Does it work on Android or only iPhone?
Any modern browser on any device. HEIC is most common on iPhone, but the file can come from anywhere.
Is there a file size limit?
No server quota — it runs on your machine, so the only limit is your device's memory.
Is it free?
Yes — completely free, no signup, no watermark, no upload.