Choose text-to-code or code-to-text and select an output format.
Developer tool
Unicode Converter & Inspector
Convert text and character codes and inspect invisible characters.
Complete guide
How to use Unicode Converter & Inspector
Convert Java/JavaScript Unicode escapes, U+ code points, HTML numeric entities and UTF-8 hexadecimal bytes. Inspect individual characters and whitespace, control or combining marks.
Three-step workflow
- 1
Choose text-to-code or code-to-text and select an output format.
- 2
Enter text or character codes, then select Convert & inspect.
- 3
Copy the converted result and inspect code points and invisible characters in the table.
What to enter and check
Supports Java/JavaScript \uXXXX escapes, U+ code points, HTML numeric entities and UTF-8 hexadecimal bytes. Input is limited to 20,000 characters and the table shows the first 300 code points. UTF-8 hex bytes may be separated by whitespace; HTML mode handles numeric entities only.
Offsets are zero-based UTF-16 positions and can differ from visible character counts. Invalid code points, unpaired surrogates and invalid UTF-8 are rejected. Whitespace, combining marks and emoji joiners may be necessary; do not remove them merely because they are highlighted. This tool does not automatically repair corrupted encodings.
The Hangul character 가 becomes \uac00. Emoji such as 😀 use two UTF-16 surrogate escapes. An unexpected U+200B in pasted text appears as ZERO WIDTH SPACE in the inspector, helping explain visually identical but different strings.
Offsets are zero-based UTF-16 positions and can differ from visible character counts. Invalid code points, unpaired surrogates and invalid UTF-8 are rejected. Whitespace, combining marks and emoji joiners may be necessary; do not remove them merely because they are highlighted. This tool does not automatically repair corrupted encodings.
Before you use the result
- Up to 20,000 input characters; the inspector displays the first 300 code points.
- Whitespace and combining marks can be legitimate. A highlighted character is not necessarily an error.
Frequently asked questions
How should I read the Unicode Converter & Inspector result?+
Offsets are zero-based UTF-16 positions and can differ from visible character counts. Invalid code points, unpaired surrogates and invalid UTF-8 are rejected. Whitespace, combining marks and emoji joiners may be necessary; do not remove them merely because they are highlighted. This tool does not automatically repair corrupted encodings.
What should I check for a more accurate Unicode Converter & Inspector result?+
Supports Java/JavaScript \uXXXX escapes, U+ code points, HTML numeric entities and UTF-8 hexadecimal bytes. Input is limited to 20,000 characters and the table shows the first 300 code points. UTF-8 hex bytes may be separated by whitespace; HTML mode handles numeric entities only. Up to 20,000 input characters; the inspector displays the first 300 code points.
Is my input uploaded or stored?+
No. This tool processes input in your current browser, and Baro Tool does not store the source content or result on its server.