JSON string & Unicode helpers

Client

One workspace for minifying, escaping quotes for concatenation, turning \uXXXX into real characters (and back), and swapping common CJK punctuation inside string values. Use Load example to try it immediately.

Learn more: strings inside JSON

This page helps with escaping, minifying string payloads, and character encoding details when JSON lives inside other text or crosses locales.

Escaping and embedding

Inside JSON, special characters in strings must be escaped—quotes, newlines, and backslashes are the usual suspects. When you embed JSON in HTML, SQL, or another language, you may need an extra layer of escaping; helpers here reduce trial and error.

Unicode

JSON text is Unicode. Tools that show UTF-8 bytes or code points help when debugging mojibake or comparing what your editor displays with what travels on the wire.

Function introduction

Actions: [Minify][Escape quotes][Minify + escape][Unescape quotes][Unicode → UTF-8][UTF-8 → Unicode][CJK punct → ASCII]

  • Parses JSON and rewrites it on one line without extra whitespace.
  • Escapes backslashes and double quotes so you can paste the snippet inside a quoted string or concatenate safely.
  • Runs Minify, then Escape quotes—same as doing both steps in order.
  • Reverses Escape quotes: turns \" into " and \\ into \.
  • Parses JSON and pretty-prints; \uXXXX sequences in string values become real characters in the output.
  • Parses JSON and pretty-prints with non-ASCII in string values written as \uXXXX (surrogate pairs as two escapes).
  • Parses JSON and rewrites string values only: common full-width / CJK punctuation becomes ASCII-style equivalents (e.g. ， → ,).

Editor & actions

?

Minify and Unicode → UTF-8 require valid JSON. Escape / Unescape work on raw text (not JSON-aware). Use Load example to try a sample payload.

Paste JSON above, then pick an action—parsing and rewriting stay in your browser.

Common use cases

  • Minify JSON before pasting it into env vars, curl snippets, or inline scripts where whitespace costs space.
  • Escape or unescape quotes when wrapping JSON inside another JSON string or SQL/CLI literal.
  • Convert \uXXXX escapes to real characters (or back) when inspecting API payloads or fixing mojibake in string values.

Common mistakes to avoid

  • Double-escaping when copying through multiple layers

    Each hop (shell, ORM, template) may add escapes. If the output looks like \" everywhere, re-check the outer wrapper instead of escaping again in the tool.

  • Treating Unicode normalization as a security boundary

    Swapping punctuation or decoding escapes changes bytes. Do not assume hashes or signatures stay the same after normalization.

FAQ

Does string processing upload my JSON?

No. Minify, escape, and Unicode helpers run entirely in your browser tab.

Will minifying change my data?

It removes whitespace between tokens. String contents and number values stay the same; only layout changes.

More tools

Related utilities you can open in another tab—mostly client-side.