Magic Bytes Identifier: common mistakes and how to fix them
The failure modes that actually happen in practice, what each one looks like in the output, and the concrete fix.
How to use
- Check the input encoding first — a stray byte-order mark or a non-UTF-8 paste corrupts the result before the tool ever runs.
- Look for silent truncation: if the output length is suspiciously round, something was cut off.
- Confirm the option you changed is the one the task needs; a leftover default is the most common cause of a wrong-but-plausible result.
- Re-run with a minimal input you can verify by hand, then add your real data back.
Examples
The PNG signature followed by the start of its IHDR chunk.
Input
89504E470D0A1A0A0000000D49484452
Output — Results
Bytes: 89 50 4E 47 0D 0A 1A 0A ASCII: .PNG.... Detected: PNG image Signature matched: 89504E470D0A1A0A → PNG image Detection is by file signature, not by extension — this is how servers should validate uploads, since a client can rename anything to .png.
Run
Description
Identify a file type from its signature bytes rather than its extension — the safe way to validate uploads.
Related tools
File to Base64 ConverterEncode any local file to Base64 — nothing is uploaded.Base64 to File DownloaderDecode Base64 back into the original file.File Hash CheckerMD5/SHA-1/SHA-256/SHA-512 of any file, computed locally.File Metadata ViewerInspect name, MIME type, size and modification time.Files to ZIP PackagerBundle multiple files into a ZIP archive locally.Base64 EncoderEncode text, JSON, URLs or files to Base64, standard or URL-safe.