Unicode & emoji tool

Character → code point

Whatever you type in the top field is broken down as you type. You get a single line of U+ values you can copy, plus a grid with one cell per character showing the character itself, its hexadecimal code point and its decimal value. A line break appears as ⏎.

The split is by code point, not by byte or by UTF-16 unit, so a character outside the basic plane — most emoji, rare CJK characters — is reported as one entry rather than as a surrogate pair.

Code point → character

Enter one or more code points in the lower field and press Convert. The accepted forms are flexible:

The U+ prefix is optional and values may be separated by spaces or commas.

One thing that catches people out

Every value is read as hexadecimal, always. Typing 65 gives you e (U+0065), not the letter A that decimal 65 would suggest. If you are working from a decimal table, convert to hex first. Invalid input returns (Invalid code point) rather than a partial result.

Why one visible character can be several code points

What looks like a single glyph is often a sequence. An emoji with a skin-tone modifier is a base emoji plus a modifier; a family emoji is several emoji joined by zero-width joiners (U+200D); an accented letter may be a base letter plus a combining mark instead of one precomposed character. Seeing that breakdown is usually what explains why two visually identical strings are not equal — and Unicode normalisation, rather than string editing, is normally the fix.