What the binary viewer shows
The main byte table displays 16 bytes per row. Every row has a hexadecimal offset, individual editable byte cells, and an ASCII column that replaces non-printable values with a dot.
Selecting bytes connects the table to a detailed interpretation panel:
- Unsigned and signed integers in big-endian and little-endian order.
- 16-, 32-, and 64-bit floating-point values when the selection width matches.
- Hex, binary, decimal, Base64, ASCII, and escaped UTF-8 representations.
- CRC-16, CRC-32, Sum-8, XOR-8, SHA-256, SHA-512, and Shannon entropy.
- Known file signatures at the start of the document.
When a browser binary viewer is useful
- Confirming a magic number and the bytes immediately after it.
- Reading a small protocol capture, binary fixture, save file, or embedded resource.
- Checking how the same bytes decode under different endianness.
- Extracting readable strings from an unfamiliar file.
- Comparing a documented field offset with the actual bytes.
Scope and interpretation limits
A generic binary viewer exposes bytes; it does not replace a format-specific parser. A plausible number, string, or file signature is evidence to investigate, not proof that the file is valid or safe.
Bitpeek intentionally limits the workspace to 256 KiB. For larger files, extract the relevant range with a trusted local tool before inspecting it.
Local processing and privacy
The Binary viewer workflow opens the same Bitpeek browser workspace. Selected file bytes, file names, pasted input, searches, edits, hashes, and comparison data are processed in local browser memory and are not sent to a Bitpeek server.
The static guide itself can be read without opening a file or creating an account.
Frequently asked questions
Can Bitpeek read a file without uploading it?
Yes. The File API provides the selected bytes directly to browser memory; Bitpeek has no file-upload endpoint.
Does the viewer support little-endian values?
Yes. Supported integer and floating-point widths are shown in both big-endian and little-endian order when enough bytes are selected.
Can it extract strings?
Yes. The string scanner identifies printable ASCII and ASCII-like UTF-16LE and UTF-16BE runs and reports their byte offsets.