We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Convert between native system encodings (like GBK, Big5) and ASCII representations to resolve garbled text and transmission issues.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Despite the labels “Native” and “ASCII,” this tool does not transcode file bytes between UTF-8, GBK, Big5, or other character sets. It changes the way text is written: ASCII characters remain as typed, while each non-ASCII UTF-16 code unit becomes a backslash, lowercase u, and four hexadecimal digits. For example, 中文 A becomes \u4e2d\u6587 A.
The reverse action replaces matching \uXXXX sequences with their corresponding code units. Hex digits may be uppercase or lowercase when reading escapes, but the prefix is lowercase u. Other notation such as U+4E2D or \u{4E2D} is not decoded by this pattern.
ECMAScript specifies Unicode escapes in string literals and represents supplementary characters using UTF-16 code units. Because this tool processes code units one at a time, an emoji such as 😀 becomes two escapes: \ud83d\ude00. These are character representations, not encryption and not the underlying UTF-8 bytes.
| Action | Input | Output |
|---|---|---|
| Native to ASCII | Hello 123 | Hello 123 |
| Native to ASCII | 你好 | \u4f60\u597d |
| ASCII to Native | \u4e2dA | 中A |
| Native to ASCII | 😀 | \ud83d\ude00 |
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Use the Native field for readable text or the ASCII field for text containing escapes. Both fields can be edited, pasted, cleared, and copied.
Choose Native to ASCII to escape non-ASCII code units, or ASCII to Native to replace recognized \uXXXX sequences with characters.
Verify that each escape has a complete prefix and four hexadecimal digits. Copy the result from its field when it is ready.
Use cases
See how the tool fits into real work and everyday tasks.
Turn non-ASCII text into visible escape sequences to examine how code units are represented. Before using the result in source code, check the syntax rules of that programming language.
If a copied string contains lowercase \u followed by four hex digits, decode it to inspect the corresponding characters, then compare with the original record.
Q&A
Find concise answers to common questions and confusing cases.
No. It works on text already present in the fields and changes non-ASCII characters to escape notation. It does not read file bytes, identify a source charset, or repair text decoded with the wrong charset.
The converter handles UTF-16 code units individually. A character outside the Basic Multilingual Plane is represented by a surrogate pair, so it appears as two four-digit escapes and can be converted back together.
No. The reverse conversion recognizes a backslash, lowercase u, and exactly four hexadecimal digits. Other forms remain ordinary text.
Notes
Review scope, result limitations, and important precautions before use.
Unicode escapes make characters visible in a different textual form; they do not hide data or restore characters already corrupted by incorrect decoding. If you need to convert an encoded file, identify its original bytes and charset and use a byte-aware decoding workflow. A sequence may also be interpreted by a programming language when placed in a string literal, so verify the destination language’s rules before embedding it. Decoding here returns characters rather than preserving the escape characters literally.
Related
Discover related tools, collections, and available API capabilities.