Uncover code points, grapheme boundaries, combining marks, invisible characters, mixed scripts and directionality controls. Your text stays in your browser.
01 / INPUT
Your text, decoded
Paste or type any Unicode text, including emoji sequences and right-to-left scripts.
Try an example
Private: no upload or remote Unicode API.UTF-8 text files up to 256 KB
02 / ANALYSIS
Character intelligence
Enter some text to explore its Unicode structure.
Code points—
Graphemes—
UTF-16 units—
UTF-8 bytes—
Flagged points—
TEXT HEALTH
Overview & findings
Flagged code points are signals to review, not proof of malicious content.
Script composition
Normalization status
Tip: a single displayed emoji can contain multiple code points. The grapheme count best approximates visible characters.
CODE POINT EXPLORER
Inspect individual scalars
UTF-16 indices are zero-based. Unicode code points are not the same as grapheme clusters.
#
Glyph
Code point
Unicode name
Script
Finding
Select a code point to see properties and offsets.
VISIBLE CHARACTER BOUNDARIES
Extended grapheme clusters
Explore character sequences such as combining accents, flags and emoji ZWJ sequences.
Select a grapheme to see its code-point sequence.
UNICODE NORMALIZATION
Four ways to normalize
NFC/NFD are canonical. NFKC/NFKD may fold compatibility characters and change semantics.
Applying a form changes the text in the editor; the previous version can be restored with Undo. Normalization does not strip bidi controls or make input safe.
WRITING SYSTEMS
Scripts & text direction
Script membership does not identify a language, author, or attack. Mixed scripts are common in legitimate text.
Directional control ledger
Scopes and matching offsets are approximate structural checks, not the full Unicode Bidirectional Algorithm. Lines and paragraph separators end scopes.
Look up any scalar
Enter a hexadecimal code point to see its properties without editing your text.
LEARN THE STRUCTURE
What Unicode inspection can reveal
U+
Code points ≠ characters
UTF-16 units, Unicode scalars and visual graphemes can have different counts, especially for emoji and combining marks.
↔
Direction can be invisible
Bidi controls affect display ordering. Inspect them before copying suspicious identifiers, logs or code.
◌
Normalization has trade-offs
Canonical normalization reconciles equivalent spellings; compatibility normalization may discard distinctions.
This is a diagnostic viewer, not a spoofing detector, Unicode confusables database, security sanitizer, or accessibility audit. The bundled name database uses Unicode 15.1; newer assigned characters may display as unknown until the dataset is updated.
Using Unicode Inspector
Inspect code points, grapheme boundaries and directional controls, compare normalization forms, and export text diagnostics for careful review.
Workflow
Enter or load text and inspect its code points and grapheme boundaries
compare normalization forms and review directional-control scope
export CSV or JSON diagnostics or a normalized UTF-8 text copy.
Example
Inspect a string containing a combining mark and a directional control, compare its code-point and grapheme views, then export a diagnostic report before sharing the source text.
Limits and data handling
Bundled character properties use Unicode 15.1, while browser normalization and Intl.Segmenter may use different versions. Script identification is not language detection, and mixed script is not necessarily malicious. The directional-control ledger is not full UAX #9 or confusable detection. Input is bounded to 30,000 code points and 256 KiB. Exported JSON includes source text, so handle it as sensitive.
FAQs
Does the inspector detect every spoofing or confusable string?
No. It reports selected Unicode properties and directional controls, not complete confusable or security analysis.
Does exported JSON omit the inspected text?
No. It includes source text; review it for private information before sharing.
