Compress a JPG to 50 KB
Three steps. The format pin is the part most generic compressors get wrong — pick JPEG as the output explicitly so the file saves as .jpg.
Upload the photo
Drop your JPG, PNG, HEIC, WebP, AVIF, or GIF onto Sukat’s drop zone. iPhone HEIC files decode in-browser — useful when the recruitment portal demands JPG but your phone shoots HEIC by default.
Set 50 KB and pin the output to JPEG
Type 50 in the Maximum File Size field and pick KB. Switch the output format selector to JPEG — this is the step the portal cares about. The downloaded file will carry a .jpg extension that the SSC, IBPS, and RRB upload widgets accept without complaint.
Convert and download
Click Convert & Download. Sukat binary-searches the JPEG quality scale; if the lowest quality is still too heavy, it downscales the dimensions and retries. The live preview shows the final output size in pixels before you commit.
When JPG specifically at 50 KB matters
The 50 KB-and-JPG combination is almost exclusively a recruitment-portal problem. The size cap is one constraint; the format lock is the one that catches people out.
- SSC OTR candidate photographs. SSC’s One-Time Registration spec runs 20–50 KB for the photo, with JPG mandatory at the upload widget. WebP gets silently rejected. See SSC Photo & Signature Compressor for the full SSC workflow.
- IBPS, RRB, SBI, and LIC banking-exam photos. PO, Clerk, RRB Officer Scale I/II, Specialist Officer, and LIC AAO applications all hardcode JPG at 20–50 KB for the candidate photograph.
- Older state PSC and university entrance portals. MPSC, UPPSC, KPSC, and similar state recruitment commissions still run on form widgets that pre-date WebP and accept only
.jpg. - HR ID-badge databases. Enterprise badge-printing systems — especially the on-premise ones — ingest only JPG and cap the photo at 50 KB to keep the printable-records database compact.
- Government tender and KYC portals. GeM, CPP-India, and bank KYC capture widgets accept JPG only at 50 KB for vendor and contractor identity photos.
- Print workflows. RIPs and print-queue systems integrated with legacy MIS software accept JPG at a fixed 50 KB ceiling for ID-card runs — the print operator never sees a format selector.
- Legacy CMS image uploaders. Intranets and academic portals built before 2018 enforce JPG at the MIME-type check; a WebP rename to
.jpgstill fails because the server reads the magic bytes.
Built for the JPG-and-50-KB double constraint
Plenty of compressors will hit 50 KB. Plenty will export JPG. Sukat does both in one pass without you toggling between two tools.
Hits 50 KB and JPG simultaneously
State the limit, pick JPEG as the output, click Convert. Sukat binary-searches the JPEG quality scale for the highest setting that lands under 50 KB — usually in about seven re-encodes. The file saves with a .jpg extension that every Indian recruitment portal accepts. 50 KB out, JPG out, every time.
Quality first, dimensions last
The algorithm reduces JPEG quality before it touches the pixel count. For most ID portraits and recruitment-form photos at 800–1000 pixels on the long edge, 50 KB still fits at the original dimensions. When it cannot, the live preview surfaces the new output size in pixels before download, so you can decide whether to accept the downscale or raise the ceiling slightly.
Honest about the JPG vs WebP gap
At 50 KB, a WebP would hold roughly 25–35% more visible detail than a JPEG of the same image — tighter skin tones, cleaner edges, fewer blocking artefacts around contrast boundaries. Sukat will tell you that if you ask. But the portal you’re uploading to does not care: it wants JPG. So Sukat does JPG, and tunes the quality scale as tightly as the format allows.
HEIC input, JPG output, one click
If the photo came off an iPhone, it is HEIC. Most compressors choke on it or quietly refuse the file. Sukat decodes HEIC in-browser and re-encodes straight to JPEG at the 50 KB ceiling — no separate HEIC-to-JPG conversion step.
EXIF and GPS stripped on re-encode
Re-encoding through the Canvas API drops embedded metadata as a side effect. For a candidate photo headed to a recruitment server, that means no GPS coordinates, no camera serial, no original timestamp leaking out of the file.
Local, no upload, no signup
Compression runs entirely in your browser. The image never leaves the device — useful when the JPG is also a copy of an ID card or marksheet. Verify by switching to airplane mode after the page loads; the tool still works because there is no network call to make.
FAQ
Why JPG and not WebP at 50 KB?
Will my JPG still look acceptable at 50 KB?
What about PNG at 50 KB for the same upload?
Does Sukat keep the original aspect ratio?
Does Sukat actually save the file with a .jpg extension?
.jpg extension and the file’s magic bytes match the JPEG/JFIF standard. That means the upload widget’s MIME-type check passes — the kind of failure where a portal accepts your file at upload but then errors at server-side validation simply does not happen.