File Type Detector

Inspect common binary file signatures without trusting a filename extension.

Local header inspection. Choose one file up to 25 MiB. A signature result is not a safety, authenticity or malware verdict.

Check a file header rather than its extension

The detector reads the first 32 bytes and checks a small set of common signatures. Output includes filename, byte count and detected family. Renaming a file does not change its header.

Inspect a file

  1. Choose one local file up to 25 MiB.
  2. Press Process.
  3. Compare the signature result with the name and the source that supplied the file.

Example: a renamed image

A PNG renamed from logo.png to logo.jpg still has a PNG header and is reported as PNG. The tool does not rewrite the file or automatically fix its extension.

Which signatures are recognized?

Checks cover PDF, JPEG, PNG, GIF, WebP, ZIP-based archives, WAV, MP3 with an ID3 header, Ogg, ISO media containers with ftyp, ELF executables and the Windows MZ executable family. Some results are broad containers: ZIP may contain Office/EPUB files, and ftyp can belong to MP4/HEIF/AVIF families without proving a particular codec.

Does recognition prove safety or validity?

No. Header bytes can exist in malformed or malicious files. The detector does not parse the complete file, verify checksums, authenticate its source or scan malware. Unknown signatures may simply be unsupported formats rather than corrupt files.

Inspection is local. Do not run an unexpected executable because its family was recognized. File Hash Checker compares complete bytes with a trusted reference; that is a separate test.