File inspection
Online hex viewer.
Open any file and read its raw bytes as offset, hex and ASCII. Jump to an offset, search for text or bytes, click a byte to see its numeric values. Large files are read a page at a time and never uploaded.
Reading a file as hex and ASCII
A hex viewer shows the actual bytes of a file, one row at a time. Each row has three parts: the offset of the first byte in the row, the bytes themselves written as two hexadecimal digits each, and the same bytes shown as characters, with a dot for anything that is not printable ASCII. It is the quickest way to answer questions such as what a file starts with, whether it has a byte-order mark, where a readable string sits inside a binary, or whether two files differ at a specific position.
This viewer runs entirely in your browser and is built for large files. It never loads the file whole. It reads one page of bytes, 512 by default, with File.slice, so a multi-gigabyte disk image opens as fast as a short text file and your browser does not run out of memory.
How to use it
- Choose a file. The first page of bytes appears immediately.
- Page with Next and Previous, or jump with Go to offset. Offsets accept
0x1F40, a decimal number like8000, or bare hex like1f40. - Search with Find next. Choose Text (UTF-8) for ordinary words, Text (UTF-16 LE) for strings stored the Windows way, or Hex bytes for patterns such as
50 4B 03 04. The match is selected and the page moves to show it. Searching scans in 4 MiB chunks, overlapping each chunk so a match that straddles a boundary is not missed, and you can cancel a long scan. - Click any byte, in the hex or the ASCII column, to select it. The value inspector shows that position read as 8, 16, 32 and 64-bit integers in both byte orders, and as a 32 or 64-bit float.
Worked example: is this really a PNG?
Open a file named picture.png. The first row reads 89 50 4E 47 0D 0A 1A 0A 00 00 00 0D 49 48 44 52 with the ASCII column .PNG........IHDR. The eight-byte PNG signature is there, followed by the length 13 of the first chunk and its name, IHDR. Click the bytes at offsets 0x10 to 0x13: the inspector shows the 32-bit big-endian value, which is the image width in pixels, because PNG stores integers in network (big-endian) order. Search for the text IEND and you find the chunk that normally ends a PNG; if it is missing or far from the end of the file, the image has been truncated or has extra data appended.
What the columns mean
- Offset. Position of the first byte of the row, counted from zero, shown in hexadecimal. Row two of a 16-byte layout starts at
00000010, which is 16 in decimal. - Hex. Each byte is 0 to 255, written 00 to FF. Two digits always, so columns line up.
- ASCII. The byte as a character if it is in the printable range 0x20 to 0x7E, otherwise a dot. A dot does not mean the byte is a dot (0x2E): it means "not printable ASCII".
Common mistakes
- Reading multi-byte numbers in the wrong order. The bytes
01 00 00 00are 1 as a little-endian 32-bit integer and 16,777,216 as big-endian. The inspector shows both; which is right depends on the format. - Mixing decimal and hex offsets. A parser error "at byte 4096" is decimal (0x1000). Use the 0x prefix when you mean hex.
- Assuming the ASCII column is the text. UTF-8 characters outside ASCII, and UTF-16 text, show as dots or spaced letters. Switch the search to UTF-16 LE to find text that Windows programs store as two bytes per character.
- Expecting to edit. This is a viewer. It never changes the file and it cannot save one.
What this tool does not do
- It does not edit, patch or write files.
- It does not decode formats: it will not draw an image or play audio, and it does not parse structures. It shows bytes and numeric interpretations only.
- It does not search backwards or with wildcards. Find next scans forward from the selection to the end of the file.
- It does not tell you whether a file is safe.
Your file stays on your device
The viewer runs in an isolated frame that has no network access and no advertising or analytics scripts. The file is read page by page with File.slice into your browser's memory and nothing is uploaded or stored. Closing the tab or pressing Clear discards everything. The ads on this page sit outside the frame and cannot see the file.
Common mix-ups
-
Often assumedEvery byte in the right-hand text column is a letter, so dots mean the file is corrupt.
What the source saysRFC 20 defines ASCII as a 7-bit code with 128 values, and the first 32 are control codes. Bytes of 0x80 and above, and control bytes, are not printable ASCII, so hex viewers show them as dots. [1]
-
Often assumedMulti-byte numbers are stored in the same byte order in every file format.
What the source saysFormats choose. The PNG specification stores multi-byte integers in network byte order, most significant byte first. Other formats use the opposite order, so check the specification before reading a value. [2]
- RFC 20: ASCII format for network interchange
- W3C: Portable Network Graphics (PNG) Specification, integers and byte order
Checked against these sources on .
Frequently asked questions
How do I view a file in hex online without uploading it?
Choose the file in this viewer. It reads the bytes in your browser with File.slice, one page at a time, and shows offset, hex and ASCII columns. Nothing is sent to a server.
Can it open very large files?
Yes. Only the current page (512 bytes by default) is held in memory, so multi-gigabyte files open quickly. Searching scans in 4 MiB chunks and can be cancelled. Search text is limited to 4,096 bytes.
How do I search for a hex pattern?
Set the search type to Hex bytes and enter whole bytes such as 50 4B 03 04 or 0x504B0304, then choose Find next. The match is selected and the view jumps to it.
What do the dots in the ASCII column mean?
A dot stands for any byte that is not printable ASCII (below 0x20 or above 0x7E), including real dots. Use the hex column for the exact value.
What is the difference between little-endian and big-endian?
It is the byte order of a multi-byte number. Little-endian stores the least significant byte first (01 00 00 00 is 1); big-endian stores it last (00 00 00 01 is 1). File formats define which they use.
Can I edit the bytes?
No. This is a read-only viewer. It cannot modify or save a file.
Why does it jump to a row start instead of my exact offset?
Pages start at a row boundary so offsets line up in columns. The byte you asked for is selected and highlighted inside the page.
Is my file uploaded?
No. The viewer runs in a sandboxed frame with no network access and no ad or analytics code. The file is read locally and discarded when you clear it or close the tab.
Sources
Sources last checked 2026-11-11.
- Blob.slice, MDN: developer.mozilla.org/en-US/docs/Web/API/Blob/slice (reading a slice of a file without loading all of it).
- ASCII format for network interchange, RFC 20: www.rfc-editor.org/rfc/rfc20 (printable range 0x20 to 0x7E).
- PNG Specification, W3C (ISO/IEC 15948): www.w3.org/TR/png (signature, big-endian integers, IHDR and IEND chunks).
- ZIP APPNOTE.TXT, PKWARE: pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT (PK\x03\x04 signature, little-endian fields).
- File signatures table, Gary Kessler: www.garykessler.net/library/file_sigs.html (common patterns to search for).