How we score antidetect browsers

Last updated: 2026-08-24

Every score on this site comes from published vendor documentation and hands-on use of the free tier. We do not run a paid testing lab, we do not buy long-term licences, and we do not claim months of monitoring data. Stating that plainly is the point of this page.

What we actually do

For each product we read the official pricing page, the help centre and the documentation; we register for the free tier where one exists and create profiles in it; and we record the date every figure was checked.

Where a vendor's own pages contradict each other, we follow the documentation rather than the marketing copy, and we tell you the contradiction exists. Documentation describes what the software requires in order to run. A landing page describes what someone wants you to believe before you install it. When the two disagree, the first one is the one you will actually experience.

What this method is good at: pricing, published limits, platform coverage, API surface, and the gap between marketing copy and documentation. What it cannot tell you: how well a fingerprint holds up against a specific platform's detection over weeks of real use. No public review can tell you that honestly, because the answer changes weekly and depends on your proxies, your accounts and your behaviour far more than on the browser.

Scoring criteria

Every criterion resolves to something you can check yourself against the vendor's own documentation. Nothing here rests on a private measurement.

Free tier20%

Profile count, time limit, and which features are withheld.

Entry price20%

Lowest paid tier, profiles included, and the annual discount.

Automation and API20%

Documented API, published rate limits, and framework support.

Team features15%

Seats included, per-seat cost, roles and permissions.

Platform coverage15%

Operating systems with an official build.

Documentation clarity10%

Whether published limits are specific, current, and internally consistent.

Scores are recalculated whenever a vendor changes published pricing or limits. The date on each product page is the date its figures were last checked.

Who writes this

Pages are produced and maintained by the site's editorial team rather than credited to a named reviewer. We would rather show you the sources than a byline: every factual claim on this site links to the vendor page or documentation it came from, with the date it was read. You can check any of it without taking a person's word for it.

Disclosure

Some links on this site are affiliate links, which means we may be paid if you sign up through them. Affiliate status does not affect a product's score or its position in any list, and the scoring weights above were fixed before any product was scored.

The clearest test of that: the one product on this site we have an affiliate relationship with ranks last of the four we have scored, and its review leads with the reasons why. We do not accept payment for placement and we do not remove low scores on request.

Corrections

Pricing in this category changes often, and vendors sometimes revise free-tier limits with little notice. If a figure here is out of date, the date stamp tells you how stale it is. Vendors who spot an error are welcome to write in; corrections are made without conditions.

Reviews scored with this method

How to read a figure on this site

Every number carries the same three things: the value, a link to the vendor page it came from, and the date that page was read. Where a figure is not the vendor's own, it is marked and the distinction is stated explicitly.

Notation · checked 2026-08-24
MarkingMeans
Plain valuePublished by the vendor on its own pricing page, help centre or documentation
Value with an asteriskNot published by the vendor. Reported by third-party sources and labelled as such wherever it appears
Em dashThe vendor does not publish this figure. Never a zero and never our estimate
Documented / advertisedThe vendor's own pages disagree. We follow the documentation and print both