How we verify requirements.

Where the numbers come from

Only from the organisation's own documents: its notification, its application guidelines, its official site. Never from coaching sites, videos, forums or other resizer tools, however popular. We note the document, its publication date when it has one, and the date we read it.

Three kinds of rule

• Required. The notice states it as a firm rule, such as “JPEG” or “10 to 20 KB”. A file that breaks it is not ready.
• Preferred. The notice says “preferred” or “about”, like IBPS's 200 × 230 px. We match it, and show it separately, but it doesn't decide whether a file is ready.
• You check. Ink colour, capital letters, how much of the frame your face fills, whether a photo is recent. A computer can't judge these from a file, so we list them for you and never tick them for you.

What “Ready to upload” means

We show it only when the finished file, re-read from its actual bytes, passes every required rule we can check by machine. Not the preferred rules, and not the checklist. It means “this file meets the stated numbers”. It does not mean a portal will accept it: portals change, and some check things we can't see.

File sizes: 1 KB is not always 1,024 bytes

Some portals count 1 KB as 1,000 bytes and some as 1,024. So we aim for the part that is safe under both: above the minimum × 1,024 and below the maximum × 1,000. And we don't aim for the edge. For a 20–50 KB rule we land well inside, around 24–46 KB.

When sources disagree

Sometimes the organisation's own documents disagree, or common advice contradicts the notice. We show the conflict on the page. If we can't settle it from official documents, we don't publish a preset until we can. That is why some well-known exams are missing from the list.

Staying current

Every set of requirements carries a cycle and a “last verified” date. We never reuse one for a new cycle. If a set has not been re-checked within 90 days, or is marked outdated, the page says “Needs re-check” and tells you to read the notification yourself.

After you download a file we ask whether the portal accepted it. A run of “No” answers is how we learn that a requirement has changed.