How to Find Out If a Document Is AI Generated (2026)
The short answer
You cannot prove a document is AI-generated from its words alone, but you can build strong evidence in four steps: check provenance signals, check the writing history, run two independent detectors, and talk to the author. As of October 10, 2026, provenance is getting stronger — OpenAI began watermarking ChatGPT and Codex text in the EU on October 5, 2026 — while text detectors still fail on short, edited or translated passages.
Step 1: Look for provenance signals
- Images and PDFs: inspect Content Credentials (C2PA) metadata. OpenAI adds Content Credentials to supported images and offers image and audio checks at openai.com/verify; Google embeds SynthID in its generated images.
- Text from ChatGPT or Codex in the EU: from October 5, 2026, OpenAI is rolling out an invisible textGrain watermark over several weeks, and API customers anywhere can opt in. The detector is not public: only approved researchers and expert organisations can apply. See what textGrain is.
- Missing metadata is not evidence. Copy-paste, screenshots and re-exports remove it.
Step 2: Check how the document was written
This is the strongest evidence most people have.
- Google Docs: File → Version history. Human writing shows dozens of small sessions; pasted AI text arrives in one or two large insertions.
- Word: check Track Changes, File → Info → Properties (total editing time) and version history in OneDrive or SharePoint.
- Writing replay: Originality.ai’s Chrome extension replays the writing process of a Google Doc; Pangram scans inside Google Docs and Gmail.
- Ask for drafts and notes. A writer can explain their sources and choices; a pasted answer usually cannot.
Step 3: Run two detectors and compare
| Tool | Price (October 10, 2026) | Strength | Watch out |
|---|---|---|---|
| Pangram | Free plan; Individual $20/month (300,000 words); Professional $65/month (5x words, $200 API credits); Team $20/seat | File upload, OCR for scanned documents, Google Docs and Gmail integrations, API | Short passages |
| Originality.ai | Free: 3 scans a day, 2,000 words each; Pro $14.95/month ($12.95 annual) for 2,000 credits (1 credit = 100 words); Enterprise $179/month | Full-site scans, Chrome writing replay, team tags | Credits expire monthly |
| GPTZero | Free tier plus paid plans with annual discounts | Built for teachers; partner of the American Federation of Teachers; API | Same limits as every detector |
| Turnitin | Institutional licence only | Already inside school workflows | Not sold to individuals |
Run the same text through two tools. Agreement on a long passage is a signal; disagreement, or a borderline score, means you do not know.
Step 4: Interpret the result honestly
- Length matters. In OpenAI’s own watermark tests, detection at a 1% false-positive rate found about 80% of 200-token passages and 95% of 400-token passages — and rates were much lower for constrained text such as mathematics. Statistical detectors face the same problem.
- Editing defeats detection. Replacing 10% of words with synonyms dropped OpenAI’s watermark detection from about 92% to 66%; replacing 25% dropped it to 17%.
- False positives fall on real people. Non-native English writers and formulaic genres (legal, technical, templated reports) score as “AI-like” more often. Never sanction anyone on a score alone.
- A detector cannot tell assistance from authorship. Grammar fixes, translation and outlining all leave traces.
Which approach fits your situation
- Teacher or professor: version history plus Turnitin or GPTZero, then a conversation.
- Editor or publisher: Pangram or Originality.ai on submissions, with writing replay for commissioned work.
- Developer screening user content: Pangram’s API, with human review on anything consequential.
- Compliance officer: provenance metadata and vendor watermarks, which the EU AI Act’s Article 50 transparency rules now require generative AI providers to supply.
For the full landscape see our guide to detecting AI-generated content and how to test AI detectors before trusting them.
Last verified: October 10, 2026.