Hexdump

Close, and readable in the same way. Each line is an 8-digit hex offset, then the bytes of that line in hex separated by spaces, then the ASCII column between pipes. Bytes from 0x20 to 0x7e print as themselves and everything else prints as a dot. Unlike hexdump -C, repeated identical lines are not collapsed into a star, so every offset in the file is present in the output.

With the bytesPerLine option: 8, 16 or 32, defaulting to 16. Sixteen matches the layout most write-ups and command line tools use, so offsets line up when you compare with a colleague. Thirty-two suits wide screens and spotting repeating structures; eight suits narrow records and 8-byte fields.

Yes. Run From hexdump on the saved text. It strips the leading offset column and the trailing ASCII column, then reads the hex pairs that remain, so this tool's own output round-trips. The rebuilt file comes back with a .bin extension.

No hard limit in the tool, but the whole file is held in your device's memory and the dump itself is roughly four times the file size as text. A few megabytes is fine on a laptop; a multi-gigabyte disk image is not what this is for. To look at one region of a large file, cut it out with Take bytes first, then dump the piece.

No. The bytes are read locally and dumped in a Web Worker in this tab. Nothing is uploaded, nothing is logged and no copy of the file is kept, which is the reason this exists as a page rather than as an upload form. You can disconnect from the network and it still runs.