Web portals & CRMs
Compress Photo 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 comfortable end of official photo rules: it tops the Passport Seva band (20–100 KB), sits mid-band for UPSC (20–300 KB) and leaves the NTA exams (10–200 KB) with room to spare. Portals that quote 100 KB usually care about storage, not sharpness — which means you can spend nearly all of it on quality instead of on pixels nobody will display.
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: what 100 KB buys at passport scale
Our test file is a 914 KB, 1500×1800 portrait JPEG. For this run we capped the long edge at a marketplace-style 1000×1000 box and gave the encoder a 100 KB ceiling:
Source file
914 KB
1500×1800 JPEG
Output
95.2 KB
9.6× smaller
Quality setting
q50
mid-range, clean
Resolution
833×1000
inside the box
Quality 50 at 0.8 megapixels is a genuinely usable photo — faces stay crisp, edges survive zoom. At full 1500×1800 resolution the same 100 KB forces quality 15 instead, which is the difference between a photo and a smear. The rule of thumb: past ~50 KB, budget pixels before quality.
Where 100 KB sits in real photo rules
| Form | Photo size rule | Dimensions | Format |
|---|---|---|---|
| India Passport Seva | 20–100 KB — 100 is the top of the band | 3.5×4.5 cm, ≥350 px wide | JPG |
| UPSC exams | 20–300 KB | 350×350–1000×1000 px, square | JPG |
| JEE Main / NEET UG (NTA) | 10–200 KB | 413×531 / 275×354 px | JPG |
From the 2025–26 cycles. In every row 100 KB is inside the band — the question this page answers is how good a photo you can get for exactly those bytes.
Frequently asked questions
Is a 100 KB photo good enough to print?
At passport print sizes, yes — 100 KB of well-spent JPEG at sensible dimensions prints cleanly. Where prints fall apart is heavy quality reduction on oversized canvases, not the KB number itself.
Why did the output come out smaller than 99 KB instead of exactly 100?
The encoder finds the highest quality setting whose result still fits under your ceiling — it does not pad the file to fill it. A 95 KB answer at q50 is simply the best fit the quality ladder allows.
The portal also states 350×350 minimum pixels — does your tool check that?
It enforces whatever maximum dimensions you enter, and it never enlarges. If your source is already at or above the portal minimum, the output stays above it; if your source is smaller, no compressor can honestly fix that — re-shoot or rescan instead.
Can I compress several files for the same portal?
Yes — run each file through the same target page. The settings stay locked, so every file you process here comes out under the same ceiling.
Why JPEG and not another format for my upload?
JPEG is the most universally accepted image format on upload forms and gives the smallest files for photographs. If your destination accepts only "images", JPEG is the safe choice.
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.