👁️ Onzichtbare-tekens-tool

Onzichtbare tekens, zoals zero-width spaces, vaste spaties of een byte order mark (BOM), sluipen vaak in gekopieerde tekst en veroorzaken lastig te vinden problemen bij weergave, zoeken en gegevensverwerking. Deze tool scant je tekst, toont elk verborgen teken met positie, Unicode-codepunt en naam, en kan ze allemaal met één klik verwijderen. De verwerking gebeurt volledig in je browser.

How to Use This Tool

Plak je tekst in het veld en klik op ‘Tekens detecteren’. Je ziet een tabel met alle gevonden onzichtbare tekens. Met ‘Verwijderen en opschonen’ krijg je een schone versie die je kunt kopiëren.

What This Tool Checks

De tool herkent de meest voorkomende onzichtbare Unicode-tekens: zero-width space, zero-width joiner en non-joiner, BOM, vaste spaties en andere Unicode-spaties, plus stuurtekens.

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

Controleer tekst die je uit pdf, Word of webpagina’s hebt gekopieerd voordat je die publiceert of importeert. Zo voorkom je mislukte zoekopdrachten, opmaakproblemen en ongeldige data.

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

Een veelgemaakte fout is aannemen dat tekst schoon is omdat die er normaal uitziet: onzichtbare tekens zijn per definitie niet zichtbaar. Controleer bij twijfel altijd.