Convert text to Unicode code points and back. Inspect characters that look similar or understand how a string is represented.
How to use
Choose the conversion direction. Enter text for encoding, or space separated U+ values for decoding. Copy the resulting sequence or text.
Example
A becomes U+0041. An emoji such as 😀 becomes U+1F600, showing that code points are not limited to four hex digits.
FAQ
Is this the same as UTF8 bytes?
No. Code points identify characters; UTF8 encodes them as bytes. Combining accents remain separate code points.
Related tools
A practical task
Use code points to distinguish similar looking characters in a copied identifier. Latin A and Cyrillic А can look almost the same while having different values. Inspect the sequence before replacing characters, especially in names, domains, and technical keys.
Another useful question
Does decoding normalize accented letters?
It reconstructs the specified code points. A decomposed letter and accent remain separate components; normalization is a different operation.
Settings and formats
| Field | Values |
|---|---|
| Operation | Encode (encode); Decode (decode) |
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Code points | A Unicode code point identifies a character or a component of one. A letter followed by a combining accent contains two code points even when the screen displays one accented letter. |
| Visible symbols | What looks like one symbol can contain several Unicode components. Emoji sequences can include a base symbol, a skin tone, and joining characters. Counting or splitting them by bytes changes their structure. |
| UTF8 bytes | UTF8 encodes characters as bytes. Basic Latin letters use one byte each, while many accented letters and other scripts use more. A byte count therefore differs from a visible character count. |
| Similar looking text | Two strings can look identical but use different Unicode sequences. An accented letter can be stored directly or as a letter plus an accent. Visual similarity alone does not establish byte equality. |
| A complete byte | A byte holds a value from 0 through 255. Binary writes that value with eight digits; hexadecimal writes it with two. Leading zeros are part of that fixed width representation and must stay in place. |
| Hexadecimal notation | Hexadecimal uses digits 0 through 9 and letters A through F. Letter case does not change the byte value. Text stored as hex still needs a character encoding before its bytes can be read as words. |
| Binary notation | Binary uses only 0 and 1. Keep byte boundaries intact when inspecting encoded text. A missing digit shifts the following bits, so a string of plausible looking zeros and ones can still fail decoding. |