Hex to text converter online: decode hex instantly

Convert hexadecimal values back to readable text in seconds with ToolHQ's hex to text converter, paste your hex string, click convert, and get the decoded output immediately.

A hex to text converter takes a string of hexadecimal values, such as "48 65 6C 6C 6F", and translates each pair of hex digits back into the character it represents, returning the human-readable text (in this case, "Hello").

Hex encoding appears in more places than most people realise: database outputs, HTTP headers, network packet captures, debug logs, encoded URLs, and cryptographic data all commonly present information in hexadecimal format. When you need to read what those values actually say, a hex to text converter does the translation in one step.

Key takeaways

• Handles both space-separated ("48 65 6C") and continuous ("48656C") hex input
• Common quick-reference values: 41=A, 61=a, 30=0, 20=space
• Converts using ASCII and UTF-8 encoding, so it handles standard and extended characters
• Converted in your browser, no data is sent anywhere
• The reverse operation, text to hex, is available at ToolHQ's text-to-hex tool

---

How hex-to-text conversion works

Every character you type has a numeric value defined by the ASCII or Unicode standard. The letter "A" is decimal 65. In hexadecimal, 65 decimal is 41. So "41" in hex represents the letter "A."

Hexadecimal uses base 16, with digits 0–9 and letters A–F representing values 10–15. Each character is represented by exactly two hex digits (one byte). Conversion follows three steps:

1. Read two hex digits (one byte): "48"
2. Convert to decimal: 4 × 16 + 8 = 72
3. Look up the ASCII character for decimal 72: "H"

According to Wikipedia's article on hexadecimal, hex is favoured in computing because each hex digit represents exactly four binary digits, making it a compact and human-readable way to express binary data without the length of a full binary string.

ToolHQ's converter accepts both space-separated hex ("48 65 6C 6C 6F") and continuous hex strings ("48656C6C6F"). The tool detects the format automatically and returns the decoded text.

---

Quick reference: common hex values

Hex	Decimal	Character
20	32	Space
30	48	0
41	65	A
42	66	B
5A	90	Z
61	97	a
62	98	b
7A	122	z
0A	10	Newline (LF)
2C	44	Comma
2E	46	Period
3A	58	Colon

The full ASCII table covers values 00–7F (0–127 decimal). Values from 80–FF represent extended ASCII or the first byte of a multibyte UTF-8 character.

---

When you encounter hex-encoded text

Database exports and logs. Some database tools output text fields as hex strings, especially when the data contains special characters or binary content. A hex decoder reveals what the field actually contains.

Network packet analysis. Tools like Wireshark display packet payloads in hex. Converting hex sections of a captured packet to text reveals the human-readable content of an HTTP request, an email header, or a plaintext protocol message.

URL encoding inspection. While URL encoding uses percent-notation (like %48%65%6C), the underlying values are hexadecimal. Converting the percent-stripped values to text shows the original characters.

Debugging encoded data. When a value arrives at your application as a hex string and you need to verify the content, pasting it into a converter is faster than writing a decode function.

Cryptographic data. Hash outputs, encryption keys, and digital signatures are typically displayed in hex. While you cannot "decode" a hash (it is one-way), you can verify whether a hex string is valid and inspect its structure.

File format inspection. Many binary file formats store metadata as hex in their headers. Opening the first bytes of a JPEG in a hex view reveals the "FF D8 FF" magic number; converting those bytes confirms the file type. Hex to text decoding lets you read any embedded text strings within binary files.

Email and MIME encoding. Certain email clients or spam filters encode message headers in hex for compatibility. When debugging email delivery issues, a hex decoder helps you read the encoded header values directly.

Hex versus other encoding formats

It helps to understand where hex fits among other common encodings:

• Binary represents each byte as eight 0s and 1s. Very verbose — "Hello" becomes 40 characters of 1s and 0s in binary, but only 10 hex characters (48 65 6C 6C 6F).
• Base64 encodes three bytes as four characters using A-Z, a-z, 0-9, +, and /. More compact than hex but harder to read byte-by-byte.
• Hexadecimal offers a middle ground: each byte maps to exactly two hex digits, making the byte structure immediately readable while staying far more compact than binary.

For raw binary inspection and one-byte-at-a-time reading, hex is the industry standard. According to Wikipedia's ASCII article, the ASCII standard itself is typically documented with hexadecimal code points precisely because of hex's readability advantages for byte-level data.

---

Mini-story: A backend developer received a bug report: a customer's name was appearing in the database as "4A 6F 68 6E 20 44 6F 65" instead of plain text. She pasted the hex string into a hex to text converter, got "John Doe," and immediately traced the issue to a serialization step that was encoding text fields unnecessarily before storage.

Try ToolHQ's hex to text converter

---

How to use the hex to text converter

1. Paste your hex string into the input box. It can be space-separated ("48 65 6C 6C 6F") or continuous ("48656C6C6F"). Mixed case (uppercase and lowercase A-F) is accepted.
2. Select encoding if needed. The default is UTF-8, which handles English and most European characters. For extended or multi-byte characters, confirm the encoding matches the source.
3. Click "Convert." The decoded text appears in the output box immediately.
4. Copy the result. Use the copy button to transfer the text to your clipboard.
5. Verify the output. If the result shows garbled characters, the source may use a different encoding (like ISO-8859-1 or UTF-16). Try switching encoding options.

---

Mini-story: A security researcher was reviewing an HTTP response that contained a suspicious header value in hex. She copied the hex string into the converter, decoded it in seconds, and found it was a base64 JWT token that had been double-encoded. Without the converter, she would have had to write a quick script to do the same thing manually.

---

Frequently asked questions

What is the difference between hex and binary encoding? Both represent the same underlying data in different numeral systems. Binary uses base 2 (0 and 1 only); hex uses base 16 (0-9 and A-F). One hex digit represents exactly four binary digits, making hex more compact to read.

Can this converter handle UTF-8 characters beyond basic ASCII? Yes. UTF-8 characters outside the basic ASCII range use two, three, or four bytes. The converter handles multibyte UTF-8 sequences correctly as long as the hex input includes all bytes of the character.

What if my hex string has no spaces? Continuous hex strings are supported. The tool reads every two characters as one byte without requiring spaces between values.

Is this the same as a Base64 decoder? No. Base64 and hexadecimal are both ways to represent binary data as text, but they use different encoding schemes. A hex string uses 0-9 and A-F; Base64 uses A-Z, a-z, 0-9, +, and /. The tools are not interchangeable.

Is my data sent to a server? No. Converted in your browser, no data is sent anywhere. All decoding happens locally on your device.

---

The short version

Hex encoding appears throughout computing, in database logs, network captures, debug output, and cryptographic tools. Reading it means converting two-digit hex pairs back to their ASCII characters, one byte at a time. The quick-reference pattern: 41=A, 61=a, 30=0, 20=space.

Decode hex to text now at ToolHQ, handles space-separated and continuous input, no account needed.

For the reverse operation, try text to hex. To convert between other formats, see binary to text or Base64 encoder/decoder.