Compress JPG to 15KB
Set the ceiling at 15KB, drop your JPG files in, and each one comes back at the highest quality that still fits underneath. Nothing is uploaded.
What happens when you compress JPG to 15KB
JPG is already a lossy format, so re-encoding it to a smaller target is straightforward. Each re-save does lose a little detail, so always compress from the original rather than from a file you have already shrunk once.
JPG is at its best with photographs, camera output, scanned documents with continuous tone. Starting from that kind of source, 15KB is a tight but usually workable target. The tool measures the actual encoded bytes on every pass rather than predicting them, so the answer it gives is true for your specific file rather than for an average one.
Who asks for 15KB
Signature and thumbprint uploads on Indian examination portals commonly specify 10–20KB, which is why 15KB shows up as its own search.
Resolution you can keep at 15KB
A useful rule of thumb: a typical photograph at moderate quality costs roughly an eighth of a byte per pixel. Working backwards from 15KB, the practical ceiling is around 128,000 pixels — approximately 440 by 290. Stay at or below that and the encoder has enough budget to look clean. Push well past it and you are spreading a fixed budget over more pixels, which is where blocking and smeared detail come from.
This is an order-of-magnitude guide, not a promise, because content matters enormously. A flat product shot, a screenshot or a scanned signature compresses several times better than the estimate. A noisy night scene or dense foliage compresses considerably worse, since noise is incompressible by design. When you compress jpg to 15kb here the tool measures the real encoded file rather than estimating, so the answer is honest for your specific image.
If the estimate says your photograph is well past that pixel budget, the better move is to reduce the dimensions deliberately before you compress jpg to 15kb, choosing what to lose rather than letting the encoder decide. A half-resolution image at a generous quality setting almost always looks better than a full-resolution one squeezed to the same number of bytes.
The method
Most compressors give you a quality slider and let you find out afterwards how big the file turned out. That is the wrong way round when you have a hard ceiling. This tool works backwards from the number: you ask it to compress jpg to 15kb, and it searches for the encoder setting that lands just underneath.
The search is a binary search over the JPEG or WebP quality parameter. It encodes at the midpoint of the remaining range, checks the byte count against 15KB, and moves the range accordingly. Nine passes narrow the setting far finer than the eye can resolve, and every pass keeps the best result that fit — so what comes back is the highest quality version that still fits, not the first one that happened to work. Nine passes is also fast enough that you can compress jpg to 15kb, look at the result, change the number and run it again without ever waiting on a progress bar.
When quality alone cannot get there, the tool reduces pixel dimensions in steps and searches again. That order matters: dropping quality first preserves your framing, while shrinking first throws away detail no quality setting can recover. Final dimensions are listed next to the file whenever a resize was needed, so an attempt to compress jpg to 15kb never quietly returns something smaller than you asked for without saying what it gave up to get there.
Processed locally, never uploaded
Nothing you drop onto this page leaves your device. The image is decoded, re-encoded and handed back entirely inside the browser tab. There is no upload, no queue, and no temporary copy sitting on someone else's disk waiting for a retention policy to delete it.
That matters more than it sounds. The files people most often need to shrink are the ones they should be most careful with: passport scans, signatures, identity documents, medical forms. Handing those to an unknown server in exchange for a smaller file is a poor trade. Because the work is local, you can compress jpg to 15kb with the network disconnected and get the same result.
It also means there is no queue to wait in and no daily allowance to run out of. Server-side compressors have to ration free use because every file costs them CPU time; here the CPU is yours, so you can compress jpg to 15kb as many times as you like, on as many files as you like, without an account.