How to use this tool
- Choose a static JPEG, PNG or WebP.
- Inspect its pixel dimensions, detected format and byte counts.
- Use the related resizer or converter only if a requirement is not met.
What the inspector reports
Pixel dimensions (width × height) from the decoded image with display orientation applied. File bytes from the selected file on disk. Decimal KB = bytes ÷ 1,000; binary KiB = bytes ÷ 1,024. Aspect ratio reduced by the greatest common divisor (400×300 → 4:3). Detected format from the file header, which may differ from the filename extension. Transparency whether any pixel has alpha below opaque.
Why bytes and pixels are separate questions
An upload form may cap format, dimensions and file size independently. A 400 × 300 plain-colour logo and a detailed photograph at the same dimensions can differ by an order of magnitude in bytes. Pixel dimensions do not predict compressed size; complexity, encoder and metadata do.
400 × 300 · 204,800 bytes → 4:3 · 204.8 KB decimal · 200 KiB binary
“200 KB” on a form often means 200,000 bytes. 200 KiB is 204,800 bytes and would exceed that cap. Read the requirement in the same units the form uses, then compress accordingly.
Inspect before you edit
Workflow: inspect → resize if dimensions must change (Resizer) → convert if format must change (Converter) → compress toward a byte target (Compressor) → re-inspect the download. Each step can change bytes; only the final inspector reading is authoritative for the file you will submit.
The built-in sample is a generated coloured graphic; its exact encoded size varies by browser. Guide: Image pixels, file size and formats explained.
What the inspector does not do
It does not enumerate EXIF tags, prove that GPS metadata is absent, validate colour profiles for print, or guarantee that a destination will accept the file. DPI/print-resolution tags are separate from screen pixel dimensions and are not changed here.
A worked example
400 × 300 pixels; 204,800 bytes
Aspect ratio 4:3; decimal size 204.8 KB; binary size 200 KiB.
Pixel dimensions do not predict compressed size. The detected container may differ from a filename extension. This inspector does not enumerate EXIF tags or establish that GPS metadata is absent.
Dimensions, bytes and transparency
The inspector reports the decoded pixel width and height, the encoded file size, the format and whether the image has an alpha channel. Aspect ratio is derived from the actual pixels, not from a filename or a thumbnail. Header checks reject unknown, empty or oversized files before a full decode.
A file byte size on disk may use decimal kilobytes (1 KB = 1,000 bytes) or binary kibibytes (1 KiB = 1,024 bytes). An upload form that says KB may mean either. Compare the number the tool reports with the form stated unit before deciding that an image is under the limit.
What the inspector cannot tell you
It does not judge visual quality, copyright, metadata privacy or whether the content is appropriate for a destination. It does not verify that a JPEG is undamaged beyond what the decoder can read, and it does not convert or compress. Use it to identify the binding constraint, then edit with the matching tool.
If the dimensions are within limits but the file is too large, compress. If the bytes are fine but the dimensions are too large, resize. If both are binding, resize first, then compress the resized result.
Processing and privacy
Image Inspector reads dimensions and headers locally; the image file is not uploaded for analysis. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.
Frequently asked questions
Does DPI determine screen dimensions?
Screen pixel dimensions come from width and height. A print-resolution tag is a separate concern and is not changed by this inspector.
Why do KB and KiB differ?
KB uses 1,000 bytes per unit; KiB uses 1,024. Upload forms often mean decimal KB—check the form’s wording.
Can the detected format differ from the extension?
Yes. The inspector reads the file header. A .png that is really a JPEG is reported as JPEG.
Does it check whether the image is “good enough”?
No. It reports objective metrics only. Quality judgments are yours or the destination’s.
Is a sample image uploaded?
No. Everything is decoded locally in the browser.
Does inspecting an image modify it?
No. The tool reads the selected file to report its properties and does not overwrite or upload it.
Why does the byte size differ from my file manager?
The file manager may use binary units or show a different rounded value. Compare the exact bytes and the unit the destination requires.
How this tool was checked
Image Inspector was checked with progressive JPEGs, transparent PNGs, WebP files, one-pixel images, corrupt headers and dimensions near the 16-megapixel limit. See the testing method or report a failure.