Unicode Inspector

Unicode Inspector is a browser utility that identifies the code points and properties inside text. Reveal the encoded building blocks that sit beneath a word, symbol, emoji, or apparently blank string. The report separates code points from what your eye perceives on screen.

Unit inspectedUnicode code point
Maximum input2,000 characters
Network transferNone

Analyze your own text

Private processingYour input remains in this browser tab.
Try a sample:
Maximum 2,000 characters · no upload

Enter text or choose a sample to generate a detailed report.

What an inspection can answer

Visual similarity is unreliable evidence. Inspection replaces a guess about appearance with an exact inventory of encoded values.

  • Confirm whether a mark is one code point or a multi-part sequence.
  • Expose spaces, joiners, variation selectors, and combining marks that may be invisible.
  • Compare UTF-8 byte sequences when text changes between systems.
  • Copy an exact U+ identifier into documentation, bug reports, or database checks.

How to interpret each result column

A row describes one code point. Several adjacent rows can still form a single grapheme—the unit a reader experiences as one character.

ColumnWhat it measuresUseful questionImportant boundary
PositionOrder in the code-point sequenceWhere does the unexpected value occur?It is not a byte offset.
CharacterA visible stand-in for the valueDoes the item render at all?Blank output can be legitimate.
Unicode nameThe stable character labelWhich assigned value is this?A formal name is not cultural interpretation.
Code pointThe scalar value written as U+hexCan two lookalikes be distinguished?Sequences require more than one U+ value.
UTF-8Bytes used by UTF-8 encodingDid an encoding boundary alter the text?Bytes do not describe typography.

Four strings that reward inspection

These cases look simple, yet their internal structures differ. Choose a sample above to verify them in the live report.

SampleUnderlying structureWhy it matters
caféUsually four code points, but the final é may also decomposeSearch and equality checks can disagree without a normalization policy.
👨‍👩‍👧‍👦Four people joined by three zero width joinersRemoving an unseen joiner changes one family glyph into separate emoji.
🇭🇰Two regional indicator code pointsUnsupported software can display letter-like fallbacks rather than a flag.
A‍BTwo letters with U+200D between themInvisible format characters can survive copying and affect processing.

A reliable inspection routine

Follow the sequence from evidence to policy. Each stage guards against a different class of Unicode mistake.

  1. Capture

    Paste the original text without retyping it. Retyping can erase the very code point you need to diagnose.

  2. Inventory

    Read every U+ value in order and note format controls, marks, selectors, or repeated spaces.

  3. Compare

    Inspect a known-good specimen separately. Compare encoded values, not screenshots or glyph shapes.

  4. Decide

    Apply the rule appropriate to your system: preserve, normalize, reject, or replace. Context determines the safe action.

Questions people ask about unicode inspector

Why does one visible emoji produce several rows?

Emoji can be grapheme clusters assembled from base emoji, modifiers, selectors, regional indicators, keycap marks, or joiners. The inspector reports the encoded ingredients rather than collapsing the cluster.

Why is the Unicode name unavailable for some input?

The browser tool ships a compact name map for this site's catalog. It still reports the exact code point and bytes for values outside that map; consult the Unicode Character Database for the authoritative name.

Can this detect homoglyph attacks automatically?

No. It exposes differences that appearance can conceal, but a complete identifier defense also needs script restrictions, confusable-data checks, and application-specific rules.

Does the tool upload pasted text?

No. JavaScript performs the inspection in the current browser tab. The page does not send the textarea value to a site endpoint.

Move to the next diagnostic

Standards behind this tool

The browser output is designed as a practical diagnostic, while normative definitions belong to the standards publishers below.

CopiedSaved to clipboard