FitMyPic

Inspection tool

Image size checker β€” the real numbers, straight from the file

File managers guess: they report dimensions from a metadata field that is often stale, and formats from the file extension, which anyone can rename. This tool decodes the image in your browser and reports what is actually inside β€” dimensions, pixel count, true format, measured size, and how efficiently those bytes are spent.

Why measure

Reported values lie in specific, predictable ways

01

Extensions are decorative

Renaming photo.webp to photo.jpg changes nothing inside the file, yet every file manager now displays the wrong format. Byte-level sniffing β€” checking the file's magic numbers β€” reports what the container really is.

02

Stale metadata

Some tools write the original dimensions into the image header and never update it after a crop. Decoding the pixels gives the dimensions the image actually has now, not the ones it was born with.

03

Bytes per pixel is the honest size score

A 2 MB photo is not "big" in itself. Divided by its pixels, 2 MB across 12 megapixels is 1.39 bytes per pixel β€” a modest spend. The same 2 MB across 0.3 megapixels would mean an unusually heavy file worth investigating before you upload it anywhere.

Every value in the report above is measured the same way our output testing method measures conversions: from the file bytes themselves, in your browser. When a form or platform quotes limits β€” "at least 600 Γ— 750", "under 2 MB" β€” check the file here first, then adjust it with the compressor and confirm the result here before you submit.

Questions

Checker FAQ

Are my images uploaded?

No. The file is decoded with browser APIs on your device; every reported number is computed locally and nothing is transmitted anywhere.

Why does the format differ from the file extension?

Because the extension is a name and the format is a fact. The checker reads the leading bytes β€” JPEG starts with FF D8, PNG with a fixed 8-byte signature, WebP with RIFF…WEBP β€” so a renamed file is reported as what it truly is.

What is a good bytes-per-pixel value?

It depends on content. Photographs typically land between 0.1 and 2 bytes per pixel; screenshots and flat graphics are often far lower as PNG; anything well above that range usually means the image stores something extra, such as a large colour profile or unstripped metadata.

Can it tell me why my file is too large?

Indirectly. Compare the bytes-per-pixel value against the content: a screenshot or flat-art file showing photo-like numbers is carrying inefficiency, and converting it to the right format (or resizing) is the fix. The image file size guide explains the mechanics.