Convert text to Unicode escapes (\uXXXX) and back - locally in your browser, with no upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
In source code, JSON or configuration files special characters are often written as a Unicode escape: an umlaut like ä then appears as \u00e4. This keeps the text limited to pure ASCII and avoids encoding problems when exchanging it between systems. This tool converts both ways: text becomes escapes, escapes become readable text again.
The direction is detected automatically: if the input contains \uXXXX or \u{...} sequences, they are decoded; otherwise the text is encoded. By default only characters outside ASCII are escaped (umlauts, accents, emojis); with the "All characters" option every character is escaped. Characters outside the basic plane (such as emojis) are represented as a surrogate pair of two \uXXXX, exactly like in JavaScript.
The whole conversion runs entirely locally in your browser in pure JavaScript - your text is not uploaded, not stored, and no foreign library is loaded from a CDN. You can download the result as a text file or copy it straight out.
| Input formats | Text input |
|---|---|
| Output format | TXT |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: It uses \uXXXX escapes (and \u{...} when decoding), as common in JavaScript and JSON. Encoding is via UTF-16 code units, so characters outside the basic plane take two escapes. Other escape forms (such as \xHH or \NNN) are not produced. Very large texts are limited by your device memory.
No. The conversion runs entirely locally in your browser; your text never leaves your device and is not stored.
Yes. If the input contains \uXXXX sequences it decodes; otherwise it encodes the text.
Then every character is written as \uXXXX, including ordinary letters - useful when the whole text must be ASCII-safe.
Yes. Emojis are encoded as a surrogate pair of two \uXXXX and reassembled correctly when decoding; the \u{...} form is read too.
Escape JSON · Encode HTML · Encode URL · Text to ASCII codes · ROT13 cipher