UTF-8 decode bytes to text

UTF-8 decoding reverses encoding: a stream of bytes becomes human-readable Unicode text. Each valid leading byte tells the decoder how many continuation bytes follow. Invalid bit patterns or truncated sequences produce errors instead of silent corruption.

When you utf8 decode online, you are translating wire-format bytes into the characters your editor would show — not performing URL decoding, HTML unescaping, or Base64 reversal. Those are separate layers applied before or after UTF-8.

This utf8 decoder uses TextDecoder with fatal mode enabled, so malformed sequences surface as clear errors rather than replacement characters you might miss in a log.

Developers paste hex from Wireshark, xxd, browser devtools, or ticket attachments to confirm what bytes actually say before blaming application logic.

Paste byte values into the input panel. Spaced hex (48 65 6c 6c 6f), compact hex (48656c6c6f), and optional 0x prefixes all work — the parser strips cosmetic formatting before decoding.

Switch to decimal mode when your source lists numeric bytes like 72, 101, 108, 108, 111. That matches decimal output from our UTF-8 Encoder and spreadsheet exports from hardware teams.

Invalid hex (odd length, non-hex characters) or out-of-range decimal values (above 255) error immediately. Fix the source string and retry rather than guessing missing bytes.

Copy decoded text with one click for pasting into bug reports, test assertions, or diff tools. Compare against the string your API documentation promises.

Packet analyzers and hexdump utilities often print spaced hex with offsets — copy only the byte columns, not address prefixes. This tool ignores 0x prefixes and comma separators automatically.

Odd-length hex means an incomplete final nibble — pad with a leading zero or fix the capture. A single stray character from a copy-paste error can invalidate the entire sequence.

Do not paste URL percent-encoding here (%48%65%6c%6c%6f) — that is a different alphabet. URL-decode first, or use our URL Encoder/decoder for percent-encoded strings.

Base64-wrapped UTF-8 must be Base64-decoded before you decode UTF-8 bytes. Chain tools: Base64 decode, then UTF-8 decode, not the reverse.

Mojibake debugging: characters look wrong in the UI but hex from the server looks plausible. Decode here to see the actual string independent of fonts and CSS.

API response inspection: copy raw body bytes from a failing integration, decode, and compare to the JSON string field your client parses. Mismatches reveal double-encoding or wrong charset labels.

Firmware and embedded logs: serial consoles often print hex byte dumps. Decode to readable messages without installing desktop hex tools on every machine.

Forensics and support tickets: attach decoded plaintext to tickets alongside hex so non-binary specialists understand the payload.

This tool targets UTF-8 only. Windows-1252, ISO-8859-1, and Shift_JIS produce different byte patterns for the same visual glyph. If decode errors or garbage appear, ask whether the source was ever UTF-8.

UTF-8 BOM (EF BB BF) at the start decodes as the Unicode character U+FEFF (zero-width no-break space). Strip those three bytes from input if your consumer expects BOM-free text.

Latin-1 misinterpreted as UTF-8 often shows as C3 xx sequences for accented letters that should be single bytes in Latin-1. Compare against a known-good UTF-8 encode of the expected string.

JSON and XML declare charset=utf-8 in headers — if decoded text is wrong but hex matches a Latin-1 file, the file was mislabeled, not mis-decoded here.

TextDecoder runs entirely in your browser. Customer data, auth tokens, and internal error hex dumps never upload. Clear the textarea on shared workstations when finished.

Pair with our UTF-8 Encoder for round-trip testing: encode a canonical string, decode the hex, and assert equality in your head or in CI.

Base64 Encoder/Decoder handles transport wrapping. URL Encoder handles percent-encoding. HTML Escape handles & and ' — use the right layer for each bug.

Document whether your hex source used spaced, compact, or decimal format in support tickets so the next engineer reproduces the same decode without re-guessing.