See the bytes and code points behind any text. Type or paste text and view its UTF-8 bytes or Unicode code points in hex, decimal, octal or binary, with prefixes like 0x, \x or U+ and your choice of separator — then paste numbers to turn them back into text. It shows the character, code point and byte counts side by side, which is where most encoding bugs hide. It's free, runs in your browser, and nothing leaves your device.
| Text | Code points | UTF-8 bytes | JS length |
|---|---|---|---|
| A | 1 (U+0041) | 1 (41) | 1 |
| é | 1 (U+00E9) | 2 (c3 a9) | 1 |
| € | 1 (U+20AC) | 3 (e2 82 ac) | 1 |
| 👋 | 1 (U+1F44B) | 4 (f0 9f 91 8b) | 2 |
A code point is the character's number in Unicode (é = U+00E9). Bytes are how UTF-8 stores it (é = c3 a9). ASCII characters are the same in both.
It counts UTF-16 code units. Most emoji are one code point and four UTF-8 bytes but two UTF-16 units.
Yes. Paste hex bytes or code points with or without prefixes like 0x or \x.
You get an error instead of question-mark characters, so a wrong decode isn't mistaken for a right one.
No. Everything runs in your browser.
There are two different numbers people mean by 'the code' of a character, and the inspector keeps them separate. Unicode code points identify characters: é is U+00E9 and 👋 is U+1F44B. UTF-8 bytes are how those code points are stored: é takes two bytes, c3 a9, and the emoji four. JavaScript's string length counts neither — it counts UTF-16 code units, which is why it reports 2 for one emoji. The tool shows all three counts and lets you view either bytes or code points in hexadecimal, decimal, octal or binary, padded to width, with prefixes such as 0x, \x, U+ or &#x and the separator of your choice. Converting back parses numbers with any of those prefixes and separators. Bytes are decoded as strict UTF-8, so an invalid sequence is reported instead of silently turning into replacement characters; code points become characters directly.