Unicode Code Points, UTF-8, UTF-16, And Escape Notation

Distinguish code points, scalar values, grapheme clusters, UTF-8 bytes, UTF-16 code units, surrogate pairs, normalization, and language-specific escapes.

Need To Check A Conversion?

Use the Text to Unicode tool for the direct action. This guide stays focused on the explanation, tradeoffs, mistakes, and reference context behind that task.

Four Counts That Are Not Synonyms

Concept What it counts Example for 😀
Grapheme cluster User-perceived text unit under segmentation rules Usually 1
Unicode code point Assigned numeric code position U+1F600, 1
UTF-16 code unit 16-bit encoding unit 2 surrogate units
UTF-8 byte 8-bit encoding unit 4 bytes

Scalar Values And Surrogates

Unicode scalar values cover U+0000 through U+D7FF and U+E000 through U+10FFFF. U+D800 through U+DFFF are surrogate code points reserved for UTF-16 and are not standalone scalar values.

A correct code-point tool iterates supplementary characters as one value. A strict U+ parser rejects standalone surrogates and values above U+10FFFF.

Notation Is Not One Universal Escape Grammar

U+1F600 is descriptive code-point notation. JavaScript, JSON, CSS, HTML, regular expressions, and programming languages use different escape grammars and may require UTF-16 surrogate pairs or another representation.

Converter247 Unicode to Text intentionally accepts only U+ hexadecimal tokens separated by whitespace or commas.

Normalization And Display

  • Precomposed and decomposed sequences can look the same while containing different code points.
  • A valid scalar may be invisible, unassigned, private-use, or unsupported by a font.
  • Code-point conversion does not detect confusables, grapheme boundaries, or intended meaning.

Related Tools

Encoding

Unicode to Text

Parse strict U+ scalar tokens and reject surrogates or out-of-range values.

 Encoding

Base64 Encode

Encode UTF-8 bytes as standard Base64 or unpadded base64url.

References

Related Guides In This Category

Base64 Encoding Explained: Bytes, UTF-8, Padding, And Base64URL

The byte-boundary and alphabet owner for both Base64 tools.

JWT Decode vs Verify: Why Readable Claims Are Still Untrusted

A distinct security-debugging owner for decode-only JWT inspection.

Browse More Encoding Guides

Need the broader support library for this topic? Visit Encoding Guides for related references, comparisons, and practical background before returning to the exact tool.

Explore The Full Category

Need another related task? Open Encoding Tools for the full tool set, quick-reference examples, and related category paths.