⌘ K
text · U+XXXX · \\u escapes · surrogate-aware · live

Convert text and Unicode code points

Convert between text, Unicode code points (U+XXXX), and JavaScript \uXXXX / \u{XXXXX} escape sequences. Surrogate-pair aware — emoji and supplementary planes work. All processing runs locally.

Unicode Converter
Input
11 B
1 lines
Output
76 B
1 lines
Status
ready
live
Ratio
6.91×
out/in
input · text
output · code points
U+0048 U+00C3 U+00A9 U+006C U+006C U+006F U+0020 U+00F0 U+0178 U+0152 U+008D
Quick Start

How to convert Unicode

Code-point view uses U+XXXX notation; escape view uses JavaScript's \uXXXX (BMP) and \u{XXXXX} (supplementary). Both round-trip cleanly.

  1. 01

    Pick a direction

    Two encodings (U+ form and \\u escapes) and four directions total.

    Bytes flow through TextEncoder/TextDecoder for predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.

    modeUTF-8TextEncoderlosslesslive
    mode · raw bytestxt→cp · UTF-8
    text → U+XXXX
    loaded · UTF-8MIME · ready
  2. 02

    Paste input

    Text, code points, or JS escape strings — placeholder shows the format.

    Hash and signature operations call crypto.subtle from the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.

    inputWeb Cryptosubtledeterministiclive
    input · optionsHéllo · live
    Héllo
    options applied · livelive
  3. 03

    Live convert

    Surrogate-aware: emoji become a single \u{1F30D} escape, not a pair.

    Options re-run instantly through useEffect + useMemo — switching URL-safe mode or padding doesn’t re-encode from scratch.

    livememoisedoptionsinstantreactive
    out · encodedU+1F30D · ready
    U+0048 U+00E9
    encoded · livelossless
  4. 04

    Copy or download

    One click to clipboard. Download as .txt.

    Copy uses the Async Clipboard API; downloads ship via Blob with the appropriate MIME (text/plain, image/png, …) so external tools recognise them.

    exportclipboardblobMIME-correctclient-side
    ok · copiedready · done
    Copied
    shipped · ready to shipsuccess
Pro tips

Encoding without surprises

Always UTF-8 first

Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.

URL-safe vs standard Base64

Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.

Hashes aren’t passwords

SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.

Watch padding rules

Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.

Use Web Crypto for keys

Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.

JWT decode ≠ verify

Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.

Related toolsASCII ConverterText to HexHTML Entity LookupHTML EncoderPunycode ConverterURL Encoder
Use Cases

When to use Unicode tools

i18n, source escaping, debugging exotic characters.

Source literals

Embed exotic characters as \u escapes in JS/JSON. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.

RFC-compliant

Glyph debugging

Find out exactly which code point your terminal showed. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.

OpenSSL-matched

Mojibake recovery

Inspect the raw code points behind garbled text. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.

lossless

Test data

Pin specific code points in test fixtures. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.

byte-identical

Emoji lookup

Read the U+ value for any emoji you can paste. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.

spec-grade

Locale debugging

Confirm CJK / RTL / combining marks come through. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.

i18n
FAQ

Frequently asked questions

\uXXXX takes exactly 4 hex digits (BMP only — U+0000 to U+FFFF). \u{XXXXX} accepts any length and supports supplementary planes (emoji, ancient scripts) without surrogate pairs.
Encoding uses [...input] which iterates code points, so emoji become one escape. Decoding uses fromCodePoint, so supplementary characters round-trip cleanly.
Code-point mode: U+XXXX, 0xXXXX, or bare hex. Escape mode: \uXXXX and \u{XXXXX} — others pass through unchanged.
é (U+00E9) is one code point but encodes to two UTF-8 bytes. Code points count characters; bytes count storage.
No. Conversion runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!