Decode a log escape
Read escaped text from server logs or diagnostic output.
\u0048\u0069
Hi
Free browser tool for logs, code, JSON, and broken text
Decode ASCII-safe escapes like \u0048, HTML entities, U+1F680, hex bytes, and mojibake into readable Unicode. Encode text back into Unicode formats without leaving this page.
Interactive tool
Ready
The format selector is used when encoding readable text into escapes or entities.
Before and after
A good converter should show the result immediately, keep users on the same URL, and make the page useful before any long explanation begins.
Landing page content rendered in HTML
An ASCII to Unicode converter turns ASCII-safe representations of text into the real Unicode characters people expect to read. Developers often see these escaped forms in JSON, logs, configuration files, databases, browser output, and API payloads.
This page keeps the converter, explanation, examples, supported formats, and FAQ on the same canonical URL so you can solve the problem without jumping between pages.
Paste the text you have, choose the mode that matches the problem, and convert in place. The result appears without opening a separate result page.
Use Unicode escapes, HTML entities, U+ notation, hex bytes, or mojibake copied from a log, API, JSON file, or old database export.
Decode to readable Unicode, encode readable text to escapes, convert HTML entities, or repair common mojibake.
Keep the result in the page, copy it to the clipboard, or download a plain text file for later use.
Selected result showcase
These hand-picked examples act like a result display area. They show what the tool can produce without creating low-quality indexed user pages.
Read escaped text from server logs or diagnostic output.
\u0048\u0069
Hi
Turn JSON-safe strings back into readable multilingual text.
\u4F60\u597D
ä½ å¥½
Convert entity text copied from HTML into the visible symbol.
☃
☃
Use U+ notation for emoji and symbols outside basic ASCII.
U+1F680
🚀
Fix common UTF-8 text that was accidentally read as Latin-1.
café
café
Create Unicode escape formats for code, docs, or tests.
A☃😀
\u0041\u2603\uD83D\uDE00
The converter focuses on formats people actually meet while debugging, parsing, and moving text across systems.
\u0048, \u{1F600}, \uD83D\uDE00, %u4F60, and U+1F680.
☃ and ☃ decode to readable symbols and can also be generated from input text.
\xE2\x98\x80 style byte sequences are decoded as UTF-8 when they form valid byte runs.
Common broken strings such as café can be reconstructed when the original bytes were UTF-8.
A single converter page should satisfy both quick tool intent and deeper search intent. These are the main situations this page is built for.
Decode escaped payloads so error messages, names, emoji, and symbols become readable during debugging.
Understand text returned by services that escape non-ASCII characters for transport or compatibility.
Convert numeric entities into real characters before editing or publishing content.
Generate stable escape strings for fixtures, snapshots, docs, and cross-language examples.
ASCII is a small character set for basic English letters, digits, and control characters. Unicode is the character standard that covers modern writing systems, emoji, symbols, and more. UTF-8 is a common way to store Unicode as bytes.
Many confusing strings happen when bytes, characters, and escape formats are mixed. This tool helps you inspect the representation and recover the text you meant to read.
Questions people ask
It decodes ASCII-safe text representations such as Unicode escapes, HTML entities, and U+ codes into readable Unicode. It can also encode readable text back into those formats.
Yes. It supports \uXXXX, \u{1F600}, surrogate pairs such as \uD83D\uDE00, and U+ notation for emoji and symbols.
Yes. Numeric decimal and hexadecimal entities such as ☃ and ☃ can be decoded into visible Unicode characters.
Mojibake often appears when UTF-8 bytes are interpreted as a different encoding. The repair mode tries to reconstruct the original UTF-8 text when that pattern is present.
Yes. The converter runs locally in your browser. The page is designed so analytics can record events without recording your pasted text.
Related converters may be added only when they solve a specific text conversion problem. This first version keeps the focus on ASCII to Unicode conversion.
Your pasted text stays in your browser. The converter does not require an account, does not upload TXT files, and does not store conversion history on our server.
The language preference is saved locally in your browser. If analytics is added later, it should record action events such as convert, copy, and download without sending input or output text.
Read the Privacy PolicyASCII to Unicode is a focused text conversion page for developers, writers, localization editors, QA testers, and operators who need readable Unicode from escaped or broken text.
The page is intentionally narrow: one converter, selected examples, supported formats, and practical explanations for common text encoding problems.
Use this tool for text inspection, debugging, content cleanup, and test data preparation. Verify important output before using it in production, legal, medical, or financial contexts.
You are responsible for the text you process and for following the rules of any system where the converted output is used.
Read the Terms of UseFor corrections, feature requests, accessibility issues, or privacy questions, contact: lisheng3698@gmail.com
When reporting a converter issue, include the conversion mode and expected output. Please do not include secrets or private text.
Open the Contact Page