Text to Hex
Convert any text to hexadecimal bytes — and decode hex back to text. Choose space, comma, 0x prefix, or no delimiter. UTF-8 encoding, emoji-safe.
How to Use the Text to Hex Converter
Features
Why Hexadecimal is the Standard for Byte Representation
Hexadecimal (base 16) has become the universal notation for byte values in computing because it achieves a natural alignment with binary. One byte (8 bits) fits exactly into two hex digits — the upper four bits map to one hex digit and the lower four bits map to another. This means a stream of bytes can be represented as a sequence of hex pairs, each byte exactly two characters, with no ambiguity about byte boundaries.
Binary (base 2) is more verbose — each byte requires 8 characters. Decimal (base 10) has no natural alignment with binary — a byte can be 1, 2, or 3 decimal digits (0–255), making byte boundaries ambiguous without separators. Hex is the engineering compromise: compact, unambiguous, and human-checkable. For working with binary representations, the Text to Binary tool covers base 2, 8, and 10.
The clean byte-to-hex mapping is also why converting between hex and binary is pure digit substitution with no arithmetic involved — each hex digit corresponds to exactly four bits, so 4 in hex is always 0100 in binary regardless of what surrounds it. Converting decimal to binary, by contrast, requires actual division and remainder calculation that doesn't align with byte boundaries at all, which is the underlying reason hex became the working standard in low-level computing rather than decimal.
Hex Encoding in Programming Contexts
Developers encounter hex representations constantly. CSS color values (#FF5733), SHA-256 hash outputs, UUID strings, MAC addresses (00:1A:2B:3C:4D:5E), IPv6 addresses (2001:0db8:85a3:0000:...), and cryptographic key material are all conventionally expressed in hex. Network protocol documentation shows packet byte sequences in hex. Memory dump outputs from debuggers display hex addresses and values. Even outside pure development work, hex shows up in places most people don't immediately connect to it — a Wi-Fi WPA key can be entered as hex bytes instead of a passphrase, Bluetooth device addresses are formatted as hex pairs, and font files reference glyphs by their hex Unicode code point.
When working with C arrays of byte values, use the Comma delimiter and format them as char or uint8_t array elements. When embedding a string literal in JavaScript or Python source, the 0x prefix format matches the language literal notation (e.g. Helis a Unicode escape format; 0x48 in a Buffer). The No delimiter format produces compact hex strings used by many APIs, hash functions, and encoding schemes.
Git commit hashes, Docker image IDs, and API keys are three everyday developer touchpoints with hex baked in that don't immediately look like "text encoding" problems but genuinely are — a truncated Git hash is just the first several hex characters of a SHA-1 digest over the commit content, and confirming two hashes represent the same underlying bytes is exactly the kind of hex comparison this tool's decode direction can sanity-check when something looks wrong.
Reading a Hex Dump Without Getting Lost
The skill that makes hex genuinely useful rather than just a wall of pairs is pattern recognition for common values. 20 is always a space. Values from 41 to 5A are uppercase letters A–Z in order; 61 to 7A are lowercase a–z. 0A is a newline, 09 is a tab. Once these land in muscle memory, scanning a hex dump for a specific string or structure becomes far faster than converting every pair back to a character mentally — you start recognising "48 65 6C 6C 6F" as "Hello"-shaped on sight, the same way experienced readers recognise word shapes rather than sounding out every letter. Digits and punctuation follow the same logic — 30–39 covers 0–9, and common punctuation clusters just below and after the letter ranges, which is worth knowing when scanning for where a text field ends and structured data begins in a byte dump. None of this needs to be memorised up front — it accumulates naturally after enough exposure to hex output, the same way any frequently-used notation becomes second nature with repetition rather than deliberate study.
Professional hex editors pair the raw hex bytes with an ASCII sidebar for exactly this reason — showing the printable character for each byte alongside its hex value catches the eye faster than the hex alone. This tool's decode direction serves the same purpose in reverse: paste a run of hex you don't immediately recognise and get the actual text back, rather than working through the conversion by hand.
Multi-byte UTF-8 sequences have their own recognisable shape once you know what to look for: a byte in the range C0–DF starts a 2-byte character, E0–EF starts a 3-byte sequence, and F0–F7 starts a 4-byte one (most emoji fall here). Continuation bytes within a multi-byte character always fall in the 80–BF range. Spotting this pattern is how you can tell, just by looking at raw hex, whether you're looking at plain ASCII or something requiring multi-byte Unicode decoding — useful when debugging encoding issues where a file looks correct in one editor and garbled in another, since mojibake is almost always a sign that bytes meant to be read as UTF-8 multi-byte sequences got interpreted one byte at a time instead.
What Hex Encoding Doesn't Give You
Worth stating plainly: converting text to hex is not encryption and provides no real confidentiality. Every hex pair maps directly and reversibly to its original byte — anyone who recognises the format, or pastes it into a tool exactly like this one, gets the original text back immediately. If the goal is genuinely hiding content rather than representing it in a different notation, that calls for actual encryption; the Text Encryptor uses AES-256 for that specific purpose, and the two tools solve entirely different problems despite both dealing in bytes.
Base64 is the other encoding people sometimes reach for expecting confidentiality and, like hex, doesn't provide any — it's a transport encoding designed to pack binary data into safe ASCII for contexts that can't handle raw bytes, not a way to hide content. All three — hex, binary, and Base64 — are reversible by design; that reversibility is the point, not a flaw, since each exists to make data representable or transportable, never to make it secret.