File Inspector
Check file metadata.
Loading tool…
How a file's real type is identified
A file extension is only a label, and anyone can change it. What actually identifies a file is its magic number: a short signature at the start of the data. A PNG begins with the bytes 89 50 4E 47, a PDF with %PDF-, a ZIP with PK, and a JPEG with FF D8 FF. Inspecting those bytes tells you what a file genuinely is, regardless of what it is called.
Beyond the signature, the inspector reports the exact size in bytes, the MIME type your system declares for the file, and its last-modified date. Signature detection is best-effort: common formats are recognised reliably, while rare or plain-text formats such as CSV and JSON have no distinctive signature to find.
Why we built this tool
You inspect a file when something does not add up: a download that will not open, an attachment with a suspicious name, or an unfamiliar extension.
A suspicious attachment is a security question, and mismatched extensions are a classic malware technique. Uploading a suspect file to an inspection service is a poor idea for privacy reasons and pointless for speed reasons, since reading a signature takes microseconds. Ours reads the bytes in your browser with the File API, so nothing is transmitted and nothing is stored — and it works on files of any size, since only the start of the file needs reading.
Tips and common mistakes
- A mismatch between the extension and the detected type is a warning sign, especially on an email attachment.
- No detected type is not automatically suspicious: text formats such as CSV and JSON have no signature.
- Zero-byte files are usually the result of a failed transfer rather than a corrupt source.
- The detected type comes from the file's own signature, which is far more reliable than its name.
Quick start: using File Inspector
- Load the file you want to identify.
- Read the detected type and compare it with the file's extension.
- Treat any mismatch as a warning sign, particularly on an emailed attachment.
- Check the size and last-modified date.
- If the extension is simply wrong, rename the file with the correct one.
For photographs specifically, Extract EXIF reads far more detail; for archives, ZIP Extractor lists the contents.
Why the extension is not the truth
A file's extension — .pdf, .jpg, .docx — is just part of its name, and names can be anything. The real type is determined by the file's actual contents, specifically the "magic number" or signature in its opening bytes. A file called photo.jpg might really be something else entirely, and a file with no extension still has a true type baked into its data. Inspection reads that real signature rather than trusting the label.
What inspection tells you
- The real file type, detected from the content signature, not the extension.
- The exact size in bytes.
- Format details and metadata the file carries.
This answers the practical questions: What is this thing? Is it what it claims to be? Will the program I am about to open it in understand it?
Where inspection matters most
- Security. A file named
invoice.pdfthat inspection reveals to be an executable is a warning sign. Disguised file types are a common malware trick, and checking the true type before opening is a real defense. - Identifying mystery files. A file with no extension, or an unfamiliar one, becomes usable once you know what it actually is and can rename or open it correctly.
- Troubleshooting. A file that "won't open" is often mislabeled — inspection shows the true format so you can use the right program or fix the extension.
- Confirming a download or transfer arrived intact and as the expected type.
Common uses
- Identify an unknown or extensionless file.
- Check a file is what it claims before opening.
- Spot disguised file types.
- Troubleshoot a file that will not open.
Further reading
Kilobytes, Megabytes and Why Your 10 MB File Shows as 9.5 MB →