Text Utilities
Reveal invisible characters: spaces become ·, tabs become →, and line endings show ¶.
Input Text box — spaces, tabs, and line breaks are instantly marked in Visualized Output.Visualization Options checkboxes to toggle Show spaces (·), Show tabs (→), and Show line endings (¶) independently.·, tabs as →, and newlines as ¶, each rendered inline so the surrounding text stays readable.Copy Visualized to copy the marked-up output, or Copy to copy your original input unchanged.Clear any time to reset the input and start over.Invisible spaces and tabs at the end of a line cause lint warnings and noisy diffs. Seeing each one as · or → makes them impossible to miss.
Tell tabs apart from spaces at a glance, so you can spot mixed indentation before it breaks Python, YAML, or Makefiles.
Confirm where real line breaks (¶) sit and where blank lines actually exist — useful before pasting into spreadsheets, CLIs, or forms.
Pasted snippets often carry hidden characters. Visualize them to find the stray whitespace breaking a command, config, or string.
Share a visualization to show a teammate exactly where whitespace sits in a snippet, spec, or diff.
Everything runs in your browser. Nothing is uploaded, logged, or sent to a server — safe for sensitive snippets.
It replaces invisible whitespace with visible symbols: spaces become ·, tabs become →, and line feeds become ¶. Everything else in your text is left untouched.
Regular spaces ( ), tabs (\t), and line feeds (\n). The three checkboxes let you toggle each symbol on or off independently.
No. The visualization only changes what's displayed in Visualized Output. Your original text is preserved, and Copy returns it unchanged.
Copy Visualized copy?It copies the output with the marker symbols included as literal characters. Use it when you want the visible ·, →, and ¶ markers in your clipboard.
Only regular spaces, tabs, and line feeds are marked. Non-breaking spaces (U+00A0) and carriage returns (\r) are not marked and appear as-is.
¶?The pilcrow (¶) is a long-standing typographic convention for marking the end of a line or paragraph, still used by many editors' "show invisibles" mode.
No. All visualization happens locally in JavaScript. Your input is never uploaded, stored, or logged by any server.