Image Width and Height Validator - (4 format)

What the image validator does

This page checks one image against a preset or a rule you define. You choose an exam, a document type and a variant, upload a file, and the page reports whether the dimensions, file size and format match. It does not crop, compress or convert the image; it only tells you what is wrong.

The check runs in two stages. A browser pre-check reads the file locally and compares it with the selected rule. A cloud check sends the file to the server and returns the final result. The page labels the browser stage as a pre-check because the server is the final authority.

Choosing a preset

The exam list is loaded from the application. Pick an exam, then a type such as photo, signature or document, then a variant if the exam offers more than one size. The panel shows the expected width, height, file-size range, format and minimum DPI for that variant.

Presets come from the site's private rule data. Coverage is not universal: an exam may have one variant, several variants, or no usable entry. If the list does not contain the form you are using, switch to the custom rule and enter the figures from the form yourself.

Building a custom rule

Custom mode lets you set a target width and height, a tolerance from 0 to 20 percent, a minimum and maximum file size in KB or MB, and an allowed format. The tolerance creates a range around the target, so a 100-pixel target with 10 percent tolerance accepts 90 to 110 pixels.

Use zero tolerance when the portal demands exact pixels. Use a small tolerance only when the form itself allows a range. The custom rule is not saved; it applies to the current check and disappears when you reload the page.

What each check means

Dimensions compares the image's natural width and height with the rule. A file can look correct in a preview and still be 299 by 300 pixels. The result table shows the required value, the actual value and a pass or fail badge.

File size compares the bytes on disk with the minimum and maximum. Some forms reject a file that is too small as well as one that is too large, so a heavily compressed image can fail even when its dimensions are right.

Format checks the real file extension and type, not just the name. Renaming a PNG to .jpg does not make it a JPEG. DPI is compared when the preset specifies a minimum; DPI is metadata and does not change the pixel dimensions.

Reading the result

A green pass means that check matched the rule. A red fail names the required and actual values. An info row explains a check that could not be decided, such as a missing DPI field or a browser limitation. Read every row, not only the overall badge.

The preview thumbnail and metadata line show the file size and the dimensions the browser read. If the thumbnail is blank, the file may be corrupt or use a format the browser cannot decode; the cloud check may still reject it.

Common failures

The usual cause is a crop that is one or two pixels off, often from a resizer that rounds a ratio. The second is a file saved at high quality that exceeds the KB ceiling. The third is a screenshot or phone photo saved as PNG when the form wants JPEG.

A fourth cause is the wrong variant: a photo rule used for a signature, or a 3.5 by 4.5 cm rule used for a 100 by 130 pixel form. Check the label, not just the exam name. A fifth is a stale preset; if the official form has changed, the preset may no longer match it, and the form is the authority.

Limits and privacy

The tool checks one image per run. It does not batch validate, repair, resize or return a corrected file. The browser pre-check is fast but incomplete, and the cloud result depends on the server being reachable.

The selected file is sent to the server for the final check. Do not upload identity documents, signatures or private photos to a public tool unless you are comfortable with that. The page does not offer a local-only cloud check. It also keeps no gallery, so download the result before closing the tab or reloading.

Why validate before uploading

Application portals often accept the rest of the form and then reject the photo at the final submit. Re-uploading means finding the file again, reopening the editor and repeating the check. A quick validation pass catches the common mismatch before you reach that step.

A pass here is not a guarantee of acceptance. The portal may apply its own hidden rules, a different DPI interpretation or a manual review. Use the result to remove obvious errors, then trust the portal message over any third-party checker.

Checking DPI and physical units

Some presets are written in centimetres or inches with a minimum DPI, not in pixels. The tool converts the physical size and DPI into an expected pixel range. A 3.5 by 4.5 cm photo at 200 DPI is roughly 276 by 354 pixels; a 2 by 2 inch photo at 96 DPI is 192 by 192 pixels.

Browsers do not read DPI metadata consistently, so the local pre-check may skip it while the cloud check can still inspect it. If the form gives physical dimensions, calculate the pixels first and use a custom rule with zero tolerance. If it gives pixels, do not add DPI guesswork. Save the corrected file with a clear name such as photo-100x130.jpg so the next upload is easy to identify, and avoid overwriting the original.

How the validator looks

The screenshots below show the exam selector, the rule panel, an upload and a result table. They are illustrative; the exact exams and variants depend on the current rule data.

Frequently Asked Questions