Photo and signature size rules for Indian exam forms (and how to hit them exactly)

SSC, IBPS, RRB, UPSC and state PSC portals each want a photo and signature at fixed pixels and a fixed KB band. Here are the actual numbers, the real reasons uploads get rejected, and the order of steps that gets it right on the first try.

Almost every Indian recruitment portal asks for the same two files: a colour passport-style photograph as a JPEG of 20 KB to 50 KB, and a signature scan as a JPEG of 10 KB to 20 KB, both at fixed pixel dimensions on a plain white background. IBPS wants 200x230 pixels for the photo and 140x60 for the signature. RRB runs tighter at 15 KB to 40 KB. UPSC accepts files up to 300 KB. The order you do the work in matters more than the tool you use, and that is what most guides get wrong.

The specs, portal by portal

These are the bands published in recent notifications. Exam bodies change them between cycles, so read this as the shape of the requirement and confirm the digits in the notice PDF for your exam.

Portal Photo dimensions Photo size Signature dimensions Signature size Format
IBPS (PO, Clerk, SO) 200 x 230 px 20–50 KB 140 x 60 px 10–20 KB JPEG
SSC (CGL, CHSL, MTS) 3.5 x 4.5 cm 20–50 KB 4.0 x 2.0 cm 10–20 KB JPEG
RRB (NTPC, ALP, Group D) 35 x 45 mm 15–40 KB not always separate 10–40 KB JPEG
UPSC (OTR, Civil Services) 350 x 350 to 1000 x 1000 px 20–300 KB 350 x 350 to 1000 x 1000 px 20–300 KB JPG
State PSC (UPPSC, BPSC, MPSC) usually 200 x 230 px 20–50 KB usually 140 x 60 px 5–20 KB JPEG
IBPS extras thumb 240 x 240 px, declaration 800 x 400 px 20–50 KB / 50–100 KB — — JPEG

Two things stand out. Nobody accepts PNG: the whitelist is JPEG, occasionally spelled JPG, and the extension usually has to match it exactly. And most bands have a minimum as well as a maximum, which is the one that catches people out. A 200x230 pixel photo at 90 percent JPEG quality often lands around 12 KB to 18 KB, under the 20 KB floor, so you have to make the file bigger rather than smaller.

IBPS also asks for a left thumb impression and a handwritten declaration as separate images, each with its own pixel size and KB band. Those two get forgotten until the upload screen refuses to move on.

Why the upload fails even when the size looks right

The validator on the other side is a short script, and it is strict about things that look invisible to you.

  • The file is not really a JPEG. Renaming photo.png to photo.jpg fools Windows, not the server. Most portals read the first few bytes of the file, and a PNG header inside a .jpg name fails immediately. Convert properly with PNG to JPG instead of renaming.
  • EXIF rotation. Your phone stores the photo sideways with a "rotate me" tag. Your gallery obeys the tag, the portal often does not, so a photo that is upright on your laptop lies on its side in the preview box. The Rotate & Flip tool bakes the corrected orientation into the pixels.
  • Dimensions off by a pixel or two. A form that wants 200x230 usually accepts a small tolerance, but some state portals compare exactly. Type the numbers, do not eyeball a drag handle.
  • Background is not white. A cream wall, a beige curtain or a shadow behind the head reads as "not a plain background" to a human verifier at the document check stage, even after the file uploads fine. Rejection then comes weeks later.
  • CMYK JPEG. Some older upload widgets only decode baseline RGB JPEG, so anything saved out of a print workflow is refused with a generic "invalid image" message.
  • File name. Spaces, brackets, Hindi characters and a second dot break more upload widgets than they should. Use photo.jpg and sign.jpg.

The error text is rarely helpful. "Please upload photograph in correct format" covers every one of those.

The order that works

Do these in sequence. Skipping to the compressor first is the usual mistake, because compressing and then cropping throws away the compression work.

  1. Start from the largest original you have. The camera file, not the WhatsApp copy, which is already compressed to roughly 100 KB and softer than it looks on a phone screen.
  2. Crop to the right shape. Open Crop Image, set the aspect ratio to Passport 35:45, and place the box so head and shoulders fill it with a small margin above the hair. Front-facing, eyes open, no cap, no dark glasses. Drag the corner handles, or type exact X, Y, width and height. Save as JPG.
  3. Set the exact pixel size. Open the Image Resizer and pick the preset your form wants, or type the numbers with Lock ratio on. The presets include 200x230 for SSC and IBPS style forms, 413x531 for a 35x45 mm passport photo, and 140x60 for a signature strip.
  4. Hit the KB band. Open Reduce Image Size in KB, type the maximum from the notification (50 if the band is 20 to 50), keep the output on JPG, and click Reduce size. The tool searches for the highest JPEG quality that still fits under your number, and only shrinks pixel dimensions if quality alone cannot get there. The note next to the download shows the final KB, width and height.
  5. Check the floor. If step 4 lands you under the minimum, send the file through Increase Image Size in KB with the minimum as your target. It re-encodes at full quality and pads the file with JPEG comment blocks that viewers ignore, so the picture does not change and the byte count does.
  6. Repeat for the signature. Sign in black or dark blue ink on unlined white paper, photograph it in daylight, crop tight to the strokes with a roughly 7:3 box, resize to 140x60, then reduce to 20 KB.

One honest caveat about step 4. If the reducer had to shrink the dimensions to meet a very tight limit, you have broken the dimension rule to satisfy the KB rule. That only happens on large targets such as UPSC's 1000x1000 at a low cap. At 200x230 pixels there is no conflict: 46,000 pixels of JPEG cannot reach 50 KB unless you push quality to the maximum.

The DPI myth

You will read that a form needs "300 DPI". No upload validator can check DPI meaningfully, because DPI is a number in the file's metadata that says nothing about the image data. The same 200x230 pixel photo tagged 72 DPI and tagged 300 DPI is identical in the part that matters, and both pass or both fail.

DPI only becomes real when a physical size is involved, which is how a notification written in centimetres converts to pixels:

  • 35 x 45 mm at 300 DPI is 413 x 531 pixels
  • 35 x 45 mm at 200 DPI is 276 x 354 pixels
  • 4.0 x 2.0 cm signature at 300 DPI is 472 x 236 pixels

So when SSC says 3.5 x 4.5 cm, produce 413x531 pixels and stop thinking about DPI. If a form gives both a centimetre size and a pixel size and they disagree, the pixel size is the one the script checks.

Keeping the face sharp at 20 KB

Quality at small file sizes is mostly decided before compression, not during it.

Crop tight. Every pixel of wall behind you is a pixel of your budget spent on nothing. A crop that puts the face across 70 percent of the frame gives the encoder far less to describe than a half-length shot, so the same 30 KB buys more detail where it counts.

Do not save three times. Each JPEG save re-quantises the image, and save-crop-save leaves visible mush around the eyes and hairline. Go original, crop once, resize once, compress once.

Photograph against a genuinely plain white wall in indirect daylight, facing a window. Flash creates a hard shadow behind the head that survives every amount of compression, and it is a common reason for rejection at document verification rather than at upload.

Do not upscale. A 300x300 crop stretched to 413x531 stays soft, and JPEG then spends bytes encoding blur.

Before you hit upload

  • Format is JPEG, produced by a converter, not a rename
  • Pixel width and height match the notification exactly
  • File size is inside the band, both ends
  • Photo is upright in the portal's own preview, not just in your gallery
  • Background is white, face is unobstructed, ink is dark on the signature
  • File names are simple: photo.jpg, sign.jpg
  • You kept the full-size originals, because the next form will want different numbers

Everything above runs inside your browser, so the photo, the signature and any ID scan stay on your own device. That matters more here than on most tools, since these are exactly the files people are told not to email around.

Frequently asked questions

My form wants 20 KB to 50 KB. What number do I type into the reducer? Type 50. The result lands at or just under 50 KB, which satisfies the maximum, and for a 200x230 photo it will usually clear 20 KB as well. If it comes out at 14 KB, run it through the increase tool with 20 KB as the target.

Can I use my Aadhaar or PAN card photo? No. These portals want a recent photograph, and SSC and RRB notices generally specify one taken within the last three months, sometimes with a date placard. A scan of a card photo is low resolution, often has a printed border and a card texture, and is rejected at verification.

Is a photo taken on a phone acceptable? Yes, and it is what most candidates use. Any phone from the last few years has far more resolution than 413x531 pixels needs. The failures come from background, lighting and rotation, not from the camera.

What if the portal accepts my photo but I am told later it was wrong? Upload validation checks bytes, dimensions and format. Human verification checks the background, the recency and whether the signature matches your other documents. Passing the first says nothing about the second, so read the photograph clause in the notification, not just the file specs.

B

Written by Bablu Kumar Jha

Founder, BeeProton AI · Mumbai, Maharashtra, India

Related posts