15 / TEXT & ENCODING

Unicode escape converter

Make escaped text readable again.

How to use ↓

Decode: turn \uXXXX or \u{1F600} into text. Encode: convert every character to \uXXXX, using surrogate pairs for emoji.

Ready

Up to 262,144 UTF-16 code units · one conversion pass

Inputs and results are not stored or uploaded. Code is never executed; results are displayed as text only.

QUICK GUIDE

Read the text hidden in your logs.

Unicode escapes are a way of writing characters, not encryption. This tool does not parse entire JSON documents.

  1. 01

    Choose a direction and enter text

    Choose Decode to read escapes or Encode to turn text into escapes. Enter the content without surrounding quotes. Any quotes and ordinary characters you enter are preserved when decoding.

  2. 02

    Check the result

    Malformed hexadecimal escapes and unpaired surrogates report errors. Editing the input or direction clears the previous result. Whitespace is not trimmed and nested escapes are not recursively decoded.

  3. 03

    Review, copy and save

    Copy the result or save it as UTF-8 TXT. Reverse with result moves it into the input and switches direction. Results exceeding the input limit can only be copied or downloaded.

UNICODE ESCAPES

Korean text and emoji examples

\ucf54\ub2c8\ud37c
→ 코니퍼

\ud83d\ude00 / \u{1F600}
→ 😀

Encoding also converts letters, digits, spaces and backslashes. A becomes \u0041, a space becomes \u0020 and a backslash becomes \u005c.

Frequently asked questions

How is this different from JSON formatting or URL encoding?

This tool converts Unicode escapes into characters. It does not validate or format JSON structures, decode %HH URL encoding or process HTML entities.

What about double backslashes and newline escapes?

Decoding turns \\ into one backslash without reinterpreting what follows. \\u0041 only becomes \u0041. Other escapes such as \n, \t and \x41 remain unchanged; outer JSON quotes are not removed.

Does this support emoji and historical scripts?

Decode emoji from UTF-16 pairs such as \ud83d\ude00 or code point escapes such as \u{1F600}. Encoding always produces four-digit \uXXXX escapes. Some characters may not display in your font.

Are line endings preserved?

Browser textareas normalize actual CR/CRLF to LF. Use Copy or Download to preserve CRLF decoded from \u000d\u000a. Moving the result into the input may also normalize it to LF.