Voter ID Photo Resizer — exact pixels, KB window and no upload

Document uploads fail for mundane reasons: the photograph is a portrait when the portal expects a square, the signature is below a minimum byte floor, or a helpful website copied a specification from a different portal generation. This tool makes the variant explicit before processing, then reports the exact dimensions and final byte size afterwards.

These are identity images. A PAN photograph, Aadhaar photograph or bank signature should not be sent to an unknown server merely to change its dimensions. The file is decoded and re-encoded in this browser tab; closing the tab discards the working copy.

Where public sources disagree, the page says so. That honesty is a feature: a confident but wrong pixel box is worse than a clearly labelled cross-checked preset and a reminder to compare the live form before final submission.

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 identity documents and application forms 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.

Signatures are not decorative images. Banks and licensing authorities compare them as behavioural marks, so consistency matters more than neatness. Sign normally, on unlined paper, with the pen you would use on the form itself; a signature redrawn slowly for the camera often looks least like the one on record.

The safest application habit is boring but effective: keep one folder per application, name files with the document and variant, and retain the untouched original. Portals time out, browsers close and verification stages ask for the same image again. A clearly named exported file turns each of those moments into a search rather than a reconstruction.

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 selected variant drives a deterministic pipeline: decode the source, centre-crop to the target aspect ratio, resample to the exact pixel dimensions, composite onto the stated background and search encoder quality until the result lands inside the KB window. Where a minimum size cannot be reached naturally by a clean signature, standards-compliant inert padding can raise the byte count without changing pixels. The result card states whether the final file is inside the window. 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. The document pipeline makes its provenance visible: the selected authority variant fixes dimensions and byte limits before any pixels are processed. That separation matters because resizing is deterministic, while specifications change. If a portal revises its field, only the record needs correction; the image engine remains the same.