Binary File Hex Viewer

Inspect file bytes

Funnel mode temporarily keeps the selected file in this browser for up to two hours. It is not uploaded.

Reading the selected slice...

The displayed type is reported by the browser and is not verified from the file signature.

bytes -


            

Only the selected slice is shown. The rest of the file was not read for this dump.

A hex dump lays out file bytes in three columns: the absolute byte offset on the left, two-digit hex values in the middle, and a best-effort ASCII view on the right. This viewer reads one bounded file slice locally in your browser. It starts at offset 0 with 64 KiB selected, and supports slices of 4 KiB, 16 KiB, 64 KiB, 256 KiB, or 1 MiB.

How to read this hex dump

  1. 1

    Drop one file

    Use any binary, text, image, archive, or executable file. The browser reads it as raw bytes.

  2. 2

    Choose the displayed slice

    Enter a decimal whole-number start offset within the file, then choose 4 KiB, 16 KiB, 64 KiB, 256 KiB, or 1 MiB. Inputs such as 0x10 are not accepted. A final short slice stops at end of file.

  3. 3

    Read 16 bytes per row

    Each line shows an 8-digit absolute hex offset, up to 16 two-digit hex byte values, and an ASCII side column.

  4. 4

    Copy or compare

    Copy the visible dump or compare bytes with known signatures. The viewer does not search, edit bytes, interpret multibyte numbers, export a file, or auto-detect formats.

Anatomy of a line

00000000  89 50 4e 47 0d 0a 1a 0a  00 00 00 0d 49 48 44 52  |.PNG........IHDR|
^offset^  ^--- 16 bytes of hex ---------------------------^  ^-- ASCII ----^
  • Offset, Zero-based absolute byte position in the file, shown as 8-digit hex.
  • Hex values, Sixteen bytes per line, with each byte rendered as two hex digits.
  • ASCII column, Bytes from 0x20 through 0x7E are printed as ASCII; every other byte is shown as ..

Common file signatures (magic bytes)

Magic bytes are clues, not guaranteed proof. They are most useful at offset zero, but formats can share a prefix or contain nested files. ZIP-based formats such as DOCX, XLSX, JAR, and APK can all start with 50 4B 03 04, and this viewer does not identify the format automatically.

Bytes (hex) Possible format clue
89 50 4E 47 0D 0A 1A 0A PNG image
FF D8 FF E0 JPEG/JFIF image
47 49 46 38 39 61 GIF89a image
25 50 44 46 PDF document (%PDF)
50 4B 03 04 ZIP local file header; also common in DOCX, XLSX, JAR, APK
7F 45 4C 46 ELF executable or object file
4D 5A DOS/Windows PE executable (MZ)
1F 8B gzip compressed data
42 4D BMP image (BM)
49 49 2A 00 TIFF image, little-endian

What this viewer can and cannot do

  • Local byte reading, The displayed dump is generated in your browser from the selected file.
  • Bounded slice inspection, Enter any valid byte offset and inspect up to 1 MiB from that point. The browser reads only that slice for the dump.
  • MIME and size context, The tool shows the browser-reported MIME type, or binary, plus the total file size in bytes.
  • Copyable output, Use the copy button to reuse the visible dump in notes, tickets, or command-line comparisons.
  • Not a full hex editor, It does not search, highlight matches, edit bytes, download exports, detect signatures automatically, or interpret 16-bit, 32-bit, or 64-bit values. Endianness is therefore not applied: bytes always appear in file order.

Display limits

The upload control accepts one non-empty file up to 100 MiB, but the hex dump reads and displays at most 1 MiB from the chosen offset. Internally, the browser takes a Blob/File slice and turns only that slice into an ArrayBuffer; file contents are not sent to the server. In funnel mode, a temporary browser-only IndexedDB copy keeps the file available between page navigations for up to two hours, and Start over removes the active copy. The regular single-page mode keeps the selected File only in page memory. For search, editing, interpreted numeric values, or automated format validation, use a dedicated hex editor or a format-specific parser.

Frequently Asked Questions

No. They are useful evidence, especially at offset zero, but they are not a complete parser. Treat them as a clue and confirm important files with a format-specific tool.

No. This tool is read-only and shows only the selected slice. It also does not interpret multibyte numbers, so little-endian and big-endian settings do not apply. For editing and typed values, use a dedicated hex editor.

No. The dump is generated locally in the browser from a Blob/File slice using arrayBuffer(). Funnel mode temporarily stores the selected file in this browser so page steps can continue; regular mode holds it only in page memory.

You can enter any valid start offset and display up to 1 MiB from there. The viewer does not search, highlight matches, export dumps, or load the whole file at once.

Related Tools