Exam photo size guide

What application portals actually ask for, why they reject a photograph that looks perfectly good, and which setting to change when the result looks soft.

By Chen Lei · Last reviewed 7 October 2026

Read this first. The figures below are the limits applicants meet most often. Requirements change without notice and vary by post, state and year. PhotoZip is independent and not affiliated with any of these bodies. The official notification for your exam is the only authoritative source — these numbers are a starting point for understanding what the form is likely to demand, not a substitute for reading it.

The three limits, and which one you failed

A portal rejection usually says something unhelpful like "invalid photograph". In practice you have failed one of three separate checks, and knowing which one tells you what to change.

1. File size (KB)

Almost always expressed as a range, not a ceiling — commonly 20KB to 50KB for a photograph, 10KB to 20KB for a signature. Both ends are enforced. A 4MB photo from a phone fails the top end; a photo squeezed to 8KB to be "safe" fails the bottom end, and that one surprises people, because the natural instinct is to compress as hard as possible.

Practical consequence: aim for the upper end of the range, not the lower. A photograph at 45KB inside a 20–50KB allowance carries visibly more detail than the same photo at 20KB, and both are equally acceptable to the form.

2. Pixel dimensions

Width × height in pixels, sometimes with a tolerance and sometimes exact. This is a hard requirement and it is independent of the file size: an image can be well under 50KB and still be rejected for being 800×600 when the form wants 200×230.

Practical consequence: if the notification states dimensions, honour them. Compressing a photo that is already the right size works best, because the tool then only has to adjust quality, not reshape the image.

3. Format, orientation and colour

Nearly always JPEG, occasionally with a required DPI value (96 or 300) and a colour photograph requirement. Orientation is the quiet one: on a phone, a "portrait" photo is often stored as a landscape image plus an EXIF orientation tag telling the viewer to rotate it. Browsers and photo apps honour that tag; a portal's server-side validator frequently does not, and rejects the photo as landscape — or worse, accepts it and prints your face sideways on the admit card.

Practical consequence: PhotoZip reads the orientation tag and bakes the rotation into the pixels, so the output is upright regardless of how the tag is treated downstream.

The trap that wastes the most time: live capture

Before you compress anything, work out which of two entirely different things the form is asking for. Many applicants lose an evening to this, because the instructions are easy to misread and the difference is not a matter of degree.

• Live capture. The portal takes the photograph through your webcam or its own mobile app, at the moment you apply. There is no file to prepare and nothing to compress. If the form does this, a resized photo is useless to you — the only thing that matters is your lighting, background and whether your face fits the guide frame.
• File upload. You prepare a JPEG to a stated size range and pixel dimension, and upload it. This is what PhotoZip is for.

SSC has moved its photograph to live capture in recent cycles, through the webcam or the mySSC app, while the signature is still a file you upload. So for an SSC form you may well need this tool for the signature only, and no amount of photo compression will satisfy the photograph field. Reports differ about how completely this has rolled out across SSC examinations, which is exactly why the next section tells you to read your own notification instead of trusting a table — including this one.

Specifications by examination family

How to find the real numbers in two minutes

This is the part worth actually learning, because it works for every exam and survives every format change. Every notification carries the specification in one of a few predictable places.

1. Open the notification PDF for your cycle. Not a blog post, not a preparation site, not this page. The commission's own PDF for the year you are applying. Search the site for "Notice" or "Advertisement" plus the exam name and year.
2. Search the PDF for "KB". Open the file and use your reader's find function. Most readers display a hit count; the relevant section is usually titled Annexure, Instructions for uploading photograph and signature, or Guidelines for scanning and upload of documents.
3. Decide live capture or upload first. If the wording is "the photograph will be captured through webcam" or "using the mobile application", stop — there is no file requirement. Only if it says "upload a scanned photograph" does the size range apply to you.
4. Write down four things: minimum KB, maximum KB, pixel dimensions, and file format. The minimum is the one people miss. If dimensions are given as centimetres ("3.5 × 4.5 cm"), that is a print size — at 200 DPI it is roughly 276 × 354 pixels, and the notification usually states the DPI too.
5. Note anything about background, spectacles and ears. These are enforced by human review at later stages, not by the upload form, and they are the reason a technically valid photo still gets an application rejected months later.

Reading a specification block correctly

A typical block looks something like this, and every clause in it is a separate requirement:

Photograph: JPEG, 20KB to 50KB, 200 x 230 pixels,
            colour, plain light background, taken after [date]
Signature:  JPEG, 10KB to 20KB, 140 x 60 pixels,
            black ink on white paper

• JPEG is the format. A PNG renamed to .jpg is not a JPEG.
• 20KB to 50KB is a window, not a ceiling. Landing at 45KB keeps more of your photograph than landing at 21KB, and both are equally valid.
• 200 × 230 pixels is independent of the file size. A photo can be inside the KB window and still rejected for being the wrong shape.
• Taken after [date] is a recency rule. An older photograph is a common cause of rejection at document-verification stage, long after the upload succeeded.

How to hit an exact size

1. Find both numbers. The maximum and the minimum, plus the pixel dimensions if they are stated. The minimum is the one people miss.
2. Compress to the top of the range. If the limit is 20–50KB, target 50KB, and check the result is above 20KB. PhotoZip reports the exact output size for each file, so you can see both at once.
3. Check the dimensions before you upload. The tool shows the output pixel size next to each file. If the portal wants 200×230 and you got 1600×1200, resize first and compress again.
4. If it looks soft, change one setting. See below.

If your result is smaller than the portal's minimum

This is the failure people do not see coming, because the instinct is to compress as hard as possible. If the form says 20KB–50KB, a 9KB file is rejected just as firmly as a 5MB one.

PhotoZip is built to respect the ceiling, so it will not push you over the maximum. But it cannot invent detail to reach a floor: the output size is bounded by the source you gave it. If a 200×230 pixel photograph compresses to 9KB at maximum quality, 9KB is genuinely all the detail that image contains, and no tool can honestly produce a 20KB version without padding it with useless data.

What that tells you is that the source is too small, not that you compressed too hard. The fix is to go back to the original file:

• Use the photograph straight from the camera or phone, not one that has already been sent through WhatsApp, a screenshot, or a previous application form. Messaging apps recompress images aggressively, and that loss is permanent.
• Check that the original is comfortably larger than the required pixel dimensions — 1200×1500 pixels or more for a 200×230 requirement. There is then plenty to compress down, and the output will land near the top of the range.
• If the original is gone, the honest answer is that you need a new photograph. A signal that reaches for "add a bit of noise to inflate the file" produces a larger file containing no more of your face, and some portals check for exactly that.

The line PhotoZip shows next to each file is the size actually produced. If it is under your portal's minimum, that is the diagnostic, and it is a statement about your source rather than a bug.

Why the result looks soft, and what to change

To fit a small limit into a large photograph, something has to give. There are only two things to spend: JPEG quality and pixel dimensions. Spending too much of either produces a bad result, but differently:

• Quality spent too far produces blocky, patchy artefacts — visible 8×8 squares, smeared colour, ringing around edges. This is the classic "over-compressed JPEG" look.
• Dimensions spent too far produces a clean but small image that simply cannot show fine detail.

For a photograph that will be viewed at thumbnail size on a form, spending dimensions is usually the better trade: a clean 400×500 image reads better than a heavily blocky 1600×1200 one. That is the default behaviour in this tool. If your portal demands large dimensions and a small file — 1600×1200 inside 50KB, say — the "Keep more pixels" setting allows a lower quality to reach it. The result will be visibly more compressed; that is unavoidable, and the notification is asking for something close to the limit of what JPEG can do.

Common questions

Found a figure here that is wrong for an exam you applied to? Tell me — corrections from people who have actually submitted the form are the most useful feedback this site gets.