Home›QuillBot AI Detector

QuillBot AI Detector: What Its Cited RAID Score Leaves Out

Type oryour text to check for AI content or
0 / 125 words (free scan)·4 free scans / day
Scan Report
Your AI detection report will appear here

By Fırat Mıhcı, founder of MeteGPT. I study how AI detectors read second-language writing, and this review opens the paperwork behind QuillBot’s headline number, with a date beside every figure. My ResearchGate profile is here. Published August 8, 2026; refreshed November 4, 2026 against QuillBot’s live pages; wording last updated November 15, 2026.

TL;DR: QuillBot’s AI detector is a free checker that scores text from 0 to 100% AI, up to 1,200 words a scan and six scans a day. Its 99% claim traces to QuillBot’s own RAID benchmark file: 99.62% at a 5% false-positive setting, the detail its page leaves out. Get a second reading from MeteGPT’s free detector, no signup.

QuillBot’s detector is free and sits in the same account as its paraphraser, which is why so many students run it before handing work in. The sections below take the questions people ask right after a scan: whether the 99% is real, how many words the free tier accepts, and how far one score should carry. Each answer rests on QuillBot’s own pages, the RAID files it cites, and the outside tests of the detector, all re-read on November 4, 2026.

What Is QuillBot’s AI Detector?

QuillBot’s AI detector is a Learneo product that answers one question about a passage you paste in: what share of it looks machine-written, expressed as a figure from 0 to 100 with the individual sentences driving that figure marked up. It lives at quillbot.com/ai-content-detector, and hardly anyone arrives there on purpose. It shares an account with QuillBot’s paraphraser, a tool millions of students and writers already keep open, so for most people the detector shows up as one more tab beside something they were already using rather than as a decision to evaluate a detector at all.

Three things need separating before any accuracy talk, because this brand carries several products with similar names. First, QuillBot’s AI detector is not QuillBot’s paraphraser or its Humanizer. One scores text, the others rewrite it, and they are different products with different jobs; I keep QuillBot’s paraphraser and Humanizer on their own page and this page holds no rewriting content at all. Second, QuillBot’s detector is not Scribbr’s detector, even though both belong to the same parent company, Learneo, a relationship that gets its own section later. Third, RAID here means the academic benchmark by that name, not any other use of the acronym.

On output, QuillBot’s product page promises a score from 0 to 100% for how likely the text was AI-generated, sentence-level highlighting, and explainer cards that say why a passage was flagged. Its FAQ, read November 4, 2026, adds that the detector sorts text into three groups: entirely AI-written, entirely human-written, and human-written with some AI refinement. (The August edition of the page described a four-way label; that wording is no longer there.) The same page now prints a plain warning, “Scores are signals, not verdicts,” and tells readers never to make an academic or employment decision on a detector score alone.

Is QuillBot’s AI Detector Accurate? RAID vs Hands-On Tests

On the benchmark it cites, the figures are high: QuillBot’s own RAID submission reads 99.62% at a 5% false-positive setting and 98.10% at the stricter 1% setting. The small outside tests on record land between roughly 78% and 100%, and none of them is large enough to settle a single student’s result. QuillBot itself calls its scores “signals, not verdicts.”

The outside record is smaller than the benchmark and less consistent. Here is every independent test of this detector I could open and verify, first gathered on August 8, 2026 and re-opened on November 4, 2026, with who ran it and what they disclosed.

Test (date)Who ran itSampleQuillBot result
ZDNet ongoing re-test (published Oct 29, 2025)David Gewirtz, ZDNet; sells no detectorfixed text set, re-run on each pass100% correct on the latest pass, after earlier passes the writer called “wildly inconsistent” across repeats of the same text
Scribbr’s own comparison (snapshot Aug 11, 2025)Scribbr, QuillBot’s sister brand under Learneo30 texts, six categories, 12 detectorsfree detector 78%, tied with Scribbr’s free tier; Scribbr’s paid tool highest at 84%
Textero review (updated Jun 19, 2026)Textero, sells its own writing tools3 textsclassic literature read 100% human; raw GPT-4 text 97% AI; that same text after QuillBot’s own paraphraser 100% AI
Originality.ai review (Oct 28, 2025)Originality.ai, a rival detector3 ChatGPT samplesall three read 100% AI, matching the reviewer’s own tool; author flags the sample as too small to generalize
Independent writer’s informal run (Apr 29, 2025)Himanshu Kumar, Medium; no tool of his own3 scenarios, no percentages givena genuinely human piece came back partly AI; an AI draft with roughly 40% manual rewriting read as human; raw AI text was flagged correctly
GPTZero’s review (Mar 2, 2026)GPTZero, a rival detectorno test of its own; cites a journalist’s“around 80% accuracy”

Read that band for what it is. The largest of those tests ran 30 texts in one pass; three of them ran three texts. A seventh source, BeLikeNative’s 50-text comparison, used to sit in this table at about 80%. When I re-opened it on November 4, 2026, its publisher had withdrawn those figures, saying no dataset or calculation had been published with them, so it no longer counts as a test here. Set against RAID’s public benchmark, these are ad hoc single-run trials, and the honest framing is not that a smaller number beats a bigger one. It is that two different kinds of evidence exist here, and neither has been reconciled with the other by anyone, including me. Where a test comes from a company selling a competing product, the table says so; that is a documented ownership fact and not a claim that any of those results were cooked.

One thread inside that table is worth pulling, because it shows how quickly an accuracy figure decays. GPTZero’s review of QuillBot cites “around 80% accuracy” and hyperlinks that phrase to a specific ZDNet article. When I re-fetched that exact article, the ZDNet writer’s current pass scores QuillBot at 100%, and he describes his earlier runs of the same text as wildly inconsistent. Nobody did anything wrong there: an ongoing test moved, and a page citing it did not. It is a good argument for asking of any detector percentage you meet, including every one on this page, when it was measured and against what.

Has QuillBot’s Detector Ever Flagged Human Writing as AI?

Yes, in documented individual cases, and no published rate exists to tell you how often. A false positive means genuine human writing scored as machine-made. The clearest recorded instance in my set comes from an independent writer with no tool of his own to sell: a piece he had actually written came back labelled partly AI-generated, while an AI draft he had rewritten by roughly 40% passed as human. QuillBot’s own FAQ, read November 4, 2026, says heavily paraphrased writing and highly formulaic content, legal jargon or academic writing for example, is more likely to draw a false positive.

Individual cases from one informal run, not a rate. QuillBot’s FAQ asks what its false-positive rate is and answers without a number.

What I could not find, on any QuillBot page I read, is a published false-positive rate for this detector. The product page FAQ even asks “What is Quillbot’s AI Detector false positive rate?” and answers without a number. The closest figure that exists is the operating point inside QuillBot’s RAID submission, which is a false-positive setting of 5% or 1% depending on the column, and that number lives in a benchmark data file rather than on the marketing page. I am reporting an absence, not inventing a substitute for it. If you came to English later in life and keep getting flagged, one piece of peer-reviewed context belongs here with its scope intact: a Stanford-led study measured heavy false-positive rates on non-native TOEFL essays across the detectors it tested, and QuillBot was not among the tools in that study. That finding describes the category this detector belongs to. It is not a QuillBot figure and I will not repackage it as one.

MeteGPT’s Own Result on QuillBot’s Detector

I hold exactly one first-party number that touches this tool, and it needs its boundaries drawn before the figure itself. Re-run on 31 August 2026, put through QuillBot’s own detector, the rewritten output of our humanizer read 0% AI. Now the boundaries. That result measures how our engine’s output reads on their tool. It says nothing about how accurately QuillBot’s detector judges anyone else’s writing, and treating it as an accuracy score for QuillBot would be a category error, so I am not making that move and neither should a reader. Five limits ride with that figure and none of them are optional. It rests on one 668-word academic essay, which I reran many times that day, and that is a narrow base. The data is our own, open to the owner on request but never audited by anyone outside this company. Inputs that sit far from ordinary academic prose, source code most obviously, read very differently on strict detectors. Detectors get retrained without announcing it. And whatever a tool reported on one day in August says nothing binding about the document you are about to submit.

What Does QuillBot’s Cited RAID Score Actually Measure?

RAID is a real academic benchmark, and this is the part of QuillBot’s claim that almost no page covering this detector opens up. The paper behind it, Dugan et al., arXiv:2405.07940, was published at ACL 2024 and, as described at publication, evaluated detectors across 11 generative models, 8 content domains, 11 adversarial attacks, and 4 decoding strategies. An adversarial attack in this sense is a deliberate alteration the benchmark applies to AI text before testing, such as rewriting it or inserting invisible characters, to see whether a detector still recognizes it. QuillBot’s participation is why any of this is checkable: the benchmark publishes each submission’s raw results in a public repository, so QuillBot’s figures can be read directly rather than taken on faith.

Read directly, they say something more specific than “99%”. A detection percentage is only meaningful next to its operating point, meaning the trade-off the tester chose between catching AI text and wrongly flagging human text. QuillBot’s submission reports both settings:

Slice of QuillBot’s own RAID submissionSettingResult
All conditions aggregated5 human documents wrongly flagged per 10099.62%
All conditions aggregated1 human document wrongly flagged per 10098.10%
AI text rewritten by the benchmark’s paraphrase attack1 per 10094.07%
AI text with zero-width characters inserted1 per 10091.39%

Two readings come out of that table. The first is the spread: moving from the friendliest condition to the hardest one I checked costs the figure about five and a half points. For context I pulled one rival’s submission file out of the same repository and ran the identical arithmetic on it. GPTZero’s entry, filed October 7, 2025, comes back at 71.60% on that same paraphrase slice at the same 1-in-100 setting, against QuillBot’s 94.07%. That is a like-for-like comparison of two self-filed result files on one slice, and nothing broader than that.

The second reading is the disclosure gap. The 99% that appears in QuillBot’s marketing is the aggregate at the 5% setting, and that setting is the price of the number: at that operating point, roughly 5 in every 100 human documents get flagged by design. QuillBot’s page states neither the setting nor the condition. Nor does it mention a detail sitting in its own submission file that shapes how the benchmark result generalizes: the threshold is calibrated separately for each of RAID’s content domains, and those thresholds span roughly four orders of magnitude, from 0.000126 for academic abstracts to 0.936 for product reviews at the 5% setting. That is standard benchmark practice and I am reporting it as methodology, not as a fault. It does mean a benchmark score is tuned per domain in a way your single document never is.

The marketing 99% is the top bar, read where 5 human documents in every 100 are allowed to be flagged. QuillBot’s page prints the number and leaves out the setting. Figures from its own RAID submission file, dated January 30, 2025.

One last piece of context, quotable and easy to verify at the link above. RAID’s own abstract opens by naming commercial detectors that claim to detect machine-generated text with very high accuracy, 99% or higher, as precisely the kind of claim the benchmark was built to interrogate. QuillBot then cites RAID in support of a 99% claim. I draw no conclusion from that. It is simply worth knowing that the source and the marketing line are aimed in slightly different directions.

The Trained-vs-Not-Trained Split QuillBot’s Page Doesn’t Show

Here is the question I most wanted to answer on this page and could not. RAID’s paper is explicit that its leaderboard has two halves. “The leaderboard is split up into two sections,” it says, “one for those who self-report having trained on the RAID dataset and one for those who do not. This is important to ensure that a clear distinction is made between detectors that are generalizing to out-of-domain data and those that are not”. The distinction matters because a detector tested on data resembling what it trained on is doing an easier job than one meeting the material cold, and a reader deciding how much to trust a 99% figure has a real interest in knowing which situation produced it.

That answer is not available to me. The metadata file every submitter to RAID fills in has no field recording the distinction at all, in QuillBot’s submission or in the repository’s own template, and RAID’s live leaderboard page returned nothing readable to the tools I use, so I could not confirm how, or whether, the split is displayed there. I am stating that as an open question rather than guessing at it, because guessing would put an implication in your head that no source of mine supports. What follows from it is narrow and worth carrying: a reader who clicks the link on QuillBot’s own page cannot determine which half of that leaderboard the 99% comes from, and neither can I.

One checkable fact does attach to the submission, and it is a date. QuillBot’s entry is dated January 30, 2025, which makes it the oldest of the major commercial submissions in that repository; GPTZero’s is dated October 7, 2025, It’s AI’s December 25, 2025, and Grammarly’s February 9, 2026. A detector marketed as continually improving is a moving object, while a benchmark submission is frozen at the day it was filed. The 99% therefore describes the detector as it stood in January 2025, which is not a criticism of the figure so much as a boundary on it.

Does QuillBot’s AI Detector Give a Score or a Category? Its Own Pages Disagree

The answer is both, and knowing that in advance keeps a result from reading as more definite than it is. QuillBot’s product page describes a percentage from 0 to 100 for AI likelihood, sentence-level highlighting so you can see which passages drove the score, explainer cards beside the result, and, per its FAQ read November 4, 2026, a split into entirely AI-written, entirely human-written, and human-written with some AI refinement. None of those groups is a finding of fact about who wrote your document. All of them are a model’s estimate, and what a percentage-style AI score tells you holds for the number on this one too.

The percentage and the group arrive together. Neither is a finding about who wrote the document, and the warning at the bottom is QuillBot’s own wording.

Where QuillBot’s own pages come apart is on the sourcing of the accuracy claim, not the output. The product page leads with the RAID citation and links the leaderboard. QuillBot’s separate blog post about the same detector mentions RAID zero times and the 99% figure zero times; I checked the page for both strings on August 8, 2026 and again on November 4, 2026. So whether you ever learn that this detector’s headline number rests on an academic benchmark depends entirely on which of QuillBot’s two pages you happen to land on. I am not claiming that is deliberate, and I have no way to know. I am recording that two live pages from one company, about one product, describe the evidence behind it differently, and that a reader trying to trace the number should make sure they are reading the page that actually cites it.

Is QuillBot’s AI Detector Free? Word Limit, Daily Scans, and What Premium Changes

Yes. QuillBot’s free AI detector scans up to 1,200 words at a time, up to six times a day, and needs at least 80 words before it will run; Premium has no word limit for detection scans and unlimited scans. Those figures come from QuillBot’s product page read live on November 4, 2026, and they match what it printed on August 8.

A study suite can set its limits another way: in the detector NoteGPT bundles with its study tools, the Pro plan draws detector checks from a quota pool it shares with summaries and chat.

Those numbers have practical consequences worth planning around. A standard 500-word assignment fits in one scan. A 4,000-word paper does not, so you would be splitting it into four chunks and burning four of six daily scans, and four chunk-level readings are not the same thing as one whole-document reading, since a score computed over a short passage carries more noise than a score over a long one. The 80-word floor also means the abstract, the cover note, or the two-paragraph discussion post you were most worried about may be too short to scan at all.

What Does QuillBot Premium Change for the Detector?

Going by the product page, Premium removes the 1,200-word cap and the six-scan limit, unlocks explainer cards across the full text where free users get one, and lets you download and share the full report. An older QuillBot source said something narrower. On August 8, 2026, its help-center article stated that “the only difference for Premium users is in file uploads” and that detection works the same on both tiers. Re-read on November 4, 2026, that article, updated in October, now says only that the detector is a free tool for all users, so the two QuillBot pages no longer disagree. If you are paying only to lift the limits, the product page is the one to check before you buy.

MeteGPT keeps its free detector open to everyone: run a short passage through MeteGPT’s detector without making an account, 125 words a scan and four scans a day, built for the paragraph you are unsure about. The MeteGPT humanizer starts with a free account of four rewrites of up to 250 words each, granted once, and scores every rewrite on the same screen. Full essays and longer documents run on a paid plan, so compare MeteGPT’s plans and word allowances when a whole assignment needs the work. Two readings from differently built tools, side by side, tell you more than either one alone.

QuillBot’s AI Detector vs Turnitin, GPTZero, and Scribbr

No same-day, same-samples head-to-head test of these tools exists anywhere in the record I gathered, so I will not manufacture a ranking. What is documented is how each of these comparisons actually differs, which matters more than a league table for someone deciding which reading to worry about.

None of the three is a ranking. Each card names the one thing to know before setting a QuillBot reading beside that tool’s.

QuillBot vs Turnitin

These two answer to different people, and that difference outweighs any percentage. QuillBot’s detector is a self-serve scan you run on yourself. Turnitin’s AI indicator runs inside an institution’s license and produces its reading for an instructor, not for you. Turnitin also reports in an unusual way that is worth knowing before you compare readings: below a 20% threshold its AI writing report displays an asterisk with no numeric score and no highlighted text, which is why I treat Turnitin as an under-20% bound rather than a precise figure anywhere on this site. The consequence is blunt. A clean QuillBot result is a self-run signal from a different model, not a preview of the reading your school will see. I keep Turnitin’s AI writing report, and why it prints a bound instead of a number, on its own dated page.

QuillBot vs GPTZero

Both detectors have entries in RAID’s public repository, QuillBot’s filed January 2025 and GPTZero’s October 2025, which is the closest thing to a common yardstick either of them has. Beyond that, the comparison most often quoted is GPTZero’s own review of QuillBot, which puts it at “around 80% accuracy” and links a journalist’s test that now reads 100% at the same URL. Weigh that as a rival’s page citing a source that has since moved, and weigh GPTZero’s own accuracy claims with the same suspicion you would apply to QuillBot’s; I put GPTZero’s own accuracy claims through the same check separately.

QuillBot vs Scribbr (Same Parent Company, Different Detector)

This is the comparison most worth understanding, because it is the one people use as a cross-check without realizing what they are doing. Learneo’s own announcement lists QuillBot and Scribbr among its operating businesses, so the two are sister brands under one parent. Scribbr publishes a detector ranking, authored by a Scribbr co-founder, that discloses a real method, 30 texts across six categories run through 12 detectors, and reports QuillBot’s free detector at 78%, tied with Scribbr’s own free tier, with Scribbr’s paid tool on top at 84%. Two observations, both about composition rather than motive. The shared parent company is not disclosed on that ranking page. And a vendor’s own comparison naming its own paid product the winner is a self-test, which is a ceiling on how much weight the 78% can carry, not proof it is wrong. The practical upshot for a reader: running a QuillBot result past Scribbr’s detector for a second opinion is not the independent check it looks like, so reach for a third tool with no relation to either; MeteGPT’s detector, which I run, is one. I cover Scribbr’s detector, including what it does and does not disclose, on its own page, and the wider field sits in my ranked record of every detector I have checked.

The ranking names its publisher’s paid product the winner and does not mention the shared parent. For a second opinion on a QuillBot score, use a tool outside the family, such as MeteGPT’s detector.

Can You Rely on a QuillBot AI Detector Score? The Verdict

Not on its own. Checked against the benchmark it credits, QuillBot’s number matches its own file at the setting it comes from: 99.62% at a 5% false-positive setting, and 94.07% on paraphrased AI text at the 1% setting. What the product page leaves out is the labelling: no operating point beside the 99%, no condition, and no way for a reader following QuillBot’s own link to learn which half of RAID’s split leaderboard the figure comes from. A percentage without its operating point cannot be compared with any other percentage, which is exactly what a person choosing between detectors is trying to do.

QuillBot named a peer-reviewed benchmark and filed results that anyone can read in a public repository, and Grammarly filed a RAID submission of its own in February 2026. Set against that, QuillBot’s own blog post about this detector never mentions RAID or the 99%, no QuillBot page publishes a false-positive rate, and the outside tests of it are small single-run trials that scatter between roughly 78% and 100%.

So treat a QuillBot reading as one dated signal from one model. If it comes back clean, that is reassuring and not a clearance from whatever system will actually judge your work. If it flags writing you produced yourself, that is a documented failure mode of the category and of this tool specifically, and the response that holds up is a record rather than a rewrite: keep your drafts and version history, ask which system produced the score and at what length, and check the same passage in MeteGPT’s detector for a second reading from a differently built engine before anything becomes formal.

Either way the score is a starting point. The flagged branch ends on a record and a second reading, not on a rewrite of work that was yours to begin with.

QuillBot AI Detector FAQ

Is QuillBot’s AI detector accurate? By the benchmark it cites, yes at a stated setting: 99.62% where 5 in 100 human documents are wrongly flagged, 98.10% at 1 in 100, and 94.07% against paraphrased AI text at that stricter setting. Small independent trials of 3 to 30 texts land between roughly 78% and 100%. Read any single score as one signal, not a verdict.

What is the QuillBot AI detector word limit? Free scans take up to 1,200 words, with an 80-word minimum and up to 6 scans a day. Premium has no word limit for detection scans and allows unlimited scans, per QuillBot’s product page on November 4, 2026.

Is QuillBot’s AI detector free? Yes. QuillBot’s help center calls it a free tool available to all users. Premium adds unlimited length and scans, explainer cards across the whole text, and downloadable reports.

Is QuillBot’s AI detector as accurate as Turnitin? No comparison in my record tests them on the same samples on the same day. They also serve different people: Turnitin runs inside your institution’s license and, below a 20% reading, shows an asterisk instead of a number. A clean QuillBot score is a self-run signal, not the reading your school will see.

Is QuillBot’s AI detector the same as Scribbr’s? No. They are separate tools with separate models as far as any source I verified shows, but both brands belong to Learneo, so a Scribbr cross-check on a QuillBot result is not an independent second opinion. Scribbr’s own testing puts the two free detectors level at 78%.

Can QuillBot’s detector flag my own writing as AI? It can, and QuillBot says so itself. One independent writer documented a human-written piece coming back partly AI-generated, alongside an AI draft with about 40% rewriting passing as human. QuillBot’s FAQ names heavily paraphrased and formulaic academic writing as more likely to draw a false positive.

Does QuillBot’s detector check for plagiarism too? Its AI detector and its plagiarism checker are separate products with separate outputs, so an AI likelihood score is not a similarity report. If someone tells you QuillBot flagged your work, ask which of the two produced the flag before you plan a response.

How this page was built (MeteGPT Evidence Protocol v1.0).

Sources here are chosen, weighted, and revisited under the MeteGPT Evidence Protocol, written out on its own page. This one weighs a single product, QuillBot’s AI detector, against QuillBot’s own live pages, against the academic benchmark QuillBot names as its accuracy source, and against every outside test of that detector I could open and confirm on August 8, 2026. Logged retrieval produced 23 candidate sources; all 23 were screened and 4 were set aside for reasons kept in the record: two competing-vendor reviews that print percentages with no test disclosed behind them, one community branch I could not verify at all, and one duplicate of an article already counted. The kept sources yielded 21 evidence records, 16 written for this page plus 5 earlier records re-opened and checked against their live sources. Records and sources do not map one to one, since five of those records come out of files in the same public benchmark repository. On November 4, 2026 every cited source was opened again, and five new dated records were added: the product page’s limits and FAQ, the shortened help-center article, QuillBot’s blog post, and BeLikeNative’s withdrawal of its figures. Every record carries its own capture date and is published in the public evidence log.

The limits of this page, stated plainly.

  • Which half of RAID’s split leaderboard QuillBot’s entry sits in is unresolved. The submission metadata carries no field for it and the live leaderboard page returned nothing readable to my tools, so no answer is asserted in either direction.
  • The rival comparison figure, GPTZero at 71.60% on the paraphrase slice, was computed by me from GPTZero’s own submission file using the same aggregation applied to QuillBot’s. Running that method against QuillBot’s file reproduced the 94.07% already on record, which is the check that makes the pair comparable. It compares two self-filed result files on one slice and is not a general ranking of either detector.
  • Every independent test in the accuracy table ran between 3 and 30 texts in a single pass, and several disclose neither their sample composition nor a repeat run. Treat the 78% to 100% spread as a set of unrelated snapshots taken under unrelated conditions, never as a range one detector was measured across.
  • Three of the tests come from companies selling a competing detector or writing product, and a fourth from QuillBot’s sister brand, which is an ownership fact recorded next to each result rather than a judgment about those results.
  • BeLikeNative’s 50-text comparison, quoted here at about 80% in August, was withdrawn by its publisher before November 4, 2026 and has been removed from the table.
  • QuillBot publishes no false-positive rate for this detector on any page I read, so none is stated here; the operating points quoted come from its RAID submission, not its marketing.
  • The community side of this question could not be sourced this cycle. Reddit is blocked to my fetch tools, and five documented query variants surfaced no verifiable thread URLs, so no community-reported claim about this detector appears above rather than being filled in from memory.
  • The Stanford non-native-English study measured a set of detectors that did not include QuillBot, so it stands as background for the category and never as a score for this tool.
  • Our own 0% reading on 31 August 2026 describes what our humanizer produces on their detector, and nothing about how that detector judges anyone else.
  • The independent second-coder pass for this run is scheduled under the protocol and is not complete; sources were verified and coded in a single curator pass, and the reconciled figure gets added when that pass runs.
  • Product limits and page wording are capture-date facts, last read on November 4, 2026, and QuillBot can change them without notice. QuillBot’s price was not read in this pass.

Who wrote this, and why it is sourced this way.

MeteGPT, which I run, makes both a detector and a humanizer, and I say so on every page. That is why each claim about QuillBot above carries a source and a date, and why our own 31 August reading is reported as exactly what it is: a measurement of our humanizer’s output on their detector, not a grade of their accuracy. The protocol behind each record is documented step by step in our methodology. If what you want is to turn an AI draft into writing that sounds like you, rather than audit a score, our own tool puts the rewrite and the score on one screen.

Refreshed November 4, 2026: QuillBot’s product page, help-center article and blog post, the RAID files, and each outside test in the table were opened again that day, and every figure above that changed was corrected in place with a new dated record. Written by Fırat Mıhcı, who builds AI writing tools and researches how detectors handle second-language writing (ResearchGate).

Two free tools on MeteGPT

What a cited score leaves out shows up on real text.

Benchmarks use curated corpora; your draft is not one. Read an independent score on your own paragraph, then rewrite the sections that score worst.