AI text detector
Gemini text detector
Gemini writes inside Gmail, Docs and Search as well as in its own app, so its text turns up in emails, reports and web pages. Paste a passage to see which AI-writing signs it shows.
Free · no sign-up · your file never leaves your device
Your text, with the signs marked
Hover a highlight to see which sign it matched. Invisible characters are shown as labelled boxes.
Gemini’s house style
Gemini answers are built to be skimmed. A typical response opens with a one-sentence summary, often in bold, then breaks the topic into headed sections with bulleted points, each starting with a bold label and a colon. Comparisons go into tables. It closes with a short wrap-up and, in the app, an offer to go deeper. When that structure is pasted into an email, a forum post or an essay, the scaffolding comes along: stray asterisks, pound-sign headings, and title-case section names on their own lines.
GPTTrace looks for exactly these artifacts. It highlights Markdown that didn’t render, title-case headings, “**Label:**” bullet patterns and the emoji bullets that Gemini and other assistants use in casual answers. These are formatting habits, not proof — some people write in Markdown — but in ordinary prose they are a strong indicator of copied chat output.
Beyond formatting
Strip the formatting and Gemini’s prose shares the general signs of AI writing: explanations that move in neat three-part steps, vague attributions like “experts note”, emphatic claims of significance and smooth transitions such as “Additionally” and “Furthermore”. Its encyclopedic tone is a particular challenge, because human-written reference text uses the same register — which is why GPTTrace weights the signs using measured data instead of treating each as damning.
Because Gemini is embedded in Google Workspace, a lot of its text arrives as lightly edited business writing: meeting summaries, project updates, customer emails. These are often short. Below about 150 words any detector, including this one, should be treated as a rough indication only.
Gemini images and audio
If the question is about a picture rather than a paragraph, Google labels its generated images with metadata that GPTTrace can read — see the Gemini image detector. For songs or voices from Google’s audio models, use the AI audio detector.
Checking AI text in work email
Many organisations now allow Gemini or similar assistants for drafting, so AI involvement in an email is not in itself a problem. Detection matters when authorship matters: a personal statement, a reference letter, a complaint presented as a customer’s own words, or a phishing email impersonating a colleague. For phishing in particular, the content of the request — urgency, payment, credentials — is a better warning sign than the writing style, and modern scams are often fluent precisely because they are written by AI.
For long internal documents, check a few sections separately. Mixed authorship is normal in collaborative work: one section may be drafted by Gemini and others written by hand, and checking the whole document at once averages them out.
How accurate is it? Our measured numbers
We test GPTTrace on labelled text samples and publish the results, including where it does badly. It is tuned to keep false accusations rare, so it misses some AI content rather than flag real work.
standard text check: AUC 0.795 (cross-validated)
2,467 labelled samples (1,258 AI, 1,209 human), run 2026-10-08. At the “Likely AI” line it caught 34% of AI samples and wrongly flagged 5% of human ones.
| Source | Truth | Samples | Result at “Likely AI” |
|---|---|---|---|
| claude-opus-5 | AI | 12 | 50% caught |
| gpt-4.1 | AI | 12 | 100% caught |
| gpt-oss-120b | AI | 12 | 100% caught |
| claude-haiku-4-5 | AI | 12 | 83% caught |
| qwen-3.8-27b | AI | 8 | 63% caught |
| pd-literature | Human | 306 | 1% wrongly flagged |
| human-pmc-esl | Human | 183 | 5% wrongly flagged |
| human-wikipedia-pre2022 | Human | 155 | 8% wrongly flagged |
| hc3-open_qa | Human | 7 | 14% wrongly flagged |
| chatgpt-3.5 | AI | 1202 | 32% caught |
| hc3-wiki_csai | Human | 558 | 6% wrongly flagged |
text check with deep scan: AUC 0.91 (cross-validated)
2,467 labelled samples (1,258 AI, 1,209 human), run 2026-10-08. At the “Likely AI” line it caught 56% of AI samples and wrongly flagged 5% of human ones.
| Source | Truth | Samples | Result at “Likely AI” |
|---|---|---|---|
| claude-opus-5 | AI | 12 | 42% caught |
| gpt-4.1 | AI | 12 | 100% caught |
| gpt-oss-120b | AI | 12 | 100% caught |
| claude-haiku-4-5 | AI | 12 | 100% caught |
| qwen-3.8-27b | AI | 8 | 75% caught |
| pd-literature | Human | 306 | 0% wrongly flagged |
| human-pmc-esl | Human | 183 | 1% wrongly flagged |
| human-wikipedia-pre2022 | Human | 155 | 1% wrongly flagged |
| hc3-open_qa | Human | 7 | 0% wrongly flagged |
| chatgpt-3.5 | AI | 1202 | 54% caught |
| hc3-wiki_csai | Human | 558 | 9% wrongly flagged |
Data sources and method: methodology & accuracy.