Paraphrased AI text
AI humanizer detector
“Humanizer” tools rewrite chatbot text to dodge detectors. Some of their tricks leave traces of their own. Paste a text to look for both the original AI patterns and the humanizer’s fingerprints.
Free · no sign-up · your file never leaves your device
Your text, with the signs marked
Hover a highlight to see which sign it matched. Invisible characters are shown as labelled boxes.
An arms race with fingerprints
Once detectors appeared, so did tools promising to defeat them. A humanizer takes the polished, predictable output of a chatbot and makes it less predictable: it swaps common words for rarer ones, varies sentence length, adds contractions and filler, and sometimes introduces deliberate small errors. More aggressive tools tamper with the characters themselves, inserting invisible Unicode between letters or replacing Latin letters with identical-looking Cyrillic or Greek ones, so that detectors reading the text as tokens see gibberish.
Each trick removes one kind of evidence and adds another. GPTTrace looks for both.
What survives humanizing
Structure
Rewriting at the word or sentence level rarely changes the shape of the answer: an introduction that restates the question, three balanced points, a tidy conclusion, paragraphs of nearly equal length. GPTTrace’s paragraph-uniformity measure and the structural signs from Wikipedia’s guide often still fire after a rewrite.
Hidden characters
Zero-width spaces, word joiners and soft hyphens are invisible on screen but present in the text. The highlighted copy below each result shows them as red labels. Scattered inside ordinary words, they are a strong sign of deliberate obfuscation; see the invisible character detector for details.
Thesaurus damage
Synonym swapping produces phrases no fluent writer would choose — “profound learning” for “deep learning”, “colossal information” for “big data”. A reader notices these at once even when a detector doesn’t. If a text has several such phrases, ask the writer what they meant.
Statistics
Humanizers aim to raise sentence-length variation, and some overshoot into an erratic pattern. The deep scan’s neural model, trained on a benchmark that includes paraphrased and adversarially modified text, is more robust to these rewrites than word lists alone.
A word of caution
Many people edit their own writing heavily, use a thesaurus or write in a second language, and their text can look “humanized” for innocent reasons. As with every detector result, use the highlighted evidence to start a conversation, not to settle one.
Homoglyphs: letters that only look English
Some humanizers replace Latin letters with look-alikes from other alphabets — a Cyrillic “а” or “о”, a Greek “ο” — that render identically but are different characters to a computer. Search engines, plagiarism checkers and detectors then fail to match words. A quick test is to search the text for a common word you can see on screen: if your browser’s find function can’t find “report” in a sentence that clearly contains it, the letters have been swapped. Pasting the text into a plain-text editor with a non-Latin-aware font sometimes makes the substitutes visibly different. Text with homoglyphs has almost always been deliberately manipulated, whoever wrote the original.
How accurate is it? Our measured numbers
We test GPTTrace on labelled text samples and publish the results, including where it does badly. It is tuned to keep false accusations rare, so it misses some AI content rather than flag real work.
standard text check: AUC 0.795 (cross-validated)
2,467 labelled samples (1,258 AI, 1,209 human), run 2026-10-08. At the “Likely AI” line it caught 34% of AI samples and wrongly flagged 5% of human ones.
| Source | Truth | Samples | Result at “Likely AI” |
|---|---|---|---|
| claude-opus-5 | AI | 12 | 50% caught |
| gpt-4.1 | AI | 12 | 100% caught |
| gpt-oss-120b | AI | 12 | 100% caught |
| claude-haiku-4-5 | AI | 12 | 83% caught |
| qwen-3.8-27b | AI | 8 | 63% caught |
| pd-literature | Human | 306 | 1% wrongly flagged |
| human-pmc-esl | Human | 183 | 5% wrongly flagged |
| human-wikipedia-pre2022 | Human | 155 | 8% wrongly flagged |
| hc3-open_qa | Human | 7 | 14% wrongly flagged |
| chatgpt-3.5 | AI | 1202 | 32% caught |
| hc3-wiki_csai | Human | 558 | 6% wrongly flagged |
text check with deep scan: AUC 0.91 (cross-validated)
2,467 labelled samples (1,258 AI, 1,209 human), run 2026-10-08. At the “Likely AI” line it caught 56% of AI samples and wrongly flagged 5% of human ones.
| Source | Truth | Samples | Result at “Likely AI” |
|---|---|---|---|
| claude-opus-5 | AI | 12 | 42% caught |
| gpt-4.1 | AI | 12 | 100% caught |
| gpt-oss-120b | AI | 12 | 100% caught |
| claude-haiku-4-5 | AI | 12 | 100% caught |
| qwen-3.8-27b | AI | 8 | 75% caught |
| pd-literature | Human | 306 | 0% wrongly flagged |
| human-pmc-esl | Human | 183 | 1% wrongly flagged |
| human-wikipedia-pre2022 | Human | 155 | 1% wrongly flagged |
| hc3-open_qa | Human | 7 | 0% wrongly flagged |
| chatgpt-3.5 | AI | 1202 | 54% caught |
| hc3-wiki_csai | Human | 558 | 9% wrongly flagged |
Data sources and method: methodology & accuracy.