The short answer
- AI detectors are probability estimates, not proof. No detector can prove a text was machine-written, and every major vendor says so in its own documentation.
- They are badly biased against non-native English writers. In the landmark Stanford study, seven detectors flagged human-written TOEFL essays as AI at an average rate of 61.22% — while flagging essays by native-born US students at near zero.
- Even the best-case numbers still break at classroom scale. A ~1% false-positive rate across 150 students × 10 assignments is roughly 15 wrongly accused submissions a term.
- OpenAI withdrew its own detector in July 2023 for low accuracy — the company that built the model could not reliably detect the model.
- Use detector output as a prompt to talk, never as evidence. Process artifacts and conversation beat scores every time.
Every school year since 2023 has opened with the same hope: that some tool will simply tell teachers which homework was written by a machine. Every year, the evidence says the tool doesn’t exist. This page is a plain reading of what researchers have actually found — because the gap between the marketing and the data is where real students get hurt.
How do AI detectors decide?
Most detectors don’t look for AI. They look for predictability. A language model, by design, tends to choose likely next words. So detectors measure two statistical properties of text:
- Perplexity — how surprising the word choices are. Low perplexity (very predictable) reads as machine-like.
- Burstiness — how much sentence length and rhythm vary. Humans write unevenly: a long, winding sentence, then a short one. Models tend to be smoother.
That’s the whole trick. A detector isn’t detecting authorship; it’s scoring how statistically ordinary your prose is. Once you understand that, every one of its failures becomes predictable — including the worst one.
Why do detectors flag non-native English writers?
Because writing in a second language produces exactly the statistical signature detectors treat as machine-generated. A student working in their second language reaches for common vocabulary and clean, simple structures. That is low perplexity. The detector doesn’t know why the text is predictable — it just knows it is.
The scale of this is not a rounding error. In the Stanford study led by James Zou’s group, researchers ran seven widely-used GPT detectors over 91 TOEFL essays written by non-native English speakers with no AI involvement at all:
| Finding | Result |
|---|---|
| Average false-positive rate across 7 detectors | 61.22% |
| Essays flagged by at least one detector | 97.8% |
| Essays unanimously misclassified by all seven | ~19.8% |
| False-positive rate on essays by native-born US students | Near zero |
Source: Liang et al., Patterns (2023), via Stanford HAI
Read that last bar against the first. The same tools, the same task, and the error lands almost entirely on one group of students. The researchers’ own recommendation was blunt: don’t use these detectors in settings with substantial non-native-speaker populations.
What do the vendors themselves claim?
Vendor numbers are best-case numbers, and the vendors say so in the fine print. Turnitin has publicly claimed roughly 98% accuracy with a false-positive rate below 1%, on documents containing at least 20% AI-written content — a meaningful qualifier that rarely survives into staffroom conversation. Turnitin also states its scores are not proof and should not be the sole basis for an accusation.
The single most telling data point isn’t from a critic. In July 2023, OpenAI withdrew its own AI Text Classifier, citing its low rate of accuracy. The organisation with the deepest possible knowledge of how its model writes could not build a reliable detector for it. Nothing since has changed the underlying maths.
Where do detectors fail hardest?
Any edit blurs the signal. Detection degrades sharply once AI text is paraphrased, restructured, or run through another tool — precisely what a student who intends to cheat will do. The result is a tool that is toughest on the honest and easiest on the deliberate.
Known failure zones:
- Non-native English writing — the flagship failure (see above).
- Edited or paraphrased AI text — accuracy drops substantially.
- Formulaic genres — lab reports, legal summaries, and standard five-paragraph essays are predictable by design.
- Neurodivergent and heavily-scaffolded writing — students taught rigid structures produce structured prose.
- Very short submissions — less text, weaker signal, noisier score.
- Deliberate evasion tools — an entire industry exists to defeat detectors, and it largely works.
The pattern is uncomfortable: detectors are least reliable exactly where the stakes are highest.
What should a teacher do with a flagged paper?
Treat the score as a reason to look, not a reason to conclude. A flag is a prompt for a conversation — one that a student who did the work can pass easily and one that a student who didn’t, generally can’t.
| Symptom | Likely cause | What to do |
|---|---|---|
| High score, student writes this way in class too | False positive — plain, predictable style | Compare with known in-class writing; drop it |
| High score, non-native English writer | Documented detector bias | Do not act on the score alone |
| High score, no drafts or version history | Possible AI use — or a student who drafts elsewhere | Ask to see process; ask about the argument |
| High score, work is unlike the student’s usual voice | Worth a conversation | Ask them to explain their reasoning aloud |
| Low score, but the work feels off | Paraphrased AI or a ghostwriter | The detector can’t help you here |
The most reliable instrument in the room is still a teacher who knows what a student sounds like.
What should a student do if they’re wrongly accused?
Produce process, not protest. Insisting “I didn’t use AI” is unfalsifiable; showing how the work happened is not.
Keep and be ready to show:
- Version history — Google Docs and Word both keep it automatically. This is the single strongest artifact you have.
- Drafts, outlines, and notes — even messy photos of handwritten planning.
- Sources you consulted — browser history, library records, annotated PDFs.
- Your own understanding — be able to explain your argument, your evidence, and what you’d change.
Then ask two fair questions: which specific passages were flagged? and what does school policy say about detector scores as evidence? Most policies are more cautious than the accusation implies.
So what actually works?
Design, not surveillance. The schools handling this best have mostly stopped trying to win an arms race they can’t win, and changed what they ask for instead: work that references a specific class discussion, in-class writing samples that establish a voice, staged assignments where the outline and draft are graded, and oral check-ins where students defend their reasoning.
None of that is free — it costs teacher time, which is the scarcest resource in the building. But it’s the only approach whose failure mode isn’t a wrongly-accused sixteen-year-old.
If you’re building that structure, start with designing AI-proof assignments and our classroom AI policy template. Parents worried about the other side of this should read how to spot AI-written homework — with the same caveats that apply here.
An honest caveat about this page
Detection research moves fast, and every number here has a shelf life. Vendors update models; Turnitin, for instance, shipped a model update in February 2026 claiming improved recall. It is entirely possible that detectors get meaningfully better than what’s described above.
What is unlikely to change is the structure of the problem: a detector infers from statistical patterns, patterns vary by writer, and some humans write predictably. Until a tool can distinguish “predictable because machine-written” from “predictable because the writer learned English at fourteen,” the false-positive floor stays where it is. Weigh the evidence accordingly — and keep the burden of proof where it belongs.
For the wider picture of AI and schoolwork, start with our complete guide to AI homework help.
Sources
- Liang, W., Yuksekgonul, M., Mao, Y., Wu, E., Zou, J. — GPT detectors are biased against non-native English writers, Patterns (2023). The 91-essay TOEFL study reporting the 61.22% average false-positive rate. Journal article · Stanford HAI summary
- Turnitin — public statements on AI-detection accuracy, the ≥20%-AI qualifier, and guidance that scores are not proof. Turnitin AI writing detection
- OpenAI — announcement withdrawing the AI Text Classifier (July 2023) for low accuracy. OpenAI
Figures reflect the cited studies and vendor statements as of August 2026. If you spot an error, tell us and we’ll correct it in place.
Frequently asked questions
How accurate are AI detectors in 2026?
Vendors claim high accuracy — Turnitin, for example, has publicly claimed around 98% accuracy with a false-positive rate under 1% on documents that are at least 20% AI-written. Independent research is less flattering, and accuracy collapses on edited or paraphrased text. The honest summary: detectors are decent at spotting raw, unedited AI output and unreliable on everything else.
Can an AI detector be wrong?
Yes, in both directions. It can clear AI-written text (false negative) and it can flag human writing (false positive). The Stanford study found seven detectors misclassified 61.22% of human-written TOEFL essays on average, and all seven unanimously misclassified about a fifth of them.
Why do AI detectors flag non-native English speakers?
Most detectors score text by how predictable it is. Writers working in a second language tend to use more common vocabulary and simpler sentence structures, which reads as statistically predictable — the same signal detectors treat as machine-like. The bias is a direct consequence of how the measurement works.
Can a teacher fail a student based on an AI detector score?
Schools vary, but a score alone is a weak basis for an academic-integrity case, and detector vendors themselves caution against using output as sole evidence. Most institutions require corroborating evidence — drafts, version history, or a conversation with the student.
What should a student do if they are falsely accused?
Stay calm and produce process evidence: draft history, version history in Google Docs or Word, notes, outlines, browser history, and your ability to explain your own argument out loud. Ask which specific passages were flagged and what the school’s policy says about detector evidence.