See what the string contains

Unicode Tools

Count, normalize, and inspect text below the visible surface. These tools distinguish code units, code points, graphemes, and UTF-8 bytes while flagging selected hidden controls.

10 available nowEligible for indexing

Start with the task

Available tools

01 · inspect

Unicode Character Inspector

Inspect code points, offsets, UTF-8 bytes, scripts, categories, and risk flags character by character.

02 · inspect

Unicode Normalizer

Compare NFC, NFD, NFKC, and NFKD output with explicit compatibility warnings.

03 · inspect

Invisible Character Detector

Locate zero-width, suspicious invisible, and bidirectional control characters by exact offset.

04 · inspect

UTF-8 Byte Counter

Compare UTF-8 bytes, code points, graphemes, and UTF-16 units without uploading the text.

05 · inspect

Character Counter

Count characters, words, lines, code points, and bytes with clear, distinct length models.

06 · inspect

Grapheme Counter

Count user-perceived characters (graphemes) and compare them to code points and UTF-16 units.

07 · inspect

Zero-Width Character Detector

Find zero-width and invisible characters that are hidden in text, with their positions.

08 · inspect

Non-ASCII Character Detector

Find characters outside the ASCII range, with their script and position, for data cleaning.

09 · inspect

Mixed Script Detector

Detect when text mixes writing systems, which can signal spoofing or accidental substitution.

10 · inspect

Confusable Character Checker

Flag characters that imitate ASCII letters, naming the letter each one mimics.

How GlyphSift decides

Principles for this collection

Length has several meanings

A visible grapheme may contain multiple code points and many encoded bytes.

Non-ASCII is not a verdict

Most languages and emoji are non-ASCII; context determines the risk.

Normalization is not sanitization

Compatibility folding does not replace mixed-script, bidi, or invisible checks.

Recommended next step

Start with the character inspector when the cause is unknown; use a focused counter or detector when the destination rule is known.

Open the shared workbench