How to use Unicode Inspector to inspect text

Understand the inspection

Unicode Inspector is designed for checking how text is represented one processed character at a time. For each non-empty input, it presents the character’s position, character value, numeric code point, uppercase hexadecimal code-point notation, UTF-8 bytes in hexadecimal form, and a broad category label. A summary also gives the number of processed characters and the total UTF-8 byte count.

This can help when you are comparing plain ASCII text with text that contains characters requiring different UTF-8 byte lengths. It can also help you inspect a short sample before using it elsewhere. Text input is optional, so you may begin with an empty field or provide a sample for closer examination. The tool has verified successful examples involving ordinary ASCII text, a single emoji, CJK text, empty text, and omitted text input.

For a useful review, choose a short sample whose characters you understand. A compact input makes it easier to connect each result row with the text you entered, while the summary values provide a quick comparison between character count and encoded byte total.

Run a focused check

1. Open Unicode Inspector.
2. Enter or paste the text you want to examine. You can also leave the input blank.
3. Run the inspection using the available control.
4. Review the character rows. For non-empty text, check the position, character value, numeric code point, uppercase hexadecimal notation, UTF-8 bytes in hexadecimal form, and category label for each processed character.
5. Check the summary values for the character count and total UTF-8 bytes. If you left the input blank, the successful result reports zero characters and zero UTF-8 bytes.

For a short comparison, inspect one sample at a time and note how the rows and totals change. The reported character count is the number of characters processed. The UTF-8 total is calculated by adding the encoded byte length of each processed character.

Interpret the returned values

The character count and UTF-8 byte total measure different aspects of the same processed text. The first indicates how many characters the tool handled, whereas the second adds the encoded byte lengths associated with those characters. Consequently, two samples with comparable character counts can have different byte totals when their characters use different UTF-8 lengths.

Use the numeric and hexadecimal code-point details to distinguish the characters shown in the rows. The character value helps you connect a row to the entered text, while the hexadecimal representation gives a compact notation for the numeric code point. The UTF-8 byte field describes the encoded bytes for that row, not a second character count.

Interpret the broad category label as a general indication only. It is not an authoritative Unicode block, script, language, or character-property classification. The inspection also does not analyze grapheme clusters, user-perceived characters, normalization, or rendered text, so a displayed visual unit may not correspond to one processed character.

Worked example

You want to compare an ordinary letter with a number while checking the row details and summary counts.

Enter the concrete sample A7 and start the inspection. Compare the two character rows with the two summary values, then use the row details to distinguish the letters and numbers.

The result contains one inspection row for each processed character, with position, character value, numeric code point, uppercase hexadecimal notation, UTF-8 bytes in hexadecimal form, and a broad category label, followed by character and UTF-8 byte totals.

Limitations

• Broad category labels are general indications rather than authoritative Unicode classifications, and the inspection does not represent grapheme clusters, normalization, rendered text, or user-perceived characters.

Common errors

• If you treat the character count and UTF-8 byte total as interchangeable, use the count for processed characters and the byte total for the sum of their encoded byte lengths.

FAQ

What happens if I leave the text field empty?

This gives you a defined empty-input result without needing to enter a sample first.

What information does Unicode Inspector show for each character?

For non-empty text, each processed character is shown with a position, character value, numeric code point, uppercase hexadecimal notation, UTF-8 bytes in hexadecimal form, and broad category label.

What is the difference between character count and UTF-8 byte total?

Use the character count to understand how many processed characters are represented. Use the UTF-8 byte total to understand the sum of the encoded byte lengths for those characters.