Are zero width characters always malicious?
No. They are valid in many languages and emoji sequences, but risky when unexpected.
Zero Width Characters
Zero width joiners and separators are not visible but still change text behavior.
Quick checks
- Catch hidden separators in IDs and tokens.
- Prevent bypasses in allow/block list filters.
- Normalize safely after inspection.
Unicode Inspector
Inspect pasted text for invisible or risky Unicode characters, visualize findings, and generate cleaned output entirely in your browser.
Drop .txt/.csv/.json here
or click to choose a file (max 2 MB)
Results
| Symbol | Category | Unicode name | Code point | Occurrences | Positions | Actions |
|---|---|---|---|---|---|---|
No findings No matching characters found in the current analysis snapshot. | ||||||
Homoglyph Detector
Detect mixed-script and confusable lookalike tokens before trusting identifiers or domains.
| Token | Scripts | Risk | Confusables | Positions |
|---|---|---|---|---|
No homoglyph risks detected. | ||||
Bidi and Trojan Source
Inspect bidirectional control sequences that can hide true token order in code, configs, and logs.
| Type | Risk | Range | Controls count | Details |
|---|---|---|---|---|
No dangerous bidi sequences detected. | ||||
Overlay view
Cleaning actions
Output
Advanced JSON report
Positions and ranges can increase payload size.
Share link
Raw text is never included in the report or share link.
FAQ
What is the common operational risk?
Search and equality logic can miss matches because hidden characters split strings.