Set a target — 20KB, 50KB, 100KB, whatever your form demands — and get a photo that fits it, without guessing quality sliders.
Working backwards from the number a form actually asks for
Type the KB number the form wants — the tool works out the right quality and resolution to hit it.
Compress as many photos as you like — no account, no watermark, no daily cap.
Your photo is processed in memory and never saved to a disk on our server.
A photo straight off a modern phone is often 8 to 15 megapixels, which typically lands somewhere between 2 and 6 megabytes as a JPEG — nowhere close to the 20KB to 200KB window that most Indian exam boards, banks, and government portals demand. Manually getting there by dragging a "quality" slider up and down and re-exporting each time is slow and imprecise: nudge it too high and the file's still too big, nudge it too low and the photo turns blocky. This tool skips the guesswork by taking the number you actually need and working backwards from it — testing compression levels until it lands as close under your target as possible, only reducing pixel dimensions as a last resort if quality alone can't get there. The result is the smallest file that still looks like a photograph rather than a smear of JPEG artifacts.
Most image compressors are built around a quality percentage — drag to 60%, drag to 80%, watch the preview, repeat. That workflow makes sense for a website owner trying to balance file size against visual quality. It makes almost no sense for someone filling out an SSC, IBPS, or university admission form, because those forms don't care about quality at all — they enforce a hard KB ceiling and reject anything over it, full stop. A photo at 71% quality that comes out to 118KB when the form demands under 100KB gets bounced exactly the same way a badly pixelated 40KB photo would be accepted. The form only reads the number.
That's the entire reason this tool exists as a separate flow from a generic compressor: instead of asking you to guess a quality percentage and check the resulting size, it asks for the size you already know you need — because you copied it straight off the form's instructions — and searches for the compression setting that gets you there. Internally this is closer to a binary search than a single pass: the tool tries a middle quality value, checks whether the resulting file is under your target, and narrows in from there, in both directions, until it finds the highest quality that still fits your KB limit. Higher quality within the same size budget means a cleaner, more recognizable photo, which matters when the form is asking for a photo ID that a human reviewer will actually look at.
When the target is small enough that no reasonable quality setting will fit — a 3000×4000 pixel photo squeezed into 15KB, for instance — quality alone can't get there without turning the image to mush, so the tool takes a second step and slightly shrinks the pixel dimensions before compressing again. This two-stage approach (quality first, resolution only if needed) is what keeps very small targets looking like an actual face rather than a block of noise.
A few common situations
UPSC, SSC, Railway, IBPS and state PSC portals each specify an exact KB range for the photo and signature upload fields, and reject anything outside it.
Many corporate and government HR systems cap resume photos or ID scans at a fixed KB size to keep their database lean.
Net banking, demat account, and KYC re-verification forms frequently need a passport photo under a specific size limit.
Online admission and scholarship portals often specify photo and signature size limits as strictly as government exam boards.
Sending several photos by email where each attachment needs to stay under a provider's or recipient's size cap.
Several visa portals specify photo file size limits in addition to pixel dimensions, catching people out who only resized.
Always check the exact figure on your own form — these vary by cycle and category
| Portal / Exam type | Photo size | Signature size |
|---|---|---|
| UPSC (Civil Services, etc.) | 20KB – 300KB | 20KB – 300KB |
| SSC (CGL, CHSL, MTS) | 20KB – 50KB | 10KB – 20KB |
| IBPS / Bank PO & Clerk | 20KB – 50KB | 10KB – 20KB |
| Railway (RRB) exams | 20KB – 50KB | 10KB – 20KB |
| NEET / JEE Main | 10KB – 200KB | 4KB – 30KB |
| State PSC (varies by state) | 20KB – 100KB | 10KB – 50KB |
A quick, factual look at getting a photo to a specific KB size
| Method | Reaches exact target | Trial and error needed | Free |
|---|---|---|---|
| EkZapp Image Size Reducer | Automatic | None | Yes |
| Manual quality slider in Paint/Photoshop | Guesswork | Several exports | Depends on software |
| WhatsApp/email auto-compress | Fixed, not adjustable | None, but wrong size | Yes |
| Screenshot + crop | Loses quality unpredictably | Several attempts | Yes |
The photo comes out looking slightly soft or blocky. This happens when the target KB is very aggressive relative to the original resolution — a high-megapixel photo squeezed into 15KB has to sacrifice some detail to get there. If your form's size limit allows any flexibility, aiming for the upper end of the range (say 45KB instead of the strict minimum) preserves noticeably more detail.
The final file is a JPG even though I uploaded a PNG. This is intentional. PNG uses lossless compression, which is excellent for graphics and text but very inefficient for photographs — it simply can't hit small KB targets the way JPEG can. Converting to JPEG is what makes hitting a 20KB–50KB target realistic at all.
A transparent background image turned white. JPEG doesn't support transparency, so any transparent area in a source PNG is filled with white before compression. If you need transparency preserved, this isn't the right tool — Convert Image or a dedicated PNG optimizer would keep it, at the cost of a larger file.
The form still rejects the file after compressing. Double-check whether the portal is also enforcing a pixel-dimension requirement (e.g. "200×230 pixels") alongside the KB limit — some forms check both, and a correctly-sized-in-KB file can still fail if its width and height don't match. In that case, use Resize Image first to fix the dimensions, then run it through this tool for the KB target.
Start from the best original you have rather than a photo that's already been compressed once by WhatsApp, a screenshot tool, or a previous "quick fix." Recompressing an already-compressed JPEG stacks quality loss on top of quality loss, so the final result looks noticeably worse than compressing a clean original by the same amount.
Read the form's instructions for the exact range, not just a single number — many portals specify "between 20KB and 50KB," not "under 50KB," and a file that's too small can be rejected just as easily as one that's too large. If your form gives a range, aim for a KB value comfortably inside it rather than right at either edge.
If the portal also lists exact pixel dimensions (common for passport-style photos), sort that out first with Resize Image, then feed the correctly-sized file into this tool — resizing after compressing can undo the careful KB targeting you just did.
The tool gets as close as possible to your target without going over it, since most portals reject a file for exceeding a limit but rarely penalize a file for landing slightly under it. For very small targets, resolution may be reduced slightly alongside quality to reach the number.
Yes. JPEG's compression is far more effective at hitting a small target size than PNG, so the output is always saved as JPEG. Any transparent areas in a PNG are filled with white before compression.
Your file is transferred over an encrypted connection, processed entirely in memory, and never written to disk or kept after your download finishes.
Compress Image lets you pick a quality level and see the resulting size. Image Size Reducer works backwards from a target KB you specify, which is what most exam and government forms actually require.
Government exam portals process millions of applications and need every uploaded photo and signature to stay small so their servers and databases don't get overwhelmed, which is why limits like 20KB-200KB are common even though modern phone photos are often several megabytes.
Yes — phone camera photos are exactly the kind of large file this tool is built to handle, typically shrinking a multi-megabyte photo down to the tens-of-kilobytes range while keeping it recognizable.
You can upload images up to 50MB, which comfortably covers even uncompressed photos straight from a high-resolution phone or camera.
JPEG shrinks a photo by discarding information the human eye is least likely to notice missing, rather than storing every pixel exactly. It converts the image into a format that separates brightness from color detail, then compresses the color information more aggressively than the brightness information, since human vision is far more sensitive to changes in brightness than in color. On top of that, it breaks the image into small blocks and reduces fine, high-frequency detail within each block — the kind of subtle texture variation that's easy to lose without the photo looking obviously different at normal viewing size.
This is why a JPEG can shrink to a fraction of its original size with only a modest, often invisible, quality loss at moderate compression — but why pushing compression too far for a very small target starts to show visible blockiness: the algorithm runs out of "unnoticeable" detail to discard and starts cutting into detail the eye does notice. Understanding this is mostly reassurance: a photo compressed to 50KB by this tool isn't a lesser-quality file in some vague sense, it's a photo that's had specifically the least-visible information removed first, which is exactly the trade-off you want when a form only cares about the file size and a human will still glance at the photo.