A hex dump represents each byte with two hexadecimal digits. This converter turns those bytes into text using strict UTF-8 decoding or a one-byte Latin-1 mapping. ASCII is included in both choices for byte values from 00 through 7F.
The converter runs locally in your browser and updates as you type. It is intended for text bytes, protocol samples, and short debugging values rather than rendering arbitrary binary files.
How to Use the Hex to ASCII Converter
Decode hex bytes, or switch direction when you need to create them from text.
- Keep Hex to text selected in the Mode control.
- Choose UTF-8 (includes ASCII) or Latin-1 (ISO-8859-1) from Decode as.
- Paste or type the byte sequence in Hex bytes; decoded Text appears immediately.
- Select Swap to move the result into the input and switch to Text to hex.
- Select Copy to copy the current Text output.
Hexadecimal Bytes, ASCII, and Character Encoding
Hexadecimal is a compact notation for numbers using digits 0–9 and letters A–F. One byte ranges from decimal 0 to 255, so exactly two hex digits describe it. For example, the ASCII bytes for Hi are 48 69.
ASCII defines characters only in the 7-bit range. Letters, digits, punctuation, control characters, and space occupy byte values 00 through 7F. A byte such as E9 is not ASCII, even if a legacy character set maps it to a familiar letter.
UTF-8 keeps ASCII bytes unchanged and represents other Unicode characters with sequences of two to four bytes. The character é, for example, is C3 A9 in UTF-8. That is why interpreting each byte independently gives the wrong result for multilingual UTF-8 text.
If you need the reverse conversion, switch to Text to hex. That direction encodes text as UTF-8 and offers Separator, Prefix, and Uppercase controls. It does not produce Latin-1 bytes, even if Latin-1 was selected before switching modes.
Accepted Hex Syntax and Input Errors
The decoder accepts adjacent byte pairs or pairs separated by whitespace, commas, colons, semicolons, or hyphens. It also removes 0x and \x prefixes without regard to letter case. Inputs such as 48 65, 0x48,0x65, and \x48\x65 therefore decode to the same two characters.
48 65 6c 6c 6f
After prefixes and separators are removed, every remaining character must be a hexadecimal digit. The tool reports the first invalid character with a message such as "G" is not a hexadecimal digit. It also rejects an odd number of digits because a final half-byte cannot form a complete byte.
Separators are ignored rather than used to enforce boundaries. For example, 4 8 becomes 48 after whitespace removal and is accepted. If byte grouping matters for a protocol review, normalize the source into clear two-digit pairs before interpreting it.
UTF-8 vs. Latin-1 Decoding and Edge Cases
UTF-8 mode uses a strict decoder. A malformed sequence, an isolated continuation byte, or an incomplete multibyte character produces These bytes are not valid UTF-8. Try Latin-1, or check the input. The tool does not silently replace malformed input with the Unicode replacement character.
Latin-1 mode maps every byte directly to a character with the same numeric value, so decoding does not fail for byte content. This is useful for inspecting legacy single-byte data, but it is not automatic encoding detection. Selecting Latin-1 for UTF-8 bytes produces mojibake such as é instead of é.
Browser terminology deserves one caveat: web platform decoders labeled iso-8859-1 often follow the Encoding Standard’s Windows-1252 mapping. This tool does not use that browser decoder for its Latin-1 option; it directly maps byte values 00–FF to the corresponding Unicode code points. Bytes 80–9F therefore become control-code characters, not Windows-1252 punctuation.
Zero bytes and other control values may be present in the decoded textarea without a visible glyph. A blank-looking result is not necessarily empty. For detailed Unicode and byte inspection, use the string inspector.
Security and Privacy When Decoding Hex Data
Hex is a representation, not encryption. Anyone with the byte sequence can decode it, and converting it does not verify where it came from or whether it is trustworthy. Tokens, passwords, and personal data remain sensitive when written in hexadecimal.
The conversion happens locally and the implementation makes no network request with the input. Output is placed in a plain textarea; it is not interpreted as HTML or executed as JavaScript. However, copied text can become dangerous if it is later inserted into an HTML sink, shell command, SQL statement, or source file without appropriate validation.
Unknown bytes may be compressed, encrypted, executable, or structured binary data rather than text. This tool offers no file signature detection and no binary parser. If the decoded value resembles JSON, inspect a sanitized copy with the JSON formatter; if the source is a different numeric representation, try the number base converter.
Frequently Asked Questions
Is hex the same as ASCII?
No. Hexadecimal is a way to write numeric byte values, while ASCII is a character encoding for values 00 through 7F. The hex pair 41 represents decimal 65, which ASCII assigns to A.
Why does my hex fail in UTF-8 mode?
The bytes may contain an incomplete or invalid UTF-8 sequence, or they may use another character encoding. Check for missing byte pairs and confirm the source encoding. Latin-1 will map every byte, but a readable result does not prove that Latin-1 was the intended encoding.
Which separators can I paste?
Whitespace, commas, colons, semicolons, and hyphens are removed before decoding. The decoder also removes 0x and \x prefixes. Other non-hex characters cause an error, and the remaining number of hex digits must be even.
Can this converter decode emoji?
Yes, when the input contains the valid UTF-8 byte sequence for the emoji and UTF-8 (includes ASCII) is selected. An emoji normally requires four UTF-8 bytes. Latin-1 treats those bytes separately and cannot reconstruct the Unicode code point.
Does the tool detect the text encoding automatically?
No. You explicitly choose UTF-8 or Latin-1, and the tool applies that interpretation. UTF-8 validation can reject malformed sequences, but successful decoding alone does not establish which encoding the original producer intended.
References: RFC 20: ASCII Format for Network Interchange · WHATWG Encoding Standard: UTF-8.