🌐 EN

👻 Invisible Character Remover

Find zero-width characters, BOM, non-breaking spaces (NBSP), and control characters hiding in text you can't see, get a table of counts by codepoint, and remove them all at once.

Characters found
0
Codepoint Name Count
GUIDE

Learn more

01

1. Why Invisible Characters Cause Trouble

Characters like the zero-width space (U+200B), joiner marks (U+200C, U+200D), and a leading BOM (U+FEFF) render as nothing on screen but are still real characters in the string. When they sneak into code or config files, they can break string equality checks, throw off regex matches, or cause JSON/YAML parse errors.

02

2. What Gets Detected

This tool detects zero-width characters (U+200B-U+200D, word joiner U+2060), the BOM (U+FEFF), the non-breaking space NBSP (U+00A0), directional marks (U+200E, U+200F), the soft hyphen (U+00AD), and C0/C1 control characters other than tab and newline. Each is listed in a table with its codepoint (U+XXXX), name, and occurrence count.

03

3. Where These Characters Come From

They commonly show up in text copied from a word processor, files opened with the wrong encoding, and zero-width characters some messaging apps or sites insert for watermarking or tracking. Left in source code or config files, they can show up as puzzling diffs or break a build — scanning with this tool before pasting anywhere sensitive is a cheap safety check.

Frequently asked questions

Is my text sent to a server?
No. All scanning and removal happens in your browser — this tool never calls a backend API.
Are tabs or regular line breaks removed too?
No. Tab (U+0009) and line breaks (U+000A, U+000D) are treated as normal formatting characters and excluded from detection and removal.
Does it detect full-width spaces?
The full-width space (U+3000) is generally considered a visible glyph and isn't currently in the detection list. Pair this with Remove Whitespace if you need to handle it too.