Scribbr AI Detector vs Turnitin: What the Documentation Actually Says

Scribbr's AI detector is a free tool available to anyone. Turnitin's AI writing detection is institution-only, and whether your own school switched it on is a separate question, covered in do colleges use AI detectors. The two tools are built by different teams using different underlying models. Each was trained on its own data and classifies text using its own approach. When two detectors use different models, they produce different scores on the same text. A passage that Scribbr flags as 65% AI might receive a 30% score from Turnitin, or the reverse. Neither result is necessarily wrong. They are probability estimates from different models trained on different datasets.

There is no universal AI-detection score that all tools converge on, and the reasons are laid out in why the same text scores differently on every detector. Each detector produces its own estimate. Treating scores from different tools as if they measure the same thing in the same units leads to confusion.

We are not making a claim about which tool is more accurate. We are describing what Turnitin's documentation says about its own system and why that system produces scores that will not match Scribbr's.

Turnitin documents a specific process for arriving at its AI writing score:

"When a paper is submitted to Turnitin, sentences from the submission are extracted and segmented into overlapping sections for prediction analysis. Each segment is classified by the AI detection model and given a value between 0 and 1, denoting the probability of the text being likely human or AI-generated. Each qualifying sentence within these segments inherits the segment's score. Since segments overlap, some sentences may have multiple scores, which are then pooled into a single score. These sentence scores are further aggregated and used to compute the overall document AI writing score."

The process involves extracting sentences, segmenting them into overlapping units, scoring each segment, pooling sentence scores, and aggregating into a document-level percentage. Other detectors, including Scribbr, may use different segmentation strategies, different prediction units, or aggregation methods. The two tools will not produce matching numbers on the same text.

Turnitin's documentation also clarifies that the AI writing detection percentage and the Similarity score are separate. "The Similarity score and the AI writing detection percentage are completely independent and do not influence each other." A document can have high similarity and low AI, or vice versa. The two numbers do not influence each other.

Turnitin publishes a specific false positive target:

"We strive to maximize the effectiveness of our detector while keeping our false positive rate - incorrectly identifying fully human-written text as AI-generated - under 1% for documents with over 20% of AI writing."

The qualifier matters. The target is stated specifically for documents with over 20% of AI writing, a threshold that does not mean what people assume, as is 20% AI too high works through. This is what Turnitin says about its own system. Scribbr may have different accuracy targets, different validation processes, or may not publish comparable figures. We cannot make a direct accuracy comparison. We can only report what Turnitin's documentation states.

Document length affects how Turnitin's detector processes text. For short documents, the scoring mechanism behaves differently. The documentation states:

"In shorter documents where there are only a few hundred words, the prediction will be mostly 'all or nothing' because we're predicting on a single segment without the opportunity to overlap."

"This means that some text that is a mix of AI-generated and original content could be flagged as entirely AI-generated."

The overlap mechanism that averages out scores in longer documents does not operate when the text is a single segment. A few hundred words of mixed human and AI content could return a 100% score, one of the routes described in why Turnitin says your work is 100% AI. This is a structural behavior on short inputs. Scribbr may process short documents through a different mechanism and arrive at a different result for the same text.

Turnitin suppresses numeric scores below 20%. The documentation states:

"To avoid potential incidence of false positives, no score or highlights are attributed for AI detection scores in the 1% to 19% range. When AI is detected below the 20% threshold in the report, it is now indicated with an asterisk (*%) and no percentage is attributed."

A document that Turnitin's model estimates at 10% AI will show an asterisk in the report, not the number 10%. No highlights are applied to the text. The rationale is to avoid surfacing potential false positives in a low-confidence range, which what the asterisk (*%) means on a Turnitin AI score covers in more detail.

Scribbr may display scores in this range as a full percentage. Other tools may highlight text at any non-zero level. Turnitin deliberately suppresses both the number and the highlights below 20%. This scoring convention means the two tools will present very different outputs for the same low-AI document.

If you are comparing Scribbr and Turnitin results on the same document, here is the summary:

• Separate models, separate scores. Scribbr and Turnitin use different detection models. Their scores are not expected to match.
• Turnitin scores by segmenting and aggregating. Sentences are extracted, segmented into overlapping units, scored, pooled, and aggregated. The AI score and Similarity score are fully independent.
• Turnitin targets under 1% false positives for documents with over 20% AI writing.
• Short documents get all-or-nothing scores. A few hundred words may come back as 0% or 100% even for mixed text.
• Scores below 20% show as an asterisk. No numeric percentage or highlights appear in the 1-19% range.

Eligible passages can be re-run at no charge.