How we test AI humanizers
The humanizer test behind every ranking on this site uses 24 AI-written inputs, 6 human-written controls, 12 tools and 5 detectors, scored with weights that are fixed per series and published here. This page is the full protocol. Any number on a tool page, from a meaning score to a detector pass rate, traces back to a run under this method and to the raw files that run publishes.
The design choice that shapes everything else: meaning kept carries more weight than detector readings. A humanizer that changes what a text says to change what a detector says has failed, and the rubric is built to catch that.
What is a humanizer test run?
One run is every tool in the test set, on the same input set, in the same week, checked on the same detectors, scored with the same rubric. A run gets an ID in the form R1-2026-12, a page of its own, and a folder of raw files. A run is never edited after publication. A correction is a new dated note on the run page, and if a number changes, a new run ID.
Three rules keep runs comparable. Each tool is run on its default mode plus, where the tool offers one, its strongest documented mode as a second row; mode names come from the tool's own interface on the run date. The plan used is the cheapest plan that accepts the input length, recorded with price and the checked-on date, and free tiers are run separately for the free humanizer ranking whenever the free limit accepts the input. One pass per input, no cherry-picking and no retries unless the tool errors; an error is logged and retried once, and a second error is recorded as a failure.
Same week
Detector models change without notice, so every tool is read against the same detector versions
Default mode plus strongest mode
A tool's best case and its typical case both appear, labelled with the mode name from its own interface
Cheapest plan that fits
The plan, its price and the checked-on date are recorded; price is reported, never scored
One pass, one retry on error
No selecting the best of several outputs; the first output is the one that is rated
Screenshots
Every tool screen at the same viewport, captioned with the capture month
What is in the input set?
The input set is fixed for a calendar year; a new set starts a new series, and scores are compared only within a series. It has two parts.
The AI-written part is 24 texts across six genres, four per genre: a school essay paragraph set of 350 to 500 words, a blog post section, a product or service description, a professional email, a cover letter, and a research-style abstract. In each genre, two texts come from one widely used chatbot and two from another, generated from the same written prompts. The prompts are published with the run. The generator, model and date sit in the raw file for each input.
The human-written part is 6 control texts, one per genre, written by the editors for this set and never published elsewhere. Their job is to show each detector's false positive behaviour on the same genres, so a reader can see what a human text scores on that detector before judging a humanized one. Liang and colleagues found that detectors flagged 61 percent of TOEFL essays by non-native English writers as AI-generated (Liang et al. 2023, Patterns), which is reason enough to publish a human baseline beside every detector reading.
Every input, AI and human, is checked on every detector before any humanizing. That baseline row makes the change a tool produces visible instead of implied.
| Genre | AI inputs | Human controls | Length guide |
|---|---|---|---|
| School essay paragraphs | 4 | 1 | 350 to 500 words |
| Blog post section | 4 | 1 | 350 to 500 words |
| Product or service description | 4 | 1 | 350 to 500 words |
| Professional email | 4 | 1 | 350 to 500 words |
| Cover letter | 4 | 1 | 350 to 500 words |
| Research-style abstract | 4 | 1 | 350 to 500 words |
| Total | 24 | 6 | 30 inputs per run |
Which tools are tested?
The launch set is 12 tools: Walter Writes AI, Undetectable AI, StealthGPT, QuillBot AI Humanizer, Grammarly AI Humanizer, Phrasly, BypassGPT, HIX Bypass, TwainGPT (now Verva), WriteHuman, GPTHuman and Clever AI Humanizer. Each has a review with the same fields, and the main ranking lists all 12 on one table.
A tool is added when it has a public web interface, a stated plan or free tier that accepts a 500-word input, and enough search demand that readers are weighing it. A tool is removed only when its service closes or stops accepting inputs; a renamed tool keeps its row under both names. Changes to the set are dated on this page.
Walter Writes AI is one of the 12 and is scored like the others: same inputs, same detectors, same raters, same fields, including a specific main limitation on its review. It receives no extra placement.
Which detectors read the outputs?
Five detectors, each read on the run date with a screenshot of the reading. "Pass" means the detector's own label is human, or its AI probability sits under the threshold the detector itself publishes; the threshold used is stated per detector in the run notes. Where a detector's page states an error rate, that figure is the vendor's own claim and is recorded as such.
| Detector | What it reads, per its own documentation | Threshold used for a human label | Documentation |
|---|---|---|---|
| GPTZero | A sentence-by-sentence deep learning classifier producing one of three document labels, human, AI or mixed, with a confidence category; the vendor states a false positive rate of no more than 1 percent (read 9 November 2026) | Document label human | GPTZero technology page |
| Originality.ai | A language model fed records of known AI, known mixed and known human content; current models are 5.0 and 5.0 Max, launched October 2026 (read 9 November 2026) | Label original, per the vendor's scan output | Originality.ai accuracy page |
| Copyleaks | Linguistic modelling and deep learning trained on human-written text, flagging deviations from human patterns; minimum 255 characters on the web platform; the vendor states a 0.03 percent false positive rate (read 9 November 2026) | Label human | Copyleaks AI Detector page |
| Pangram | A transformer classifier trained with hard negative mining and synthetic mirrors across 10 text domains and 8 language models, per its technical report (arXiv 2402.14873, version of July 2024) | Label human | Pangram technical report |
| ZeroGPT | Multi-stage analysis from document level to sentence level, trained on internet, educational and synthetic datasets; the vendor states 98.4 percent accuracy and under 1 percent false positives as its own metrics (read 9 November 2026) | Label human, with the AI percentage recorded | ZeroGPT DeepAnalyse page |
Turnitin is not on the list. Its AI writing detection is sold to institutions and is not available to the public, so this site cannot run it. Turnitin's product page states that its checker identifies when "AI bypassers (also called humanizers)" may have been used and reports likely AI-paraphrased content (Turnitin, AI writing detection page, read 9 November 2026). Pages on this site report that statement and the peer-reviewed literature; no page states a pass or fail result for Turnitin.
How is each tool scored?
Four dimensions, weighted to 100. The weights are fixed for a series and published before the first run in it.
| Dimension | Weight | What is measured | Who measures it |
|---|---|---|---|
| Meaning kept | 35 | Each output rated against its input on a 1 to 5 scale, where 5 means every claim kept and nothing added; invented facts and dropped claims counted separately and named in the review | Two editors, blind to the tool; disagreements of 2 or more points go to a third read |
| Errors introduced | 20 | Grammar errors, wrong words and broken sentences per 100 words of output; readability change reported but not scored | The same two editors |
| Detector pass rate | 30 | Share of outputs labelled human across the five detectors, reported per detector and pooled | Detector readings on the run date, screenshot each |
| Limits and access | 15 | Words per request, words per month on the tested plan, free allowance, sign-up required | Vendor's own pages on the run date; price reported, never scored |
The headline score out of 100 is the weighted sum, to one decimal, with all four sub-scores shown beside it. The formula, the weights and every tool's inputs to it live in one data file that the pages, the structured data and the downloadable CSV all read from, so a number appears once and the same everywhere.
Meaning kept outweighs detector pass rate by design. Krishna and colleagues showed that a paraphraser dropped one detector's detection rate from 70.3 percent to 4.6 percent at a 1 percent false positive rate (Krishna et al. 2023, arXiv 2303.13408); the paper measured evasion, not whether the paraphrased text still made the same claims. Weber-Wulff and colleagues tested 14 detection tools and found all below 80 percent accuracy, falling further on paraphrased and machine-translated text (Weber-Wulff et al. 2023, International Journal for Educational Integrity). Both results show that moving a detector score is easy. Keeping the argument intact while doing it is the harder test, so it carries the larger weight. The guide on whether AI humanizers work covers these studies in more detail.
Price is never scored. There is no "cheapest" or "best value" verdict anywhere on the site; price appears as a fact with its checked-on date.
What is published per run?
Each run publishes a page and a set of files, all served from this site's own domain and reusable under the licence in the terms of use (attribution and a link).
| Item | Contents |
|---|---|
| Run page | Summary table, per-tool rows, per-detector breakdown, run notes on tool changes and errors, and the line "Tested: Month Year. Page updated: date" |
| inputs.csv | Every input text with its ID, genre, generator, model and generation date |
| outputs.csv | Tool, mode, input ID and the full output text |
| detector-readings.csv | Every detector reading for every input and output, with the baseline row before humanizing |
| ratings.csv | Both raters' meaning and error scores under blind IDs, plus the third read where one was needed |
| Screenshots | Every tool screen and every detector reading, zipped, captioned with the capture month |
| Revision log entry | The run ID and date added to the log at the bottom of this page |
Nothing in a published run is edited later. If a vendor disputes a reading, the dispute and the response are recorded in the corrections log, and any change to a number is a new run ID. The editorial policy covers how tools are chosen, how vendor claims are treated and how disputes are handled.
What are the limits of the method?
Four facts about what a run can and cannot show.
Detector models change without notice. A reading is true for its date, and the date is on every reading. A tool that passes a detector in one run may not in the next, and the run notes record which detector versions could be identified.
Twenty-four inputs per run is a small sample. The per-detector tables show the spread across inputs rather than hiding it in an average, and the genre column lets a reader see whether a tool handles essays and abstracts differently.
Meaning ratings are human judgment. The rubric, both raters' scores and the third reads are published so that anyone can check a rating against the output text in outputs.csv.
Turnitin is not available to the public. The site relies on Turnitin's published statements and on peer-reviewed studies for anything said about it, and no page states a Turnitin result for any tool.
No detector score should be the only evidence in a misconduct case. GPTZero's own technology page describes its results as a conversation starter rather than a final verdict, and Originality.ai's accuracy page states that detection scores alone should not be used for disciplinary action (both read 9 November 2026). This site publishes the human controls so that readers can see the same thing in the data.
Revision log
- 2026-11-09: protocol v0.1 published. Input set defined (24 AI inputs across six genres, 6 human controls), launch set of 12 tools named, five detectors named, weights published: meaning kept 35, errors introduced 20, detector pass rate 30, limits and access 15.
Questions about the method
How does this site test AI humanizers?
Every tool runs on the same 24 AI-written inputs and 6 human-written controls in the same week, every output is checked on GPTZero, Originality.ai, Copyleaks, Pangram and ZeroGPT, and two editors blind-rate meaning kept and count errors before a weighted score is computed.
Why is meaning kept weighted more than detector pass rate?
Because a tool that lowers a detector score by dropping a claim or inventing a fact has not done the job; meaning kept carries 35 of 100 points and detector pass rate 30, so the two never trade off silently.
Which AI detectors are used in the test?
GPTZero, Originality.ai, Copyleaks, Pangram and ZeroGPT, each read on the run date with a screenshot, and each with its own published threshold for a human label stated on this page.
Why is Turnitin not one of the detectors?
Turnitin's AI writing detection is sold to institutions and is not available to the public, so this site cannot run it; pages report only what Turnitin publishes about its own detection and what peer-reviewed studies found.
Can I download the raw test data?
Yes: each run publishes inputs.csv, outputs.csv, detector-readings.csv, ratings.csv from both raters, and a screenshot archive, all served from this site's own domain.
How often are the tests re-run?
A run is announced by its ID and date on this page's revision log when it completes; a run is never edited after publication, and a correction becomes a dated note or, if a number changes, a new run ID.


