File Signature Inspector
Inspect file header markers, identify common format families and flag possible extension mismatches locally.
About the File Signature Inspector
A filename extension and browser-declared MIME type are not proof of a file's contents. File Signature Inspector reads only the first 4 KiB and looks for supported byte markers. It reports likely formats or container families, common compatible extensions and possible extension mismatches. The first 256 bytes are displayed as escaped hex and printable ASCII.
Supported markers cover common images, PDF and RTF documents, ZIP and other compressed archives, OLE containers, SQLite, several audio/video families, executable-family files, WebAssembly and fonts. ZIP packages such as DOCX, EPUB and APK share markers; OLE documents, EBML media and other container families can also remain ambiguous. CAFEBABE is explicitly reported as shared by Java and universal Mach-O.
This is header inspection, not complete format validation, decompression or malware scanning. Markers can be forged, files can be truncated and polyglots can contain multiple formats. Plain text, JSON, CSV, XML, SVG and unsupported types may have no recognized signature. Unknown is reported without guessing from the filename. The optional JSON report contains the filename and displayed header bytes, which may be private.
Key features
- Bounded 4 KiB header read regardless of file size
- Common format and container-family markers
- Extension compatibility and mismatch indications
- Explicit unknown and ambiguous results
- 256-byte hex / ASCII preview
- Optional local JSON inspection report
How to use
- 1Choose a local file; no extension filter is applied.
- 2Read detected marker details and the extension comparison.
- 3Inspect the hex preview without executing or opening the file contents.
- 4Use a format-aware validator or trusted security scanner for integrity and safety checks. Review the report before sharing.
Examples
PNG header bytes in a file named photo.exePNG marker found with a possible filename-extension mismatch; no claim that the file is safe or fully valid.Frequently asked questions
- Does a matching signature mean a file is safe?
- No. A marker can be forged or appear in an unsafe, malformed or polyglot file. This tool is not an antivirus scanner and does not validate the full file.
- Why does a DOCX show a ZIP-family container?
- DOCX and several other package formats use ZIP. Their shared header does not prove which internal package type is present; this tool deliberately does not decompress or inspect entries.
- Is the complete file loaded?
- No. Only up to 4,096 bytes are read. The displayed hex preview includes at most 256 of those bytes.
- Does an unknown result mean the extension is wrong?
- No. Many formats have no fixed supported marker, and truncated or unsupported headers may be unrecognized. The tool does not guess a type from the extension or browser MIME.
Continue your workflow
Open a related tool to prepare your files or refine the finished result.
- Security & CryptographyFile Hash Checker
Compute MD5, SHA-1, SHA-256 and SHA-512 checksums of a file.
Open tool - Productivity & TimeZIP Creator & Extractor
Create ZIP archives, inspect their contents and extract individual files or a selected bundle locally.
Open tool - Productivity & TimeVideo Trimmer & Video-to-GIF
Re-encode a short video range or create a silent animated GIF locally with browser-native processing.
Open tool
