Unicode Escape Converter

Escape notation examples

Step-by-step calculation

1. 1Map every code point to the javascript escape syntax.
2. 2Every code point is escaped so the output is unambiguous; use a dedicated URL or HTML encoder when readable ASCII should be preserved.
3. 3Astral characters above U+FFFF use a surrogate pair or a code-point escape depending on the notation.

Quick check

Best for: Everyday conversions, debugging and code reviews

• Method: Paste the text or bytes into the text and encoding conversion tool and read the headline result.
• Precision: UTF-8 byte counts and Unicode code points are exact; display-width estimates are approximate.
• Safeguards: Cross-check one ASCII value, one accented value and one emoji before trusting a length rule.

Production implementation

Best for: Shipping code that reads, stores or transmits text

• Method: Use an explicit encoding, decode with errors="strict", and keep the byte and character layers separate.
• Precision: Match the exact encoding and normalization form used by the storage layer or wire protocol.
• Safeguards: Add tests for ASCII, CJK, emoji, combining marks, embedded NULs and lone surrogates.

Security review

Best for: Input validation, identifiers and URL handling

• Method: Normalize before comparing, reject unexpected control characters, and encode at the correct output context.
• Precision: Apply NFC for identifiers and the output-context encoder (HTML, URL, JSON) for the destination.
• Safeguards: Test homoglyphs, zero-width characters, double encoding and mixed-script input.

Escape syntax by language

Unicode encodings compared

Core relationship

escaped = Σ escape(codePoint); decoded = parse(escaped)

Verification

1. Decode the output with the stated encoding. 2. Round-trip it back to the original and compare. 3. Check the code-point, UTF-16 and UTF-8 counts independently. 4. Repeat with ASCII, accented text, CJK and one emoji.

ASCII plus emoji

Inputs

A😀 — JavaScript

Math

A → \u0041; 😀 → \u{1F600}

Result

\u0041\u{1F600}

JSON escape

Inputs

A😀 — JSON

Math

😀 is encoded as the surrogate pair \uD83D\uDE00

Result

\u0041\uD83D\uDE00

Decode HTML

Inputs

Hi

Math

0x48 = 72 → H; 0x69 = 105 → i

Result

Hi

Python

Python 3 strings are sequences of Unicode code points. Use len(text) for code points, len(text.encode('utf-8')) for UTF-8 bytes, and the unicodedata module for normalization. For unicode escape converter, prefer str.encode/decode with an explicit codec and errors='strict' so invalid input fails loudly. The standard library handles surrogate pairs and most legacy codecs; do not hand-roll UTF-8 parsing.

JavaScript / TypeScript

JavaScript strings are UTF-16 code units. Use Array.from(text) for code points, TextEncoder/TextDecoder for UTF-8, and Intl.Segmenter for grapheme clusters where available. For unicode escape converter, avoid split('') on text that may contain emoji; it splits surrogate pairs. Buffer and btoa are not available in browsers, so use TextEncoder plus a small Base64 helper.

Java / Kotlin

Java String.length() counts UTF-16 code units; codePointCount() counts code points. Use StandardCharsets.UTF_8 with getBytes and new String for byte conversion, and Normalizer for NFC/NFD. Kotlin’s String is the same UTF-16 representation. For unicode escape converter, specify the charset explicitly instead of relying on the platform default.

Go

Go strings are immutable byte sequences, usually UTF-8. Ranging over a string yields runes (code points); len(s) yields bytes. Use utf8.RuneCountInString for code points, []rune(s) for rune slices, and golang.org/x/text/unicode/norm for normalization. For unicode escape converter, validate with utf8.ValidString when the input may be malformed.

Rust

Rust strings are guaranteed UTF-8. Use .chars() for code points, .bytes() for bytes, and the unicode-segmentation crate for grapheme clusters. Slicing a String by byte index can panic if it lands inside a code point. For unicode escape converter, work with char_indices() when you need both position and character, and use encoding_rs for legacy encodings.

C / C++

C and C++ distinguish char, wchar_t, char16_t and char32_t. UTF-8 is usually stored in char arrays; convert with codecvt, ICU or a dedicated library rather than manual byte surgery. For unicode escape converter, keep the byte length separate from the display width and validate the input before conversion. Do not assume wchar_t is 32-bit on every platform.

Mistakes that break conversions

• Converting bytes without confirming their source encoding first.
• Assuming a character count equals a byte count or a UTF-16 length.
• Counting UTF-16 code units and calling them characters; JavaScript and Java lengths are not character counts.
• Decoding bytes with the wrong encoding, which produces mojibake instead of an error.
• Treating Base64, percent-encoding or HTML escaping as encryption; all three are reversible by anyone.
• Truncating between surrogate halves or inside a multi-byte UTF-8 sequence.

Pro tips for production code

• Record the encoding next to every stored or transmitted string.
• Round-trip a value before trusting a conversion.
• Specify the encoding at every boundary: file, network, database and display.
• Normalize identifiers with NFC before comparing them, and reject control or zero-width characters where they serve no purpose.
• Use byte length for storage limits and grapheme clusters for user-facing character limits.
• Prefer the platform encoder or serializer over hand-built escaping; it handles the edge cases you will forget.