TFT

Unicode Character Inspector

Inspect every character in your text. See detailed Unicode properties like code point, category, script, and bidirectional class for each character.

Unicode Character Inspector

Analyze each character in a text string for Unicode properties

How the Unicode Character Inspector Works

Paste or type any text into the input field. Click Inspect to analyze each character. The tool displays a table with detailed Unicode properties for every character in your text.

Each row shows the character itself, its code point in U+XXXX format, the official Unicode name, general category (letter, number, symbol, etc.), and the Unicode block it belongs to. This reveals exactly what characters you're working with.

Click the copy button on any row to copy that specific character. Useful for extracting individual characters from complex text or copying characters that are hard to type directly.

When You'd Actually Use This

Debugging text encoding issues

Text displays wrong? Inspect reveals the actual characters. That "quote mark" might be a curly quote (U+201C) instead of straight quote (U+0022).

Finding specific Unicode characters

Need the exact code point for a symbol? Type or paste it, inspect to get U+221E for infinity. Use the code point in documentation or code.

Analyzing text for security review

Check for homoglyph attacks. Cyrillic "a" (U+0430) looks like Latin "a" (U+0061). Inspection reveals the difference in mixed-script text.

Working with emoji and special symbols

Emoji are complex. Family emoji use ZWJ sequences. Skin tones use modifiers. Inspection shows the component characters and their relationships.

Developing fonts or text rendering

Font developers need to know which blocks their font covers. Inspect sample text to verify character coverage and identify missing glyphs.

Learning about Unicode structure

Students can explore how Unicode organizes characters. See which block a character belongs to, understand categories like "Math Symbol" vs "Letter".

What to Know Before Using

Some characters are invisible.Zero-width space, combining marks, and format characters don't display but affect text. They show in the table with their code points and names.

Emoji may be sequences.A single visible emoji like "" can be multiple code points. The inspector shows each component - base emoji, skin tone modifier, ZWJ, etc.

Category names are technical."Lu" means Uppercase Letter, "Nd" means Decimal Number. These are Unicode general categories used for character classification in algorithms.

Block names show character origin.Blocks group related characters. "Greek and Coptic" contains Greek letters. "Emoticons" has emoji faces. Some characters span multiple blocks.

Pro tip: When debugging text issues, inspect both the expected and problematic strings side by side. Differences in code points reveal the root cause.

Common Questions

What does U+ mean in code points?

U+ is the standard notation for Unicode code points. U+0041 means the character at hexadecimal position 41, which is "A". The U stands for Unicode.

Why are some character names generic?

Not all characters have unique names in the tool's database. Private use characters, unassigned code points, and rare symbols show generic names.

How do I find characters by code point?

This tool inspects existing text. To find characters by code point, use a character map or enter the character directly if you can type it.

What are combining characters?

Combining marks modify the previous character. Accents, diacritics, and emoji modifiers are combining. They stack on the base character visually.

Can this detect bidirectional text?

The inspector shows character properties but doesn't visualize bidirectional ordering. RTL characters like Arabic have their own category and block.

Why do some characters show as boxes?

Your system lacks a font for that character's block. The code point and name still display correctly. Install fonts that support the script.

Is there a limit to how much text I can inspect?

Very long text creates large tables. Keep input under a few thousand characters for best performance. For longer text, inspect sections separately.