How do I check an image's real format?

Drop the file above. The tool reads the first bytes of the file, which every format stamps with a unique signature, and reports the true type. It then compares that to the file's extension and flags any mismatch. Everything runs in your browser, with no upload.

Why doesn't the file extension tell me the format?

An extension is just the end of the name, and anyone can rename a file. A .png that is really a JPEG, or a screenshot saved with the wrong extension, is common. The actual format is decided by the bytes inside the file, which is what this checker reads, so it cannot be fooled by a renamed extension.

My file is .jfif. Is that a real format?

A .jfif file is simply a JPEG with a different extension; the bytes are identical to a normal JPEG. The checker confirms this, so you do not need to convert it. If a form rejects the .jfif name, you can rename it to .jpg, but the data is already JPEG.

What does a format mismatch mean for me?

It usually explains why a file will not open or upload. A program expecting a real PNG may refuse a JPEG that was simply renamed .png. Renaming does not convert a file, so the fix is to run it through an actual converter rather than changing the extension again.

Which formats can it identify?

It recognises the common image formats by their signatures: JPEG, PNG, WebP, GIF, BMP, TIFF, AVIF and HEIC. If the bytes do not match any of these, it reports that the file is not a recognised image rather than guessing.

Is my file uploaded to check it?

No. Only the first few bytes are read, and they are read in your browser. Nothing is sent to a server, so the check is instant and private.

Image Format Checker

Image format checker

Drop a file to find out what image format it really is. The tool reads the file's own bytes, not its extension, to identify the true type and flag a renamed or wrong suffix. It runs in your browser, so nothing is uploaded.

Files never leave your device
Runs in your browser
Free, no signup

How it works

1
Drop a file
Add any image. Only its first bytes are read, in your browser, to identify the format. There is no upload.
2
Read the true format
See what the file actually is, decided by its signature, alongside its extension and the browser's reported type.
3
Spot a mismatch
If the bytes and the extension disagree, the tool says so, which usually explains why a file would not open or upload.

What the format checker shows

Reads bytes, not the name

The format is identified from the file's signature, so a renamed file cannot fool it. A JPEG called .png is reported as JPEG.

Explains upload failures

A wrong extension is a common reason a file is rejected or will not open. Seeing the real type next to the name pinpoints the cause.

Instant and private

Only the first few bytes are read, in your browser. Nothing is uploaded, so the check is immediate and stays on your device.

Where this helps

Troubleshooting

A file that will not open

When an image refuses to open, check whether its real format matches its name. A renamed file is a frequent and easily fixed cause.

Forms

An upload that keeps failing

A portal expecting a real PNG may reject a renamed JPEG. Confirm the true format before you keep retrying the upload.

Downloads

Sorting out a .jfif download

A .jfif file is just a JPEG. The checker confirms it, so you know whether a rename is enough or a real conversion is needed.

Workflow

Verifying a batch of files

When images come from mixed sources, check that each one's contents match its extension before you process the set.

Tips that help

1
Renaming is not converting
Changing the extension relabels a file but leaves its bytes unchanged. To truly change the format, re-encode it with a converter.
2
Trust the bytes
When the extension and the real format disagree, the bytes are the truth. The signature is part of the file and does not change on rename.
3
.jfif is just JPEG
A .jfif download is a normal JPEG. If a form is fussy about the name, rename it to .jpg, but the data is already correct.
4
Match the format to the requirement
If a system genuinely needs a different format, convert it. Confirming the real type first tells you whether a rename or a conversion is the fix.

What format is this image, really? Reading the bytes, not the extension

The extension on an image file is a label, not proof. Files get renamed, downloaded with the wrong suffix, or saved by apps that disagree about what to call them, and the result is an image whose name and contents do not match. That mismatch is behind a surprising number of 'this file won't open' and 'the upload was rejected' problems. This guide explains how a file's true format is actually determined and what to do when the label is wrong.

The extension is a label anyone can change

An extension like .jpg or .png is just text at the end of the filename. Renaming a file changes that text but touches none of the data inside, so a JPEG renamed to photo.png is still a JPEG byte for byte; only its label lies.

This happens more than people expect. A browser saves an image with the wrong suffix, a chat app strips the real extension, or someone renames a file hoping to change its type. In every case the name now disagrees with the contents.

Software, on the other hand, reads the contents. That is why a renamed file so often fails to open or upload: the program looks at the bytes, sees a format it was not expecting under that name, and refuses it.

How the true format is read

Every image format begins with a signature, a short fixed sequence of bytes at the very start of the file, sometimes called a magic number. PNG starts with one specific pattern, JPEG with another, GIF spells out 'GIF', and so on. These signatures are part of the format and do not change when a file is renamed.

This checker reads those first bytes and matches them against the known signatures to report what the file actually is. Because it never relies on the extension, a renamed file cannot fool it: a JPEG called .png is reported as JPEG.

It then shows the extension and the browser's own guess alongside the real format, so you can see exactly where the disagreement is and decide what to do about it.

Fixing a mismatch the right way

If the real format and the extension disagree, renaming the file to match is sometimes enough, for instance when a genuine JPEG is wrongly labelled .png and the receiving app only checks the name. The .jfif case is exactly this: it is already a JPEG, so renaming to .jpg is harmless.

But renaming never converts. If you actually need the file in a different format, because a system requires a true PNG or a real WebP, you must re-encode it with a converter, which rewrites the data into that format. Changing the suffix alone leaves the bytes untouched and the problem unsolved.

So the workflow is simple: check the real format here, and if the file just needs the right label, rename it; if it needs to genuinely become another format, send it through a format converter instead.

Frequently asked questions

Honest answers to what people ask before using this tool.

Image format checker

How it works

Drop a file

Read the true format

Spot a mismatch