4629 · Text · v1.0.0

Unicode Explorer

See the structure inside a glyph.

Inspect code points, names, categories, grapheme boundaries, UTF encodings and normalization forms without confusing visible glyphs with storage units.

Processed locally in your browser

Normalization form

Text-only workspace. Never executes input. General limit: 200,000 UTF-16 units per editor; some operations have tighter limits.

INPUT13 UTF-16

OUTPUT0 UTF-16

Private session · history disabled

Opt in to store up to five recent text transformations on this device. Never stored on an account or synchronized. Files are never included. Disable history stops new saves; Clear history deletes saved items.

Enable local history for this session

How to use Unicode Explorer

Paste input, select a command and its options, then run the transformation. Review diagnostics before copying or downloading the result. Input is not executed.

A code point is a Unicode numeric value. A UTF-16 code unit is 16 bits; supplementary characters need two. A grapheme is a user-perceived text unit and can contain many code points. A glyph is a rendered shape and depends on the font. Grapheme segmentation uses the browser’s Unicode implementation.

Privacy and boundaries

Editor contents stay in your browser. Transformations run in a disposable worker and are never sent to a formatting or AI service. History starts disabled; enabling it writes text to local browser storage only. Clearing that history removes this tool’s saved entries, not data saved by other applications. The surrounding website may load its normal navigation and analytics, but the utility workspace is excluded from content-interaction capture.

Use the labeled operation selector for the available capabilities. Keyboard users can reach every control with Tab; Ctrl or Command plus K opens the command palette. Copy requires clipboard permission. Download creates a local text file. Clear removes the current workspace; it does not automatically delete an opted-in history. Inputs and outputs are always rendered as text, never as a runnable preview.

What is Unicode?

Unicode assigns code points and properties to characters. UTF-8, UTF-16 and UTF-32 are different ways of representing those values, not different alphabets.

FIELD GUIDE · PURPOSE AND BOUNDARIES

Unicode Explorer: practical use and context

Unicode Explorer makes the structure of text visible: code points, names, categories, UTF representations and grapheme boundaries. It is intended for localization, interface testing and careful diagnosis of visually similar strings.

↑ Back to the application

A glowing globe circled by glass tiles bearing glyphs from several writing systems — Application artwork reused from its publication image family. The interactive interface is above.

Purpose and practical uses

Use this workspace when a name looks correct but fails comparison, when an emoji appears to count as several characters, or when a copied string contains an unexpected invisible separator. A rendered glyph is not a reliable description of storage. Fonts can draw different code-point sequences similarly, while the same sequence may look different on another device.

A deliberate workflow

Paste the exact sample and inspect it before choosing normalization. Read the code-point and encoding information alongside the displayed text. Then select NFC, NFD, NFKC or NFKD only if your downstream application calls for that form. Keep the original so you can compare what changed. Normalization is a transformation, not a cosmetic display toggle.

Canonical forms address canonical equivalents; compatibility forms can remove distinctions that matter in identifiers, scholarly transcription or typography. Decide what equivalence means for your task before applying a form to real data. This tool reports structure, but it cannot choose a universal text-identity policy for an account system or database.

A practical example

Inspect the included sample with a combining accent, an emoji sequence and a supplementary musical symbol. Compare the perceived characters with the code points and UTF-16 units. Normalize the accented part to NFC, then inspect again. The useful observation is the change in representation, not an assumption that one display is more correct than the other.

Read the result correctly

UTF-8 measures bytes, UTF-16 measures code units, and a grapheme groups text as a user may perceive it. These counts answer different questions. A field limit specified in bytes cannot safely be enforced by counting visible symbols. Likewise, slicing a string at an arbitrary code-unit position can break a surrogate pair or split a grapheme.

Limits and troubleshooting

Grapheme boundaries follow the browser’s Unicode implementation, so platform versions can matter. Character inspection is not a complete confusable-character, spoofing or identifier-security audit. It also does not transliterate text into another language. If a suspicious string will become a public URL or username, combine this inspection with the explicit validation policy of that system.

Services

Company

Resources