See the UTF-8 bytes, Unicode code point and UTF-16 unit count of every character, plus a hex dump of the whole string
| Character | Code point | UTF-8 bytes | UTF-16 |
|---|
Yes. Garbled text usually happens when bytes written in one encoding are read as another. By checking the UTF-8 bytes and code point of each character here, you can see how many bytes every character really takes and pinpoint where the data stops matching your expectations.
Characters outside the BMP, such as most emoji, are a single code point but are stored as two units (a surrogate pair) in a JavaScript string. This tool lists one row per code point and also shows the UTF-16 unit count, so you can see the difference between the two at a glance.
No. Encoding the text into bytes and rendering the result happen entirely in your browser using the JavaScript TextEncoder API. The text you enter is never uploaded to a server.