UTF-8 byte values to text

Worked example

UTF-8 serializes Unicode text into bytes; ASCII uses one byte, while many other characters use two to four bytes. Convert locally in your browser. For example, entering "67 97 102 195 169 33" produces "Café!". Compare both sides character by character; the visible spelling can hide different bytes or combining marks. In this direction the encoded representation becomes readable text. Paste the complete sequence, including any padding or escape signs, and check the decoded characters against the source system. A syntactically valid encoded string can still contain bytes that are not valid UTF-8 text.

How the representation works

UTF-8 encodes Unicode scalar values as byte sequences. ASCII letters and digits use the same single byte values as ASCII; accented characters and emoji usually use more. A decimal byte list shows the exact transport bytes, not code points or a base-ten interpretation of the whole string. The decoder validates continuation bytes, overlong forms and invalid scalar ranges with a strict UTF-8 decoder rather than silently inserting a replacement character. Byte order does not change for an individual UTF-8 sequence. This display helps inspect protocol payloads, debug character corruption and distinguish a Unicode text value from the physical bytes that carry it. UTF-8 serializes Unicode text into bytes; ASCII uses one byte, while many other characters use two to four bytes.

A text transformation has a direction. First identify whether your source is readable Unicode text, a list of bytes, code points or an already encoded string. Paste one short value whose meaning you know, inspect the result and only then process a larger input. Keep a copy of the source. An encoded sequence can be reversible while still revealing every original byte to anyone who knows the format; encoding alone is not a privacy measure. Processing runs in this browser, so the converter does not send your pasted content to a conversion server. The result still becomes sensitive if you copy it into a shared document, issue tracker or URL.

Limits and reliable use

Enter unsigned decimal bytes separated by whitespace, commas or semicolons. Invalid UTF-8 sequences are rejected instead of silently replaced. Use the exact alphabet, byte encoding and normalization form required by the receiving system. Similar looking formats are not automatically compatible. A decoded string can contain markup or control characters and must be treated as untrusted input by the next application. A valid conversion also does not prove that the data is authorized, safe or semantically correct. Try a round trip when the operation is intended to be reversible, and compare Unicode code points or UTF-8 bytes if two strings look equal but fail an exact comparison. For records that will be stored or signed, document the transformation as part of the data contract rather than relying on a visual preview.