In practice
What people open a hex editor for
Most of the time the application that created a file is the right way to read it. A hex editor is for the moment when that view is missing, wrong, or not the question you are asking.
A file will not open
The usual symptom is a dialog and no further information. The bytes are still there. Looking at them tells you which of a few ordinary situations you are in: the file is empty, it is a different format wearing this file’s name, the beginning is damaged, or the beginning looks perfectly normal and the problem is later.
A hex editor does not repair a file by itself. It lets you see the damage, and it lets you put a byte back if you already know what belonged there. If you do not, changing things at random makes a second, quieter problem.
You want what was stored
Applications show an interpretation. A spreadsheet shows numbers, not the record layout. A music player shows a title, not the tag sitting after the audio frames. Export sometimes drops fields the application still keeps in the file. The bytes are the place those fields remain.
Saved games, and other private formats
A saved game is a file format that usually has no public specification. People open one in a hex editor, change a number of lives or a score in the game, save again, and compare. The byte that changed is a candidate for that field. It is slow, and it only works when you can produce two files that differ in a way you understand. It is also the clearest demonstration of what a hex editor is for: the game will not show you its save format, and the file will.
Learning a format on purpose
PNG, WAV, and ZIP are documented. A pleasant way to learn them is to open a small file next to the specification and name the fields as you go. The specification says “four bytes, big-endian, the length of the next chunk.” The editor shows you those four bytes. After a few files, the format stops being a diagram and becomes a layout you can point at.
Telling text, structure, and noise apart
Readable words in the text column usually mean the file contains text, or a binary format that stores strings. Long runs of 00 are padding or empty fields. A region with no readable text and no obvious repetition is often compressed or encrypted. The editor will not decompress it. It will stop you treating that region as if it were a sentence.
Pointing at an exact place
Offsets give two people a shared address. “Look at offset 1C0” is a place in the file, independent of which application last opened it. That is useful in support, in class, and whenever a bug report would otherwise say “somewhere near the end.”