UUID Studio

UUID Studio

JSON Unicode Escape

Emit ASCII-safe JSON with \u escapes.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • Unicode text 
    {"greeting":"Hello 世界"}

About JSON Unicode Escape

Some transports and legacy parsers only trust ASCII, but real-world content is full of accents, emoji, and non-Latin scripts. Sending raw UTF-8 through one of those pipes can mean silent corruption.

This re-encodes a JSON string's non-ASCII characters as \uXXXX escapes, producing output that's still perfectly valid JSON.parse input but safe for ASCII-only systems and older log pipelines.

FAQ

Is the output still valid JSON?
Yes - escaped output remains valid JSON.parse input.