Unicode Escape/Unescape
Convert text to Unicode escape sequences (\uXXXX) and back.
Unicode Escape & Unescape: Convert Text to \uXXXX Sequences & Back
You are building a multilingual website, editing a legacy Java .properties translation file, or sending international text through an older backend API. You type a German umlaut (Γ€), a Japanese kanji character (ζ₯), or an emoji (π)βonly to discover it turns into unreadable garbage symbols like ä or question marks.
Character encoding mismatches (like Latin-1 or ASCII pipelines intercepting UTF-8 text) remain a frequent source of data corruption. Unicode escape sequences solve this by representing any character on Earth using safe, 7-bit ASCII hexadecimal notation like \u00e4.
Our free Unicode Escape and Unescape Tool lets you convert special characters, symbols, and non-Latin alphabets into standard Unicode escape sequences (\uXXXX), JSON-escaped strings, and decode raw escape sequences back into readable human text instantly in your browser.
How Unicode Escape Sequences Work
In computing, every letter, number, and glyph in every human language is assigned an integer code point by the Unicode Consortium. An escape sequence encodes that code point into a text string that any ASCII-only compiler or terminal can read without encoding confusion:
Used in JavaScript, JSON, Java, and C# for characters in the Basic Multilingual Plane (U+0000 to U+FFFF).
"CafΓ©" β "Caf\u00e9"
Characters above U+FFFF (like modern emojis) split into two 16-bit code units in UTF-16 environments.
"π" β "π"
Modern JavaScript allows variable-length braces for astral plane symbols without splitting pairs.
"π" β "\u{1f680}"
Real-World Development Scenarios for Unicode Escaping
Java Resource Bundles & .properties Files
By default, Java .properties localization files expect ISO 8859-1 (Latin-1) encoding. Storing Chinese, Hindi, or Arabic translations requires escaping characters with \uXXXX to prevent runtime corruption.
Safe Regular Expressions
When matching non-printable control characters, zero-width spaces (\u200b), or right-to-left marks in regular expressions, writing the explicit Unicode escape prevents invisible character bugs in your regex strings.
Preventing Source Code Git Merge Clashes
When teammates collaborate across Windows (often defaulting to CP-1252) and macOS/Linux (UTF-8), raw accented characters in source code files can trigger spurious Git merge conflicts or garbled build output. Escaping preserves code portability.
Bidirectional Conversion: Escaping vs. Unescaping
Escaping (Text β \uXXXX)
Takes human-readable text containing non-ASCII symbols, accents, or emojis and turns every special character into its hexadecimal code point. ASCII letters (A-Z, a-z, 0-9) remain untouched for clarity.
Unescaping (\uXXXX β Text)
Takes raw machine output filled with escape sequences like \u0048\u0065\u006c\u006c\u006f or JSON responses and converts them back into clean, readable sentences.
Frequently Asked Questions
Does this tool support HTML entities like © or ©?
This tool focuses specifically on programming language Unicode escape sequences (\uXXXX). For web markup entities, you can check our HTML Encoder/Decoder tool.
What is the difference between UTF-8 and Unicode?
Unicode is the universal registry mapping characters to numbers (code points). UTF-8 is a variable-length binary encoding scheme that translates those Unicode numbers into 1, 2, 3, or 4 bytes for transmission and disk storage.
Are zero-width characters detected by this tool?
Yes! Invisible characters like zero-width spaces (\u200B) or zero-width joiners (\u200D) become immediately visible when escaped into their hexadecimal sequences.