Web portals & CRMs
Compress Image to 100 KB
Preset and ready: drop a file and the output lands under 100 KB as JPEG — processed entirely in your browser.
Drop your image here or browse
JPEG, PNG, WebP — everything stays on your device
Why this exact limit matters
A hundred kilobytes is the most common ceiling on the general-purpose web: portals, CRMs, application systems and intranets that never published a rule but reject anything past 100 KB all the same. It is also the budget where a decision appears that did not exist at 20 KB — keep full resolution at modest quality, or cap the frame and keep quality you can actually see.
A target-size compressor removes the trial and error: state the ceiling the portal enforces and receive a file that passes it on the first attempt. 100 KB is a moderate limit, common for application portals, and this page is preset to exactly that ceiling.
How to compress to 100 KB
- Drop your image into the box above — it stays on your device.
- Confirm the target: under 100 KB as JPEG.
- The MozJPEG encoder searches its quality range so the JPEG output lands just under your limit. Dimensions are left at their original size unless the target demands otherwise.
- Preview the result, compare it with the original if you want, and download — the filename carries its actual size.
Tip: Screenshot-heavy uploads (ID cards, receipts, documents) shrink dramatically; if your portal limit seems impossible for a photo, it is usually trivial for a document scan.
Measured: the full-resolution route to 100 KB
Our standard test file — a 914 KB, 1500×1800 portrait JPEG — against a bare 100 KB ceiling:
Source file
914 KB
1500×1800 JPEG
Output
95.6 KB
9.6× smaller
Quality setting
q15
the price of 2.7 MP
Resolution
1500×1800
unchanged
Quality 15 at full frame passes any byte-level check and still looks acceptable at thumbnail size — but the same ceiling with an 800-pixel frame holds quality 56, visibly cleaner where the image is actually displayed. Portals store your file; they rarely show it large. Spend the budget where it is seen.
Frequently asked questions
The portal rejects 95 KB files — what am I missing?
Check format expectations first (JPEG-only rules are common), then pixel maxima, then whether the portal counts a kilobyte as 1000 bytes. Our 95.6 KB output is 97.8 by that arithmetic — still under, but close enough to explain borderline rejections elsewhere.
Will anyone notice the difference between q15 and the original?
At full zoom, yes — quality 15 shows mild blockiness in smooth areas. At portal display sizes, rarely. If the image is meant for close inspection, cap the frame instead of the quality.
Does it matter that my source is PNG or HEIC?
Only that the portal almost certainly wants JPEG. The tool decodes all three and encodes to your chosen output — a 3 MB HEIC becomes a portal-ready sub-100 KB JPEG in one step.
Why do portals have such small file size limits?
Storage cost and legacy infrastructure. The limits are rarely about quality — they are about keeping uploads predictable, which is exactly why hitting just under the number is the correct strategy.
How does the tool hit the exact JPEG size?
It encodes your image with the MozJPEG encoder several times, binary-searching the quality setting until the output lands just under your limit — then keeps that best result.
Is my image uploaded to a server?
No. All decoding and encoding runs locally in your browser via WebAssembly. There is no server-side pipeline, no storage, and no way for us to see your file.