Find invisible characters that interfere with text searches
Invisible characters can make copied names or codes fail searches despite looking identical. Inspect their reported positions before deciding which cleanup is appropriate for the text and its language.

How to use this tool
- Enter the affected text or add its file.
- Run inspection with removal disabled.
- Review positions, then rerun with removal if appropriate.
- Download the report and resulting text.
Choose the right settings
Start with removal disabled to inspect characters in the unchanged source text. Enabling removal deletes U+200B and BOM only, rather than every control character or space included in the inspection report.
- Supported input
- TXT,MD
- Available settings
- Remove only U+200B and BOM
Before you start
Choose content or file organization
Decide whether the task concerns wording, document structure, hidden information or filenames. Keep an original copy and check the supported input. Extracted plain text is useful for reviewing words, but it does not reproduce every picture, font, equation or page arrangement in the source.
Where separators, normalization or text cleanup are available, try a short passage with headings, unusual characters and meaningful line breaks. For inspection or file comparison, include all relevant source files instead of assuming the visible page tells the whole story. For renaming copies, confirm the selected order and keep the mapping between old and new names.
Before text cleanup, decide which spaces, repeated lines or characters carry meaning; a spelling difference may be intentional. Where the task is file inspection or organization, record the files included and the literal naming or comparison choices instead. To diagnose a problem, compare a short source passage or a known file pair with the result. Check an intermediate copy separately: a previous extraction, normalization or rename may explain the difference before this tool is involved.
Check meaning as well as appearance
Read the result’s beginning, ending and transitions between sections. Compare names, table values and special characters with the source. If the tool produces a report, locate sample findings in the original file; an inspection result is a review aid, not automatic removal of the identified information.
For downloadable file copies, verify names, extensions and correspondence to the originals before using them elsewhere. If wording is missing or jumbled, distinguish unsupported embedded content from an encoding or ordering issue. A filename change does not change the underlying format, and a matching appearance does not prove two files have identical bytes.
Example input and output
text with invisible characters → location/code-point reportExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Locate reported line and column positions in the source and review each code point. Test the cleaned text in the actual search box or input field to check whether the original problem is resolved.
If the result is different from what you expected
Characters remaining after removal may be outside the supported deletion set rather than an error. Direction controls or nonbreaking spaces can have intentional uses, so inspect the source language and formatting before changing them separately.
Limits to keep in mind
- Report line, position and code point. Optional removal affects only U+200B and BOM.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.