Unicode Code Point Viewer
Inspect Unicode names, categories, graphemes and encoding offsets in supplied text. Compare normalization forms, filter the rows and export JSON.
Read Graphemes and Unicode Byte Offsets
Unicode Code Point Viewer: how to use it
- Paste text or open a Unicode text file. Choose Source form to inspect the decoded text as supplied.
- Choose Inspect code points. Filter by code, name, block or category. Read the grapheme number and encoding offsets in the table.
- Compare with NFC or another normalization form if needed. Download the full JSON report for the current form.
Limits and notes
Up to 16,000 UTF-16 code units before and after normalization. Names, blocks and categories come from the local Unicode 18.0.0 database snapshot. Grapheme boundaries use your browser. Offsets are measured in the inspected text, excluding the file byte-order mark.
How your privacy works →Unicode Code Point Viewer: common questions
Why can one emoji have several code points?
Minimally styled and compound emoji can use several scalar values in one grapheme. Compare the code point rows that share the same grapheme number.
What is the difference between a UTF-8 and a UTF-16 offset?
A UTF-8 offset counts bytes. A UTF-16 offset counts 16-bit code units. Both start at zero in the inspected text.
Does filtering change the JSON download?
The filters change which rows you see and copy. The JSON report keeps every code point in the selected normalization form.