Grok detector
What the Grok detector does
The Grok detector is a free Grok AI detector: paste in a paragraph, a post, an email or a comment, and it checks the writing against habits typical of Grok, xAI's assistant. It answers the question people type into a search bar, is this written by Grok, with a plain-language list of what it found and why, not a single score dressed up as a verdict.
This is a server tool, not a browser script. Your text is sent to our AI server to be scored; you get 5 free checks in any rolling 24 hours. There's no account to create, and no text you paste is needed twice.
What comes back is a list, not a verdict. A detector that returns a bare number asks you to trust it blind; this one names each pattern it found (a wry aside, a contrarian framing, a joke tucked into parentheses) so you can weigh the evidence yourself.
How it works
How to check text for Grok writing in three steps
It takes less time than reading the result does. There's no file upload, no formatting to strip out first, and nothing to configure before you run the check: paste, run, read.
- Step 1
- Paste the text you want checked. A paragraph is enough to run; a full page gives the check more to work with.
- Step 2
- Press Check text. It goes to our AI server once, gets scored against Grok's writing patterns, and the result comes back to the page.
- Step 3
- Read each flagged signal and the reason behind it, then judge for yourself. The detector explains its reasoning; it doesn't hand down a ruling.
Grok's writing patterns
How Grok's writing actually differs
Grok is tuned for a looser, more personality-forward register than most assistants, closer to the register of the platform it grew up on. None of these prove anything alone: stacked across a page, they're what a Grok checker reads for.
- Parenthetical asides
- A quick joke or aside dropped mid-sentence in brackets, more than most assistants reach for and more than most people write.
- Contrarian framing
- An opening that positions the answer against a supposed conventional wisdom, even when nobody was arguing the opposite.
- An informal, wry register
- Casual phrasing and dry humour sitting inside what's otherwise a fairly structured, informative answer.
- Rhetorical questions mid-answer
- A question posed to the reader and then answered in the next sentence, used as a pacing device.
- Platform-flavoured references
- Turns of phrase and cultural references that read like they came from a social feed rather than a reference book.
- A confident, opinionated close
- A closing line that states a view rather than hedging it, distinct from the softer closings other assistants default to.
Straight answer
Can you tell which AI model wrote something?
Not with certainty. Grok, ChatGPT and Claude train on overlapping data and keep converging on similar phrasing at the structural level, so the tells that separate them are a matter of degree, not a fingerprint.
A system prompt changes almost everything, too: tell Grok to write in a flat, formal register with no asides, and most of its default personality disappears. That's why this tool reports patterns typical of Grok's default voice, not a claim about which model, or which person, wrote a piece of text. Treat a match as a lead worth a closer look, never an answer on its own.
Why flags happen
Why false positives happen
The patterns a Grok checker looks for are also, in places, just a writer's voice. Plenty of people write with a wry, informal register and drop a joke in parentheses on purpose, especially in blog posts, newsletters and social captions. A writer with a naturally contrarian streak reads the way Grok does, for reasons that have nothing to do with a model.
Casual, conversational writing gets flagged often, unfairly. An aside, a rhetorical question, an opinionated close: these are ordinary tools of informal prose, not evidence on their own. A false positive here isn't a flaw in the writer; it's a flaw in treating a distinctive voice as proof of anything by itself.
If you're flagged
What to do if you're accused of using Grok
A flag is a signal, not a verdict; no one should treat it as one. If someone has raised it against your work, the strongest response is evidence of your process, not an argument about the detector.
- Keep your drafts
- Earlier versions, outlines and notes are the plainest evidence a piece grew, rather than appearing whole.
- Keep version history on
- Google Docs, Word and most editors log revisions automatically. Don't clear it while a question is open.
- Be ready to talk through the work
- Someone who wrote a piece can usually explain a specific choice in it, including a joke. That's harder to fake than the prose itself.
- Ask what the flag actually found
- A named signal (a contrarian opener, a run of asides) can be discussed on its merits. A bare score can't.
Who uses it
Who uses the Grok detector, and when
Same tool, several reasons to open it.
- Editors and publishers
- Screening submissions for signs of an unedited Grok draft before it reaches a human editor's time.
- Teachers
- Getting a second opinion on writing that reads unusually polished, as one input among several, not a grading tool.
- Hiring teams
- Checking a writing sample or cover letter for a voice that doesn't match the interview.
- Writers checking their own work
- Running a draft through before submitting it, to see whether their own habits read as machine-made.
- Community moderators
- Getting a quick read on a wall of posts that all arrived sounding oddly alike, before deciding whether to look closer.
Free checks
How many free Grok detector checks you get, and why
This is a server tool: your text travels to our AI server to be scored, then the result travels back. That round trip makes the check possible, and it's why there's a limit.
You get 5 free checks in any rolling 24 hours, tracked without an account, on a ceiling that resets on a rolling clock, not a fixed hour. Five is enough for most real uses: one submission, one email, one flagged paragraph at a time.