Skip to content

Hex Viewer & File Type Checker

Inspect binary bytes and compare recognized file signatures with the extension.

Found a problem, or something that could be better? We read every message and we fix things quickly.

Hex viewer reads a local file in 256-byte pages and displays hexadecimal bytes beside printable ASCII.

Header signatures can reveal a renamed WebP, PDF or executable header, but they cannot prove safety. ZIP-based Office documents and other containers remain ambiguous without deeper parsing.

How to use

  1. Choose a local file; the viewer reads only the header and current page.
  2. Review the recognized signature, browser MIME type and extension comparison.
  3. Move through pages or jump to a decimal or 0x hexadecimal byte offset.

Frequently asked questions

Can a renamed JPG actually be WebP?

Yes. A WebP file normally begins with a RIFF header and WEBP marker. This viewer compares recognized signatures with the filename instead of trusting the extension.

Is an executable header a malware verdict?

No. MZ identifies a DOS/Windows executable header, not malicious intent. A matching extension also does not prove that a file is safe.

Why are DOCX and ZIP grouped together?

Modern Office documents are ZIP containers. A header-only check cannot establish which files are inside; the result deliberately stays at container level.

Can I inspect a large file?

The viewer reads bounded slices rather than loading the entire file. Display is limited to 256 bytes at a time, and no file content is uploaded.

Different kinds of type evidence

The extension is a name, the browser MIME value is supplied metadata and the signature is a small structural clue. These can disagree without identifying the complete content or its safety.

Offsets and readable characters

Offsets are absolute byte positions. ASCII replaces nonprintable bytes with dots for legibility; it does not decode UTF-8 text or modify the original file.