How to use Text to Hex Converter
What it does & when you need it
This tool prints the raw bytes of your text as hexadecimal and reads hex back into text. It is handy whenever you need to see what is actually inside a string — debugging an encoding bug, comparing bytes against a spec, building a test fixture, or checking how many bytes a multi-byte character really takes. Because it encodes as UTF-8 first, emoji and non-Latin scripts reveal their true byte sequences rather than a single opaque character.
How to use
- Choose Encode or Decode.
- In Encode mode pick a Delimiter (space, none, colon, or comma) and toggle
Uppercase if you prefer
AFoveraf. - Paste text or hex on the left, or press Sample. Copy the result with
Copy result or
Ctrl/Cmd+Enter.
Things worth knowing
Two hex digits per byte. An ASCII letter is one byte — A is 41 — while a
character like é is two bytes (c3 a9) and an emoji is four. The byte count,
not the character count, is what the hex reflects, which is exactly why hex is so
useful for spotting encoding surprises.
Decoding is forgiving. Spaces, tabs, newlines, commas, colons, and dashes
between bytes are ignored, and an optional 0x prefix on each group is stripped.
So a MAC address, a hex-editor dump, or a 0x48 0x69 style list all decode
without cleanup. An odd number of digits, or any character outside 0-9 and
a-f, is flagged with a clear error.
Case and delimiter are cosmetic. They change how the hex looks, not what it
means, so 48 69, 4869, and 48:69 all decode to the same text. To carry bytes
more compactly, try Base64 or Base58; to
fingerprint them instead, see the Hash Generator.