IsThisAI?

Home / Guides

A free AI detector for teachers, and how to use it fairly

If you teach, you've probably read an essay recently and thought, "Did a student write this?" A detector can help you decide whether to look closer. It can't tell you what happened. Here's how to use one without hurting a student who did nothing wrong.

Updated October 11, 2026 ยท By the IsThisAI? team

Checking a submission

With IsThisAI?, you paste the text or upload a .txt, .docx, or .pdf file and get a score with the most AI-like sentences highlighted. The check runs in your browser, so the student's text isn't sent to us or stored. That matters: Vanderbilt warns that many third-party detection tools have unknown privacy and data-use policies, so entering student work into them may conflict with student privacy protections such as FERPA (Vanderbilt).

Before you run anything, a few habits make the result more useful:

Want a quick second opinion on a piece of writing? Paste it into IsThisAI? and see which sentences read as AI-like.

Check your text free →

Reading the result

A detector score is a probability from a statistical model, not a measurement. Some practical ways to read it:

Why a score isn't proof

Even the biggest vendor says this. Turnitin's documentation states its model "may not always be accurate" and "should not be used as the sole basis for adverse actions against a student" (Turnitin Guides). Its own target is a document-level false positive rate under 1% for documents with over 20% AI writing, which still means roughly one human-written paper in a hundred could be flagged (Turnitin FAQ).

Universities have taken that seriously. Vanderbilt disabled Turnitin's AI detection in 2023 and noted that, at its volume of 75,000 papers a year, a 1% false positive rate could mean around 750 wrongly flagged papers (Vanderbilt). The University of Pittsburgh's Teaching Center recommends against using AI detection tools, because they aren't accurate enough to prove a student violated an academic integrity policy (Pitt Teaching Center). The University of Iowa's teaching office goes further and says instructors "should refrain from using AI detectors on student work" (University of Iowa). MIT Sloan's teaching team gives similar advice (MIT Sloan).

So use a detector the way you'd use a hunch: as a reason to look closer and ask questions, not as a finding.

Talking to the student

The conversation is where you actually learn something. A few approaches that tend to go well:

  1. Lead with curiosity, not accusation. "Walk me through how you wrote this" opens a very different conversation than "A detector says you used AI."
  2. Ask about the content. Why did they choose that source? What did they mean in paragraph three? What would they change? People who wrote a piece can usually talk about it.
  3. Ask for process evidence. Google Docs or Word version history, outlines, notes, and earlier drafts. Our guide on how students can prove they wrote something lists what to look for.
  4. Share the report. If you used Turnitin, students can't see the AI report themselves, but you can download it and share it (Turnitin FAQ). Letting them see exactly what was flagged is fair.
  5. Follow your institution's process. If you still have concerns, use the formal academic integrity process rather than deciding alone.

A classroom policy template

Most confusion comes from unclear rules. A short, specific policy at the top of the syllabus prevents a lot of it. Here's a starting point you can adapt:

AI use in this course. You may use AI tools for [brainstorming / grammar and spelling checks / nothing] in this course. You may not submit text written or rewritten by an AI tool as your own work. If you use an AI tool in any way, add a short note saying which tool and how.

Keep your process. Write your assignments in Google Docs or a cloud-saved Word file so version history is available. Keep your notes and drafts until grades are final.

How concerns are handled. I won't treat an AI detector score as proof. If I have a concern, I'll talk with you first and ask about your process before taking any further step.

Pair the policy with assignments that make the process visible: in-class drafting, short reflections on how a paper developed, or a quick conversation about a draft. Iowa's teaching office recommends exactly this: clear expectations, a focus on the writing process, and open conversations about acceptable AI use, instead of detection (University of Iowa).

For background on the numbers, see are AI detectors accurate? and AI detector false positives.

Check any essay, email, or post for AI-sounding writing. Free, no sign-up, and your text stays on your device.

Check your text free →

FAQ

Is there a free AI detector for teachers?

Yes. IsThisAI? is free with no sign-up, and the check runs in your browser so student text isn't stored. Like every detector, it can be wrong, so use it to decide whether to look closer, not as proof.

Can I fail a student based on an AI detector?

Turnitin itself says its score should not be the sole basis for adverse action against a student, and several universities, including Pitt and Vanderbilt, advise against relying on detectors. Talk to the student and look at process evidence first.

What's the most reliable way to tell if a student used AI?

There's no reliable automated test. Comparing to the student's in-class writing, asking them to explain their work, and checking version history tell you much more than a score.

Are AI detectors biased against ESL students?

Research says yes for many tools. Liang et al. (2023) found seven detectors flagged more than half of essays by non-native English writers as AI, while classifying essays by US eighth graders almost perfectly.

More guides

Sources

  1. Turnitin, "Turnitin's AI writing detection capabilities FAQs" (Turnitin Guides, updated Oct 7, 2026). https://www.turnitin.com/products/features/ai-writing-detection/faq
  2. Turnitin, "Using the AI Writing Report" (Turnitin Guides). https://guides.turnitin.com/hc/en-us/articles/22774058814093-Using-the-AI-Writing-Report
  3. Liang, Yuksekgonul, Mao, Wu & Zou, "GPT detectors are biased against non-native English writers," Patterns 4(7), 2023. https://www.cell.com/patterns/fulltext/S2666-3899(23)00130-7
  4. Vanderbilt University Brightspace team, "Guidance on AI Detection and Why We're Disabling Turnitin's AI Detector" (Aug 16, 2023). https://www.vanderbilt.edu/brightspace/2023/08/16/guidance-on-ai-detection-and-why-were-disabling-turnitins-ai-detector/
  5. Vanderbilt University, "Academic Integrity and Generative AI". https://www.vanderbilt.edu/generative-ai/academic-integrity/
  6. University of Pittsburgh Teaching Center, "Encouraging Academic Integrity" (statement about AI detectors). https://teaching.pitt.edu/resources/encouraging-academic-integrity/
  7. University of Iowa Office of Teaching, Learning, and Technology, "The case against AI detectors" (Sept 30, 2024). https://teach.its.uiowa.edu/news/2024/09/case-against-ai-detectors
  8. MIT Sloan Teaching & Learning Technologies, "AI Detectors Don't Work. Here's What to Do Instead.". https://mitsloanedtech.mit.edu/ai/teach/ai-detectors-dont-work/
  9. Weber-Wulff et al., "Testing of detection tools for AI-generated text," International Journal for Educational Integrity 19, 26 (2023). https://link.springer.com/article/10.1007/s40979-023-00146-z

This guide is general information, not legal or academic-policy advice. AI detection results, including ours, can be wrong.