Switch to Check Risk for a detectability score and the sentences behind it. No account, no upload to check, no word limit.
The score above measures how detectable your text reads, not whether a machine wrote it. This page takes the number apart: the four inputs, what each one is worth, and the sentence that produced every finding.
Four bands, with the cutoffs written down. Below 25 words the meters stay blank, because a rate computed over two sentences is noise.
Nothing in the registry fired often enough to matter and your sentence lengths vary the way human drafting varies. A detector can still flag you.
A handful of stock constructions, or rhythm that has started to flatten. Usually one or two paragraphs carry the whole score. The report names them.
Tells are stacking: negation pivots, three-item lists, idle transitions, near-identical sentence lengths. This is the range where human writing gets accused most often.
The text reads the way generated text reads, whoever wrote it. Every contributing sentence is highlighted, so you see the reading before anyone else runs it.
Here is the whole composite, with the weights the engine uses. Tell density carries most of the score. Rhythm, vocabulary and hedging make up the rest.
When a passage has fewer than three sentences the rhythm reading is meaningless, so its weight folds back into tell density instead of scoring as zero risk.
The registry ships 44 detectors: 41 surface patterns plus 3 whole-document cadence readings. Each one highlights the exact characters that triggered it and carries a written explanation of why it fired, so you can judge the finding clause by clause and keep the lines you meant to write.
The negation pivot is one of the strongest single predictors of machine text. Say the positive thing directly.
Scene-setting that describes no scene. Detectors weight it heavily because almost nothing else opens this way.
Post-2023 generated text uses this verb at many times the human rate. It is close to a fingerprint.
Six words of distance between you and your own claim.
Almost every AI checker on the market is built from the same two measurements. Here is what each one reads, and what it cannot see.
A language model reads your text and records how surprised it is by each next word. Predictable word choices give low perplexity. Generated text is predictable by construction, because the model that produced it was choosing likely words. So is careful, correct, textbook prose written by a person.
The variation in that surprise across a document, usually tracked alongside sentence length. Human drafting tends to lurch: a long clause, then four words. Generated paragraphs even out. So do dictated paragraphs, translated paragraphs and anything that has been through a grammar tool.
Those numbers go into a classifier trained on examples someone labelled. What comes back is that classifier's confidence, printed as a percentage. It is not a reading taken off the text the way a thermometer reads a room. Nothing in a sentence records its own origin, so an AI checker is inferring, and it inherits every bias in whatever it was trained on.
Stanford HAI researchers ran 91 TOEFL essays, all written by people, through seven commercial detectors. 61% of the essays by non-native English speakers were falsely flagged as AI-generated. Essays by native speakers came through nearly clean. Liang et al., 2023.
Every detector that returns a percentage received your document to do it. This one never gets it. Scoring is JavaScript that runs in this tab, over a string that stays in this tab.
A high reading has two causes and they need opposite responses. Either the draft really is machine-flat and needs rewriting, or you wrote it yourself and a detector is about to be wrong about you. Work out which before you touch a word.
Fix the writing, not the score. The humanizer walks the highlighted clauses one at a time and rewrites them inside your own measured style, so the result sounds like you rather than like a different machine. You approve every rewrite before it lands.
Open the AI humanizer →Keep your voice and bring proof instead. Draft in the editor and export a signed evidence report: your local edit history and drafting cadence, sealed with a key your browser generated. Anyone can check the signature without an account.
Four readings make the score. Here is what each one counts, what it is worth, and what it reads in your draft. The result is a prompt to reread a paragraph, not a verdict on who wrote it.
A weighted count of registry matches per 100 words. High-severity patterns count for more than low ones, so four soft hedges do not outweigh one "not just X but Y".
How little your sentence lengths vary across the draft. Commercial tools call this burstiness. Dictated and heavily edited prose evens out the same way generated prose does.
The rate of vocabulary generated text over-produces: delve, leverage, foster, robust, myriad. Counted per 100 words, so a long draft is not penalised for its length.
Stacked qualifiers and distancing frames, the "it could be argued that" register. It is the smallest input and the fastest one to clear by hand.
Yes. The checker on this page is free and has no account, no sign-up and no word cap. It runs in this tab, so the score and the reasons are never metered.
A high score means your text carries the features commercial detectors key on: predictable phrasing, flat sentence rhythm, stock vocabulary. Those tools run their own classifiers and publish no thresholds, so read the score as a warning about your draft rather than a prediction of their output.
A low score means the obvious tells are gone. Detectors still flag human writing, especially from second-language, autistic and assistive-technology writers, so the report also shows you the sentences a reader is most likely to question.
The checker on this page is JavaScript running in your browser over your own buffer. No request carries your text while you check it, and your text is never sent to a detector. Open your network tab and watch.
No. Text carries no record of its own authorship, so every detector infers from surface statistics. If you need to show your work, the editor exports a signed evidence report with your local drafting history, and anyone can check the signature on the verifier page without an account.
Yes. Load the page once, then turn off your connection. The checker runs in your browser, so the score, the highlights and the reasons all come from code already in the tab.
Free. No account. No word limit.