Hex Editor

Open any file as bytes: browse it in hex and ASCII, jump to an offset, search for hex or text, read the numbers at the cursor in both byte orders, change bytes and save an edited copy. Works on files of any size, in your browser.

Viewer Media & Files Updated Oct 16, 2026
Learn how this works
How to Use
  1. Drop a file on the box, or click it to choose one. It opens at offset 0, and the first bytes tell you what it really is (compare the file signature table).
  2. Move around with the arrow keys, Page Up and Page Down, the Previous and Next buttons, or type an offset such as 8000 or 0x1F40 in Go to.
  3. Click a byte to put the cursor on it. The data inspector shows what the bytes there mean as 8-, 16-, 32- and 64-bit numbers in both byte orders, as floats and as a character.
  4. To edit, click a byte and type two hex digits, or click the ASCII column and type letters. Changed bytes turn orange; Ctrl+Z or Undo takes a change back.
  5. Press Download edited copy to save the changes as name-edited.ext. The original file is never touched.
Input
Drop any file, or
Any size — read on your device, never uploaded
No file chosen yet.
8000 or 0x1F40
Presets (sample files)
Bytes
Click a byte, then type. Arrows, Page Up/Down move.
Drop a file or press a preset.
Cursor
—
Byte
—
Edits
—
Type
—

Worked Example

Following a pointer in an .exe. A Windows program starts with 4D 5A (“MZ”). At offset 0x3C it stores where its real header begins, as a 32-bit little-endian number. The bytes there are 80 00 00 00, so the value is 0x80 + 0x00 × 256 + 0x00 × 65,536 + 0x00 × 16,777,216 = 128. Go to offset 128 (0x80) and the bytes read 50 45 00 00: “PE” followed by two zero bytes, the start of the Portable Executable header.

The same idea in a PNG, in the other byte order. After the 8-byte signature and the 4-byte length and “IHDR” name, the image width sits at offset 0x10 as a big-endian number: 00 00 00 02 = 2 pixels. To change a byte, click it and type: in the text sample, typing 57 over the 77 at offset 0x07 turns “world” into “World”, and the saved copy is still exactly 28 bytes.

The common mistake: reading in the wrong byte order. Read the .exe’s 80 00 00 00 as big-endian and you get 0x80000000 = 2,147,483,648, an offset far beyond the end of a 160-byte file. When a number looks absurd, try the other column of the inspector: Windows and x86 formats are little-endian, while PNG, JPEG and network data are big-endian.

Show Work

Open a file or press a preset to see how the bytes at the cursor are read.

Formulas

One byte in hex
0xHL = H × 16 + L
0x57 = 5 × 16 + 7 = 87, the letter “W”
32-bit little-endian
b0 + b1·28 + b2·216 + b3·224
Smallest byte first: Windows, x86, ZIP
32-bit big-endian
b0·224 + b1·216 + b2·28 + b3
Biggest byte first: PNG, JPEG, network order
Signed 8-bit
v ≥ 128 ⇒ v − 256
Two’s complement: FF is 255 unsigned, −1 signed
Where a byte is shown
row = ⌊offset ÷ 16⌋ × 16, column = offset mod 16
0x1F43 sits in row 0x1F40, column 3
Printable ASCII
0x20 ≤ b ≤ 0x7E
Everything else is shown as a dot

Background: Why Files Start with Magic Numbers

Hexadecimal is the natural way to look at bytes: each byte is exactly two hex digits, 00 to FF, so a 16-column row is 16 bytes and offsets line up neatly in hex. Most binary formats begin with a fixed “magic number” that identifies them regardless of the file name, which is why the first row of a hex editor usually tells you what a file really is.

The PNG signature is a well-documented example of a magic number designed on purpose. Its 8 bytes, 89 50 4E 47 0D 0A 1A 0A, each have a job, according to the PNG specification: the first byte is not ASCII, so a text file is unlikely to be mistaken for PNG and a transfer that strips the top bit is caught; “PNG” names the format; the CR LF pair (0D 0A) catches transfers that convert line endings; 1A (Ctrl+Z) stops the file being listed under MS-DOS; and the final LF catches the opposite line-ending conversion.

About This Tool

This hex editor shows any file as offsets, hex bytes and ASCII, 512 bytes at a time, and lets you jump to an offset, search for byte patterns or text, and overwrite bytes with undo. The data inspector reads the bytes under the cursor as signed and unsigned integers of 8 to 64 bits in both byte orders, as 32- and 64-bit floats and as a UTF-8 character, and the Type readout recognises the format from its first bytes. Edits are saved as a separate copy built from the original file and your changed bytes.

Everything runs in your browser and nothing is uploaded, and because the file is read in slices there is no size limit. It suits anyone checking what a file really is, reading a header field, patching a save or config file, or learning how file formats are laid out.

Related tools: Checksum Calculator, MIME Type Lookup and File Viewer.

Frequently Asked Questions

Can I edit a file, not just view it?

Yes. Type hex digits over a byte, or letters in the ASCII column, then download the edited copy. Editing overwrites bytes in place, so the file keeps its size and every offset stays where it was; inserting or deleting bytes is not offered because it shifts everything after it, which breaks most binary formats.

What is little-endian and big-endian?

The order in which a number’s bytes are stored. Little-endian puts the smallest byte first: 80 00 00 00 is 0x00000080 = 128, which is how Windows executables and most PC formats store numbers. Big-endian puts the biggest first: the same bytes read as 0x80000000 = 2,147,483,648, the order used by PNG, JPEG and network protocols. The inspector shows both.

How large a file can it open?

Any size. Only the 512 bytes on screen are read from disk at a time, so a 20 GB disk image opens as fast as a small text file. Find reads the file in 4 MiB slices without freezing the page, and the edited copy is built from the original file plus your changed bytes, without loading it into memory.

How do I tell what kind of file it is from the bytes?

Look at the first few bytes, the “magic number”. 89 50 4E 47 0D 0A 1A 0A is PNG, FF D8 FF is JPEG, 50 4B 03 04 (“PK”) is ZIP and the Office formats built on it, 25 50 44 46 (“%PDF”) is PDF and 4D 5A (“MZ”) is a Windows program. The Type readout names the format from these bytes and warns when they disagree with the file name.

Is my file uploaded?

No. The file is read from your own disk by your browser and the edited copy is put together there too. Nothing is sent to a server, so firmware, save games and private documents stay on your device.

How do I use the Hex Editor?

Just type your numbers. The answer shows up right away — there is no button to press. Change anything and it updates by itself.

Is it free? Does it work without internet?

Yes to both. It is free with no sign-up, and once the page has loaded it keeps working even with no internet.

Where does my data go?

Nowhere — every calculation runs on your own device. Nothing you enter is uploaded, logged, or stored.

Common Use Cases

What is this file really?

A download called invoice.pdf that starts with 4D 5A (“MZ”) is a Windows program, not a PDF.

Reading a header field

Put the cursor on 0x3C of an .exe: the 32-bit little-endian value there (128) is the offset of the “PE” header.

Patching a save or config file

Change one byte at a known offset, say 0x1F40 from 03 to 63 (3 lives to 99), and save an edited copy.

Finding text in a binary

Search a 500 MB firmware image for “version” or for the bytes 1F 8B (a gzip stream) without the page freezing.

Last updated: