About Unicode Escape

Escape non-ASCII chars as \uXXXX or decode them back. Part of the DevTools Surf developer suite. Browse more tools in the Text / String collection.

Use Cases

• Debugging invisible zero-width characters in user-submitted text
• Escaping non-ASCII characters for safe inclusion in JSON strings
• Converting emoji to escape sequences for cross-platform compatibility
• Identifying hidden Unicode characters causing string comparison failures

Tips

• Paste emoji or accented text to see their \uXXXX codes
• Toggle between escape and unescape modes instantly
• Use this to debug invisible Unicode characters in strings

Fun Facts

• Unicode 1.0 was published in October 1991 with 7,161 characters; as of Unicode 15.1 (2023), it contains 149,813 characters covering 161 scripts.
• The \uXXXX escape syntax originated in Java 1.0 (1996) and was later adopted by JavaScript, JSON, Python, and many other languages.
• The Unicode Consortium assigns code points up to U+10FFFF, giving a theoretical maximum of 1,114,112 possible characters.

FAQ

When do I need \uXXXX escapes?

When embedding non-ASCII text in ASCII-only contexts: JS string literals without UTF-8, JSON meant for ASCII-safe transport, URL query strings, and Java/Python source files with ASCII source encoding.

Are surrogate pairs handled?

Yes — characters outside the Basic Multilingual Plane (most emoji, CJK extension) use UTF-16 surrogate pairs or \u{} syntax in newer JS. The tool produces both depending on your target.

What about decoding?

Yes — paste escaped text and get unescaped back. Round-trips are lossless for valid input.

Does it escape printable ASCII?

No by default — printable ASCII passes through unchanged. Toggle 'escape all' for fully universal ASCII-only output.