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 Chinese characters and UTF-8 encoding online. Supports fast conversion between plain text strings and percent-encoding formats.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This converter changes between text and a specific readable byte notation: repeated \xHH escapes. Encoding starts with the text, converts it to UTF-8 bytes, then writes each byte as a backslash, lowercase x, and two uppercase hexadecimal digits. For example, A becomes \x41; the Chinese character 你 becomes \xE4\xBD\xA0. Each escape represents one byte, not one whole character.
That distinction matters for Chinese characters and emoji: one visible character can correspond to multiple UTF-8 bytes. Hexadecimal is a way to write byte values; Unicode code points use notation such as U+4F60 and answer a different question. This page does not produce URL percent encoding such as %E4%BD%A0.
For the reverse direction, the input should consist of byte values in \xHH form. The converter removes each literal \x marker, parses pairs of hex digits into bytes, and asks a UTF-8 decoder to read those bytes as text. UTF-8 uses sequences of one or more bytes per encoded character; a multibyte Chinese character must be supplied with all its byte escapes in the original order.
The Encoding Standard and RFC 3629 describe UTF-8 as an encoding between Unicode text values and bytes. This tool’s escape notation is a display format around those bytes, not a security operation. It is also narrower than a general-purpose hex decoder: it does not select arbitrary encodings or decode percent escapes.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Type or paste text in the upper field and choose the text-to-UTF-8 action. Read the resulting sequence as two-digit byte escapes; retain their order when copying.
Paste consecutive \xHH byte escapes in the UTF-8 field and choose the reverse action. Include each byte marker and exactly two hexadecimal digits per byte.
Compare the decoded text with the original. A Chinese character’s bytes normally span several escapes, so do not split or reorder them.
Use cases
See how the tool fits into real work and everyday tasks.
When a log includes a UTF-8 string in \xHH notation, decode the byte sequence to inspect the readable text, then compare it with the original record.
Encode a short Chinese word or punctuation mark and count the byte escapes. Use the result to distinguish byte encoding from a character’s Unicode code point.
Q&A
Find concise answers to common questions and confusing cases.
\xE4\xBD\xA0 the same as %E4%BD%A0?They can describe the same byte values, but they are different notations used in different contexts. This converter emits and expects backslash-x byte escapes, not URL percent encoding.
UTF-8 represents text as bytes, and a character outside the ASCII range can use multiple bytes. Each \xHH group displays one byte, so a character may take several groups.
U+4F60?No. The decoder expects pairs of hexadecimal digits preceded by \x markers. A Unicode code point is not the same as the character’s UTF-8 byte sequence.
Notes
Review scope, result limitations, and important precautions before use.
UTF-8 hex is encoding, not encryption: it provides no confidentiality or access control. Keep in mind that malformed or incomplete escape input may be rejected by the page’s format checks or may not decode as intended. This tool is meant for text byte inspection, not binary-file reconstruction, security testing, or proof that a byte sequence is safe to execute in another context.
Related
Discover related tools, collections, and available API capabilities.