How to edit a file in hexadecimal
- Open or paste the data. Choose Open for a local file, or paste complete hexadecimal bytes such as
DE AD BE EF. - Navigate to the target offset. Use the offset column, Go to control, or hexadecimal search. Search accepts full-byte and nibble wildcards such as
??andD?. - Edit deliberately. Double-click a byte cell to enter a new value, select one byte to toggle bits, or use Reverse and Invert on a selection.
- Review and export. Undo and redo byte changes, inspect the updated representations, then save a separate binary download. Opened files use a
.bitpeek.binsuffix.
Hex editing capabilities
Bitpeek is designed for small, targeted binary inspection rather than unrestricted multi-gigabyte editing. The workspace accepts files up to 256 KiB and keeps an in-memory edit history.
- Hexadecimal, binary, decimal, UTF-8 text, and Base64 input modes.
- Hex and ASCII rows with stable byte offsets.
- Direct byte editing, single-bit toggles, selection inversion, and byte-order reversal.
- Exact or wildcard byte-pattern search and direct offset navigation.
- Undo and redo for byte edits and selection transforms.
- Local export without replacing the original file automatically.
Useful hex editor workflows
A byte editor is useful when the location and meaning of the change are already understood. Typical Bitpeek workflows include:
- Checking a file header or protocol fixture against documented bytes.
- Changing a small flag, identifier, or test value at a known offset.
- Building compact binary examples for documentation or unit tests.
- Comparing the effect of one controlled byte change on checksums, hashes, or interpretations.
Editing limits and safe handling
Bitpeek edits raw bytes; it does not understand every format rule or repair dependent length fields and checksums automatically. Work on a copy and validate the exported file with the software that owns the format.
Saving creates a new download. The original file on your device is not overwritten, and Bitpeek does not retain an uploaded server copy because no upload occurs.
Local processing and privacy
The Online hex editor 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
Does Bitpeek upload the file I edit?
No. The browser reads the selected file into local memory and all byte editing happens on the device.
What is the maximum file size?
The current workspace limit is 256 KiB per opened file. This keeps inspection and editing responsive in the browser.
Can I undo a hex edit?
Yes. Direct byte changes, bit toggles, reverse operations, and invert operations can be undone and redone during the current session.
Will saving overwrite the original?
No. Bitpeek downloads a separate file, and opened source files use a .bitpeek.bin suffix. The original remains unchanged.