Non-Breaking Space

Non-breaking spaces look like regular spaces but change wrapping and parser behavior.

Quick checks

  • Spot copy/paste whitespace drift.
  • Fix equality checks that fail unexpectedly.
  • Normalize content before storage.

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

SymbolCategoryUnicode nameCode pointOccurrencesPositionsActions

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.

TokenScriptsRiskConfusablesPositions

No homoglyph risks detected.

Bidi and Trojan Source

Inspect bidirectional control sequences that can hide true token order in code, configs, and logs.

TypeRiskRangeControls countDetails

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

Why does wrapping look inconsistent?

Non-breaking spaces keep words together, which changes line breaks in UI and documents.

Can NBSP break parsing?

Yes. Tokenizers and strict split logic may treat NBSP differently from regular space.