What Is the Hex Dump & Magic Byte Inspector?
The Hex Dump & Magic Byte Inspector is a forensic and binary inspection utility running entirely in the browser. It displays file contents in standard hexdump format (8-digit hexadecimal offset, sixteen space-delimited hex byte pairs, and a printable ASCII sidebar). It automatically checks the initial magic bytes (file signatures) to verify true file types (such as PNG, PDF, ZIP, ELF, WebAssembly, or SQLite) and detect spoofed or missing file extensions, alongside an interactive hex byte pattern search.
How to Inspect Files and Hex Dumps
- 1Select Inspect Local File to upload any file (image, binary, document, archive) or switch to Inspect Text Bytes to view string encodings.
- 2Review the detected Magic Header badge to verify the real underlying file format independently of its file extension.
- 3Scroll through the color-coded hexadecimal dump: offsets in gray, hex values in purple, and printable ASCII text in green.
- 4Type a hexadecimal pattern (such as 50 4B 03 04) into the search bar to locate specific byte offsets.
- 5All file reading occurs via browser ArrayBuffer APIs without transmitting file bytes across the network.
Common Binary & Hex Inspection Scenarios
Detect True File Formats & Spoofed Extensions
Examine the leading magic bytes of suspicious downloads to confirm whether a file disguised as .jpg or .pdf is actually an executable (PE/ELF) or script.
Reverse Engineering & Protocol Packet Inspection
Inspect network payloads, firmware dumps, and serialized binary structures with exact 16-byte alignment and ASCII decoding.
Verify File Corruption & Header Truncation
Check whether downloaded archives (ZIP, GZ) or images have missing headers or trailing zero padding that cause extraction failures.
Frequently asked questions
What is a file magic number or file signature?
A magic number is a specific sequence of bytes located at the very beginning of a file (offset 0x00000000) that operating systems and utilities use to identify the format (e.g., %PDF for PDF documents, or PNG for PNG images).
Is my uploaded file sent to any server?
No. The file is read directly into your browser's local memory using the File and FileReader/ArrayBuffer APIs. No network requests are made.
Why is the display capped at 16 KB for large files?
To prevent browser DOM rendering freezing on massive multi-gigabyte files, the viewer renders the first 16 KB where headers, metadata, and magic signatures reside.