Zum Inhalt springen
uencoder

Codieren Unicode text into an ASCII-safe representation

Konvertieren text containing non-ASCII characters (emoji, CJK, accents) into pure-ASCII forms like \uXXXX escapes or HTML entities so it survives ASCII-only channels.

  1. 1

    Legacy systems, source-code comments, and some APIs reject non-ASCII bytes. Unicode escape sequences (\u00e9 for é) and HTML entities (é) are two ASCII-only encodings that preserve the exact character and are reversible.

  2. 2
    Unicode-Konverter →

    Paste text with accents or emoji. The tool outputs \uXXXX escape sequences that any JSON parser or JS engine reads back identically.

  3. 3
    HTML-Entity-Kodierer →

    For HTML contexts, encode the same text as numeric entities (é) so it renders correctly in any ASCII-only HTML file.

  4. 4

    Choose the escape style based on destination: \uXXXX for JSON/JS source, \xXX for single-byte strings, &#xNNNN; for HTML, and U+NNNN for documentation.

Häufige Fragen

Why do some characters become two \u escapes?
Characters outside the Basic Multilingual Plane (emoji, rare CJK) are encoded as surrogate pairs — two \uXXXX sequences that together represent one code point. This is standard JSON behavior.
Are HTML entities and Unicode escapes interchangeable?
They encode the same characters but for different parsers. HTML entities work in HTML/XML; \u escapes work in JSON/JS. Using the wrong one means the literal text shows up unrendered.

Workflows, die diese Aufgabe lösen

Verwandte Tools