Unicode Escape-- Escape & Unescape Unicode

Convert text to Unicode escape sequences or decode them back to readable characters.

Enter text to escape or unescape

Unicode Output

Why Use Our Unicode Escape Tool?

Full Unicode

Supports all Unicode planes including emoji and CJK characters.

Surrogate Pairs

Correctly handles supplementary plane characters as surrogate pairs.

Two-Way

Both escape and unescape directions in a single tool.

100% Private

All processing happens in your browser. Data never leaves.

One-Click Copy

Copy escaped or unescaped output to clipboard instantly.

Free Forever

No signup, no limits. Convert unlimited text completely free.

Other Encoding Tools

Base64 Encode

Encode text to Base64 format

Base64 Decode

Decode Base64 back to text

Base64 Image

Convert images to Base64 data URIs

URL Encode

Percent-encode text for URLs

URL Decode

Decode percent-encoded URL text

URL Parser

Parse URLs into components

Query Builder

Build URL query strings

HTML Encode

Encode special chars to HTML entities

HTML Decode

Decode HTML entities back to text

JWT Decoder

Decode and inspect JWT tokens

JWT Builder

Build JWT tokens from JSON

Hex Encode

Encode/decode hexadecimal

ROT13

ROT13 cipher encoder/decoder

Complete Unicode Escape Guide

Unicode escaping is the process of converting Unicode characters into their \uXXXX escape sequence representation, where XXXX is the hexadecimal code point of the character. This enables non-ASCII characters to be represented using only ASCII characters, which is essential when working with systems that don't support full Unicode.

For example, the Chinese character "\u4F60" (meaning "you") has the Unicode code point U+4F60, so it escapes to \u4F60. ASCII characters like 'A' (U+0041) become \u0041. Characters outside the Basic Multilingual Plane (above U+FFFF), such as emoji, are represented as UTF-16 surrogate pairs using two \uXXXX sequences.

The \uXXXX format originated in Java and has been adopted by JavaScript, JSON, C#, and many other languages and formats. It provides a standardized, portable way to represent any Unicode character using only printable ASCII characters.

Our free online tool handles both escaping (characters to sequences) and unescaping (sequences back to characters). All processing occurs locally in your browser for complete privacy and security.

The escaping process converts each character to its Unicode code point, then formats the code point as a 4-digit hexadecimal number preceded by \u. The code point is obtained via JavaScript's codePointAt() method.

For characters in the Basic Multilingual Plane (U+0000 to U+FFFF), a single \uXXXX sequence suffices. For supplementary plane characters (U+10000 and above), the character must be encoded as a UTF-16 surrogate pair: a high surrogate (U+D800 to U+DBFF) followed by a low surrogate (U+DC00 to U+DFFF).

The surrogate pair calculation: subtract 0x10000 from the code point, take the upper 10 bits and add 0xD800 for the high surrogate, take the lower 10 bits and add 0xDC00 for the low surrogate. For example, the globe emoji (U+1F30D) becomes \uD83C\uDF0D.

Unescaping reverses the process: \uXXXX patterns are identified in the string, the hex value is parsed, and the corresponding character is substituted. Surrogate pairs are automatically combined by the JavaScript engine to produce the original character.

JavaScript Source Code

Include non-ASCII characters in JavaScript string literals when source files must be ASCII-only. Common in older build systems and certain deployment environments.

JSON Data Files

JSON natively supports \uXXXX escapes. Use them to ensure JSON files are pure ASCII for maximum compatibility across systems and parsers.

Encoding Debugging

Escape text to see exact code points when debugging character encoding issues. Reveals invisible characters, zero-width spaces, and look-alike characters.

Cross-Platform Data

Ensure text survives transmission through systems with different encodings. ASCII-only Unicode escapes work identically on every platform.

Internationalization (i18n)

Prepare translated strings with Unicode escapes for resource bundles and localization files in Java, .NET, and other platforms.

Regular Expressions

Include specific Unicode characters in regex patterns using escape sequences. Essential for matching CJK characters, symbols, and diacritics.

Understanding Unicode organization helps when working with escape sequences:

Plane	Range	Escape Format	Content
BMP (0)	U+0000-U+FFFF	\uXXXX (single)	Latin, CJK, Arabic, Greek, etc.
SMP (1)	U+10000-U+1FFFF	\uXXXX\uXXXX (pair)	Emoji, historic scripts, symbols
SIP (2)	U+20000-U+2FFFF	\uXXXX\uXXXX (pair)	Extended CJK ideographs

The vast majority of commonly used characters fall in the BMP and require only a single \uXXXX sequence. Emoji (introduced primarily in Plane 1) are the most commonly encountered supplementary plane characters requiring surrogate pairs.

What is Unicode escaping?

Unicode escaping converts characters to their \uXXXX escape sequence representation, where XXXX is the 4-digit hexadecimal Unicode code point. For example, 'A' becomes \u0041 and '你' (Chinese 'you') becomes \u4F60.

What is Unicode unescaping?

Unicode unescaping reverses the process, converting \uXXXX sequences back to their corresponding characters. For example, \u0048\u0065\u006C\u006C\u006F becomes 'Hello'.

Why would I need to escape Unicode?

Unicode escaping is needed when: working with ASCII-only systems, creating JavaScript/JSON string literals, debugging character encoding issues, ensuring text survives transmission through non-Unicode systems, and generating source code with non-ASCII characters.

How are emoji characters escaped?

Emoji and other characters outside the Basic Multilingual Plane (above U+FFFF) are escaped as surrogate pairs: two \uXXXX sequences. For example, the globe emoji becomes \uD83C\uDF0D (a high surrogate followed by a low surrogate).

Is this the same as URL encoding?

No. Unicode escape uses \uXXXX format for embedding in source code and strings. URL encoding uses %XX percent-encoding format for safe URL transmission. They serve different purposes and use different formats.

Can I escape only non-ASCII characters?

Our tool escapes all characters to their Unicode sequences for consistency. In practice, ASCII characters (U+0000 to U+007F) often don't need escaping, but full escaping ensures maximum compatibility.

Is my data secure during conversion?

Yes, all processing happens locally in your browser using JavaScript. Your text never leaves your device, is never transmitted to any server, and is never stored anywhere.

What about surrogate pairs?

Characters with code points above U+FFFF (like emoji) require surrogate pairs in UTF-16/UCS-2 encoding. Our tool handles these correctly, producing the correct high/low surrogate pair sequences.

Can I use Unicode escapes in JSON?

Yes, JSON supports \uXXXX escape sequences in string values. This is the standard way to include non-ASCII characters in JSON while maintaining ASCII-only encoding. All JSON parsers handle these sequences.

What programming languages use \uXXXX format?

JavaScript, Java, C#, Python (in string literals), JSON, and many other languages support the \uXXXX Unicode escape format. The format originated in Java and has become a cross-language standard.