Escape and unescape \u sequences

Only the characters that need escaping are escaped, so a config file stays legible after the conversion.

How Unicode Escape works

Bytes are transformed with the browser's own encoders. Encoding and decoding are reversible, so the page can prove the round trip without keeping a copy. That matters when the payload is a token or a credential: a round trip you can see is safer than one you have to trust.

That is the whole architecture: static files, one script, no upload endpoint to leak or log. Close the tab and the work is gone.

Good to know

  • Works offline once loaded, including on flights and in locked-down networks.
  • No file size limit beyond your device's own memory.
  • Free to use, with no account and no usage counter.
  • Results are produced locally, so they are not logged or shared with anyone.

Questions

Why are only some characters escaped?

Because escaping ASCII too would make the output unreadable and no larger in benefit. Keys, punctuation and English text stay as they are.

How are emoji handled?

As a surrogate pair — two \u escapes, which is what JavaScript and Java expect. The newer \u{1F600} braces form is accepted on the way back.

Will this break my JSON?

No. \u escapes are valid inside JSON strings, which is exactly where they are usually needed.

Does it store my text?

No.

Keep going

More encoding tools