How we test Chrome extensions

Last updated 17 September 2026

Every review on this site follows the same method. Here is exactly what we do, what we look at and how we decide which extension makes a best-of list.

The short version

We install the extension in a clean Chrome profile, use it for the tasks it advertises, and write down what actually happened. We do not publish a review for an extension we have not opened. Where we could not verify a claim, we say so on the page instead of repeating the developer's marketing copy.

What we check on every extension

Does it do the job it promises? The headline feature is tested first. If an extension claims to block ads, we load the same set of pages with and without it and compare what is left on screen.
What permissions does it ask for? We read the permissions list from the Chrome Web Store listing and flag anything that looks broader than the job needs — for example, access to all sites for an extension that only works on one site.
How does it behave under load? We open a normal browsing session (30+ tabs) and watch for slowdowns, crashes and memory growth. Extensions that noticeably slow the browser are called out in the cons section.
Is it maintained? We record when the listing last received an update and how the developer answers user reports. An abandoned extension with a broken feature is a warning for readers, not a recommendation.
What does it cost? Free, freemium and paid plans are separated clearly. If a feature is locked behind a subscription, the review says which one.
What are the alternatives? No extension is reviewed in isolation. Each page links to the closest rivals and to a head-to-head comparison where one exists.

Where the data comes from

Ratings, install counts, version numbers and the last-update date on a listing page come from the public Chrome Web Store entry and are refreshed on a schedule. The written review, the verdict, the pros and cons and the FAQ answers are written by our editors — they are not scraped from the store or generated from the developer's description.

We are explicit about that split because it matters: numbers change weekly, opinions should not change quietly. When we revise an opinion we change the "last reviewed" date shown on the review.

What we will not do

We do not accept payment for a place in a best-of list or for a better verdict.
We do not publish reviews of extensions we have never installed.
We do not copy the store description and call it a review.
We do not hide a paid plan behind the word "free". If money is involved, the review says so in the first two sentences.

Corrections

Extensions update constantly, so reviews go stale. If a feature has changed, a bug has been fixed or an extension has been sold to a new developer, tell us and we will re-test and update the page. Corrections are made in the open and the review date is bumped.