I first needed one of these when a web API demanded a signature as a hex string and my input was plain text. Typing hex pairs by hand lasted about two words before I started making mistakes. A text to hex converter encodes every character as its two-digit hexadecimal pair — "Hello" becomes 48 65 6C 6C 6F — instantly, in your browser, with nothing to install.
What Is a Text to Hex Converter?
Every character has a numeric code, and hex (base-16) is the most compact readable way to write bytes. This tool takes your text, finds each character's code, and writes it as two hex digits: H (72) → 48, e (101) → 65, l (108) → 6C. Two digits per character, always, because one byte is exactly two hex digits.
Hex-encoded text shows up in API signatures, cryptographic hashes, URL percent-encoding (%20 is a space), color-adjacent data, and debugging output. It is the lingua franca between human-readable text and machine-readable bytes — compact like binary data, readable like a table.
One detail worth knowing: the tool typically outputs uppercase (48 65 6C) or lowercase (48 65 6c) — both are valid hex, and case never changes the value. Pick whichever matches the system consuming your output.
How to Use the Text to Hex Converter
Type or paste your text into the input box. Click Convert and the hex output appears — usually as space-separated pairs (48 65 6C 6C 6F) or a continuous string (48656C6C6F), depending on the tool's settings. Copy it to your clipboard or download it as a text file.
If you are building an API signature or hash input, choose the continuous format — most crypto libraries expect unbroken hex. If you are debugging or doing homework, the spaced format is far easier to read, since each pair maps to one character. Students verifying encodings should encode one word by hand first (try "Cat" → 43 61 74), then check against the tool.
One habit worth building: when your target system expects a 0x prefix (0x48656C6C6F), add it yourself or check whether the tool offers a prefix option. Forgetting it is a classic source of "invalid hex" errors in code.
How Text to Hex Conversion Works
Two short steps per character — the same pipeline as text-to-binary, ending in base-16 instead of base-2.
Step 1 — Character to code. Each character maps to its number: H → 72, e → 101, space → 32.
Step 2 — Code to hex. The number converts to base-16: 72 → 48 (4×16+8), 101 → 65 (6×16+5), 108 → 6C (6×16+12). Values 10–15 in a digit position become A–F.
Worked example — encode "Hi!": H → 72 → 48; i → 105 → 69 (6×16+9); ! → 33 → 21 (2×16+1). Output: 48 69 21. A whole document encodes in milliseconds, and decoding it back with a hex-to-text tool should return your original text exactly — the round trip is the best correctness check there is.
Common Text to Hex Examples
The pairs you'll reach for most often:
| Character | Decimal | Hex |
|---|---|---|
| A | 65 | 41 |
| H | 72 | 48 |
| a | 97 | 61 |
| e | 101 | 65 |
| 0 | 48 | 30 |
| Space | 32 | 20 |
| ! | 33 | 21 |
| . | 46 | 2E |
| < | 60 | 3C |
| > | 62 | 3E |
Words to try: "Cat" → 43 61 74; "OK" → 4F 4B; "Hello World" → 48 65 6C 6C 6F 20 57 6F 72 6C 64. The space → 20 pair is worth memorizing — in URL encoding it appears as %20, which you have seen a thousand times without realizing it.
Who Uses Text to Hex Converters?
Developers prepare hex-encoded inputs for APIs, cryptographic functions, and debugging tools that speak in bytes.
Students in computer science courses practice character encodings, verifying hand-computed hex with instant feedback.
Cybersecurity learners encode messages for CTF challenges, where hex is one of the most common obfuscation layers.
Embedded engineers convert text labels and configuration strings into hex for firmware that stores data as byte arrays.
Web developers debug URL encoding and form submissions, where %20-style escapes are hex in disguise.
Key Features
- Instant encoding — long texts convert in milliseconds.
- 100% free — no signup, no subscription, no limits.
- Private by design — everything runs locally in your browser; nothing is uploaded.
- UTF-8 support — emoji and international characters encode as correct multi-byte hex.
- Flexible output — spaced pairs, continuous string, or 0x-prefixed.
- Case options — uppercase or lowercase hex to match your target system.
- Copy and download — one click to copy or save the result.
- Works everywhere — any modern browser on desktop or mobile.
Frequently asked
Yes — free, no account, no limits.
48 65 6C 6C 6F — each letter becomes its two-digit hex pair.
One character is one byte, and one byte is exactly two hex digits (each digit holds 4 bits).
No. 6C and 6c are the same value — case is purely stylistic.
Yes, with UTF-8 mode. They become multi-byte sequences — é encodes as C3 A9, for example.
Use the matching hex-to-text tool: pair the digits, convert each pair to decimal, and look up the character.
Yes. Encoding happens entirely in your browser — your text never leaves your device.
It is the hex encoding of a space (hex 20 = decimal 32), written with a % prefix — the same encoding this tool produces.