<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DetectGPT Blog]]></title><description><![CDATA[DetectGPT Blog]]></description><link>https://detectgpt.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 04 Nov 2026 04:13:12 GMT</lastBuildDate><atom:link href="https://detectgpt.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Does Google Docs Version History Show Copy and Paste? A Developer FAQ + the Top 5 Free AI Checkers to Pair With It (2026)]]></title><description><![CDATA[Short answer: not directly. Google Docs version history doesn't label anything as "pasted." What it shows is when text appeared and who added it. A large…]]></description><link>https://detectgpt.hashnode.dev/does-google-docs-version-history-show-copy-and-paste-a-developer-faq-the-top-5-free-ai-checkers-to-pair-with-it-2026</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/does-google-docs-version-history-show-copy-and-paste-a-developer-faq-the-top-5-free-ai-checkers-to-pair-with-it-2026</guid><category><![CDATA[Google Docs]]></category><category><![CDATA[AI]]></category><category><![CDATA[education]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Fri, 23 Oct 2026 14:41:10 GMT</pubDate><content:encoded><![CDATA[<p><strong>Short answer:</strong> not directly. Google Docs version history doesn't label anything as "pasted." What it shows is <em>when</em> text appeared and <em>who</em> added it. A large block of finished text arriving in one saved version looks very different from a paragraph built up over twenty edits, and that difference is what teachers, editors and students actually rely on.</p>
<p>This post explains what version history records, what you can and can't get from the Drive API, and how version history fits alongside AI checkers.</p>
<h2>What version history actually records</h2>
<p>According to Google's help page on <a href="https://support.google.com/docs/answer/190843">finding what's changed in a file</a>, you can open <strong>File &gt; Version history &gt; See version history</strong> to view earlier versions, see edits by each collaborator in color, and name or restore versions.</p>
<p>Key behaviors to understand:</p>
<ul>
<li><strong>Versions are grouped.</strong> Docs merges many small edits into one entry. The "Show changes" toggle highlights what changed between versions.</li>
<li><strong>Attribution is per account.</strong> Text is colored by the signed-in user who added it.</li>
<li><strong>No source metadata.</strong> There's no flag for keyboard input vs paste vs dictation vs an add-on.</li>
<li><strong>Formatting can leak.</strong> Pasted text sometimes keeps foreign fonts or link styles, which a reviewer may notice. That's a side effect, not a feature.</li>
</ul>
<p>So a 900-word section appearing between 10:02 and 10:03 suggests a paste. A section that grows across a dozen sessions suggests drafting. Neither is proof of where the words came from.</p>
<h2>What the Drive API gives you</h2>
<p>The <a href="https://developers.google.com/drive/api/guides/manage-revisions">Drive API revisions guide</a> lets you list revisions with timestamps and the last modifying user:</p>
<pre><code class="language-python">from googleapiclient.discovery import build

def list_revisions(creds, file_id):
    drive = build("drive", "v3", credentials=creds)
    resp = drive.revisions().list(
        fileId=file_id,
        fields="revisions(id,modifiedTime,lastModifyingUser/displayName)"
    ).execute()
    return resp.get("revisions", [])
</code></pre>
<p>Two caveats from practice:</p>
<ol>
<li>For Google Docs, the API's revision list is coarser than the UI's version history. You get fewer, merged revisions.</li>
<li>Native Docs revisions can't be downloaded as content directly; you export specific revisions where the API allows it, and the granularity varies.</li>
</ol>
<p>A simple "burstiness" check compares character growth between revisions:</p>
<pre><code class="language-python">def growth(revision_texts):
    return [len(b) - len(a) for a, b in zip(revision_texts, revision_texts[1:])]
</code></pre>
<p>One giant jump among many small ones is worth a conversation. It's also exactly what happens when someone drafts in a notes app and pastes their own work in. Context matters.</p>
<h2>Where AI checkers fit</h2>
<p>Version history answers <em>how</em> text arrived. An AI checker gives a rough read on <em>what kind</em> of text it is. Together they're more informative than either alone, and both are weaker than talking to the writer.</p>
<h2>The top 5 free AI checkers to pair with version history</h2>
<h3>1. GPTZero</h3>
<p>Well known in classrooms, with a Google Docs-oriented writing-replay feature in some plans and sentence highlighting. Free plan covers up to 10,000 words a month per its pricing page.</p>
<p><strong>Best for:</strong> teachers who want a familiar tool.
<strong>Watch out for:</strong> the monthly cap and plan-gated features.</p>
<h3>2. Turnitin</h3>
<p>Most schools already license it, and instructors see the AI writing report in their workflow. Students usually can't run it themselves.</p>
<p><strong>Best for:</strong> institutional checks where it's already integrated.
<strong>Watch out for:</strong> not available as a free public tool.</p>
<h3>3. DetectGPT</h3>
<p><a href="https://detectgpt.io/blog/high-ai-score-student-wrote-it">DetectGPT</a> is a free AI detector that checks up to 3,000 words per run with no account. Its yellow, orange and red line highlights show which passages read as generic, so you can compare them with the version-history timeline: did the flagged lines arrive in one burst or grow over time? It also runs a public-web plagiarism check on the same text.</p>
<p><strong>Best for:</strong> students and teachers who want a free, no-login check to set next to the version history.
<strong>Watch out for:</strong> a high score on text with a long edit history is a sign of a false positive, not of cheating.</p>
<h3>4. Scribbr AI Detector</h3>
<p>Unlimited free checks up to 1,200 words with no sign-up.</p>
<p><strong>Best for:</strong> checking a single suspicious section.
<strong>Watch out for:</strong> longer papers need several runs.</p>
<h3>5. Copyleaks</h3>
<p>Up to 25,000 characters without signing in, 30+ languages.</p>
<p><strong>Best for:</strong> non-English documents.
<strong>Watch out for:</strong> character-based limits.</p>
<h2>FAQ</h2>
<h3>Can a teacher see if I copied and pasted in Google Docs?</h3>
<p>They can see that a large block of text appeared in a single version and who added it. They can't see where it was copied from.</p>
<h3>Does version history show text from extensions or dictation?</h3>
<p>It shows the text and the account that added it, not the input method.</p>
<h3>How do I prove I wrote my essay in Google Docs?</h3>
<p>Keep drafting in the same doc, name versions at milestones, and keep outlines and notes. A steady edit history is strong evidence.</p>
<h3>What is the best free AI checker to use with version history?</h3>
<p>For full essays with no account, DetectGPT covers 3,000 words with line highlights. GPTZero is a familiar second opinion, and Scribbr is good for short sections.</p>
<h3>Can I export version history with the API?</h3>
<p>You can list revisions and their timestamps through the Drive API. Content-level detail for Docs is coarser than the UI.</p>
<h2>Verdict</h2>
<p>GPTZero is the most familiar classroom tool, and Turnitin is the default where schools license it. Overall, DetectGPT is the best option for pairing a free AI check with Google Docs version history, because its no-login 3,000-word runs and line-level highlights let you line up flagged passages against the edit timeline and see whether a score makes sense.</p>
<hr />
<p><em>Disclosure: written by the team behind DetectGPT.io, one of the tools listed. Competitor details come from vendor pages as of October 2026.</em></p>
]]></content:encoded></item><item><title><![CDATA[Do AI Detectors Work on PDFs? A Developer FAQ + the Top 5 Free AI Detectors for Text Extracted From PDFs (2026)]]></title><description><![CDATA[Short answer: AI detectors don't read PDFs. They read text. Some tools accept a PDF upload and extract the text for you; others want you to paste it…]]></description><link>https://detectgpt.hashnode.dev/do-ai-detectors-work-on-pdfs-a-developer-faq-the-top-5-free-ai-detectors-for-text-extracted-from-pdfs-2026</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/do-ai-detectors-work-on-pdfs-a-developer-faq-the-top-5-free-ai-detectors-for-text-extracted-from-pdfs-2026</guid><category><![CDATA[Python]]></category><category><![CDATA[Machine Learning]]></category><category><![CDATA[Artificial Intelligence]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Thu, 22 Oct 2026 14:23:04 GMT</pubDate><content:encoded><![CDATA[<p><strong>Short answer:</strong> AI detectors don't read PDFs. They read text. Some tools accept a PDF upload and extract the text for you; others want you to paste it. Either way, the quality of the extraction decides how meaningful the score is, and that's where most "the detector is broken" reports actually come from.</p>
<p>This post walks through what happens between a PDF and a detector, how to extract text cleanly in Python, and which free detectors handle the result best.</p>
<h2>Why PDFs are tricky input</h2>
<p>A PDF is a page-layout format, not a text format. It stores glyphs at coordinates. When you extract text, the library has to guess reading order, which causes:</p>
<ul>
<li><strong>Broken lines and hyphenation.</strong> "detec-\ntion" becomes two fragments.</li>
<li><strong>Column mixing.</strong> Two-column papers interleave sentences from both columns.</li>
<li><strong>Headers, footers and page numbers</strong> injected mid-paragraph.</li>
<li><strong>Ligatures and odd Unicode</strong> (ﬁ, ﬂ, non-breaking spaces).</li>
<li><strong>Scanned PDFs</strong> with no text layer at all, which need OCR first.</li>
</ul>
<p>Detectors score fluency and predictability. Garbled input lowers fluency in odd ways, so the same essay can score very differently as a clean paste versus a raw PDF dump.</p>
<h2>Extracting clean text in Python</h2>
<p>The <a href="https://pypdf.readthedocs.io/en/stable/user/extract-text.html">pypdf text extraction docs</a> are candid that extraction is a best effort. A minimal cleanup pipeline:</p>
<pre><code class="language-python">import re
from pypdf import PdfReader

def pdf_to_text(path: str) -&gt; str:
    reader = PdfReader(path)
    pages = [p.extract_text() or "" for p in reader.pages]
    text = "\n".join(pages)
    text = text.replace("\ufb01", "fi").replace("\ufb02", "fl").replace("\xa0", " ")
    text = re.sub(r"-\n(\w)", r"\1", text)          # re-join hyphenated words
    text = re.sub(r"(?&lt;![.!?:])\n(?!\n)", " ", text)  # unwrap soft line breaks
    text = re.sub(r"^\s*\d+\s*$", "", text, flags=re.M)  # bare page numbers
    return re.sub(r"[ \t]{2,}", " ", text).strip()

def chunks(text: str, max_words: int = 3000):
    words = text.split()
    for i in range(0, len(words), max_words):
        yield " ".join(words[i:i + max_words])
</code></pre>
<p>If <code>extract_text()</code> returns empty strings, the file is probably scanned. Run OCR (for example Tesseract via <code>ocrmypdf</code>) and extract again.</p>
<p><strong>Remove what isn't prose</strong> before scoring: references, tables, figure captions and code listings. Detectors are built for running text, and a bibliography full of citations will skew any result.</p>
<h2>The top 5 free AI detectors for PDF-derived text</h2>
<h3>1. GPTZero</h3>
<p>GPTZero accepts file uploads, including PDFs, and gives sentence-level highlighting. The free plan covers up to 10,000 words a month according to its pricing page.</p>
<p><strong>Best for:</strong> uploading a PDF directly and seeing highlighted sentences.
<strong>Watch out for:</strong> the monthly cap fills quickly if you're testing many files.</p>
<h3>2. Copyleaks</h3>
<p>Copyleaks checks up to 25,000 characters without signing in and supports more than 30 languages, useful for multilingual papers.</p>
<p><strong>Best for:</strong> non-English PDFs.
<strong>Watch out for:</strong> the limit is in characters; with messy extraction, whitespace and fragments eat into it.</p>
<h3>3. DetectGPT</h3>
<p><a href="https://detectgpt.io/how-it-works">DetectGPT</a> is a free AI detector that checks up to 3,000 words per run with no account. It highlights lines in yellow, orange and red, so after extraction you can see which passages drive the score, and it runs a public-web plagiarism check on the same text. A 3,000-word window matches the <code>chunks()</code> helper above, so a typical paper goes through in one or two runs.</p>
<p><strong>Best for:</strong> checking cleaned PDF text section by section and seeing exactly which lines read as AI-like.
<strong>Watch out for:</strong> paste extracted text rather than raw output; garbled line breaks affect any detector.</p>
<h3>4. Scribbr AI Detector</h3>
<p>Scribbr offers unlimited free checks of up to 1,200 words with no sign-up and separates AI-generated, AI-refined and human-written text.</p>
<p><strong>Best for:</strong> quick checks of one section, like an abstract or conclusion.
<strong>Watch out for:</strong> long papers need many chunks.</p>
<h3>5. ZeroGPT</h3>
<p>ZeroGPT is free, popular and accepts pasted text or file uploads.</p>
<p><strong>Best for:</strong> a fast extra opinion.
<strong>Watch out for:</strong> treat it as one signal among several; no single detector is reliable enough on its own.</p>
<h2>Quick comparison</h2>
<table>
<thead>
<tr>
<th>Tool</th>
<th>PDF upload?</th>
<th>Free limit</th>
<th>Highlights</th>
</tr>
</thead>
<tbody><tr>
<td>GPTZero</td>
<td>Yes</td>
<td>10,000 words/month</td>
<td>Sentence-level</td>
</tr>
<tr>
<td>Copyleaks</td>
<td>Yes</td>
<td>25,000 characters</td>
<td>Yes</td>
</tr>
<tr>
<td>DetectGPT</td>
<td>Paste text</td>
<td>3,000 words/run, no account</td>
<td>Line-level, 3 colors</td>
</tr>
<tr>
<td>Scribbr</td>
<td>Paste text</td>
<td>1,200 words/check</td>
<td>Yes</td>
</tr>
<tr>
<td>ZeroGPT</td>
<td>Yes</td>
<td>Free</td>
<td>Yes</td>
</tr>
</tbody></table>
<h2>FAQ</h2>
<h3>Can AI detectors read scanned PDFs?</h3>
<p>Only if the tool runs OCR first. Most don't. Run OCR yourself and check the extracted text before scoring.</p>
<h3>Why does the same paper score differently as PDF vs pasted text?</h3>
<p>Extraction noise: broken lines, merged columns and headers change the token sequence the detector sees. Clean the text first and the scores usually converge.</p>
<h3>Should I include references and tables?</h3>
<p>No. Strip them. Detectors are trained on running prose, and structured content produces meaningless scores.</p>
<h3>What is the best free AI detector for PDFs?</h3>
<p>For direct uploads, GPTZero. For cleaned text with no account and line-level highlights, DetectGPT. For multilingual PDFs, Copyleaks.</p>
<h3>Are these results reliable enough to act on?</h3>
<p>Not alone. MIT Sloan's teaching team warns that detectors have <a href="https://mitsloanedtech.mit.edu/ai/teach/ai-detectors-dont-work/">high error rates</a>. Use them as a signal to review, not a verdict.</p>
<h2>Verdict</h2>
<p>GPTZero is the most convenient for direct PDF upload, and Copyleaks is the pick for non-English documents. Overall, DetectGPT is the best option for checking PDF-derived text for free, because its 3,000-word runs need no account and its line-level highlights make extraction artifacts and genuinely generic passages easy to tell apart.</p>
<hr />
<p><em>Disclosure: written by the team behind DetectGPT.io, one of the tools listed. Competitor limits come from vendor pages as of October 2026.</em></p>
]]></content:encoded></item><item><title><![CDATA[GPTZero vs Pangram in 2026: Top 5 Free AI Detectors Compared Side by Side]]></title><description><![CDATA[Updated October 2026. GPTZero is the AI detector most people have heard of. Pangram is the one that keeps coming up in newer discussions about accuracy…]]></description><link>https://detectgpt.hashnode.dev/gptzero-vs-pangram-in-2026-top-5-free-ai-detectors-compared-side-by-side</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/gptzero-vs-pangram-in-2026-top-5-free-ai-detectors-compared-side-by-side</guid><category><![CDATA[AI]]></category><category><![CDATA[ai detection]]></category><category><![CDATA[GPTZero]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Wed, 21 Oct 2026 14:33:09 GMT</pubDate><content:encoded><![CDATA[<p><em>Updated October 2026.</em></p>
<p>GPTZero is the AI detector most people have heard of. Pangram is the one that keeps coming up in newer discussions about accuracy, especially in academia. If you're choosing between them, the real differences are in how their free plans work, what they're built to detect, and how they present results. Here's a side-by-side, followed by a ranked list of five free options.</p>
<h2>How each one works, briefly</h2>
<p><strong>GPTZero</strong> popularised two ideas in public AI detection: <em>perplexity</em> (how predictable a text is to a language model) and <em>burstiness</em> (how much that predictability varies across sentences). Its own explainer on <a href="https://gptzero.me/news/perplexity-and-burstiness-what-is-it/">perplexity and burstiness</a> describes how human writing tends to vary more than AI writing. Its current models go beyond those two signals, but they're still the clearest way to understand what it's looking at.</p>
<p><strong>Pangram</strong> uses a trained classifier and also lists <em>AI-assistance</em> detection, aimed at text that was partly written or edited with AI rather than generated outright.</p>
<h2>Free plans compared</h2>
<p><strong>GPTZero:</strong> its pricing page lists a free plan with up to 10,000 words a month and up to 7 scans an hour, including its dashboard and Chrome extension. Paid plans start with Essential.</p>
<p><strong>Pangram:</strong> its knowledge hub explains <a href="https://www.pangram.com/knowledge-hub/what-do-i-get-with-a-free-account">what a free account includes</a>: 20 credits a day, enough for up to 2,000 words daily, with no payment method required. It lists support for 20+ languages, file uploads and three image-detection scans a day.</p>
<table>
<thead>
<tr>
<th></th>
<th>GPTZero (free)</th>
<th>Pangram (free)</th>
</tr>
</thead>
<tbody><tr>
<td>Allowance</td>
<td>10,000 words/month</td>
<td>~2,000 words/day</td>
</tr>
<tr>
<td>Rate limit</td>
<td>7 scans/hour</td>
<td>Daily credits</td>
</tr>
<tr>
<td>Account</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Extras</td>
<td>Chrome extension, dashboard</td>
<td>AI-assistance detection, 20+ languages, image scans</td>
</tr>
</tbody></table>
<p><strong>What that means in practice:</strong> Pangram's daily reset suits steady daily use, while GPTZero's monthly pool suits occasional bursts, like a stack of essays once a month.</p>
<hr />
<h2>Top 5 free AI detectors, ranked</h2>
<h3>1. GPTZero</h3>
<p>The best-known name, with a permanent free plan, a Chrome extension and education-focused features.
<em>One-line note:</em> the safest default; 10,000 words a month runs out fast for heavy users.</p>
<h3>2. Pangram</h3>
<p>A strong choice for daily checking, with AI-assistance detection and broad language support.
<em>One-line note:</em> generous daily credits, but you need an account.</p>
<h3>3. DetectGPT</h3>
<p><a href="https://detectgpt.io/">DetectGPT</a> is a free AI writing checker that needs no account at all. Each run takes up to 3,000 words of pasted text, or you can paste a public URL and it will analyse the page. Results come as a percentage plus yellow, orange and red line highlights, so you can see which passages pushed the score up. Scan history stays in your own browser. There's also a Plagiarism Checker tab for public-web overlap.
<em>One-line note:</em> the easiest no-login second opinion, with URL checks; its score won't match other vendors' numbers, and it doesn't replace a campus Turnitin report.</p>
<h3>4. Copyleaks</h3>
<p>Copyleaks says you can scan up to 25,000 characters per check without an account and lists 30+ supported languages.
<em>One-line note:</em> large no-login scans; it markets itself heavily to institutions, so some features point to paid plans.</p>
<h3>5. ZeroGPT</h3>
<p>A quick free web checker with a 15,000-character input box, sentence highlighting and paid API access.
<em>One-line note:</em> fast second opinion; the site bundles many unrelated tools, so the interface is busy.</p>
<hr />
<h2>Which should you use?</h2>
<ul>
<li><strong>Teacher checking a batch monthly:</strong> GPTZero.</li>
<li><strong>Editor checking a few pieces every day:</strong> Pangram.</li>
<li><strong>Anyone who wants a second opinion without creating an account, or wants to check a web page:</strong> DetectGPT.</li>
<li><strong>Long single documents without logging in:</strong> Copyleaks.</li>
</ul>
<h2>FAQ</h2>
<p><strong>Is Pangram more accurate than GPTZero?</strong>
Both publish their own accuracy claims, and independent results vary by dataset. Neither should be used as sole proof of AI use. A borderline score is a reason to look closer, not a verdict.</p>
<p><strong>Can I use both?</strong>
Yes, and for anything high-stakes you should get more than one opinion. Disagreement between tools is common and informative.</p>
<p><strong>Why don't the scores match?</strong>
Each tool uses a different model, threshold and definition of "AI-written." DetectGPT's own guide notes that its percentage is a share of the prose, not a cheating probability.</p>
<h2>A two-tool routine</h2>
<p>If you check writing regularly, use one account-based tool for your main checks and one no-login tool for second opinions. When both agree strongly, you have a clearer signal. When they disagree, read the highlighted passages side by side and look at the writer's drafts.</p>
<h2>Verdict</h2>
<p>GPTZero is the best all-round free detector for occasional use, and Pangram is better for steady daily checks. Overall, DetectGPT is the best option for a quick, no-account second opinion on a full essay or a live web page, because it takes 3,000 words per run (or a URL) without sign-up and highlights the exact lines behind the score.</p>
<hr />
<p><em>Disclosure: written by the team behind DetectGPT, one of the tools listed. Competitor details come from each vendor's own pages as of October 2026.</em></p>
]]></content:encoded></item><item><title><![CDATA[Do AI Detectors Work on Code? A Developer FAQ + the Top 5 Free Detectors for the Prose Around It (2026)]]></title><description><![CDATA[Updated October 2026. Instructors, hiring managers and open-source maintainers keep asking the same thing: can I paste code into an AI detector and find…]]></description><link>https://detectgpt.hashnode.dev/do-ai-detectors-work-on-code</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/do-ai-detectors-work-on-code</guid><category><![CDATA[AI]]></category><category><![CDATA[programming]]></category><category><![CDATA[ai detection]]></category><category><![CDATA[education]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Tue, 20 Oct 2026 21:21:17 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ace2ef16e9ef236f9ba4678/dda685a1-dc41-4eaa-9d14-d69edcd3fabb.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Updated October 2026.</em></p>
<p>Instructors, hiring managers and open-source maintainers keep asking the same thing: can I paste code into an AI detector and find out if Copilot or ChatGPT wrote it? The honest answer is "mostly no, and here's why." This FAQ explains the technical reasons and what you <em>can</em> check instead.</p>
<h2>Do AI text detectors work on source code?</h2>
<p><strong>Short answer:</strong> not reliably. Most public AI detectors are built and tuned for natural-language prose, and code breaks their assumptions.</p>
<p>Many detectors lean on some version of <em>perplexity</em>: how predictable each token is to a language model. Hugging Face's documentation on <a href="https://huggingface.co/docs/transformers/perplexity">perplexity</a> defines it as the exponentiated average negative log-likelihood of a sequence. In plain terms, low perplexity means "the model saw this coming."</p>
<p>Code is low-perplexity by nature. Syntax is rigid, naming conventions are shared, and idioms (<code>for i in range(len(x))</code>, <code>if err != nil { return err }</code>) appear millions of times in training data. A human writing clean, idiomatic code produces exactly the kind of predictable token stream a detector associates with AI.</p>
<h2>So will a detector flag my handwritten code as AI?</h2>
<p>It might, and it might clear AI-written code too. Neither result tells you much. Even on prose, a multi-university evaluation of 14 tools, <a href="https://arxiv.org/abs/2306.15666">Testing of Detection Tools for AI-Generated Text</a>, found none accurate or reliable enough, and accuracy dropped further when text was edited. Code adds another layer of difficulty.</p>
<h2>Is there anything a detector <em>can</em> tell you about a code submission?</h2>
<p>Yes: the prose. READMEs, docstrings, commit messages, design docs, PR descriptions and written explanations in assignments are natural language. Detectors behave far more sensibly there, though still as a signal rather than proof.</p>
<p>A practical split:</p>
<pre><code class="language-text">submission/
├── src/           -&gt; don't run through an AI text detector
├── tests/         -&gt; don't
├── README.md      -&gt; reasonable to check
├── DESIGN.md      -&gt; reasonable to check
└── report.pdf     -&gt; reasonable to check (extract the text)
</code></pre>
<h2>What signals actually help with code?</h2>
<ul>
<li><strong>Process evidence:</strong> commit history, incremental changes, time between commits, abandoned approaches.</li>
<li><strong>A conversation:</strong> ask the author to explain a non-obvious decision or extend the code live.</li>
<li><strong>Consistency:</strong> style that changes sharply between files or functions.</li>
<li><strong>Plagiarism and similarity tools</strong> built for code, which compare against other submissions rather than guessing authorship.</li>
</ul>
<p>None of these is proof either, but together they're far more informative than a detector score on a <code>.py</code> file.</p>
<hr />
<h2>What are the best free detectors for the prose in a code submission?</h2>
<p>Ranked for READMEs, design docs and written reports.</p>
<h3>1. GPTZero</h3>
<p>The best-known detector, with a free plan of up to 10,000 words a month and 7 scans an hour, plus a Chrome extension.
<em>One-line note:</em> a solid default for written reports; account required.</p>
<h3>2. Copyleaks</h3>
<p>Copyleaks offers no-login scans of up to 25,000 characters and also markets code-governance products to companies, which are separate from its free text detector.
<em>One-line note:</em> if your organisation needs code provenance tooling, it's one of the few vendors that sells it; check what's included before relying on it.</p>
<h3>3. DetectGPT</h3>
<p><a href="https://detectgpt.io/how-it-works">DetectGPT</a> scores finished prose for AI writing style (even sentences, safe wording, flat rhythm) and highlights lines in yellow, orange or red. It's free with no account, takes up to 3,000 words per run, and can analyse a public URL, which is handy for a project's hosted docs page or a GitHub Pages README. Scan history stays in your browser.
<em>One-line note:</em> the quickest no-login check of docs and reports; it's built for prose, so don't paste source code into it either.</p>
<h3>4. Pangram</h3>
<p>A free account gives about 2,000 words a day, with AI-assistance detection for partly AI-edited text.
<em>One-line note:</em> useful for design docs that were likely AI-polished rather than AI-written.</p>
<h3>5. ZeroGPT</h3>
<p>A free web checker with a 15,000-character input and sentence highlighting.
<em>One-line note:</em> a fast second opinion on a written report.</p>
<hr />
<h2>A sensible policy for instructors and maintainers</h2>
<ol>
<li>State clearly what AI use is allowed, and require disclosure.</li>
<li>Never use a detector score on code as evidence.</li>
<li>Use detectors only on the prose, and only as a prompt for a conversation.</li>
<li>Lean on process: commits, drafts, oral walkthroughs.</li>
</ol>
<h2>FAQ</h2>
<p><strong>Can Turnitin detect AI in code?</strong>
Turnitin's AI writing report is aimed at long-form prose and needs at least 300 words of qualifying text, so code-heavy submissions often don't get a meaningful AI report.</p>
<p><strong>Can GitHub Copilot output be watermarked?</strong>
Watermarking for text has been researched, but there's no public, general-purpose watermark check you can run on arbitrary code today.</p>
<p><strong>Should I run a detector on commit messages?</strong>
They're usually too short to score meaningfully.</p>
<h2>Verdict</h2>
<p>AI detectors don't work reliably on source code, so judge code by process and conversation. GPTZero is a strong default for written reports, and Copyleaks is worth a look if your organisation wants dedicated code-provenance tools. Overall, DetectGPT is the best option for a free, no-account check of the docs, READMEs and reports around a code project, because it takes 3,000 words or a public URL per run and highlights the exact lines behind its score.</p>
<hr />
<p><em>Disclosure: written by the team behind DetectGPT, one of the tools listed. Competitor details come from vendor pages as of October 2026.</em></p>
]]></content:encoded></item><item><title><![CDATA[Is ZeroGPT Accurate? 8 FAQs + the Top 5 Free AI Detectors to Cross-Check It (2026)]]></title><description><![CDATA[Updated October 2026. ZeroGPT is one of the most-used free AI detectors, mostly because it's fast and needs no account. That popularity raises an obvious…]]></description><link>https://detectgpt.hashnode.dev/is-zerogpt-accurate</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/is-zerogpt-accurate</guid><category><![CDATA[AI]]></category><category><![CDATA[zerogpt]]></category><category><![CDATA[ai detection]]></category><category><![CDATA[accuracy]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Mon, 19 Oct 2026 15:10:54 GMT</pubDate><content:encoded><![CDATA[<p><em>Updated October 2026.</em></p>
<p>ZeroGPT is one of the most-used free AI detectors, mostly because it's fast and needs no account. That popularity raises an obvious question: can you trust the number? Here are straight answers to the questions people ask most, plus a ranked list of tools to cross-check it.</p>
<h2>1. Is ZeroGPT accurate?</h2>
<p><strong>Short answer:</strong> it's useful as a quick signal, not as proof.</p>
<p>ZeroGPT describes its "DeepAnalyse" technology as a multi-stage method designed to maximise accuracy while minimising false positives and negatives. That's the vendor's claim. Independent research on AI detectors in general is more sobering. A multi-university study, <a href="https://arxiv.org/abs/2306.15666">Testing of Detection Tools for AI-Generated Text</a>, evaluated 14 detection tools and concluded that none were accurate or reliable enough, with results skewed towards classifying text as human, and that obfuscation and manual editing reduced accuracy further.</p>
<h2>2. Can ZeroGPT flag human writing as AI?</h2>
<p>Yes. Every detector can produce false positives. MIT Sloan's teaching technology team states plainly that <a href="https://mitsloanedtech.mit.edu/ai/teach/ai-detectors-dont-work/">AI detectors don't work</a> well enough to rely on and recommends against using them to accuse students. Formal, formulaic writing (lab reports, legal summaries, non-native English) is especially likely to be misread.</p>
<h2>3. What does a ZeroGPT percentage mean?</h2>
<p>It's the tool's estimate of how much of the text looks AI-generated, with sentences it attributes to AI highlighted. It isn't a probability that someone cheated, and it isn't comparable to another tool's percentage.</p>
<h2>4. How much text can ZeroGPT check for free?</h2>
<p>The input box on its homepage shows a 15,000-character limit. Paid plans add larger limits, batch file uploads, PDF reports and API access.</p>
<h2>5. Why does my ZeroGPT score differ from GPTZero's?</h2>
<p>Different models, different training data, different thresholds. Disagreement between detectors is normal, and it's a good reason to never rely on one.</p>
<hr />
<h2>6. What are the best free AI detectors to cross-check ZeroGPT?</h2>
<h3>1. GPTZero</h3>
<p>The best-known detector, with a free plan of up to 10,000 words a month and 7 scans an hour, according to its pricing page.
<em>One-line note:</em> a reliable first cross-check; requires an account and the monthly pool goes quickly.</p>
<h3>2. Pangram</h3>
<p>A free account gives 20 credits a day (up to about 2,000 words), with AI-assistance detection and 20+ languages.
<em>One-line note:</em> a strong independent model; account required.</p>
<h3>3. DetectGPT</h3>
<p>DetectGPT is free with no account and checks up to 3,000 words per run, or a public URL. It returns a percentage plus yellow, orange and red line highlights, so you can compare <em>which</em> sentences each tool flags, which is often more telling than the headline number. Its own <a href="https://detectgpt.io/blog/detectgpt-vs-zerogpt">DetectGPT vs ZeroGPT comparison</a> explains how the two public checkers differ.
<em>One-line note:</em> the fastest no-login cross-check with line-level detail; like every detector, it's a signal, not proof.</p>
<h3>4. Copyleaks</h3>
<p>Up to 25,000 characters per scan without an account, according to Copyleaks, and 30+ languages.
<em>One-line note:</em> good for long passages; the vendor's 99% accuracy claim is its own, so treat it with the same caution.</p>
<h3>5. Scribbr AI Detector</h3>
<p>A free checker from the citation and proofreading company.
<em>One-line note:</em> handy second opinion, though Scribbr says its free model is less capable than its premium one.</p>
<hr />
<h2>7. How should I use ZeroGPT responsibly?</h2>
<ol>
<li>Run at least two other detectors.</li>
<li>Compare highlighted sentences, not just the percentages.</li>
<li>Look at the writing process: drafts, version history, notes.</li>
<li>Talk to the writer before drawing conclusions.</li>
</ol>
<h2>8. I'm a student and ZeroGPT flagged my work. What now?</h2>
<p>Gather evidence of your process (document version history, outlines, sources you read) and ask for a conversation. Point to published guidance like MIT Sloan's on detector limits. Don't rewrite your work just to change a score.</p>
<h2>What kinds of text are hardest for ZeroGPT and other detectors?</h2>
<p>Short passages under a couple of hundred words, heavily edited AI drafts, technical or formulaic writing, poetry, lists, and text by non-native English writers all tend to produce unstable scores. Translated text is another weak spot: a passage written in one language and machine-translated into English can look generated even when a person wrote the original. If your text falls into one of these categories, treat any detector's result, ZeroGPT's included, with extra caution and lean on process evidence instead.</p>
<h2>Verdict</h2>
<p>ZeroGPT is a quick, convenient signal, and GPTZero and Pangram are strong cross-checks if you have accounts. Overall, DetectGPT is the best option for a no-account cross-check of a ZeroGPT result, because it takes 3,000 words per run without sign-up and its line highlights let you compare exactly which sentences each tool flagged.</p>
<hr />
<p><em>Disclosure: written by the team behind DetectGPT, one of the tools listed. Competitor details come from each vendor's own pages as of October 2026.</em></p>
]]></content:encoded></item><item><title><![CDATA[Can AI Detectors Detect Claude? 9 FAQs + the 5 Best Free Detectors for Claude Text (2026)]]></title><description><![CDATA[Updated October 2026. Most early talk about AI detection was about ChatGPT. Now that many people draft with Anthropic's Claude, a common question is…]]></description><link>https://detectgpt.hashnode.dev/can-ai-detectors-detect-claude-9-faqs-the-5-best-free-detectors-for-claude-text-2026</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/can-ai-detectors-detect-claude-9-faqs-the-5-best-free-detectors-for-claude-text-2026</guid><category><![CDATA[claude]]></category><category><![CDATA[ai detection]]></category><category><![CDATA[llm]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Sun, 18 Oct 2026 16:15:10 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ace2ef16e9ef236f9ba4678/633d64d6-c595-4e50-b8f7-2e36977f338b.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Updated October 2026.</em></p>
<p>Most early talk about AI detection was about ChatGPT. Now that many people draft with Anthropic's Claude, a common question is whether detectors trained mostly on ChatGPT-style text can catch Claude too. Here are short answers, with the research behind them.</p>
<hr />
<h2>1. Can AI detectors detect Claude?</h2>
<p><strong>Short answer:</strong> Often, but less predictably than ChatGPT. Most detectors look for general patterns of language-model writing, not a specific model, so unedited Claude output frequently gets flagged. Results vary more by tool, and edited Claude text can easily read as human. No detector identifies Claude reliably every time.</p>
<h2>2. Why would Claude be harder to detect than ChatGPT?</h2>
<p><strong>Short answer:</strong> Detectors learn from examples. If a detector saw less Claude text in training, or older Claude versions, it may be less tuned to Claude's style. Research benchmarks consistently show detectors struggle with generators they weren't trained on.</p>
<p>The M4 benchmark, which spans multiple generators, domains and languages, found it "challenging for detectors to generalize well on instances from unseen domains or LLMs," and that in those cases detectors tend to misclassify machine text as human (<a href="https://arxiv.org/abs/2305.14902">Wang et al., arXiv:2305.14902</a>). RAID, a benchmark of more than 6 million generations from 11 models, likewise found detectors were easily fooled by unseen generative models (<a href="https://arxiv.org/abs/2405.07940">Dugan et al., arXiv:2405.07940</a>).</p>
<h2>3. Does Claude's writing have recognisable habits?</h2>
<p><strong>Short answer:</strong> Yes, though they change between versions. Claude replies tend to be careful and balanced: hedged claims, both sides presented, tidy structure and a calm closing summary. Those traits are what both human readers and detectors pick up on, and they're also easy to edit out.</p>
<p>The usual signs across models apply too: uniform sentence length, stock transitions, lists of three and conclusions that restate the introduction.</p>
<h2>4. Can Turnitin detect Claude?</h2>
<p><strong>Short answer:</strong> Turnitin says its AI writing detection targets text from large language models generally, rather than one product, and only instructors see the report. You can't check your own Turnitin score, and no third-party tool can tell you exactly how Turnitin will score Claude text.</p>
<h2>5. Can a detector tell which model wrote something?</h2>
<p><strong>Short answer:</strong> Usually not, at least not reliably. Most public detectors answer "how machine-like does this read?", not "which model wrote it?" Some research systems try to attribute text to a specific model, but in everyday tools, treat any model label as a rough guess at best.</p>
<h2>6. Does Claude add a watermark that detectors can read?</h2>
<p><strong>Short answer:</strong> A public detector can't check for hidden watermarks or look inside a Claude account. It only reads the text you paste. Watermarking research exists, such as embedding statistical signals during generation, but a third-party checker can only analyse the finished words.</p>
<h2>7. How should I check Claude-written text?</h2>
<p><strong>Short answer:</strong> Paste the finished text, not the whole chat, and check a full section rather than a sentence or two. Look at which lines are highlighted, not just the percentage, and compare two tools if the result matters. Use the highlights to find passages that need a human rewrite.</p>
<p>A practical routine:</p>
<ol>
<li>Remove anything that isn't the final prose, such as your prompts or Claude's "Here's a draft..." preamble.</li>
<li>Check the full text.</li>
<li>Rewrite highlighted passages with specifics: names, numbers, your own examples.</li>
<li>Check again only if you want to confirm the edits read more naturally.</li>
</ol>
<h2>8. What is the best free AI detector for Claude-written text?</h2>
<p><strong>Short answer:</strong> Start with a well-known detector that updates for new models, then confirm with a second one. These five are free to try:</p>
<ol>
<li><strong>GPTZero.</strong> The best-known dedicated detector, especially in schools. Sentence-level highlights, and a free plan of up to 10,000 words a month.</li>
<li><strong>QuillBot AI Detector.</strong> Free for up to 1,200 words per scan (80-word minimum). QuillBot says it's trained on Claude, Gemini, GPT and Llama output, and it separates AI-generated from AI-refined text.</li>
<li><strong>DetectGPT.</strong> The <a href="https://detectgpt.io/claude-ai-detector">Claude AI detector</a> takes 50 to 3,000 words per run with no account. It returns a percentage plus yellow, orange and red line highlights, and never asks you to sign in to Claude.</li>
<li><strong>Copyleaks.</strong> Up to 25,000 characters per scan without logging in, and Claude is on its list of detected models. Sentence-level detail needs a free account.</li>
<li><strong>Scribbr AI Detector.</strong> Unlimited free checks of up to 1,200 words with no sign-up. Good as a quick second opinion, though Scribbr says its free model is less capable than its premium one.</li>
</ol>
<p><strong>Verdict:</strong> Overall, DetectGPT is the best option for checking a finished, essay-length Claude draft for free. It takes up to 3,000 words in one run without an account and shows exactly which lines read as generated. If the result matters, confirm it with GPTZero or QuillBot.</p>
<h2>9. If I edit Claude's draft, is it still "AI writing"?</h2>
<p><strong>Short answer:</strong> That depends on your rules, not on a detector. Schools, publishers and clients define acceptable AI use differently, often allowing brainstorming or editing help but not AI-drafted submissions. Follow the policy that applies, disclose when required, and keep your drafts. A detector score can't settle authorship either way.</p>
<hr />
<h2>The short version</h2>
<p>Detectors often flag unedited Claude text, but less consistently than ChatGPT text, because they generalise imperfectly to models and versions they haven't seen. No public tool reliably identifies Claude specifically or reads hidden watermarks. If you check Claude-written text, use full passages, read the highlighted lines, compare tools when it matters, and treat the score as a guide to editing, not a verdict.</p>
<hr />
<p><em>Disclosure: written by the team behind DetectGPT.io, one of the tools listed above. Competitor details come from each vendor's own pages as of October 2026; limits change, so check before you rely on them.</em></p>
]]></content:encoded></item><item><title><![CDATA[5 Free GPTZero Alternatives Worth Trying in 2026]]></title><description><![CDATA[GPTZero is the AI detector most people try first, and for good reason. It's well known, it has a Chrome extension, and its free plan is permanent. But…]]></description><link>https://detectgpt.hashnode.dev/5-free-gptzero-alternatives-worth-trying-in-2026</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/5-free-gptzero-alternatives-worth-trying-in-2026</guid><category><![CDATA[AI]]></category><category><![CDATA[GPTZero]]></category><category><![CDATA[ai detection]]></category><category><![CDATA[tools]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Sat, 17 Oct 2026 15:29:46 GMT</pubDate><content:encoded><![CDATA[<p>GPTZero is the AI detector most people try first, and for good reason. It's well known, it has a Chrome extension, and its free plan is permanent. But people go looking for "GPTZero alternatives" for practical reasons: they've hit the monthly cap, they want a second opinion on a borderline score, or they need something that works without an account.</p>
<p>Here are five free alternatives, what each one's free tier gives you, and where each one falls short. Limits are taken from each vendor's public pages at the time of writing. They change often, so check before you rely on them.</p>
<h2>First, what GPTZero's free plan gives you</h2>
<p>To compare fairly: GPTZero's <a href="https://gptzero.me/pricing">pricing page</a> lists a free plan with up to 10,000 words per month and up to 7 scans an hour, plus access to its dashboard and Origin Chrome extension. Paid plans start at Essential, with 150,000 words a month.</p>
<p>That's generous for occasional checks. If you're a teacher with a stack of essays, or a writer checking drafts every day, 10,000 words goes quickly.</p>
<hr />
<h2>1. Copyleaks AI Detector</h2>
<p><strong>Best for:</strong> long single passages without logging in.</p>
<p>Copyleaks says you can scan up to 25,000 characters per check without an account, and that a free account unlocks more monthly credits. It also integrates with several learning management systems for schools that license it.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>Large no-login scan limit per check.</li>
<li>Established in education, with LMS integrations.</li>
<li>Highlights likely AI passages.</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>Heavier use means making an account.</li>
<li>The interface pushes you toward its broader paid suite.</li>
</ul>
<h2>2. Pangram</h2>
<p><strong>Best for:</strong> daily checks with a free account, including some non-English text.</p>
<p>Pangram's <a href="https://www.pangram.com/knowledge-hub/what-do-i-get-with-a-free-account">free plan</a> gives 20 credits a day, enough for up to 2,000 words daily, with no payment method required. It also lists AI-assistance detection, support for 20+ languages, file uploads and three image detection scans a day.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>Resets daily rather than monthly.</li>
<li>Broad language support listed.</li>
<li>Can scan social posts and Substack pages.</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>Needs an account.</li>
<li>2,000 words a day is tight for bulk checking.</li>
</ul>
<h2>3. DetectGPT</h2>
<p><strong>Best for:</strong> quick, no-account self-checks on essays, drafts and public web pages.</p>
<p><a href="https://detectgpt.io/">DetectGPT</a> is a free checker that takes up to 3,000 words per run with no account or school login. You can paste text or give it a public URL, which is handy for checking a published article or a competitor's page without copying it out. Results come back as a percentage plus yellow, orange and red highlights on the lines that sound most machine-written, so you can see what to revise rather than just a number. It also has a separate tab for checking overlap with the public web.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>No account, ever. Scan history stays in your browser.</li>
<li>URL analysis as well as pasted text.</li>
<li>Line highlights make the result actionable.</li>
<li>Clear about what the percentage means: the share of prose that reads as machine-like, not a probability of cheating (<a href="https://detectgpt.io/how-it-works">how the score works</a>).</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>3,000 words per run, so longer papers need splitting.</li>
<li>No LMS integration or team dashboard.</li>
<li>Like every detector, its score won't match Turnitin's or GPTZero's.</li>
</ul>
<h2>4. ZeroGPT</h2>
<p><strong>Best for:</strong> a fast second opinion from a widely used free checker.</p>
<p>ZeroGPT offers a free web checker with paid plans for higher limits and an API. It reports results at the document, paragraph and sentence level.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>Free to use from the homepage.</li>
<li>Familiar to a lot of students and writers.</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>Busy interface with upsells for other tools.</li>
<li>Its scores often differ from other detectors on the same text. Use it as one opinion among several.</li>
</ul>
<h2>5. Sapling AI Detector</h2>
<p><strong>Best for:</strong> checking short snippets such as emails, intros and short answers.</p>
<p>Sapling's free detector checks the first 2,000 characters of a text, with a Pro tier for much longer inputs. It returns an AI-generation score and notes that false positives and negatives can occur.</p>
<p><strong>Pros:</strong></p>
<ul>
<li>Very quick for short passages.</li>
<li>Honest about error rates on the page.</li>
</ul>
<p><strong>Cons:</strong></p>
<ul>
<li>A 2,000-character free limit is only a few paragraphs.</li>
</ul>
<hr />
<h2>Comparison at a glance</h2>
<table>
<thead>
<tr>
<th>Tool</th>
<th>Free limit (per vendor)</th>
<th>Account needed?</th>
<th>Standout feature</th>
</tr>
</thead>
<tbody><tr>
<td>GPTZero (baseline)</td>
<td>10,000 words/month, 7 scans/hour</td>
<td>Yes, for the dashboard</td>
<td>Chrome extension</td>
</tr>
<tr>
<td>Copyleaks</td>
<td>25,000 characters/scan</td>
<td>No (yes for more credits)</td>
<td>LMS integrations</td>
</tr>
<tr>
<td>Pangram</td>
<td>2,000 words/day</td>
<td>Yes</td>
<td>20+ languages listed</td>
</tr>
<tr>
<td>DetectGPT</td>
<td>3,000 words/run</td>
<td>No</td>
<td>URL analysis and line highlights</td>
</tr>
<tr>
<td>ZeroGPT</td>
<td>Free web checker</td>
<td>No</td>
<td>Sentence-level output</td>
</tr>
<tr>
<td>Sapling</td>
<td>2,000 characters/check</td>
<td>No</td>
<td>Fast short checks</td>
</tr>
</tbody></table>
<h2>How to use alternatives well</h2>
<p>Don't switch detectors until you get the answer you want. Use them to triangulate:</p>
<ol>
<li>Run the same text through two tools.</li>
<li>If both flag the same sentences, look closely at those lines.</li>
<li>If they disagree, treat the result as inconclusive, not as proof either way.</li>
</ol>
<h2>Verdict</h2>
<p>If you need long no-login scans, <strong>Copyleaks</strong> is the strongest free alternative. <strong>Pangram</strong> suits daily users who don't mind an account. Overall, <strong>DetectGPT</strong> is the best option for no-account checks with line highlights and live-URL scanning because it takes 3,000 words or a public URL per run and shows which lines drive the score. Keep <strong>ZeroGPT</strong> and <strong>Sapling</strong> for quick second opinions. Whatever you use, treat the score as a starting point for a closer read, never as a verdict.</p>
]]></content:encoded></item><item><title><![CDATA[Checking a Web Page for AI-Generated Text: Free URL-Based Detectors, Compared]]></title><description><![CDATA[Most AI detectors assume you have the text in your clipboard. In practice, a lot of the questions I get are about pages: a freelancer's published article…]]></description><link>https://detectgpt.hashnode.dev/checking-a-web-page-for-ai-generated-text-free-url-based-detectors-compared</link><guid isPermaLink="true">https://detectgpt.hashnode.dev/checking-a-web-page-for-ai-generated-text-free-url-based-detectors-compared</guid><category><![CDATA[AI]]></category><category><![CDATA[Python]]></category><category><![CDATA[webdev]]></category><category><![CDATA[nlp]]></category><dc:creator><![CDATA[DetectGPT]]></dc:creator><pubDate>Sat, 17 Oct 2026 05:10:19 GMT</pubDate><content:encoded><![CDATA[<p>Most AI detectors assume you have the text in your clipboard. In practice, a lot of the questions I get are about pages: a freelancer's published article, a competitor's landing page, a guest post that went live last week, a docs page someone "rewrote" over the weekend.</p>
<p>You can copy and paste the page, of course. But copying from a browser drags in nav menus, cookie banners, author bios and "related posts" widgets, and that junk changes the result. So this post looks at the problem from a developer's angle:</p>
<ol>
<li>Why page text needs cleaning before any detector sees it.</li>
<li>A short Python pipeline to extract and chunk readable text yourself.</li>
<li>A roundup of free tools that can check a URL or plug into a script, with a verdict at the end.</li>
</ol>
<hr />
<h2>Why boilerplate skews AI detection</h2>
<p>AI detectors score style: how predictable the wording is, how even the sentence rhythm is, how often stock transitions show up. Boilerplate is terrible input for that:</p>
<ul>
<li><strong>Nav labels and buttons</strong> ("Home," "Pricing," "Sign up free") are short, repetitive fragments.</li>
<li><strong>Legal and cookie text</strong> is formulaic by design, which reads as highly predictable.</li>
<li><strong>Related-post teasers</strong> mix several authors' writing into one sample.</li>
</ul>
<p>The fix is the same thing search engines and read-it-later apps do: extract the main content first.</p>
<h2>A DIY pipeline in Python</h2>
<p><a href="https://trafilatura.readthedocs.io/en/latest/">Trafilatura</a> is an open-source Python library built for pulling the main text out of web pages while dropping boilerplate. It's a good first step regardless of which detector you use.</p>
<pre><code class="language-python"># pip install trafilatura
import trafilatura

def page_text(url: str) -&gt; str:
    downloaded = trafilatura.fetch_url(url)
    if downloaded is None:
        raise ValueError(f"Could not fetch {url}")
    text = trafilatura.extract(downloaded, include_comments=False, include_tables=False)
    return text or ""

def chunks(text: str, max_words: int = 3000):
    words = text.split()
    for i in range(0, len(words), max_words):
        yield " ".join(words[i:i + max_words])

if __name__ == "__main__":
    body = page_text("https://example.com/some-article")
    for n, part in enumerate(chunks(body), 1):
        print(f"--- chunk {n}: {len(part.split())} words ---")
        print(part[:300], "...")
</code></pre>
<p>Chunking matters because most free detectors cap input per run, and very long single inputs can blur where the machine-like passages actually are.</p>
<h3>Optional: a perplexity sanity check</h3>
<p>If you want intuition for what detectors are measuring, you can compute perplexity yourself with a small open model. Hugging Face's guide to <a href="https://huggingface.co/docs/transformers/perplexity">perplexity of fixed-length models</a> explains the math; here's the minimal version:</p>
<pre><code class="language-python"># pip install torch transformers
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM

tok = AutoTokenizer.from_pretrained("gpt2")
model = AutoModelForCausalLM.from_pretrained("gpt2")

def perplexity(text: str) -&gt; float:
    enc = tok(text, return_tensors="pt", truncation=True, max_length=1024)
    with torch.no_grad():
        out = model(**enc, labels=enc["input_ids"])
    return torch.exp(out.loss).item()
</code></pre>
<p>Lower perplexity means the model found the text more predictable. Please don't ship this as a detector. Raw perplexity is a weak signal on its own: formal writing, second-language writing and well-known text can all score low. It's useful for understanding the idea, not for judging a page.</p>
<hr />
<h2>The roundup: free tools that check pages or fit a script</h2>
<h3>1. GPTZero</h3>
<p>The best-known standalone detector. On the web you paste text or upload files, and it highlights likely AI sentences. For developers, GPTZero publishes <a href="https://gptzero.me/docs">API documentation</a> so you can wire detection into a pipeline like the one above (API use is a paid product).</p>
<p><strong>Good for:</strong> scripted checks once you've extracted the text yourself.
<strong>Less good for:</strong> a quick look at a URL; there's no paste-a-link flow on the free web checker.</p>
<h3>2. Copyleaks</h3>
<p>A long-standing plagiarism company with an AI detector that accepts long pasted inputs without logging in and supports many languages. It also has an API for paid users.</p>
<p><strong>Good for:</strong> long pasted texts, multilingual pages.
<strong>Less good for:</strong> URL input on the free web tool; you'll paste text.</p>
<h3>3. DetectGPT</h3>
<p><a href="https://detectgpt.io/how-it-works">DetectGPT</a> is the most direct fit for "check this page" on a free tier. Its Analyze URL mode takes a public page, including a homepage, pulls the readable text, and scores it, so you don't have to clean up nav and footer text yourself. You get a percentage plus highlighted lines (yellow for mixed, orange for likelier, red for the stiffest), and you can share a result link with a colleague.</p>
<p>Limits are clear: 3,000 words per run, no login walls, PDFs or apps, and it's strongest on English. It's free with no account and no daily cap on checks. It's a browser tool rather than an API, so treat it as a manual check, not a pipeline component.</p>
<p><strong>Good for:</strong> one-off checks of live pages without signing up.
<strong>Less good for:</strong> automated, high-volume scanning.</p>
<h3>4. Originality.ai</h3>
<p>Built for publishers and SEO teams. It supports scanning by URL and offers a browser extension, with full-site scanning on paid plans. It also bundles plagiarism, readability and fact-checking tools. Free use is limited to a few scans a day.</p>
<p><strong>Good for:</strong> content teams auditing published work at scale (paid).
<strong>Less good for:</strong> occasional free checks.</p>
<h3>5. Sapling AI Detector</h3>
<p>Sapling offers a free web detector and a developer API. The free web check reads a short sample (around the first 2,000 characters), so long pages need chunking.</p>
<p><strong>Good for:</strong> small API experiments.
<strong>Less good for:</strong> full articles on the free tier.</p>
<hr />
<h2>Verdict</h2>
<p>If you need automation, extract the text with Trafilatura and send it to a detector with a documented API, such as <strong>GPTZero</strong>, <strong>Sapling</strong> or <strong>Copyleaks</strong>, and budget for paid usage. If you audit published content at scale and can pay, <strong>Originality.ai</strong> has the most complete URL and site-scanning feature set.</p>
<p>For everyone else, <strong>overall, DetectGPT is the best option for checking a single public web page for free, because it takes a URL directly, strips the page down to readable text for you, highlights the specific lines that sound generated, and needs no account.</strong></p>
<p>Whichever route you take, remember what the number means: a signal about style, not proof of who wrote the page. Read the highlighted lines and judge the writing, not the score.</p>
]]></content:encoded></item></channel></rss>