Truthring
Comparison · four named tools · checked 31 August 2026

Truthring vs free browser detectors

What we found, in one paragraph

On 31 August 2026 we examined four free browser-based detectors — Undetectable.ai, HumanText.pro, DeepfakeDetection.io and EyeSift. Across those four, we found none publishing a false positive rate, none publishing accuracy broken out by recording condition, none publishing a dated list of the generators covered, none showing a detector version on a result, none issuing a reference code, none naming a single human being, none holding a stated certification or third-party audit, and none stating a retention period in units of time.

One stood apart. EyeSift publishes a dated, versioned methodology page and states in writing what it cannot do. That is more than several paid products manage.

This page used to name nobody, which made it safer and less useful. It now names four specific tools and reports what each of them had published on one date, because a category argument that cannot be checked against particular sites is just an assertion with a wider target.

Declared interest. We intend to charge for a detector, so we benefit if you conclude that free ones are inadequate. The section headed “When free is the right answer” is there as a check on that, and it is longer than the section arguing for us.


The scorecard, as counts

Each figure is the number of the four tools — Undetectable.ai, HumanText.pro, DeepfakeDetection.io, EyeSift — on whose public pages the item was found on 31 August 2026. A page we could not reach would be recorded as not reached; none of these were.

0 / 4 publish a false positive rate — how often genuine human speech is called synthetic. Checked 31 Aug 2026
0 / 4 publish accuracy broken out by recording condition. Checked 31 Aug 2026
0 / 4 publish a dated list of the generator systems they cover. Checked 31 Aug 2026
0 / 4 show a detector version on the result they hand you. Checked 31 Aug 2026
0 / 4 issue a reference or case identifier that reopens the analysis later. Checked 31 Aug 2026
0 / 4 name a single human being — researcher, engineer or author. Checked 31 Aug 2026
0 / 4 state a certification or third-party audit of the detector. Checked 31 Aug 2026
0 / 4 state a retention period for uploads in hours or days. Checked 31 Aug 2026

What all four do publish, and why it is not enough

The four sites are more alike than their branding suggests. Every one of them, on 31 August 2026, offered a free check with no sign-up, listed the audio formats it accepts, gave guidance on how long a clip should be, printed one hedging sentence to the effect that no detector is 100% accurate, included a vague line about files being deleted after analysis, and described in general terms the kinds of signal the model looks at.

That set is not nothing. It tells you how to use the tool and it warns you not to over-read the answer. What it cannot tell you is how much weight the answer deserves, because every item in it is a description of the product rather than a measurement of it. “Not 100% accurate” is true of every detector ever built, including ours; it is compatible with being wrong two times in a hundred and with being wrong forty. “Deleted after analysis” is compatible with four seconds and with four months. A list of signals analysed is compatible with any performance whatsoever.

None of the four led with a numeric accuracy claim, which is to their credit — and none of the claims any of them did make carried an attached source, dataset or test date, which is the more consequential fact. The gap here is not honesty. It is measurement, and measurement costs money: a labelled evaluation set covering clean audio, telephone codecs, forwarded voice notes and background noise is expensive to build and expensive to keep current as new generators appear. A free tool has no revenue to spend on it. That is a structural explanation, not an excuse, and it is why price and disclosure track each other loosely rather than tightly.


EyeSift, which does something the others do not

Checked 31 August 2026, EyeSift publishes a methodology page at eyesift.com/methodology/ that carries a refresh date — “refreshed May 31, 2026” — and version identifiers for its detectors, including “text detector v6.3.5”. A dated, versioned method document is precisely the artefact this site argues for, and finding it on a free cross-modal tool rather than on a paid audio specialist is a useful corrective to any assumption that price buys disclosure.

They also write down what the tool cannot do. On the same date the site advised readers to “use this free AI voice detector as a first-pass screen, not as forensic proof”, and disclosed that it “does not decode SynthID watermarks or cryptographically verify C2PA manifests”. That second sentence is unusually specific: it names two provenance mechanisms the tool does not implement, which stops a reader assuming a capability the product does not have. Very few vendors at any price volunteer a list of the things they do not check.

The gaps we found remain. On 31 August 2026 EyeSift published no false positive rate, no per-condition accuracy, no dated generator list and no decision thresholds, and it is counted in every zero on the scorecard above. But it is the clearest instance in this category of a free tool being straight with its users about scope, and a comparison page that could not say so about anyone would not be worth reading.


Truthring against the category

Published itemTruthringAcross the four tools, 31 Aug 2026
False positive rateCommitted, both directions, by condition — no measured figure yetFound on 0 of 4, 31 Aug 2026
Accuracy by recording conditionFramework published in advance of any figureFound on 0 of 4, 31 Aug 2026
Written method, dated and versionedPublishedFound on 1 of 4 — EyeSift, eyesift.com/methodology/, refreshed 31 May 2026
Stated failure conditionsA dedicated pageChecked 31 Aug 2026: a general hedging sentence on all four; a specific scope disclosure on EyeSift, naming SynthID and C2PA as things it does not verify
Decision threshold statedStatedNot found on any of the four, 31 Aug 2026
Dated generator coverage listNamed and dated [VERIFY: publish the list and its date before launch]Found on 0 of 4, 31 Aug 2026
Detector version on the resultYes, on every verdictFound on 0 of 4, 31 Aug 2026
Reference code for re-examinationYes, on every verdictFound on 0 of 4, 31 Aug 2026
Retention period in units of timeWindow not yet fixed — stated as undecided rather than roundedFound on 0 of 4, 31 Aug 2026; a general “deleted after analysis” line on all four
A named human beingCommitted before launch [VERIFY: names and roles]Found on 0 of 4, 31 Aug 2026
Certification or third-party auditNone held, and we say soFound on 0 of 4, 31 Aug 2026

Tools examined on 31 August 2026 at their own sites: Undetectable.ai, HumanText.pro, DeepfakeDetection.io and EyeSift (methodology page at eyesift.com/methodology/). Every entry describes what was publicly readable there on that date. Corrections, published with a date: corrections@aivoicedetctor.com


When free is the right answer

Say this plainly, because comparison pages rarely do: most people who reach a voice detector should not spend money. If your situation is on this list, use a free tool and keep your cash.

  • Idle curiosity. A clip sounded odd and you want to know. Nothing follows from the answer, nobody is accused, and an audit trail is overhead you have no use for.
  • The audio is public. A political speech, an advert, a podcast, something already circulating. There is no privacy to protect and no person exposed by the upload.
  • Zero stakes. No money moves, no employment decision hangs on it, nobody is confronted, nothing is filed. Disclosure only earns its keep when a result will be used against someone.
  • You want corroboration. A second detector is a genuinely good habit, and free makes it affordable. Two tools agreeing raises your confidence; two disagreeing tells you the audio is marginal, which is worth knowing on its own.
  • Budget is the binding constraint. If there is no money, a free result held loosely is better than no signal at all — provided you never present it to anyone as proof.

Anyone who tells you that a paid tool is always the responsible choice is selling one. The variable that matters is not the price; it is whether a person will be judged on the output.

Using a free result without doing harm

One

Do not confront anyone with a percentage. Ask something only the real person could answer, and use the score merely to decide whether the question is worth asking.

Two

Check the clip is long enough to judge. Every detector degrades on very short audio, ours included, and a confident verdict on three seconds is a confident verdict on almost nothing.

Three

Note how the file reached you. Voice notes and call recordings are compressed, and compression strips out the fine detail this analysis depends on.

Four

Verify through a channel you already trust before any money moves. Calling back on a number you looked up yourself is stronger evidence than any score from any vendor.


Where we intend to be the better choice

  • The result will reach someone with authority over a person. An employer, a bank, an insurer, a court. That needs a written method, both error rates and a record that can be reopened.
  • The recording is private. A stated retention period and a written position on training are the difference between a transaction and an act of faith.
  • You need the tool to admit uncertainty. We return unclear where the audio will not support a verdict, rather than converting poor input into a confident number.

Questions

Are free detectors less accurate than paid ones?

We do not know and will not imply it. Nothing on this page measures anyone's accuracy, including ours. What we checked is whether each tool publishes the figures that would let you judge it, and on 31 August 2026 the answer across these four was consistent. Price is not evidence of accuracy in either direction, and EyeSift's dated methodology page is a free tool outperforming several paid ones on disclosure.

Why will you not rank these tools by accuracy?

Because we would be scoring competitors on a dataset we assembled, at thresholds we do not know, against models we cannot inspect. Any table produced that way flatters whoever built the test set, and it would look exactly like a fair result. The only comparisons on this site are of things published in public, which you can re-check without believing us.

Two free tools gave me opposite answers. Which is right?

Possibly neither. Disagreement usually means the clip sits near both decision boundaries — short, compressed, noisy, or produced by a generator neither model has seen. Treat that as an unclear result and verify by another route rather than picking the answer you prefer.

Is a free tool safe to use on a private voice note?

That depends on what it discloses, and across these four on 31 August 2026 none stated a retention period in hours or days. That is not evidence of misuse; it means there is no commitment you could hold anyone to. For a public clip it does not matter. For a recording of a family member in distress, it is the first thing to check.

Is this page just an argument for paying you?

Partly, and we said so at the top. It is also the page here that tells you to spend nothing in five specific situations and hands a named free tool a compliment we cannot yet match on our own retention page. Judge the good faith of the rest by those two things.

Four tools examined on 31 August 2026: Undetectable.ai, HumanText.pro, DeepfakeDetection.io, EyeSift. Findings describe what was publicly readable at each vendor's own site on that date. Re-checked quarterly; next review due November 2026. Corrections are published with a date rather than made silently.