What image inspector results mean

The findings that usually explain your problem

Dimensions. The first thing to check against whatever rejected your image. Most upload rules are a minimum, a maximum, or an exact size, and a mismatch here is the single most common cause.

File size. The second. Watch for floors as well as ceilings - some document systems require a minimum, which catches files that were compressed for something else.

Format. What the file really is, read from its bytes rather than its name. An extension mismatch is worth fixing because some systems trust the name and others trust the content.

Transparency. If an image has an alpha channel and you convert it to JPEG, the transparent areas become solid. That explains most "why is there a white box behind my logo" questions.

The findings that are usually just facts

Interlaced or progressive. How the image loads - in passes rather than top to bottom. For JPEG it is usually slightly smaller and looks better on a slow connection; for PNG it usually makes the file a little larger. Neither is a problem.

Colour model and bit depth. Almost never the cause of anything, unless a printer or a specific system asked for a profile.

Megapixels and aspect ratio. Descriptive. The ratio matters when something will crop your image, which is worth knowing in advance rather than discovering afterwards.

Metadata is a different category

It is not about quality at all. Metadata is what the file records beside the picture: camera, settings, timestamp, editing software, and often the coordinates where the photograph was taken.

None of it affects how the image looks or whether it uploads. It matters when you are about to publish the file somewhere, and the field that matters most is location - it can be accurate enough to be a street address. Removing it deletes the fields and changes nothing about what the picture itself shows, which is a distinction worth holding onto.

From finding to fix

A diagnostic is only useful if it leads somewhere. Each finding has a fix, and they are not interchangeable:

1. 1Too large in bytes - compress, which trades quality for size and shows you the trade before you accept it.
2. 2Too large in pixels - resize, which usually saves more than compression and costs nothing visible on screen.
3. 3Nearly a standard size - resize to the exact one. A 1918 x 1080 file is not oversized, it is two pixels short of what something is about to demand.
4. 4Wrong format, or a name that disagrees with the contents - convert, which writes a file whose name and bytes agree.
5. 5Transparency you need to keep - convert to PNG or WebP rather than JPEG.
6. 6Animated - use the animation tools, which work frame by frame instead of flattening to the first one.
7. 7Location recorded - remove it, and then consider what the picture itself shows.

Frequently asked questions

Why does the inspector say my file is not the format its name claims?

Because it reads the first bytes of the file rather than trusting the extension. A file renamed from .png to .jpg is still a PNG inside, and systems disagree about which to believe - some read the name, some read the contents. Converting properly makes the two agree.

Should I worry about a progressive or interlaced image?

Almost never. It describes how the image paints as it loads rather than anything about quality. A progressive JPEG is usually a slightly smaller file and looks better on a slow connection; an interlaced PNG is usually slightly larger. Neither will cause an upload to fail.

Does the inspector change or upload my image?

Neither. It reads the file in your browser to describe it, produces nothing, and sends nothing. That is also why it can describe formats your browser cannot display - it is reading the header rather than decoding the picture.