How to use it
- Type or paste the text into Text. Spaces, line breaks and emoji are inspected too.
- Read Totals for the counts of graphemes, code points and bytes.
- Read Code points: each line gives the code point, its Name, Category, Block, UTF-8 and UTF-16 bytes, and the HTML and JavaScript escapes.
- Type a word of a Unicode name under Search a character name to find characters, such as snowman.
Names, categories and blocks
Every code point has a name, a general category and a block. The category is a two-letter code: Lu is an uppercase letter and So is another symbol. The block is a range of related code points, such as Basic Latin. The names and categories are the identifiers the Unicode Standard defines in English, so they are shown in English here, in every language; the explanations on the page are in your language.
Graphemes and code points
A code point is a number in the Unicode table. A grapheme is what a reader takes for one character. A thumbs-up with a skin tone is one grapheme made of two code points, and a letter with a combining accent is one grapheme of two code points. The code points table lists each code point under the number of its grapheme, so you can see which ones belong together.
UTF-8 and UTF-16 bytes
- UTF-8 writes a code point in one to four bytes. An ASCII letter takes one byte; the snowman takes three, E2 98 83.
- UTF-16 writes a code point in one or two 16-bit units. Above U+FFFF it takes two units, a surrogate pair: U+1F44D is D83D DC4D.
HTML and JavaScript escapes
- HTML: &, <, >, " and ' have names; every other character is written as a hexadecimal reference, such as ☃.
- JavaScript: \u2603 for a code point up to U+FFFF, and \u{1F44D} above it, as the ECMAScript 2015 syntax allows.
Unicode data and its licence
The names, categories and blocks come from the Unicode Character Database (UnicodeData.txt, Blocks.txt, Jamo.txt and PropertyValueAliases.txt) of Unicode 18.0.0, dated 8 July 2026. Copyright © 1991-2026 Unicode, Inc. The data is distributed under UNICODE LICENSE V3, whose full notice is in the data file of this tool and at https://www.unicode.org/license.txt. Hangul syllable names are built from the Jamo short names, and CJK ideograph names from their code point. A range such as Private Use is shown with the label the data gives it, because the data does not name each character in it.
Worked example: the snowman ☃
Type ☃ in Text. The character is U+2603. Its name is SNOWMAN, its category is So (Other Symbol), and it belongs to the block Miscellaneous Symbols. In UTF-8 it takes three bytes, E2 98 83; in UTF-16 it is one unit, 2603.
| Property | Value |
|---|---|
| Character | ☃ |
| Code point | U+2603 |
| Name | SNOWMAN |
| Category | So Other Symbol |
| Block | Miscellaneous Symbols |
| UTF-8 bytes | E2 98 83 |
| UTF-16 units | 2603 |
| HTML | ☃ |
| JavaScript | \u2603 |
Frequently asked questions
What is the difference between a grapheme and a code point?
A code point is one number in the Unicode table. A grapheme is one character as a reader sees it, and it may be made of several code points: a letter with an accent, or an emoji with a skin tone.
Why does an emoji with a skin tone count as two code points?
The base emoji and the skin-tone modifier are two separate code points in the standard. A reader sees one face, so the page counts one grapheme made of those two code points.
What does an unassigned code point mean?
It is a number that the Unicode version of the data does not give a character yet, so it has no name and its category is Cn. Text can contain such a number, but most fonts show it as a replacement box.
Why are the names in English?
The Unicode names are identifiers the standard defines in English. They are the same in every language, so they are the reliable way to search for a character. The explanations on this page are written in your language.
Is the text I inspect sent anywhere?
No. The data file is loaded into the page, and the text is inspected in your browser. Nothing is uploaded or stored.
Sources
- Unicode Character Database: UnicodeData.txt (Unicode 18.0.0)
- Unicode Character Database: Blocks.txt
- UNICODE LICENSE V3
- RFC 3629: UTF-8, a transformation format of ISO 10646 (IETF)
- RFC 2781: UTF-16, an encoding of ISO 10646 (IETF)
Figures and text last checked on Tuesday, November 10, 2026.