Windows and Linux
A hex editor for Windows and Linux
Windows and Linux do not store files in a different kind of byte. A hex editor on either system shows the same three things: an offset, the bytes in hexadecimal, and a text reading of those bytes. A file you inspect on Linux can be the same file you inspect on Windows. The editor is not translating it.
Line endings are the detail people trip over. A text file from Windows often marks the end of a line with the two bytes 0D 0A. A text file from Linux often uses only 0A. In the text column both look like a break. In the hex column you can see which convention the file actually uses.
Hexinator
Hexinator is the hex editor for Windows and Linux from the people who publish this guide. Open it when you need the bytes. When a format keeps coming back, describe it with a grammar so the fields are labeled instead of counted, and use a script — including Python — when you need to check or rewrite something the grammar can already find.
On a Mac, the editor in the same line is Synalyze It!.
macOS
Synalyze It!
A hex editor for the Mac. Read and change the bytes, then describe a file format once so the next file of that type is already labeled.
Visit Synalyze It!Windows and Linux
Hexinator
The same kind of editor for Windows and Linux: the raw bytes, grammars for formats you see often, and scripts when a format needs a calculation.
Visit HexinatorA small Linux and Windows checklist
- Look at the first bytes before you trust the file name. Extensions are labels, not contents.
- If the text column is nonsense but you expected words, try another encoding before you assume the region is compressed.
- Keep a copy. The editor will write the byte you type, including the byte you did not mean.