Skip to content

Exam Photo and Signature Size Rules

SSC, UPSC, IBPS, SBI, RRB, NEET and GATE in one table: pixel dimensions, file size caps and format rules for both photo and signature.

Indian exam portals almost always want a photograph of 200 by 230 pixels at 20 KB to 50 KB, and a signature of 140 by 60 pixels at 10 KB to 20 KB, both in JPG. Those 4 numbers cover the majority of recruitment and admission forms. The exceptions are the national testing bodies, which allow wider ranges and larger files.

Every exam body publishes its own upload rules, the rules change between cycles without notice, and the official instruction sheets sit three clicks deep inside a notification PDF. The table below collects the requirements that appear most often so you can prepare files before starting, rather than after a rejection.

Photo and signature requirements by exam

Check these values against the current year notification before you upload, because caps move between cycles. The figures below reflect the requirements published across recent recruitment and admission rounds.

Exam bodyPhoto pixelsPhoto sizeSignature pixelsSignature size
SSC200 x 23020 KB to 50 KB140 x 6010 KB to 20 KB
UPSC350 x 35020 KB to 300 KB350 x 35020 KB to 300 KB
IBPS200 x 23020 KB to 50 KB140 x 6010 KB to 20 KB
SBI200 x 23020 KB to 50 KB140 x 6010 KB to 20 KB
RRBNot fixed15 KB to 40 KBNot fixed10 KB to 40 KB
NEETNot fixed10 KB to 200 KBNot fixed4 KB to 30 KB
GATEMinimum 480 x 6405 KB to 200 KBNot fixed5 KB to 200 KB

All 7 bodies require JPG. None of them accept HEIC from an iPhone, PNG on the photograph field, or PDF where an image is requested.

The 2 patterns that hold almost everywhere

Photographs run larger than signatures, and both are checked on dimensions as well as file size. A 15 KB image at the wrong pixel size is still refused, because the portal runs the 2 checks separately.

The second pattern concerns shape. A photograph is taller than it is wide, close to a 6 by 7 ratio, while a signature is roughly 3 times wider than tall. Uploading a square crop into either field produces a stretched preview that a verification officer can mark as defective even after the file has been accepted.

Before you start

  • Scan or photograph the signature on plain white paper, not lined, because printed lines cost kilobytes and help nothing.
  • Crop tightly. Whitespace above the head and beside a signature adds file size and removes clarity.
  • Resize first, compress second. Doing it the other way round wastes quality that cannot be recovered.
  • Shoot the photograph against a plain light wall, since busy backgrounds consume compression budget the face needs.
  • Keep the original camera file, because you will need a fresh crop for the next form.

How to prepare both files

To produce an accepted photograph and signature pair, follow these 7 steps.

  1. Open the notification PDF and write down 6 numbers: photo pixels, photo minimum and maximum KB, signature pixels, signature minimum and maximum KB.
  2. Crop the photograph to head and shoulders with a small margin above the hair.
  3. Resize the photograph to the exact pixel dimensions listed, using fill and crop so the numbers match precisely.
  4. Photograph the signature from directly above on unlined white paper, then crop so the ink fills the frame.
  5. Resize the signature to the listed dimensions, usually 140 by 60.
  6. Compress each file to its own KB target, aiming a little under the maximum rather than at it.
  7. Confirm both files are minimum size or larger, since many portals reject files that are too small as well as too large.

The minimum size rule surprises applicants more than the maximum. A signature compressed to 4 KB when the form demands at least 10 KB is rejected, and the fix is to raise quality rather than lower it.

Why the same photo fails on one portal and passes on another

Portals validate different things, and each portal only reports the first failure it finds. One system checks file size before dimensions, another checks the file header first, and a third checks nothing until a human reviews the application weeks later.

That inconsistency explains a common experience: the same photograph is accepted by a state portal in March and refused by a central portal in June. The photograph did not change. The validation order did.

Requirements the tool cannot check for you

Dimensions and file size are technical, while the remaining rules are photographic and have to be right when the picture is taken. No resizer can fix any of the 5 conditions below after the fact.

  • The photograph must be recent, usually taken within the last 3 to 6 months.
  • The face must be uncovered, facing the camera, with both ears visible on most forms.
  • Some bodies require the applicant to hold a placard showing name and the date the photograph was taken.
  • Caps, sunglasses and heavy shadows across the face cause rejection at verification.
  • The background must be plain and light, with white or off white specified most often.

When the notification and the upload page disagree

Follow the upload page, because the validation code sits behind that page rather than behind the PDF. Notifications are written months before the portal opens, and the 2 documents fall out of step more often than either body admits.

Where the 2 sources give different ranges, prepare a file that satisfies both. A photograph at 200 by 230 pixels and 35 KB sits inside a 20 KB to 50 KB range and inside a 30 KB to 100 KB range at the same time. Aiming for the overlap costs nothing and removes the need to guess which document the server actually enforces.

Uploading in the final 48 hours

Prepare every file before the last 2 days, because portals slow down sharply as the deadline approaches. Traffic on recruitment portals concentrates heavily in the closing window, and a slow server turns a 5 MB upload into a timeout.

A 30 KB photograph uploads in a fraction of a second even on a congested server, while a 4 MB camera file may fail repeatedly and give no useful error. Sizing files correctly is partly about passing validation and partly about finishing the upload at all. Keep the finished files in one folder on the device you will use, so no time is lost searching a phone gallery while a session timer runs.

Keeping a reusable set of files

Prepare one master photograph and one master signature at high quality, then export sized copies per exam. Applicants typically fill 4 to 8 forms in a season, and re-cropping from the camera original each time produces inconsistent results across applications.

Keep the master photograph at around 1200 by 1400 pixels and the master signature at around 1400 by 600. Every exam variant can be produced from those 2 files in under a minute. Consistency also matters at document verification, where an officer compares the uploaded photograph against the one on your admit card.

Preparing files for several exams at once

Resize and compress in batches, because the numbers differ per exam while the source files stay the same. Drop the masters in, set the pixel size and KB target for the first exam, download, then repeat with the next set of numbers.

Up to 500 files can be processed in one batch, and everything runs inside your browser rather than on a server. That matters here because an exam photograph and a signature together are enough to impersonate an applicant, and neither file should be sitting in an unknown company log. No upload request is made, so there is nothing stored anywhere to retain or leak.

Store the finished sets in folders named after each exam, holding the photograph, the signature and any thumb impression the body requires. Recruitment cycles repeat annually with the same specifications, so a folder built this season is usually still correct next season. Checking 6 numbers against a fresh notification takes 2 minutes, and it is the only part of the preparation that has to be repeated.

Back to blog