AI text detector
Grok text detector
Grok writes replies, summaries and threads directly inside X, and its text is copied everywhere from there. Paste a passage to check it for Grok’s markup leftovers and the general signs of AI writing.
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.
Grok in the wild
Grok is different from most chatbots because of where it lives. People summon it in replies on X with “@grok is this true?”, X uses it to summarise trending topics, and its answers are screenshotted and quoted constantly. That puts Grok-written text in front of millions of people as social posts rather than as chatbot transcripts, and it gets reused in articles, comments and newsletters.
The model’s voice shifts with the mode. In casual exchanges it aims for personality: jokes, rhetorical questions, informal phrasing and occasional edginess. Asked to explain or summarise, it switches to the familiar assistant structure of a summary line, bolded sections and bullet points, with vocabulary that overlaps heavily with other models.
What GPTTrace looks for in Grok text
- Leftover markup. Internal tags and card identifiers from Grok’s interface sometimes survive copying, just as ChatGPT’s citation tokens do. GPTTrace flags them as chat-interface markup.
- Formatting artifacts. Asterisks and pound signs from Markdown, bolded “Label:” bullets and title-case headings pasted into plain-text places.
- General AI-writing signs. Inflated significance, “not just X, but Y” contrasts, vague attributions and rule-of-three lists, from Wikipedia’s catalogue.
- Statistics. Uniform sentence lengths and paragraph sizes, which persist even when the tone is playful.
Grok’s jokey register can lower the vocabulary signals, so structure and statistics matter more for its casual output. Turn on Deep scan for the neural model when the text is long enough.
Images and video from Grok
Grok also generates images and short videos on X. Those can’t be checked with a text detector; use the Grok image detector or the AI video detector instead.
Why short posts are hard
Detectors need words to work with. A 30-word reply contains too few patterns for statistics like sentence-length variation or compression to mean anything, and a single phrase such as “It’s worth noting” is common in human posts too. GPTTrace warns when a text is under 150 words. For short posts, look instead at the account: a sudden change in writing style, replies posted within seconds of the original, identical phrasing across many replies, and generic answers that don’t engage with the post are better signs of automated accounts than any style detector.
Threads and long-form X articles are different. Once a text runs to several hundred words, the structural signs and statistics become informative, and the deep scan adds a neural check on top.
Grok’s summaries of trending topics are also worth knowing: X displays them as short explainers, and they are often copied into articles verbatim. A news story whose background paragraph matches a Grok summary word for word was probably not written by the reporter.
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.