Convert non-ASCII characters such as Chinese, emoji, and special symbols to \uXXXX Unicode escape sequences. Ideal for JSON data debugging, internationalization, and API data dumping. All processing is done locally in your browser — no data is uploaded.
Features
Convert non-ASCII characters to \uXXXX Unicode escape sequences
Supports Chinese, emoji, CJK, special symbols and all non-ASCII characters
Preserves ASCII characters as-is, escapes only non-ASCII parts
Supports plain text and JSON-formatted content
Real-time conversion with statistics display
All processing done locally in your browser — no data uploaded
How to Use
1Paste or type text in the input area
2Non-ASCII characters are automatically converted to \uXXXX escape sequences
3Results are displayed in real time and ready to copy
4Click "Insert Example" for a quick demo
5View statistics: input chars, escape count, and output length
FAQ
What is a Unicode escape sequence?
A Unicode escape sequence is an encoding format starting with \u followed by four hexadecimal digits, used to represent non-ASCII characters in JSON or source code. For example, the Chinese character 「中」 escapes to \u4e2d, and the emoji 「😀」 escapes to \ud83d\ude00.
Why use Unicode escaping?
Unicode escaping ensures non-ASCII characters are correctly transmitted and displayed across different encoding environments in JSON data exchange, internationalization development, and log output. Many APIs and systems require or recommend escaped Unicode sequences.
Are all characters escaped?
No. Only non-ASCII characters (code points above U+007F) are escaped to \uXXXX format. ASCII characters such as letters, digits, and common punctuation remain unchanged.
How are emoji characters escaped?
Emoji and other characters outside the Basic Multilingual Plane (BMP) are represented using surrogate pairs — two \uXXXX sequences for a single emoji character. For example, 😀 becomes \ud83d\ude00.
Is the escaped content still valid JSON?
Yes. The \uXXXX format is a standard escape form defined in the JSON specification. Escaped content remains valid JSON strings that any standard JSON parser can correctly parse.