JSON Tools for AI Developers · Runs locally

For AI developers JSON Workbench

Natural language generation · Schema · Zod · OpenAPI · Function Calling · MCP · 30+ tools

JSON Unicode

Some APIs and logs write Chinese as \u4e2d\u6587. That is hard to read and hard to compare with product copy.

Chinese → Unicode helps when a config only accepts ASCII. The other direction restores a readable string.

It handles common \uXXXX. Surrogate pairs and mixed HTML entities need an extra check.

Conversion stays local. Copy and nicknames don't need to be redacted first.

When you must convert to \u

Legacy systems, some mail gateways, or ASCII-only config files require escaped Chinese. Modern JSON can hold UTF-8 — skip the convert when you can.

Check emoji

Some emoji are surrogate pairs and may render differently across fonts. For important copy, check a real client after convert.

How to use it

Paste Chinese or \uXXXX text.
Choose Chinese → Unicode or Unicode → Chinese.
Confirm the JSON structure was not torn apart — only string writing changed.
Copy the result. Use Escape if you still need quotes and newlines.
If HTML entities are mixed in, decode them first, then convert Unicode.

When to use it

Read a legacy API that only emits \u escapes.
Turn copy into an ASCII-safe JSON fragment.
Check that product copy and the API return the same characters.
Pair with Format: restore Chinese, then expand to read.

Keep in mind

Fields are not reordered. Only string escape writing changes.
Spot-check characters outside the BMP.
Data stays in the browser.

FAQ

Can emoji convert?

Common BMP characters are fine. Some emoji are surrogate pairs — check the display after convert.

Does it change JSON structure?

It only changes escape writing inside strings. Fields are not reordered.

How is this different from Escape?

Escape handles quotes and newlines. This page is for Unicode code-point writing.

Is the text uploaded?

No.

Can \u{1F600} decode?

Common \uXXXX is the focus. Convert ES6 code-point form to paired \u first.

Is it case-sensitive?

\u4e2d and \u4E2D are usually both recognized.

Can I encode only Chinese and keep English?

Chinese → Unicode usually encodes non-ASCII only. Trust this page's output.

Should I use Clean with this?

Clean BOM and junk first, then convert Unicode, so you fail parse one less time.