1. Hex is bytes, text needs an encoding
The byte E9 can mean “é” in Latin-1, while UTF-8 encodes “é” as C3 A9. Pick the intended encoding instead of assuming every hex string is ASCII.
A byte-accurate, browser-local hex workbench for text, files, packets and binary debugging — with strict multi-format parsing, UTF encodings, hexdumps, byte inspection, signature detection, endianness tools and verified round trips.
Hex represents bytes, not characters. OneFreePlace keeps those layers separate: it parses bytes strictly, applies the encoding you chose, detects BOMs and binary signatures, and independently converts the result back before Copy/Download is enabled.
Engine ready. Ctrl/Cmd + Enter converts.
The inspector uses the exact byte stream from the last successful conversion or loaded binary file.
No bytes inspected yet.
| Offset | Hex | Decimal | Binary | ASCII |
|---|
Reverse byte order inside fixed-size words without changing word order. Useful for registers, packet fields and binary debugging.
Requires a byte length divisible by the selected word size.
Raw-file mode never decodes the file as text. Hex-to-binary mode uses the strict parser and skips files with malformed hex.
No files selected.
Presentation only; byte values are unchanged.
Used by hexdump output and the byte inspector.
Available for UTF-8, UTF-16 LE and UTF-16 BE.
Auto encoding uses BOM first and otherwise defaults to UTF-8.
Prevents invisible replacement or cross-runtime differences when encoding text.
This setting affects files opened as text, not raw binary files.
Accepts compact/spaced hex, colons/dashes/commas, 0x tokens, \\xHH, %HH, and OneFreePlace hexdumps. Odd nibbles and invalid characters are blocked.
Conversion, signature detection, byte inspection, endianness transforms and ZIP generation run locally. No upload endpoint or remote runtime API is required.
The byte E9 can mean “é” in Latin-1, while UTF-8 encodes “é” as C3 A9. Pick the intended encoding instead of assuming every hex string is ASCII.
Auto recognizes UTF-8, UTF-16 LE and UTF-16 BE byte-order marks. Without a BOM it uses strict UTF-8. If the bytes are arbitrary binary, use Download bytes instead of forcing them through a text decoder.
The parser understands 48 65 6C 6C 6F, 48656C6C6F, 0x48, 0x65, \\x48\\x65, %48%65 and generated hexdumps. It rejects ambiguous or malformed half-bytes.
The Byte Inspector shows offsets, binary values, printable ASCII, entropy, CRC-32, BOMs and common file signatures such as PNG, JPEG, PDF, ZIP, GZIP, ELF, PE, SQLite, WebP and WAV.
Open binary reads file bytes directly. This is useful for packet captures, firmware fragments, images, archives and other content that must not be decoded as text first.
Swap 16-, 32- or 64-bit words when interpreting little-endian and big-endian fields. The tool refuses incomplete words instead of silently padding them.
Text → Hex is parsed back into bytes and decoded again. Hex → Text is re-encoded and compared with the decoded byte stream. Copy and normal text downloads remain disabled if exact reconstruction fails.
Convert multiple raw files to hex or strict hex files back to binary and download the results as one ZIP generated locally in your browser.