Exam photo resizer — starting presets

Recruitment applications can have different requirements for file format, pixel dimensions, file size and appearance. These may change between cycles.

Some recent RRB and SSC notices require a live photo in the official application. A resized file cannot replace a required live capture.

Use a preset only when the relevant application explicitly asks for an existing image, and compare every value with the latest official notification.

Specification failures cost candidates entire application cycles. The portal names neither the pixel size nor the byte window when it rejects a photograph, so the only reliable route is to produce a file that is unambiguously inside the spec before you start.

The numbers are recorded here with their source and revision date because boards change them between cycles. Where a specification is our transcription rather than an official figure, the page says so.

Keeping the specification out of the user's hands is deliberate: you should not need to know what a 1:1.29 aspect ratio is to apply for a job. The pipeline applies it and explains what it did afterwards.

This tool exists for examination photographs and signatures handled in a hurry: no queue, no account, no upload, and a result you can verify on the spot. The explanation below is the same one we would give a colleague who asked how it works.

Boards and commissions revise photograph and signature requirements between cycles. Presets are independent starting references, not a substitute for the official notification. Confirm the current file format, dimensions, size and any live-capture rules with the issuing authority.

Applications usually need two or three separate files per person — a photograph, a signature, and on some portals a thumb impression or a handwritten declaration — and each has its own window. Keep every exported file named clearly for the exam it belongs to. When a portal lets you re-upload before the fee is paid, having the correctly-sized file already on your device turns a rejected upload into a two-minute correction rather than a fresh scramble.

Accepted inputs are JPEG, PNG, WebP, AVIF, HEIC, GIF and BMP images up to 50 MB each. SVG, HTML and other script-bearing formats are refused outright rather than sanitised, because a file that can execute code has no business being re-encoded — and an upload field that accepts one is a security hole rather than a feature. The tool works on one file at a time, which keeps the result unambiguous.

The resizer centre-crops to the preset pixel box and searches compression quality without silently shrinking that box. If it cannot meet the byte cap at those dimensions, it reports the miss. The image is processed in your browser. The pipeline is deterministic and ordered: decode while honouring the EXIF orientation tag, centre-crop to the mandated aspect ratio, resample to the exact pixel box with progressive halving to avoid aliasing, composite onto the required background colour so transparency never renders black, then search the encoder quality inside the byte window. Where a portal enforces a minimum size a clean signature cannot reach naturally, spec-legal inert bytes are added — a JPEG comment segment or a PNG text chunk, both of which decoders skip. Not one pixel is altered by that step. Photo presets fit the selected pixel box; signature presets preserve the whole mark with padding where needed. Transparent areas can be flattened onto white, but the tool does not remove an existing background. A byte window may be impossible, so check the result card and the official instructions.