How to use MIME Type and File Signature Checker
- Choose up to 20 files, or enter file names or extensions in the lookup field. You can use both in one run.
- Select Inspect file signatures.
- Compare the opening-byte evidence, expected extension type and verdict in each row. An unknown signature or unreadable file needs further inspection.
- Download file-type-report.json to retain the rows and file results. A matching header does not establish that a file is complete or safe to open.
Example: MIME Type and File Signature Checker
Look up two file extensions without selecting a file.
Options
- Extension lookup
- Enter names or extensions such as report.docx, .png or archive.tar.gz, separated by commas, spaces or semicolons. The table records the usual type and MIME name for supported extensions. Unknown names stay unknown; no file bytes are inspected in a lookup.
- Opening-byte evidence
- The checker compares the first 4,096 bytes with its supported signatures, including image, document, archive and executable headers. RIFF markers and ISO base media brands can distinguish some container families. Printable UTF-8 is weaker evidence than a format-specific binary header.
- ZIP containers
- DOCX, XLSX, PPTX, ODT, EPUB and other formats share ZIP headers. The report adds the first stored entry name when readable; the extension still supplies the claimed family. This does not validate the entries or identify the complete format.
Supported inputs and limits
- Inspect up to 20 files, or look up at most 40 names or extensions within 4,000 characters.
- File inspection reads the opening 4,096 bytes, with an extra window of up to 64 KiB for a ZIP’s first entry name.
- Files are read in your browser and are not uploaded.
- Unsupported signatures remain unrecognized; text without a format-specific header has lower-confidence evidence.
- The JSON report retains the displayed rows and file results.
More details
This check does not unpack archives, validate a whole file, repair an extension or scan for malware.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
What a file signature can and cannot prove
Signature bytes are a claim by whoever wrote the file, not a guarantee. A damaged download can keep its opening bytes while the rest is broken, and a file can be built with one format's header and another format's payload. Use the signature to catch a wrong extension or a mislabelled upload, and keep the real checks for size, structure and origin with the system that consumes the file.
Questions about MIME Type and File Signature Checker
Why does a DOCX come back as a ZIP container?
Because it is one. Word, Excel, PowerPoint, OpenDocument and EPUB files are all ZIP archives with a particular set of entries inside, so the shared opening bytes cannot separate them on their own.
Does a matching verdict mean the file is safe?
No. A match only says the opening bytes look like the format the name claims. Safety depends on where the file came from and what it contains, which this page does not examine.
Why is a text file reported with lower confidence?
Text has no signature bytes at all. The check can only say the opening bytes decode as UTF-8 without control characters, which many text formats share with each other.
How much of my file is read?
A few kilobytes from the start, plus a slightly larger window for a ZIP container so the first entry name can be found. The rest of the file is never opened.