How we choose Chrome extensions

How does Xplorekit pick extensions?

We start from two sources: the extension's Chrome Web Store listing and its official website or source code. From those we check what it does, the main permissions it asks for, whether it needs an account, its price and whether it is open source. It must also be updated in the last 12 months and run on current Chrome.

Here is the full list of checks for every pick:

• What it does. One clear job, described from the listing and the official site.
• Main permissions. What access it asks for, such as reading the sites you visit.
• Account. Whether you have to sign in to use it.
• Price. Free, free with paid extras, or paid.
• Open source. Whether its code is public.
• Maintained. Updated in the last 12 months.
• Works today. Runs on the current version of Chrome.

If an extension fails the update check, or we can't confirm a fact the page needs, it waits. We don't list it until we can.

Xplorekit has no sponsors and no affiliate deals; no one pays to be listed or ranked.

Are the extensions in the directory safe?

We can't promise any extension is safe. They are third-party tools, not built or run by Xplorekit. What we can do is show you the facts that matter for safety: permissions, publisher, open-source status and when it was last updated. Installing, and what data the extension handles, is between you and its publisher.

That is why every directory page:

• Says clearly that the pick is a third-party extension.
• Links to the official Chrome Web Store listing, so you install from the source.
• Lists the main permissions where we could confirm them.
• Notes when the code is open source, so anyone can check it.

Our own extensions are different. We build them, and they collect no data. See About Xplorekit for details.

Why don't you show star ratings or user counts?

Because we can't verify them. Store ratings and install counts change all the time, and we can't check where they come from. So we don't show ratings, user counts or download numbers on any page. We also leave out any other fact we can't confirm. If we aren't sure, it isn't on the page.

You can still see ratings and reviews on each extension's Chrome Web Store listing. We link to it from every page.

Who reviews the picks, and how often?

Picks are reviewed by Xplorekit's independent developer. Each page shows a “Last checked” date, so you can see when we last looked at it. We recheck picks over time. If an extension stops being maintained, we remove it from the directory rather than leave an out-of-date recommendation in place.

How can I check an extension myself before installing it?

Open the extension's Chrome Web Store listing and spend two minutes on it. Look at the permissions it asks for, who publishes it, when it was last updated and what recent reviews say. If something doesn't add up, skip it. These are the same checks we use, and they work for any extension.

Before you click “Add to Chrome”:

1. Read the permissions. Does it ask for more than its job needs? A simple timer has no reason to read every site you visit.
2. Check the publisher. Is there a real website or source code behind it? Does the name match the official project?
3. Check the update date. An extension that hasn't been updated in over a year may not keep up with Chrome.
4. Read recent reviews on the store. Look for recent complaints about ads, redirects or sudden changes.
5. Look for open source. Public code isn't a guarantee, but it means others can check it.
6. Install fewer extensions. Each one you add is one more thing with access to your browser. Remove the ones you no longer use.

How do I suggest an extension or report an error?

Use our contact page. Tell us the extension's name and its Chrome Web Store link. If you spot a mistake, such as an out-of-date fact or an extension that no longer works, send the page link and what is wrong. We fix the page, or remove the pick if it no longer meets our checks.

Browse the picks in the Extension Directory, or read more about Xplorekit.