Skip to main content

About the Site

About CleanPastedText

CleanPastedText editorial · Updated

A visible report for invisible problems

A word can look correct while containing a zero-width space that breaks a search. Two spaces can look identical while only one allows a line break. The cleaner reports character names and code points so you can inspect the cause instead of guessing from appearance.

Detection examines the original input before normalization. Each result lists supported characters that were removed, replaced, or kept, along with counts. The output preview lets you review the result before copying or downloading it.

How the rules are checked

The cleaning rules are covered by automated tests that run on every change, including each preset and the emoji sequences the cleaner must leave intact. The methodology page documents each rule, which preset applies it, and what it changes.

If a result looks wrong, the change report is the fastest way to find out why: it lists each character by name and code point, such as U+200B, along with the action taken. Switching to Safe Clean or Keep Typography narrows the changes to hidden characters and spacing.

What the results can tell you

A detection identifies a character; it does not identify its author or why it was inserted. Ordinary documents, languages, and emoji use many of the same characters. An empty report means the supported checks found no matches, not that the text has passed an exhaustive security review or an AI authorship test.

Review output carefully for multilingual text and code. Unicode normalization can change compatibility characters, and removing join controls can affect some writing systems. The cleaning methodology explains the settings and limitations. The privacy and data handling page explains what is processed locally and how site analytics work.

Continue reading

Related guides & tools