UTF-8 Byte Inspector

Inspect the UTF-8 bytes used to encode text, with decimal and hexadecimal values.

Processing stays in this browser. Input limit: 50,000 UTF-16 code units. Unpaired surrogates are rejected; pasted line endings may normalize to LF. Inspector reports are limited to 20,000 rows.

Inspect text as UTF-8 bytes

Paste text and choose Process input to see zero-based byte offsets, decimal values and two-digit hexadecimal values. The tool uses the browser's UTF-8 encoder. It does not read a file's original encoding or infer an encoding from arbitrary bytes.

Example: variable-width encoding

The loaded Aé😀 example produces seven bytes: 41, C3, A9, F0, 9F, 98 and 80. A uses one byte, é uses two, and the emoji uses four. The offsets run from zero through six. Byte count therefore differs from the three Unicode code points and four UTF-16 code units in the source.

What the report establishes

The report describes the UTF-8 encoding of the received text only. It does not prove the original clipboard or disk source used UTF-8, preserve an original file's BOM, or measure compressed transfer size. A U+FEFF character explicitly present in the input is encoded as data. Unpaired surrogate code units are rejected instead of allowing an encoder to silently replace them.

Use Hex Text Encoder Decoder for a compact hexadecimal string and strict reverse decoding. Use UTF-16 Code Unit Inspector to compare browser string indexing with UTF-8 byte indexing.

Preview, export and limits

The table previews the first 200 rows; the JSON download includes all rows with index, decimal and hex fields. It contains numeric representations rather than the source text. Input is limited to 50,000 UTF-16 code units, with a maximum report size of 20,000 bytes or code units. A shorter source is required when its encoded report exceeds that bound. Browser textareas may normalize pasted line endings before inspection. Processing remains local, and changing the input clears stale reports and download links.