Rhythm & burstiness
Variation in sentence and paragraph length. People write in bursts — a fragment, then a long winding clause. Default model output is far more even.
AI detector / AI content checker
Check any text for the writing patterns typical of ChatGPT, Claude, Gemini and other models. Every signal behind the score is shown, and nothing you paste leaves your browser.
Client-side · deterministic · no account
Each bar shows how far one signal leans toward machine-typical writing. These are stylistic measurements, not evidence of authorship — a careful human writer can score high on all of them.
Want this to read less like a machine?
Rework the cadence and vocabulary with 0Humanizer.
Sentence-level analysis
Read this before you trust a number. No AI detector — this one included — can prove who wrote a text. It measures writing style, not origin. Formal, academic and non-native English writing scores higher regardless of author, and edited AI text scores lower. Never use a detection score as the basis for an accusation or for any decision about someone's grades, job or reputation.
Method
Nine stylistic measurements, combined into one weighted score. No model, no black box, no randomness — the same text always returns the same number.
Variation in sentence and paragraph length. People write in bursts — a fragment, then a long winding clause. Default model output is far more even.
Density of roughly 70 phrases and connectives that language models over-produce — "furthermore", "delve", "it is important to note" — plus lexical diversity adjusted for text length.
Contractions, first and second person, passive constructions, punctuation range, and how often sentences start the same way. Assistant-default prose is short on all of these.
Next step
A high score means the writing reads as generic — which is a writing problem worth fixing on its own terms, detector or no detector.
A number, a date, a name, something that happened to you. Generic prose is what scores high; detail breaks the pattern and makes the piece better to read.
Mix short sentences with long ones. Machine prose is metronomic. Break it. Then let a sentence run on a little further than the reader expects, the way people actually talk.
"Furthermore", "moreover", "it is important to note". They add nothing and they are the strongest single signal here. Delete them and the sentence usually improves.
FAQ
Accurate enough to tell obviously generic machine prose from lively personal writing, and not much more than that. It measures style, not origin. Every detector on the market — including paid ones with confident-looking dashboards — has the same ceiling, because the underlying problem is genuinely hard and getting harder as models improve.
No. Please don't. Students have been failed and staff disciplined on detector output that was wrong, and the harm falls hardest on non-native speakers and on people who write formally. If you are assessing someone's work, talk to them about it — a five-minute conversation about how they wrote something tells you more than any score here.
Because formal writing genuinely shares its statistical shape with model output: even sentence lengths, few contractions, no first person, heavy connectives. The tool cannot tell a careful human from a careful machine, and it doesn't claim to. Open the signal breakdown — it will usually show exactly which measurement pushed the score up.
Not necessarily. Other tools use different signals — some use trained classifiers rather than rules — so scores don't transfer. We can't promise a result on a third-party system and won't pretend to.
It's a weighted average of nine stylistic measurements, each scaled 0 to 1. Roughly: under 35% the writing has clear human texture, 35–65% is genuinely ambiguous, above 65% it reads as machine-typical. The same text always returns the same number — there is no randomness in the calculation.
.txt, .docx, .pdf and .rtf, parsed in your browser. Legacy .doc isn't supported — save as .docx first. Scanned PDFs without a text layer won't work, since there is nothing to read.
No. The whole analysis is JavaScript running on your machine. Nothing is sent to a server, so there is nothing to store, log or train on. You can confirm it by opening your browser's network tab and running a scan.