Google Play download count: how to see how many downloads any app has, and track it over time

The Google Play download count is the first number people check on a competitor's listing, and the least precise one. Every listing shows a figure such as "500K+ Downloads", which can mean 500,000 or 4.9 million. Developers who want a real number for a competitor, a market estimate or an investor deck usually end up asking the same question on forums: is there any way to see how many downloads an app actually has?

There is more than the badge, but less than an exact count. This guide explains how the public Google Play download count works, the more precise figure that sits in the listing's page data, where your own numbers live in the Play Console, why the App Store and the Chrome Web Store work differently, and how to track downloads for any app day by day with a short Node.js script. The figures below were read from public listings on October 17 and 18, 2026.

Key takeaways

• The visible Google Play download count is a bucket: 100K+, 500K+, 1M+, 5M+, 10M+ and so on. The real number can be up to five times the label (or twice it, for buckets that start with 5).
• The listing page also carries a more precise figure, such as 678,441 for an app labeled "500K+". Google does not document it, so treat it as an estimate.
• That precise figure is the same in every country and moves day to day, so the daily change is a usable estimate of downloads per day.
• For your own app, the Play Console is the source of truth. The App Store shows no public download count at all.
• Track the number daily rather than checking it once. A trend is far more useful than any single value.

How the Google Play download count works#

Every Google Play listing shows a "Downloads" figure next to the rating and the content rating. It is never exact. As Android Central puts it, what you get is a range, not a specific number.

The buckets follow a 1, 5, 10 pattern. On the listings we checked in October 2026, labels included 100K+, 500K+, 1M+, 5M+, 10M+, 50M+, 100M+, 500M+, 1B+ and 10B+. K-9 Mail, at about 9.5 million by the precise figure described below, still showed "5M+", while Todoist, at about 49.8 million, showed "10M+":

So an app labeled "1M+" can have five times as many downloads as another app with the same label. The jump between buckets is also why the badge can stay the same for months, then change overnight.

Google has not published how the public number is calculated. Developers on the Android Enterprise community asked whether Managed Google Play installs count and got no official answer; one reply described the figure as cleaned to remove duplicate downloads from the same person, and added that they knew of no documentation. Take any precise definition you read with caution, including the one in this article.

The more precise figure behind the badge#

The listing page carries more than the label. Open any Google Play listing's page source and you will find a small array next to the download label. For the Firefox listing on October 18, 2026, it was:

["500,000,000+", 500000000, 519584379, "500M+"]

The four values are the long label, the bucket floor, a more precise figure and the short label. Here is what we saw on a sample of listings on October 18, 2026:

Three observations from checking these by hand:

1. Every precise figure falls inside its bucket. Termux at 44 million is still "10M+" because the next step is 50M+.
2. It is global, not per country. Spotify's figure was identical when fetched with gl=US, gl=JP and gl=DE, and only the label was localized ("1 Mrd.+" in German). Ratings, by contrast, do differ by country, as our guide to Google Play rating calculation shows.
3. It moves daily. Spotify read 3,163,056,958 at 23:03 UTC on October 17 and 3,164,141,417 at 23:09 UTC on October 18, an increase of 1,084,459 in about 24 hours. Two reads a few minutes apart returned the same value, so it does not update in real time.

This is the figure that open-source tools expose. The google-play-scraper package, for example, returns it as maxInstalls next to minInstalls and the installs label. Remember what it is: an undocumented value in a web page, not an API. Google can rename it, remove it or change what it counts at any time, and nothing says it matches the Play Console. Use it to compare apps and to watch trends, not as an audited number.

How to see how many downloads your own app has#

For an app you publish, use the Play Console, not the public listing. Our guide to Google Play Console statistics covers the metrics in detail; the short version:

• New users and device acquisitions in the Statistics page count new installs per day, and can be filtered by country, device and Android version.
• A cumulative total is a report setting, not a separate metric. A walkthrough on Zenn shows how: open Statistics, pick the new-user acquisition metric and change the calculation to cumulative.
• Active users are a different question from downloads. A high download count with few active users is a retention problem, and the Console shows both.

If your public label looks low compared with the Console, remember the bucket: 4.9 million downloads still show as "1M+".

Track a competitor's Google Play downloads day by day#

A single reading of the precise figure tells you roughly how big an app is. Daily readings tell you how fast it is growing, which is usually what you want to know about a competitor. This script reads the figures from a listing:

// play-downloads.mjs: read the public download figures from a Google Play listing.
// Node.js 18+ (global fetch). Not an official API: keep volume low and cache results.
const INSTALLS = /\["([\d,]+)\+",(\d+),(\d+),"([^"]+)"\]/;

export async function getPlayDownloads(packageName) {
  const url = `https://play.google.com/store/apps/details?id=${encodeURIComponent(packageName)}&hl=en_US&gl=US`;
  const res = await fetch(url, { headers: { 'user-agent': 'Mozilla/5.0 (compatible; store-stats-check)' } });
  if (res.status === 404) return null; // not on Google Play, or not in this country
  if (!res.ok) throw new Error(`Google Play returned ${res.status} for ${packageName}`);
  const match = (await res.text()).match(INSTALLS);
  if (!match) throw new Error(`No download figures found for ${packageName}; the page format may have changed`);
  const [, , floor, precise, label] = match;
  return {
    packageName,
    label,                        // what the listing shows, e.g. "500K+"
    bucketFloor: Number(floor),   // lower bound of the public bucket
    approxTotal: Number(precise), // undocumented, more precise figure
    checkedAt: new Date().toISOString(),
  };
}

if (import.meta.url === `file://${process.argv[1]}`) {
  for (const id of process.argv.slice(2)) console.log(await getPlayDownloads(id));
}

Run it with package names (the id= part of a listing URL):

node play-downloads.mjs com.spotify.music com.kunzisoft.keepass.free

On October 18 it returned { label: '1B+', bucketFloor: 1000000000, approxTotal: 3164141417 } for Spotify and { label: '500K+', bucketFloor: 500000, approxTotal: 678441 } for KeePassDX, and null for a package that does not exist.

Store one row per app per day#

Call the script once a day from a scheduler and write one row per app per day. A table like this is enough:

CREATE TABLE play_downloads (
  package_name text   NOT NULL,
  day          date   NOT NULL,
  label        text   NOT NULL,
  approx_total bigint NOT NULL,
  PRIMARY KEY (package_name, day)
);

-- Estimated downloads per day, from the change in the precise figure.
SELECT package_name, day,
       approx_total - lag(approx_total) OVER w AS est_daily_downloads
FROM play_downloads
WINDOW w AS (PARTITION BY package_name ORDER BY day)
ORDER BY package_name, day;

Our guide to PostgreSQL time series for daily app and extension stats covers idempotent writes, gaps and 7-day growth rates for exactly this kind of table.

Read the trend with care#

• Look at 7-day sums, not single days. The figure updates on Google's schedule, so a day can show zero and the next day twice as much.
• Expect the occasional correction. If the precise figure ever goes down, treat it as a recount, not uninstalls.
• Compare apps in the same category. Downloads per day only mean something next to similar apps.
• Pair it with ratings. An app adding 5,000 downloads a day while its rating falls is in a different position from one adding 5,000 with a rising rating.

Be a polite client#

Fetch each listing once a day, not once a minute. Send a clear user agent, cache results, back off on HTTP 429 and stop if you see a block page. Do not put anything personal in your requests. If you only need a few apps, a daily job is a handful of requests and well within reason.

What about the App Store and the Chrome Web Store?#

Other stores answer the "how many downloads" question differently:

On the App Store, a developer on the Apple Developer Forums asking how many downloads they had was pointed to App Store Connect, because nothing is public. For other apps, the rating count from the iTunes lookup endpoint is the closest public signal, as our guide to the iTunes Search API explains.

Browser extensions show users, not downloads. A Chrome extension's public count is weekly active users rounded into brackets, which is why it can stay flat for weeks; our guides to the Chrome Web Store stats API and to why Chrome extension weekly users drop explain the rounding. For extensions, growth in users is the metric to watch, and Chrome extension user growth shows how to calculate it.

Track every store from one dashboard#

If you ship on Google Play and the browser extension stores, or you watch competitors on several of them, checking each listing by hand does not scale. Extenify records store listing data every day for your apps and extensions on Google Play, the App Store, the Chrome Web Store, Edge Add-ons and Firefox Add-ons, next to the competitors you choose: installs or users, ratings, reviews and versions, with a growth rate for each listing. It is a cross-platform extension dashboard with competitor extension monitoring built in, and it sends a daily digest or app store rating alerts to email, Slack, Discord, Telegram or Teams when something moves. Every plan starts with a free trial; see the pricing page.

Frequently asked questions#

How do I see how many downloads an app has on Google Play?#

Open the listing: the figure next to the rating, such as "1M+ Downloads", is the public count. It is a range, so "1M+" means between one and five million. The listing's page data also holds a more precise, undocumented figure, which tools such as google-play-scraper return as maxInstalls.

What does 10K+ downloads mean on Google Play?#

At least 10,000 downloads and fewer than 50,000. The next bucket after 10K+ is 50K+, then 100K+.

Is the Google Play download count accurate?#

The label is accurate as a range. How Google counts (for example, whether reinstalls or managed installs are included) is not documented, and the precise figure in the page data has no official definition. Your own Play Console statistics are the authoritative numbers for your app.

Can I see how many downloads an iPhone app has?#

No. The App Store shows no download count, and Apple offers no public endpoint for it. Developers see their own downloads in App Store Connect. For other apps, rating count and chart rank are the only public hints.

How often does the Google Play download count update?#

The visible label changes only when an app crosses into the next bucket, which can take months. The precise figure changed between our daily readings, but not between reads a few minutes apart, so plan on daily checks.

Summary#

The Google Play download count on a listing is a bucket on a 1, 5, 10 ladder, so it can understate an app by up to five times. A more precise, undocumented figure sits in the listing's page data; it falls inside the bucket, is the same in every country and changes day to day, which makes the daily difference a reasonable estimate of downloads per day. For your own app, use the Play Console. The App Store has no public download count, and browser extension stores report users instead. Whatever the store, one reading tells you little: record the figures every day and read the trend.

Image credits#

• Cover photo: Motorcycle digital meter at 15,000 km by PRABIN M on the WordPress Photo Directory, CC0.