Open, inspect and edit binary files in your browser. Hex + ASCII view, byte editing, hex/text search, data inspector, code export. Free, nothing uploaded.
This online hex editor opens a binary file in your browser and shows you exactly what is inside it: every byte in hexadecimal, the matching ASCII alongside, and the offset of each row. You can search it, jump to an offset, change bytes in place, bookmark interesting positions, and export the modified file back out. There is nothing to install and nothing to upload — the file is read locally through the browser’s File API and the bytes never touch a server.
It exists for the moments when a file will not open the way it should. A .bin dump from a device, a firmware image, a save file, a proprietary format with no documentation, a “corrupt” download you want to check the header of. A hex viewer is how you find out what a file actually is rather than what its extension claims.
48 65 6C 6C 6F or 0x48,0x65,0x6C are both accepted, which is handy for inspecting a hex blob copied out of a log or a packet capture.1A4F.00 to FF. Modified bytes stay highlighted and are counted, so you always know what you have changed.Large files stay usable because the hex view is virtualised: only a window of rows is rendered at a time, and scrolling or jumping moves that window. You are not waiting on the browser to lay out a million table rows.
Every row of a hex dump has three parts. On the left, the offset — the position of the first byte on that row, written in hexadecimal. In the middle, the bytes themselves, two hex digits each. On the right, the ASCII rendering, where printable characters appear as themselves and everything else shows as a placeholder.
At 16 bytes per row the offset advances by 0x10 each line, so the byte at offset 0x0000002B sits on the row starting at 0x00000020, eleven columns across. That arithmetic is why the row-width control matters: a structure with 8-byte fields reads cleanly at 8 or 32 bytes per row and looks like noise at anything else.
The first few bytes of a file are usually the most informative, because most formats begin with a magic number:
| Leading bytes | ASCII | Format |
|---|---|---|
4D 5A | MZ | Windows executable (PE/EXE/DLL) |
7F 45 4C 46 | .ELF | Linux/Unix executable |
50 4B 03 04 | PK.. | ZIP, and everything built on it (DOCX, XLSX, JAR, APK) |
89 50 4E 47 | .PNG | PNG image |
FF D8 FF | — | JPEG image |
25 50 44 46 | PDF document | |
1F 8B | — | gzip archive |
If a file’s extension and its magic number disagree, the magic number is telling the truth. For a systematic check across a much longer signature list, use the file magic number checker.
Raw bytes only become meaningful once you decide how to interpret them. Select any byte and the data inspector decodes the bytes starting at that offset as every common primitive at once: int8 and uint8, the binary expansion of that byte, int16/uint16, int32/uint32, float32, int64/uint64, float64, the ASCII character, and a UTF-8 decoded string.
A little-endian and big-endian toggle sits alongside, because the same four bytes mean different numbers depending on byte order. Take 01 00 00 00: read little-endian — least significant byte first, the convention on x86 and ARM — that is the 32-bit integer 1. Read big-endian, the convention in most network protocols and on some older architectures, it is 16,777,216. Getting endianness wrong is the classic reason a length field looks absurd, and flipping the toggle is usually the fastest way to confirm you have found the right field.
.bin extension says nothing about content. A hex viewer shows the header and tells you whether you are looking at firmware, a disk image, a ROM, or a serialised blob.IEND, or a ZIP has a valid end-of-central-directory record, quickly separates truncated files from otherwise broken ones.For a first-pass look at whether a region is compressed or encrypted, the entropy analyzer complements this tool; obfuscated script payloads found inside a file are a job for the malware deobfuscator.
For inspection, targeted edits, and quick analysis, yes — and it works on any operating system with no install, which desktop tools cannot claim. Dedicated desktop editors still win for very large files, disk and memory editing, binary templates, and file comparison. Use this when you need an answer now and do not want to install anything.
No. The file is read in your browser through the File API and every operation — rendering, searching, editing, exporting — happens locally. Nothing is transmitted. The only data that ever leaves the page is a permalink you explicitly choose to copy, and that is limited to 1024 bytes of content.
Yes. Select a byte, enter a new value between 00 and FF, and repeat for as many bytes as you need. Edited positions stay highlighted and the count of changes is shown. Export downloads a new copy of the file with your modifications applied; your original file on disk is untouched.
Drag it onto the drop zone. It is displayed as hex with an ASCII column immediately. Start at offset 0 and read the first bytes — those usually identify the real format even when the extension does not.
Byte order for multi-byte numbers. Little-endian puts the least significant byte first and is what x86 and ARM use; big-endian puts the most significant byte first and is standard in network protocols. The data inspector has a toggle, and switching it changes every multi-byte value it reports.
The hex view is virtualised, so it renders only a window of rows at a time and stays responsive on files far larger than a naive editor would handle. The practical ceiling is your browser’s available memory, since the whole file is held in a buffer. Very large images are better handled by a desktop tool.
Yes. Switch the search mode to ASCII and type the string. Hex mode accepts patterns like 4D5A or 4D 5A. Both modes highlight every match and let you step through them.
Yes — free, unlimited, and no account required, like the rest of our security tools.
A hex editor displays and edits binary file data in hexadecimal (base-16) format, alongside an ASCII/Unicode text view. Unlike text editors that interpret a file as readable characters, a hex editor shows the raw bytes that compose a file — letting you inspect and modify any file at the binary level, regardless of format or extension.
This is a free online hex editor and binary file viewer that runs entirely in your browser. You can open a file from disk (drag-and-drop or file picker) or paste a hex string directly, then view, navigate, search, edit, and export the bytes. Nothing is uploaded — file reads happen locally via the browser File API.
Hex editors are indispensable for reverse engineering, forensic analysis, malware research, file-format investigation, data recovery, firmware inspection, and low-level debugging.
48 65 6C 6C 6F or 0x48,0x65,0x6C to inspect a snippet without creating a file.Each byte (8 bits) is shown as two hexadecimal digits (00–FF), representing values 0–255:
| Decimal | Binary | Hex | ASCII |
|---|---|---|---|
| 0 | 00000000 | 00 | NUL |
| 65 | 01000001 | 41 | A |
| 90 | 01011010 | 5A | Z |
| 97 | 01100001 | 61 | a |
| 255 | 11111111 | FF | (non-printable) |
The view has three columns: offset (position), hexadecimal bytes, and the ASCII interpretation. Non-printable bytes appear as dots in the ASCII column. Color coding distinguishes null, printable, control, whitespace, and extended (0x80–0xFF) bytes at a glance.
Select any byte and the data inspector decodes the bytes starting at that offset into the values a binary format would store there:
This turns the editor into a quick struct/header decoder — point at a length field, timestamp, or pointer and read it without manual math.
A hex editor allows you to view and edit binary files at the byte level. It is commonly used for analyzing file formats, reverse engineering, examining malware samples, editing game saves, recovering corrupted data, patching executables, and understanding how programs store data internally.
Enter the hexadecimal offset in the Jump to Offset field and click Jump. The view will scroll to that location and select the byte at that offset. You can also click directly on any byte in the hex view to select it, and the info bar will show the offset in both hexadecimal and decimal formats.
Yes, the search feature supports both hex pattern and ASCII text search modes. For hex search, enter byte values like 48 65 6C 6C 6F (spaces are optional). For ASCII search, enter the text directly. Search results are highlighted in green, and you can navigate between matches using the arrow buttons.
Double-click on any byte in the hex view to open the edit dialog. Enter the new value in hexadecimal format (00 to FF) and click Save. Modified bytes are highlighted in yellow. Your changes are tracked separately from the original file and can be exported when you are ready.
Bookmarks let you mark important byte offsets with notes for later reference. Select a byte, click Add Bookmark, and enter a description. Bookmarked bytes are highlighted in purple. Click any bookmark in the list to jump directly to that offset. This is useful for marking file headers, important data structures, or areas of interest.
Click the Export Modified button to download a copy of the file with all your changes applied. The button shows the number of bytes you have modified. The original file remains unchanged since all editing happens in browser memory. The exported file is saved with a .modified extension.
The bytes per row setting controls how many bytes are shown on each line. 8 bytes per row is easier to read on narrow screens. 16 bytes is the traditional hex editor view. 32 bytes per row shows more data at once on wide screens. Choose the setting that best fits your screen size and preference.
Yes. This is a full online hex editor and binary file viewer — drag a file onto the drop zone or use the file picker to open it. The file is read in your browser with the File API, so it is never uploaded to a server. You see the raw bytes in hexadecimal alongside an ASCII view, with color coding for null, printable, control, whitespace, and extended bytes. You can also paste a hex string instead of uploading a file.
Select any byte and the data inspector decodes the bytes starting at that offset into the values a binary format would store there: int8/uint8, int16/uint16, int32/uint32, int64/uint64 (signed and unsigned), float32 and float64, the ASCII character, and a UTF-8 string preview. A little/big-endian toggle reinterprets multi-byte numbers instantly — use little-endian for x86/ARM data and big-endian for network byte order. This lets you read length fields, timestamps, and pointers from a header without doing the math by hand.
Yes. The hex view is virtualized: it renders only the rows currently on screen and slides that window as you scroll, so multi-megabyte binaries stay responsive instead of locking up the page. Every byte is still reachable — scroll to it, use Jump to Offset, run a hex/ASCII search, or click a bookmark. Because the file lives in memory and is processed locally, no upload step slows you down.
No file is uploaded. This hex editor is 100% client-side — files are read in your browser with the File API and all viewing, editing, inspecting, searching, and exporting happens on your device. Nothing is sent to a server, which makes it safe for analyzing sensitive binaries, firmware images, and forensic artifacts. The optional permalink feature only encodes small pasted-hex inputs into the URL; uploaded or large files are never put in a link.