Is 100 KB the same as 102,400 bytes?

Not here. FlashKit Tools treats 100 KB as 100,000 bytes (1 KB = 1,000 bytes), which is how most government portals count. A file of 100,601 bytes can fail a “max 100 KB” check even if it is under 100 KiB.

Does the tool drop JPEG quality to 10% before it shrinks the photo?

No. Target mode keeps JPEG/WebP quality at about 55% or higher and shrinks width and height first. Quality only goes lower if an exact box (for example a PAN 10 KB signature) still will not fit.

Which target should I pick for a form?

Use the number on the form. 100 KB is the usual “photo” cap. 50 KB is tighter and usually means a smaller pixel grid, not a 10% smear of the same 12 MP frame. 20 KB and 10 KB are for small ID and signature boxes, not full-frame portraits.

Can a compress make the file bigger?

Yes, especially a small WebP re-encoded as JPEG at high quality. If the output would be larger, the compressor keeps the original and tells you. The percent saved will not show a double minus.

Compress Images under 100 KB vs 50 KB: Quality You Keep

“Under 100 KB” and “under 50 KB” are not two points on the same quality slider. They are two budgets. A 12 megapixel phone JPEG is often 2–5 MB. Getting that under 100,000 bytes always means fewer pixels, a lossy encode, or both. FlashKit Tools’ image compressor searches a quality floor first (about 55% for JPEG/WebP), then reduces width and height, and only goes below that floor when an exact box still will not fit. It does not smear a full-size frame at 10% quality and call that a 50 KB photo.

This is the quality comparison. For a hard 20 KB form see compress to 20 / 50 / 100 KB. For signatures see 10 KB for forms.

Try 100 KB then 50 KB

Same photo, two budgets. The row shows bytes, pixels, and quality. 1 KB = 1,000 bytes.

Open Image Compressor

What the two budgets usually buy

On a detailed 12 MP photograph, 100 KB is typically a downscaled JPEG that still looks like the same scene on a form preview. 50 KB is the same strategy with a smaller grid. You should expect the 50 KB file to be noticeably softer on a laptop, and still readable as a face on a portal thumbnail. Neither result is “without quality loss.” Lossy JPEG is a trade. The honest claim is: the tool stays at or under N × 1,000 bytes and avoids collapsing quality before it collapses size.

100 KB (100,000 bytes): everyday ID and exam photo caps. Start here if the form says 100 KB.
50 KB (50,000 bytes): tighter portals. Same face, fewer pixels. Do not “fix” it by raising quality and ignoring dimensions — that is how you miss the cap.
20 KB / 10 KB: small boxes (PAN photo / signature), not a holiday photo. See the PAN and signature guides.

How to read the row

After a run you get original size → new size, original W×H → new W×H, and a Q% for JPEG/WebP. Within target means the file is ≤ the budget in decimal kilobytes. Exceeds target means even the smallest usable result we will emit is still over — crop tighter, switch PNG to JPEG, or raise the limit. If a Quality-mode re-encode would grow the file (common with an already-small WebP), the original is kept and the row says so instead of showing a fake “−64%”.

WebP versus JPEG at these sizes

WebP often wins on a photo that is already WebP. It does not always win if you transcode a tiny WebP to JPEG at 80%. The compressor will not force a larger file on you. For government portals that only accept JPEG, pick JPEG in the output row before you chase 50 KB.

Step-by-step

Open Image Compressor. Target Size is the default.
Drop one photo. Click 100 KB. Note bytes and Q%.
Click 50 KB. Dimensions should drop before quality falls through the floor.
Download the file the form asked for. Do not upload the 100 KB file to a 50 KB field.

100 KB or 50 KB, on purpose

Decimal kilobytes, quality floor, then scale. Original kept if the encode would grow.