Why does trimming fail in some systems?
Different runtimes and libraries treat Unicode whitespace classes differently.
Whitespace Characters
Unicode includes many whitespace characters that look similar but behave differently across tools.
Quick checks
- Spot tabs, NBSP, narrow NBSP, and ideographic spaces.
- Fix mismatches in search, split, and deduplication.
- Normalize whitespace before indexing and export.
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
Is replacing all whitespace with plain space safe?
Not always. Some contexts require preserved line breaks or tabs for readability and semantics.
When should I normalize whitespace?
Normalize at ingestion boundaries, then keep a predictable internal format across your pipeline.