Chrome extension weekly users dropped? How the Chrome Web Store counts users and how to find the cause

Your Chrome extension weekly users dropped by a fifth in one week, installs look normal, and nobody on the team shipped anything risky. It is one of the most common worried posts in extension developer communities, and the answer is usually one of a handful of causes. Some are real losses, like an update that quietly disabled your extension for existing users. Others are counting effects that fix themselves within a week or two.

This guide explains what the Chrome Web Store actually counts as a weekly user, how to tell a real drop from noise, the causes worth checking in order, and how to set up tracking so the next drop reaches you the day it starts instead of a month later.

Key takeaways

• Google documents weekly users as an installation count: "The Users stats only captures installations; it doesn't monitor whether users are active or not." A drop means fewer browsers reporting the extension, not necessarily fewer people using it.
• The number on your public listing is not the dashboard number. It is rounded for large extensions, can lag for weeks, and is hidden entirely when Google detects suspicious activity.
• The most damaging cause is an update that adds a permission warning. Chrome disables the extension until each user accepts, and many never do.
• Seasonal dips are real. A reply in the Chromium Extensions group blamed a January drop on holidays and predicted "a bounce-back soon as people get back to their daily lives."
• Break the drop down by item version, operating system and country before you guess. Where the drop is concentrated usually names the cause.

How the Chrome Web Store counts weekly users#

Google has never published the exact formula. What it has said is short. The store listing metrics documentation says you can monitor weekly users "categorized by country, language, operating system, and item version", and that "the Users stats only captures installations; it doesn't monitor whether users are active or not."

Developers have filled in the rest by comparing notes. In a Chromium Extensions thread on what counts as a user, the most cited explanation is that the figure reflects unique update checks over a 7-day period. No one from Google confirmed it in that thread, but it matches what developers see: Chrome checks installed extensions for updates "every few hours", according to the extension update documentation, so a browser that is running and has your extension installed shows up, and a laptop that stays closed for a week does not.

Three practical consequences follow:

• It counts browsers, not people. A user signed in to Chrome on three machines can count three times. Our guide to measuring extension retention and uninstall rate explains why weekly users is never simply installs minus uninstalls.
• It is a footprint, not engagement. Someone who installed your extension a year ago and never clicked it still counts as long as their browser runs it.
• Anything that changes how many browsers are online moves it. Holidays, school breaks and office closures all show up, with no uninstalls behind them.

The public listing number is a different thing#

The number visitors see on your listing is related to the dashboard figure but not the same. When a developer asked why the listing still showed 2,000 users after 3,000 new installs, the reply in the Chromium Extensions group was that "the user count on the chrome store takes into account the weekly active users, not the installs", and that it moves in larger brackets as it grows.

You can see the rounding on any listing. At the start of October 2026, uBlock Origin Lite showed "21,000,000 users" and Dark Reader "7,000,000 users", while a small extension showed an exact "79 users". For big extensions, the listing can stay flat for weeks while the dashboard moves, and then jump a whole step at once.

The listing count can also vanish. Chrome Extensions DevRel explained in 2022 that "the user count is not shown when we detect suspicious or potentially abusive activity", without saying what triggers it.

First, check whether the drop is real#

Before you go looking for a cause, rule out the three explanations that need no fix.

1. Compare full weeks. Weekly users is a rolling 7-day figure, so compare the same weekday window to the same window a week, a month and a year earlier. A drop that lines up with late December, a national holiday in your biggest country or the start of summer break is probably seasonal. The January reply quoted above expected exactly that kind of dip to recover on its own.
2. Look at installs and uninstalls for the same days. If installs held steady and uninstalls did not spike, but weekly users fell, browsers went quiet rather than users leaving. If uninstalls jumped, something pushed people to remove the extension.
3. Do not read the latest day or two in isolation. A 2023 reply in the Chromium Extensions group warned that the stats "can often have anomalies" and advised waiting "2 or 3 days to have a stable idea" before reacting.

If the drop survives those checks, work through the causes below. They start with the cause that does the most damage and is quickest to rule out.

The usual causes of a drop in Chrome extension weekly users#

1. An update added a permission warning#

This is the one to rule out first, because it does the most damage and it is self-inflicted. Chrome's permission warnings documentation is blunt: when an update adds a permission that triggers a new warning, "the extension will be disabled until the user accepts the new permission."

Users see a disabled extension and a prompt they did not ask for. Many ignore it, and some remove the extension. The best-documented case is Metastream Remote, which lost 50,000 users over several days after an update added one required permission, against a normal rate of around 700 uninstalls a day. The developer reverted within hours of noticing, but the users who had already left did not come back.

How to confirm it:

• In the Weekly Users page, break the chart down by item version. If the version you just shipped grows much more slowly than the previous one shrinks, existing users are not making the jump.
• Diff the manifests of the two versions. Anything new in permissions, host_permissions or content script matches can add a warning.

A small script in your release pipeline catches this before it ships:

// permission-diff.mjs
// Usage: node permission-diff.mjs old/manifest.json new/manifest.json
import { readFileSync } from 'node:fs';

function requiredAccess(path) {
  const manifest = JSON.parse(readFileSync(path, 'utf8'));
  return new Set([
    ...(manifest.permissions ?? []),
    ...(manifest.host_permissions ?? []),
    ...(manifest.content_scripts ?? []).flatMap((script) => script.matches ?? []),
  ]);
}

const [before, after] = process.argv.slice(2, 4).map(requiredAccess);
const added = [...after].filter((entry) => !before.has(entry));

if (added.length === 0) {
  console.log('No new required permissions or host patterns.');
} else {
  console.log('New required permissions or host patterns:');
  for (const entry of added) console.log(`  + ${entry}`);
  console.log('Check whether any of these adds a permission warning before you ship.');
  process.exitCode = 1;
}

Not every new entry adds a warning, so treat a failure as "look before you ship", not as a hard block. To see the exact prompt existing users will get, Chrome recommends the extension update testing tool. The long-term fix is to move anything you can into optional_permissions and request it at runtime, which never disables the extension.

If you already shipped the warning, publishing a version without the new permission removes the prompt, according to the same 2023 thread, and users who had the extension disabled can turn it back on. The sooner that version is live, the more users you keep. How long that takes depends on the review queue, which our guide to Chrome Web Store review time covers in detail.

2. Seasonality and dormant browsers#

If the drop is spread evenly across versions and operating systems, but concentrated in a few countries, check the calendar for those countries. Work tools dip during holidays, education tools during school breaks, and shopping tools often move the other way. These drops recover without any action, which is exactly why you want a year of history: last year's chart is the best predictor of this year's dip.

3. A takedown, a policy warning or a malware flag#

Since Chrome 117, Safety Check on the extensions page tells users when an installed extension was unpublished by its developer, taken down for a policy violation or marked as malware, and offers to remove it. Extensions marked as malware are disabled automatically. If your listing was taken down, even briefly, expect a lasting drop as users follow that prompt.

These are not rare in 2026. In a thread from September 23, 2026, a developer whose extension disappeared learned that "everything that happened on the Chrome Web Store side was because your Google Account was suspended." Check your developer email, the dashboard status of every item, and the takenDown and warned flags that the Chrome Web Store API returns for your items, which our Chrome Web Store stats API guide shows how to read.

4. Manifest V2 is gone#

If you still had a Manifest V2 build anywhere, it no longer counts. The Manifest V2 support timeline shows Manifest V2 extensions disabled for all Chrome users from July 24, 2025, and "all remaining Manifest V2 extensions have been removed from the Chrome Web Store" as of August 31, 2026. This matters even if you migrated long ago: a competitor that did not migrate will have vanished from search, and a category that suddenly looks different can change your impressions and installs too.

5. Managed browsers in companies and schools#

If your extension is popular with organizations, an admin decision can remove thousands of browsers at once. Chrome's ExtensionInstallBlocklist policy disables blocked extensions that are already installed, with no way for the user to turn them back on. A drop concentrated in one country and one operating system, with no rise in uninstalls from your feedback page, fits this pattern. There is no way to see it in the dashboard directly, but enterprise customers will often tell you if you ask.

6. A real product problem#

When none of the above fits, assume users are leaving for a reason. Read your newest reviews and support email, since a broken feature usually shows up there before it shows up in the weekly users chart. Check whether a browser release landed in the same week: with Chrome, Edge and Firefox now shipping every two weeks, a regression can start without any release of yours. And check competitors. If every extension in your category dropped the same week, the cause is the store or the browser, not you.

A step-by-step diagnosis#

Work through these in order and stop when one explains the drop.

Track weekly users every day so you catch it early#

The Developer Dashboard is the authoritative source for your own extension, but it only shows numbers when you go and look, and it only shows your own items. Most of the drops above are cheap to fix on day one and expensive on day thirty. A permission warning caught the morning after release can be reverted before most users have even seen the prompt. Caught a month later, the users who uninstalled are gone for good.

Three habits make the difference:

• Record the public numbers daily, for your extension and a few competitors. If a rival's users fall the same week as yours, you can stop looking for a bug in your own code.
• Put release dates on the same timeline. A drop that starts the day a version went live is almost always that version. Our checklist of what to watch in the week after an extension release covers the rest of that week.
• Alert on change, not on schedule. A threshold alert on users and uninstalls beats a weekly report nobody opens. Setting up store change alerts your team will actually read covers which changes deserve a same-day ping.

That is what Extenify was built for. The browser extension analytics dashboard records installs, ratings, reviews and versions for your Chrome Web Store, Edge Add-ons and Firefox Add-ons listings every day, puts version markers on the growth chart, and sends a daily alert to email, Slack, Telegram, Discord or Teams when users or ratings move past the thresholds you set. You can track competitors the same way, since it only needs the public listing. Tracking one extension is free, and the pricing page lists what the paid plans add, including longer history and CSV export.

Frequently asked questions#

Why did my Chrome extension's weekly users drop when uninstalls did not increase?#

Weekly users counts browsers that have the extension installed, so it falls when fewer of those browsers are online, even if nobody uninstalls anything. Holidays, school breaks and synced devices going quiet all cause this. If installs and uninstalls are normal, compare the same weeks last year before assuming a real loss.

How often does the user count on a Chrome Web Store listing update?#

Google has not published a schedule. The listing reflects weekly users rounded into brackets, and developers have reported it staying unchanged for several weeks while the dashboard moved. Use the Developer Dashboard for your own numbers, and treat the public figure as a rough, delayed signal.

Why is the user count missing from my Chrome Web Store listing?#

Chrome hides the listing user count when it detects suspicious or potentially abusive activity, according to Chrome Extensions DevRel. Google does not say what triggers it, so the most useful thing you can do is check whether any recent traffic or install source behaves very differently from the rest.

Will users come back after I remove a permission that triggered a warning?#

Some will. Publishing a version without the new permission removes the prompt, and users whose extension was disabled can re-enable it. Users who already uninstalled are gone, so speed matters more than anything else once you spot the problem.

Do disabled extensions still count as weekly users?#

Google has not documented this. The dashboard shows an enabled versus disabled breakdown, which suggests disabled installs are tracked separately, and in the Metastream case the loss played out over several days rather than overnight. Watch both the weekly users chart and the uninstall chart after any risky update.

Summary#

A drop in Chrome extension weekly users is either a counting effect or a real loss, and the dashboard can usually tell you which within a few minutes. Compare full weeks against last year, check whether uninstalls moved, and break the drop down by version, operating system and country. If the newest version is not picking up users, look for a permission warning first. If the whole category dropped, look at the browser and the store. Then make sure the next drop reaches you on day one, with daily tracking, release markers and an alert on the numbers that matter.

Image credits#

• Cover photo: Empty auditorium with rows of blue seats by Tomek Lach on the WordPress Photo Directory, CC0.