Unicode Encode
Convert text to Unicode escape sequences
What is Unicode Encode?
Not every system tolerates raw Unicode. Configuration files, legacy Java tooling, and ASCII-only pipelines choke on characters like "é" or "中". The Unicode Encode tool converts those characters into portable \uXXXX escape sequences — "café" becomes "caf\u00e9" — so the text survives transport through systems that only speak ASCII.
Escaping is standard practice in internationalization: Java properties files, JSON payloads targeting strict parsers, and source code that must compile on any locale all store non-ASCII text as escapes. Encoding guarantees the characters arrive intact regardless of what encoding the receiving system assumes.
How to use
- Type or paste your text into the input box — any script, any symbols, any emoji.
- Choose whether plain ASCII characters stay as-is (the usual choice) or get escaped too. Keeping ASCII readable makes the output far easier to scan.
- Click encode. Every non-ASCII character becomes a \uXXXX escape; characters beyond the four-digit range become surrogate pairs.
- Copy the escaped string into your properties file, JSON document, or source code.
Common use cases
- Java properties files: The classic .properties format is Latin-1 by specification, so non-Latin text must be \u-escaped. Generate those escapes instead of hand-converting.
- Strict JSON APIs: Some legacy parsers mishandle raw UTF-8. Escaping the payload's non-ASCII content sidesteps the problem entirely.
- ASCII-safe source code: String literals containing special characters compile identically everywhere when escaped, avoiding "works on my machine" encoding bugs.
- Email headers: Systems that still expect ASCII-only headers encode display names and subjects as escapes before sending.
Example
Input: naïve façade Output: na\u00efve fa\u00e7ade
FAQs
Why not just send UTF-8 directly?
Modern systems should — and usually do. Escaping is for the long tail of legacy software: old Java tooling, mainframe feeds, and protocols specified before UTF-8 won. When both ends handle UTF-8, raw text is simpler; escapes are the compatibility fallback.
How are emoji encoded?
As surrogate pairs: two \u escapes representing the high and low halves of the character. 🎉 becomes "\uD83C\uDF89". Any compliant JSON or JavaScript parser reassembles the pair into the single emoji on reading.
Can I escape ASCII characters as well?
Yes, though it is rarely needed. Full escaping turns "A" into "\u0041", which some test suites use to verify parsers handle escapes in every position. For normal use, leaving ASCII readable is clearer.
Is the process reversible?
Entirely. The Unicode Decode tool converts every \uXXXX sequence back to its character, restoring the original text exactly — surrogate pairs included.