Image Info

What is an image info inspector?#

Drop an image onto this page and it tells you everything the browser can determine about the file without sending it anywhere: the filename, IANA media type, byte size, pixel dimensions, aspect ratio (both as a reduced fraction and a decimal), total megapixels, and the last-modified timestamp. It is the quick “what exactly is this file?” check you reach for before uploading, embedding, or debugging a layout that breaks because an image is the wrong shape.

Two things in this tool deserve explanation. First, sizes are reported in IEC binary units (KiB, MiB) on a 1024 base, not decimal SI units (KB, MB) on a 1000 base — the same convention used throughout this tool suite, and the one storage and memory actually use. Second, the aspect ratio is reduced to its smallest integer form via a greatest-common-divisor pass, so 1920×1080 reports 16:9 rather than 1920:1080, and the decimal 1.78 is given alongside for CSS aspect-ratio use.

Dimensions come from the image’s naturalWidth and naturalHeight — the true pixel size of the decoded bitmap, not the CSS display size — so a thumbnail stretched to 100% width still reports its real source resolution.

How to use it#

1. Drop an image onto the dashed zone (or click it to open the file picker).
2. Read the results in the table:
   • Filename — the original file name.
   • Type — the detected MIME, for example image/png.
   • Size — bytes plus a human-readable IEC label, for example 2.4 MiB.
   • Dimensions — WxH in true pixels.
   • Aspect — reduced ratio and decimal.
   • Megapixels — total pixel count in millions.
   • Last modified — the file’s stored timestamp.

There is no upload step and no “submit” button — the moment the file is dropped, the page decodes it in-memory and fills the table. Drop another file to inspect it instead.

Key features#

• True source dimensions. Reads naturalWidth/naturalHeight, so CSS scaling cannot fool it.
• Reduced aspect ratios. A GCD pass collapses 3840×2160 to 16:9, 4032×3024 to 4:3 — the form you actually use in CSS and design tools.
• IEC byte units. Consistent KiB/MiB labelling; files smaller than 1 KiB report in plain bytes.
• Megapixel total. Useful for comparing sensor resolution and estimating memory footprint.
• Nothing leaves the page. The image is read with the in-browser File and Image APIs; no network request, no server storage.

Worked example#

Drop a phone photo named IMG_2026.jpg. The table reports:

That single read tells you the photo is a 12 MP 4:3 JPEG weighing just under 4 MiB — exactly what you need to decide whether to compress it before attaching to an email, and to set aspect-ratio: 4 / 3 on its container so the layout does not jump when it loads.

A 1920×1080 screenshot, by contrast, reports 16:9, 2.07 MP; a 512×512 icon reports 1:1, 0.26 MP.

FAQ#

Why KiB and not KB?#

IEC binary units (KiB = 1024 bytes) match how memory and storage are actually addressed; decimal SI units (KB = 1000 bytes) are what drive manufacturers use for marketing. This suite uses IEC everywhere to avoid the persistent 7% gap between the two.

The aspect ratio doesn’t match the common 16:9 or 4:3 — why?#

Because the image genuinely isn’t a standard ratio. The tool reduces to the true lowest terms: 1600×900 is 16:9, but 1600×899 is 1600:899 since 899 is prime. A slightly-off ratio usually means the source was cropped or resampled to an unusual size.

Does it read EXIF metadata?#

No — that is a separate concern. Use the EXIF tool for camera make and model, GPS, exposure and other embedded metadata. This page reports only the file-level and pixel-level facts.

Can it inspect an image without a file?#

If you have a data URL or pasted base64, convert it to a file first with the Base64 tool, then drop it here.