👁️ Invisible Character Tool

Invisible characters are real Unicode code points that occupy space in a string but render as nothing you can see — zero-width spaces, zero-width joiners, byte-order marks, non-breaking spaces, and dozens of other formatting and control characters. They ship in text all the time: pasted from PDFs and design tools, injected by rich-text editors, embedded by translation software, or added on purpose to disguise plagiarism, evade spam filters, or break search matching. When one lands in a URL slug, a keyword, a schema field, a CSV cell, an API payload, or a piece of source code, the human eye sees nothing wrong while the machine sees a different string. This tool scans any text you paste in, reports every invisible character it finds with its position, Unicode code point, and human-readable name, and — with one click — returns a clean copy with the invisibles stripped out.

How to Use This Tool

Paste the text you want to check into the box and press Detect Characters. The tool scans the string in your browser and lists every invisible character it found: where it appears (character index), its Unicode code point in U+XXXX form, its official Unicode name where known, and how many times that character occurs. To get a cleaned version, press Remove & Clean — the tool removes the detected invisibles and shows the cleaned text in a copyable box below. Copy Cleaned Text puts the result on your clipboard. Reset clears everything so you can check another string. Nothing is uploaded: the entire scan runs in your browser using standard JavaScript string APIs, and no version of your text ever leaves your device.

What This Tool Checks

The scanner recognises the common families of invisible and problematic whitespace: zero-width space (U+200B), zero-width non-joiner (U+200C), zero-width joiner (U+200D), word joiner (U+2060), zero-width no-break space (U+FEFF, also the BOM), left-to-right and right-to-left marks and embedding controls (U+200E, U+200F, U+202A–U+202E, U+2066–U+2069), Mongolian vowel separator (U+180E), soft hyphen (U+00AD), non-breaking space (U+00A0), narrow no-break space (U+202F), figure/punctuation/hair/six-per-em spaces and the other U+2000–U+200A whitespace variants, ideographic space (U+3000), Hangul filler (U+3164), and additional formatting/tag characters up to U+E007F. It does not flag ordinary ASCII space, newline, or tab — those are usually intentional.

Understanding Your Results

A zero count is what you want for URL slugs, schema property values, JSON keys, keyword targets, product SKUs, and anywhere else a machine needs to match the string exactly. Small counts (a single BOM at the start of the file, a few non-breaking spaces inside a translated paragraph) are usually harmless in flowing prose but should still be removed from anything a computer will parse. High counts distributed evenly through the text — especially zero-width spaces between every other letter — are a strong indicator that the text has been deliberately obfuscated, either to bypass a plagiarism check, hide an origin, or evade a keyword filter. The Position column tells you exactly where each character sits so you can trace back to its source (a specific paragraph in your CMS, a particular row in your CSV, a broken import).

How to Fix Common Problems

For a one-off cleanup, use the Remove & Clean button and paste the cleaned text back where you found it. If invisibles keep coming back, fix them at the source: check whether your rich-text editor is set to "keep source formatting" on paste (turn it off), whether a translation plugin is inserting formatting marks it doesn't need, whether the file is being saved with a UTF-8 BOM by an editor that adds one by default (most modern editors let you disable this), and whether a CSV import is preserving non-breaking spaces from spreadsheet cells. For code, most editors can show invisible characters via a "render whitespace" or "show invisible characters" setting, and most linters can flag them automatically — turn those on.

SEO Best Practices

Run URL slugs and schema field values through this tool before publishing anything you care about ranking for — an invisible character in a canonical URL or a schema @id can silently break equality checks. Clean text pulled from PDFs, Word documents, or emails before pasting it into your CMS. When accepting user-submitted content (comments, forum posts, product reviews), strip invisibles server-side as part of your sanitisation pipeline so an attacker can't use them to bypass a content filter or duplicate a legitimate username. Save files as UTF-8 without BOM unless you have a specific reason to include one.

Example

A product page title that reads "Wireless Headphones" but was pasted from a design brief may contain a zero-width space between "Wireless" and "Headphones" — the tool will report one invisible character at position 8, code point U+200B, name ZERO WIDTH SPACE, count 1. Removing it makes the string identical to what a searcher would type. As a second example, a CSV export from an accounting tool often has a byte-order mark (U+FEFF) at position 0 of the very first cell of the first row, which confuses parsers that don't strip BOMs — cleaning the file once before import fixes the problem for good.

Common Mistakes to Avoid

Don't assume "empty" fields are actually empty — a field containing a single zero-width space has length 1 but looks empty in every editor. Don't use invisible characters yourself to try to bypass duplicate-content detection; modern search engines and plagiarism checkers normalise text before comparing, so it doesn't work and can look like manipulation. Don't treat every non-ASCII character as bad — proper Unicode letters, curly quotes, em dashes, and emoji are all legitimate and should stay; this tool only targets characters that render as nothing visible.