Home › ChatGPT Detector › Accurate

Accurate ChatGPT detector: sentence-level evidence, measured false positives.

No detector is 100 percent accurate on every text it sees, and any vendor who says otherwise is selling a billboard. TextSight scores text at the sentence level so you can see which lines triggered the flag, and we publish how often it wrongly flags human writing: 5.85% of 1,180 human-written academic papers. That is a result panel you can defend in a conversation, and a number you can check.

Run an accurate scan See the workflow
5.85% of human papers wrongly flagged Benchmark data published Sentence-level evidence on every scan
Why TextSight is accurate

Three things that move accuracy in this category.

Accuracy in AI detection depends on what the model was trained on, where the signal is scored, and whether anyone measured how often it is wrong on real human writing.

1. A neural classifier, not a word list

TextSight runs a neural classifier trained on human and AI-written text, with lighter pattern checks blended in. It reads the overall fingerprint of machine-written prose rather than counting a few telltale words, which is why simple rewording rarely moves the score. The model is English-only.

2. Sentence-level signals, not just a document percentage

Every sentence gets its own probability score. The result panel colours each sentence green, yellow, or red and lists the specific GPT-4 signals that triggered each flag (sentence-length floor, nested-clause density, the polite-assistant register, the "thoughtful synthesis" closer). A document-level percentage alone is brittle. A document percentage backed by sentence evidence holds up when a teacher, editor, or recruiter has to explain why the call was made.

3. A measured false-positive rate

We ran the detector over 1,180 human-written academic papers published in 2018, all of which predate ChatGPT, so every AI flag is a false positive by construction. It wrongly flagged 5.85% of them (95% confidence interval 4.65% to 7.34%), and a further 20.0% came back Mixed or Uncertain rather than a clean human verdict. The full method and per-document data are on our benchmark page.

Honest accuracy framing

What TextSight actually scores, and what it does not.

Accuracy in this category depends on three variables: the source model, the length of the text, and whether the text has been edited or humanized. Here is where TextSight lands on each.

No accuracy percentage, on purpose

We do not publish an accuracy percentage, because accuracy moves with text length, genre and how much the text was edited, and formal, encyclopedic human writing is the kind most likely to be wrongly flagged. Unedited ChatGPT output of a few hundred words is where detection has the most signal to work with; short or heavily edited text is where it has the least.

Lower on heavily edited or humanized text

If a passage went through several rounds of human edits, or through a dedicated humanizer, every detector loses signal, TextSight included. Weight the call accordingly and lean on the sentence-level evidence.

5.85 percent false positives on human academic writing

We ran the detector over 1,180 human-written academic papers published in 2018, all of which predate ChatGPT, so every AI flag is a false positive by construction. It wrongly flagged 5.85% of them (95% confidence interval 4.65% to 7.34%), and a further 20.0% came back Mixed or Uncertain rather than a clean human verdict. Second-language writers were flagged 4.6% of the time against 8.1% for native writers, a gap whose confidence interval crosses zero, so the honest statement is no significant difference in either direction.

No detector is 100 percent accurate

That sentence will eat most competitor marketing, and it is still true. Treat any ChatGPT detector score as a conversation starter, not a verdict. The 0 to 100 Humanization Score and the sentence colours together give you enough evidence to decide whether to escalate a paper, push back on a freelancer, or move on. They do not give you the right to declare a piece "AI" with no further review.

Second-language writers

Why the ESL gap is the accuracy problem that matters.

False positives on second-language writers are the most consequential failure in this category, because they send real students into academic-integrity hearings they should not be in. Here is what we measured, and what we have not built.

Why it happens

Second-language writers often use shorter sentences, a more uniform rhythm and a narrower vocabulary, and a detector can mistake those features for machine writing. Liang et al. (2023) found seven detectors flagged 61.3% of TOEFL essays by non-native writers on average, against near zero for essays by native US eighth-graders.

What we measured

Our training data includes second-language academic prose, and we checked whether our detector treats those writers differently. Second-language writers were flagged 4.6% of the time against 8.1% for native writers, a gap whose confidence interval crosses zero, so the honest statement is no significant difference in either direction. There is no separate calibration layer or per-language threshold in the product.

What that means for you

5.85% is not zero, for any writer. Never treat a TextSight score on its own as proof that a student used ChatGPT. Read the sentence-level evidence and talk to the writer first.

Plans & pricing

Same classifier on every tier.

A free scan and a Business scan on the same text produce the same Humanization Score, the same sentence colours, and the same per-model confidence. Paid tiers raise the cap and unlock the humanizer, file upload, and API.

Free
$0/forever

 

Try the accurate detector. No card, no email.
  • 3 actions a day (scans, uploads, rewrites)
  • 13,500 chars per scan
  • Sentence-level evidence
  • Same detector as paid plans
Start free
Starter
$7.49/month

Billed $89.88/year — Save $30

For writers checking individual articles regularly.
  • 20 scans / day
  • 40,000 humanizer words/mo
  • Chrome extension
  • Email support
Get Starter
Business
$29.99/month

Billed $359.88/year — Save $120

For schools and teams running accuracy at scale.
  • 100,000 humanizer words/mo
  • REST API access
  • 5 team seats
  • White-label PDFs
Get Business

Yearly billing saves 25%. View full pricing →

30-second workflow

Four steps from paste to defensible call.

Accuracy is only useful if the workflow around it is short. The standard TextSight scan takes about thirty seconds end to end on an 800-word essay.

1. Paste the text

Open app.textsight.ai. Paste up to 5,000 characters on the free tier, or up to 10,000 on Pro. The character counter ticks as you type or paste. No signup is required for your first scan.

2. See the score

Click Scan. The classifier runs in around six seconds for short text, thirty seconds for an 800-word essay. The result panel returns a 0 to 100 Humanization Score, a per-sentence colour map, and a list of the top three GPT-4 fingerprint signals found in the text.

3. Review the evidence

Open the sentence-level panel. Every red sentence is annotated with the specific signals that triggered it: the sentence-length floor, the nested-clause syntax, the polite-assistant register, the synthesis closer, or the "intricate tapestry" vocabulary cluster. Yellow sentences are borderline and listed separately so a reviewer knows where the genuine uncertainty lies.

4. Decide

If three or more red sentences carry classic GPT-4 fingerprint signals on long-form text, the call is solid. If red sentences are isolated quotes or technical definitions, downgrade to "inconclusive". If the text is under 300 words or has been heavily edited, the result panel surfaces a low-confidence warning and you should treat the score as directional rather than precise.

Honest scope

Where this detector should not be the final word.

No AI detector is accurate enough to be the sole basis of an academic-integrity ruling or a freelancer firing. These are the cases where the published numbers still leave too much room for a wrong call.

Under 200 words

Every detector loses statistical power. Short paragraphs do not give the classifier enough sentence-level data points to score reliably. TextSight surfaces a "low confidence" warning when input length drops below the threshold the model was tuned for.

Heavily humanized AI text

A passage that went through three rounds of human edits or a dedicated humanizer no longer carries the surface signals the classifier was trained on. Accuracy drops. The Humanization Score is still useful as a directional reading, but a single low score should not be treated as proof.

Borderline mixed passages

Text that is 80 percent ChatGPT and 20 percent human edits sits in a no-man's-land that no detector handles cleanly. TextSight reports a Humanization Score rather than forcing a binary classification, and the sentence colour map handles this case better than a document-level percentage. The borderline sentences themselves are still the hardest to call.

Use as conversation starter, not verdict

The most defensible workflow we have seen: scan with TextSight, read the sentence-level evidence, then have a conversation with the writer. A direct conversation produces more clarity than any percentage. If the conversation goes badly, the sentence evidence is the documentation you keep for the next step.

FAQ

Accuracy questions people actually ask.

How accurate is the TextSight ChatGPT detector?
We do not publish an accuracy percentage, because accuracy moves with text length, genre and how much the text was edited, and formal, encyclopedic human writing is the kind most likely to be wrongly flagged. What we publish instead is a false-positive measurement with its data attached: on 1,180 human-written academic papers from 2018 the detector wrongly flagged 5.85%.
Does it wrongly flag non-native English writers?
Published research (Liang et al., 2023) found several detectors flag essays by non-native English writers far more often than essays by native speakers. We measured our own detector on this: Second-language writers were flagged 4.6% of the time against 8.1% for native writers, a gap whose confidence interval crosses zero, so the honest statement is no significant difference in either direction. There is no separate calibration layer for second-language writing in the product, and 5.85% is not zero.
What does sentence-level evidence look like?
Every sentence gets its own probability score and a colour: green for human, yellow for borderline, red for AI. You see exactly which sentences triggered the document score, with the GPT-4 fingerprint signals listed beside them. That is more useful than a single percentage when you have to decide whether to escalate a paper or push back on a freelancer.
Is no detector 100 percent accurate, so why bother?
Correct, no detector is 100 percent accurate. TextSight treats the score as a conversation starter, not a verdict. The score is most useful combined with sentence-level evidence that lets a human reviewer judge the borderline cases. We publish where the tool fails so you can use it where it works.
How do you measure accuracy honestly?
By publishing the measurement and its data rather than a headline number. Our false-positive benchmark ran the detector over 1,180 human-written academic papers from 2018, which predate ChatGPT, so every AI flag is wrong by construction. It flagged 5.85%, and the per-document results are downloadable on the benchmark page.
Does paid accuracy beat free accuracy?
No. The same classifier runs on every tier. A free scan and a Business scan on the same text produce the same Humanization Score, the same sentence colours, and the same per-model confidence. Paid tiers raise the volume cap and unlock the humanizer, file upload, and API. They do not swap in a different model.
How should I act on a borderline score?
Treat any score between 30 and 70 as inconclusive on the document level, then read the sentence-level highlights for evidence. If three or more sentences flag red with classic GPT-4 fingerprint signals like the nested-clause syntax or the synthesis closer, that is real evidence. If the red sentences are isolated quotes or technical definitions, that is more likely a false positive. Use the colours, not the headline.
Related

More for the accuracy workflow.

Further reading

Run an accurate scan. See the evidence.

Free to try, no card, your first scan in about six seconds. Sentence-level evidence and a published false-positive benchmark.

Run an accurate scan See pricing
Sentence-level evidence · 5.85% measured false-positive rate · Benchmark data published

More ChatGPT-detection guides

Detect ChatGPT output wherever you work.

ChatGPT Detector Online — Browser-Based, No Install ChatGPT Detector Bulk — Scan 50+ Docs via UI or API ChatGPT Detector Notion — Copy-Paste Flow ChatGPT Detector PDF — Direct .pdf Upload 2026 ChatGPT Detector Word — Direct .docx Upload ChatGPT Detector Free — 3 Scans/Day, No Signup