Decode Hex to text
Convert hexadecimal byte sequences back to readable UTF-8 text. Strips spaces, commas, 0x and \\x prefixes automatically. All processing runs locally.
Hello, world!
How to decode hex
Reads byte pairs (00-ff) and reassembles them as UTF-8 text. Spaces, commas, `0x` and `\x` prefixes are all stripped before parsing.
- 01
Paste hex bytes
Any common format works — spaces, commas, 0x prefixes.
Bytes flow through
TextEncoder/TextDecoderfor predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.inputUTF-8TextEncoderlosslessliveinput · raw byteshex · UTF-848 65 6c 6c 6f
loaded · UTF-8MIME · ready - 02
Auto-strip
Separators and prefixes are removed before decoding.
Hash and signature operations call
crypto.subtlefrom the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.cleanWeb Cryptosubtledeterministicliveclean · options48656c6c6f · live48656c6c6f
options applied · livelive - 03
Live decode
Bytes become UTF-8 chars as you type.
Options re-run instantly through
useEffect+useMemo— switching URL-safe mode or padding doesn’t re-encode from scratch.livememoisedoptionsinstantreactiveout · encodedtext · readyHello
encoded · livelossless - 04
Copy or download
One click to clipboard. Download as .txt.
Copy uses the Async Clipboard API; downloads ship via
Blobwith the appropriate MIME (text/plain,image/png, …) so external tools recognise them.exportclipboardblobMIME-correctclient-sideok · copiedready · doneCopied
shipped · ready to shipsuccess
Encoding without surprises
Always UTF-8 first
Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.
URL-safe vs standard Base64
Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.
Hashes aren’t passwords
SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.
Watch padding rules
Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.
Use Web Crypto for keys
Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.
JWT decode ≠ verify
Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.
When to decode hex
Reverse engineering, protocol debugging, file inspection.
Hexdump output
Translate hexdump/od columns back to readable text. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.
RFC-compliantNetwork packets
Decode payloads captured by Wireshark or tcpdump. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.
OpenSSL-matchedFile formats
Read magic numbers and header strings. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.
losslessMemory dumps
Pull strings out of memory snapshots. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.
byte-identicalCrypto debugging
Inspect hex-encoded ciphertext or keys. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.
spec-gradeURL fragments
Decode %-stripped hex blobs in logs. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.