A PhD student in my network wrote her thesis with zero AI.
Turnitin flagged it: 67% AI-generated.
She spent 2 weeks dumbing down her writing to beat the detector. The paper got worse.
So I tested 5 detectors myself on 50 samples: Turnitin, GPTZero, Copyleaks, ZeroGPT, and Originality.ai.
The Test
- 10 Human papers
- 10 AI-generated
- 10 AI + human edit
- 10 AI + humanized
- 10 ESL human papers
The Results
No tool broke 84.4% accuracy. Worst was 69.4%.
1 in 4 verdicts was wrong.
- Originality.ai: 84.4% best overall. Still missed 50% of humanized text.
- Turnitin: 72%. Flagged 40% of ESL papers. One hit 52%.
- GPTZero: Caught all AI but had 12% false positive rate.
- ZeroGPT: Gave different results 30% of the time on the same text.
Why They Fail
- Hybrid text: AI + human edit drops accuracy to
54-71% - ESL Bias: 28-61% false positives on non-native writers
- Academic prose: Formal writing looks "AI" to detectors Dev Takeaway Don't use detector scores as proof. If you're building with AI, keep git history, prompts, and drafts. Demand human review.
Full data + charts: [https://worldcutruygdski.blogspot.com/2026/07/ai-detector-accuracy-2026-test-results.html]
What has your experience been with false positives?
Top comments (1)
I found the results of your test on AI detectors to be quite eye-opening, especially the high false positive rate for ESL papers. I've had similar experiences with Turnitin in the past, where it flagged some of my colleagues' papers as potentially AI-generated simply because of their non-native writing style. I'm wondering if the developers of these detectors have considered incorporating more diverse training data to mitigate this ESL bias. Do you think it's possible to develop a more accurate detector that can account for the nuances of human writing, or are we stuck with these limitations for the foreseeable future?