Hex to Text Converter

Convert text to hexadecimal bytes and hex back to text, with space, colon or 0x delimiters, upper or lowercase output, and UTF-8 support.

No uploadsNo sign-upInstant results
UTF-8 or Latin-1 bytesSpace · colon · 0x100% Local • Zero Uploads
Convert Hex ↔ Text
Offline engine ready100% private in-browser workspace • Zero cloud uploads
100% Private • Zero Server File Uploads

Why Use Utiliome's Free Hex to Text Converter?

Built from the ground up for strict privacy, instant execution, and zero friction. No subscriptions, paywalls, or account registrations required.

Configurable Delimiter Formats

Format hex byte outputs with spaces, no spaces, colons (48:65:78), or 0x prefixes (0x48 0x65).

Accurate UTF-8 Bytes for Any Language

Serializes characters through UTF-8 bytes to convert accented characters and emojis accurately without truncation, with a Latin-1 option for legacy single-byte data.

Flexible Hex Delimiters & Prefix Stripping

Decodes space-separated hex (48 65 6C), continuous hex (48656c), 0x prefixes (0x48, 0x65), and \x escape sequences without manual cleanup.

100% Local Uint8Array & UTF-8 Byte Inspection

Serializes and reconstructs raw UTF-8 byte streams locally in your browser using TextEncoder and TextDecoder with zero server uploads.

Utiliome vs Traditional Cloud Alternatives

Compare our local-first WebAssembly engine against legacy cloud tools.

Feature Utiliome (Local Browser) Legacy Cloud Converters
Accepted Hex Input Formats Parses spaced (48 65), unspaced (4865), 0x48, \x48, and comma-separated hex Rejects hex strings containing 0x prefixes, commas, or line breaks
Multi-Byte UTF-8 & Emoji Fidelity Full TextEncoder/TextDecoder pipeline preserving 2-, 3-, and 4-byte UTF-8 characters Converts each byte with String.fromCharCode(), corrupting all non-ASCII UTF-8 text
Output Formatting Controls Customize uppercase/lowercase hex digits and byte separators (space, none, 0x, \x) Single fixed lowercase output format
Packet & Key Material Privacy 100% client-side conversion — Wireshark hex dumps and keys never leave browser Transmits pasted hex dumps to backend servers
How it works

How to Use Hex to Text Converter in 3 Easy Steps

No software installation required. Everything runs directly inside your web browser.

1

Enter Text or Hexadecimal Bytes

Paste text or hex digits into the editor or drop a plain-text file.

2

Select Delimiters and Casing

Choose space, colon, none, or 0x delimiters, toggle uppercase vs. lowercase hex digits, and pick UTF-8 or Latin-1.

3

Copy or Download Formatted Output

Copy the hexadecimal string or decoded UTF-8 text with a single click.

How Text Becomes Hexadecimal Bytes

Quick Answer: Utiliome converts text into hexadecimal by encoding characters into UTF-8 octets via TextEncoder and mapping each Uint8Array byte to its two-digit base-16 representation (00–FF), and decodes hex dumps back to Unicode strings via TextDecoder with automatic 0x, \x, and whitespace stripping.

Hexadecimal representation is widely used in network packet inspection, firmware debugging, and cryptographic signatures. This tool serializes text into UTF-8 bytes and provides configurable formatting:

Given this input text containing an emoji:

Utiliome 🚀

Formatting with space delimiters and uppercase hex produces:

55 74 69 6C 69 6F 6D 65 20 F0 9F 9A 80

Switching delimiters formats the same byte sequence for specific programming contexts (turn off uppercase for 5574696c…):

Colon-delimited:   55:74:69:6C:69:6F:6D:65:20:F0:9F:9A:80
0x Prefix:         0x55 0x74 0x69 0x6C 0x69 0x6F 0x6D 0x65 0x20 0xF0 0x9F 0x9A 0x80
Continuous:        5574696C696F6D6520F09F9A80

Hex Delimiters, Byte Sizes and Decoding Rules

Quick Answer: Because each hexadecimal digit represents exactly 4 bits (one nibble), two hex digits represent one 8-bit byte (0x00 to 0xFF), making base-16 the universal compact notation for inspecting UTF-8 text encodings, magic file headers, cryptographic digests, and network packet payloads.

Observe these technical standards when working with hexadecimal text:

  • Flexible hex input: By default the decoder keeps only the hex digits, so 0x prefixes, colons, commas, quotes and other punctuation from Wireshark, gdb or memory logs are ignored (remove line offsets first, since they are hex digits too). Turn on Strict to have the first stray character reported instead.
  • UTF-8 or Latin-1: Bytes are decoded as UTF-8 by default. If a byte sequence is not valid UTF-8 (for example E9 on its own), the tool says so and suggests switching to Latin-1, where every byte is exactly one character.
  • Two-digit byte alignment: Hex decoding groups digits into pairs of two. Odd-length hex strings alert you to missing leading zeros before processing.

For binary (0s and 1s), use Binary to Text Converter.

ASCII & UTF-8 Hexadecimal Byte Encoding Specification Table

Quick Answer: Under RFC 4648 Section 8 (Base16) and RFC 3629 (UTF-8), every 8-bit byte splits into a high nibble (bits 7–4) and a low nibble (bits 3–0) encoded as 0–9 and A–F, expanding byte length by 2× while remaining 100% human-inspectable.

Use this reference table to identify common ASCII ranges, control characters, and multi-byte UTF-8 markers in hex dumps:

Character Class Hex Byte Range Decimal Range Common Examples & Hex Values
ASCII Control Codes 0x00 – 0x1F, 0x7F 0 – 31, 127 NUL (00), TAB (09), LF (0A), CR (0D), ESC (1B)
ASCII Space & Punctuation 0x20 – 0x2F 32 – 47 Space (20), ! (21), " (22), # (23), / (2F)
ASCII Digits (0–9) 0x30 – 0x39 48 – 57 '0' (30), '1' (31), ..., '9' (39)
Uppercase Latin (A–Z) 0x41 – 0x5A 65 – 90 'A' (41), 'B' (42), ..., 'Z' (5A)
Lowercase Latin (a–z) 0x61 – 0x7A 97 – 122 'a' (61), 'b' (62), ..., 'z' (7A)
UTF-8 Multi-Byte Sequences 0xC2 – 0xF4 (lead) 194 – 244 é (C3 A9), € (E2 82 AC), 🚀 (F0 9F 9A 80)

Explore related byte and character tools: Binary to Text Converter, Base64 Encoder & Decoder, ASCII Reference Table, and Unicode Code Point Converter.

Debugging File Magic Bytes, BOMs, and Mojibake in Hex Dumps

Quick Answer: Inspecting the first 2 to 8 hexadecimal bytes of a string or file immediately reveals Byte Order Marks (EF BB BF for UTF-8, FE FF for UTF-16BE), binary file signatures (89 50 4E 47 for PNG, 25 50 44 46 for PDF), and double-encoded Latin-1 mojibake.

When a string looks visually identical in an editor yet fails strict equality checks or JSON parsing, converting it to hexadecimal exposes every hidden byte:

  • UTF-8 Byte Order Mark (BOM): Appears at the start of a file as EF BB BF (U+FEFF). Invisible in most editors, it breaks JSON.parse() and Unix shebang (#! = 23 21) scripts.
  • CRLF vs LF Line Endings: Windows line breaks encode as 0D 0A (\r\n), whereas POSIX/macOS line breaks encode as 0A (\n).
  • Classic UTF-8 Mojibake: When UTF-8 bytes C3 A9 (é) are misread as Windows-1252 and re-encoded to UTF-8, they expand into the 4-byte sequence C3 83 C2 A9 (é).
FAQ

Hex to Text Converter FAQ and Technical Guide

Everything you need to know about using Utiliome's free online hex to text converter.

Can this tool decode hex strings formatted with 0x prefixes or colons?

Yes. By default the decoder ignores prefixes, separators and other non-hex characters, so colon-separated bytes (48:65:78) and C-style arrays (0x48, 0x65) decode directly. Turn on Strict if you want stray characters reported instead.

Why does an emoji produce 4 hex pairs instead of 1?

Emojis reside in the astral Unicode plane and require 4 bytes when encoded in UTF-8. Each byte is represented as a 2-digit hex pair (e.g., F0 9F 9A 80).

Why does the letter é become C3 A9 instead of a single byte?

The tool encodes text as UTF-8, the standard used on the web and in most files. In UTF-8, characters outside basic ASCII take two to four bytes: é is C3 A9, the euro sign is E2 82 AC and most emoji are four bytes such as F0 9F 9A 80. Plain English letters stay one byte, so H is 48.

What is the difference between hex and binary text encoding?

Both represent the same bytes. Hexadecimal writes each byte as two characters from 0-9 and A-F (48), while binary writes it as eight 0s and 1s (01001000). Hex is four times shorter and is what you see in debuggers, hash values and colour codes. For bit-level output use the Binary to Text Converter.

Why does an emoji turn into 4 hex bytes (8 hex digits) instead of 1 or 2?

Emojis live in the Unicode Supplementary Planes (U+10000 and above). In UTF-8 encoding, any code point from U+10000 to U+10FFFF is serialized into a 4-byte sequence starting with F0 (for example, 🚀 U+1F680 encodes as F0 9F 9A 80).

Can I paste C or Python style hex arrays like "0x48, 0x65, 0x6c" or "\x48\x65"?

Yes. In Decode mode, our parser automatically strips 0x and \x prefixes as well as commas, spaces, and newlines before pairing the hexadecimal nibbles into bytes.