Stats

Downloads, and roughly how many copies are in use, counted from GitHub's anonymous download counters. Nothing else is tracked.

The numbers are updated once a day.

Downloads

Downloads, all versions

macOS and Windows installers

macOS

.dmg downloads

Windows

installer downloads

Updates delivered

by the apps' updaters

Copies in use, per day (estimate)

How many installed copies checked for updates each day: the day-to-day growth of the update feed's download count. Read the caveats below before quoting these.

Show as a table

Day (UTC)	macOS	Windows

Per release

Version	macOS downloads	Windows downloads	macOS updates	Windows updates	Update checks

"Updates" count the update files the apps download when they update themselves; "update checks" count fetches of that release's update feed.

How it's counted, and why it's approximate

Downloads are GitHub's own count of each installer file (the macOS .dmg and the Windows -windows-setup.exe). Every click counts, including a second download by the same person, one that's never installed, and bots.
Updates are counted separately: the Mac updates from its own .zip and Windows from a -windows-update.exe that only the updater uses (the same bytes as the installer), so updating copies don't inflate the downloads.
Copies in use: about once a day, every running copy fetches its update feed (appcast.xml on the Mac, appcast-windows.xml on Windows) from the latest release, and GitHub counts each fetch. A snapshot of the counts is saved every day; the growth from one day to the next is the estimate.
It's rough. A copy that's opened and closed several times a day can check more than once, and one that isn't opened that day doesn't check at all, so it's closer to "copies opened that day" than "copies installed". Offline copies, copies blocked by a firewall, and copies with updates turned off never show up; scripts and bots that fetch the feed do.
On the day a release comes out, copies fetch the old release's feed until it's published and the new one's after. The estimate adds up the growth of every release's feed, so that day isn't split or lost.
If a daily snapshot is missed, the growth over the gap is spread evenly over its days (marked on the chart). The first snapshot has nothing to compare with, so it gives no estimate.
A file that's replaced on a release starts its count from zero again; fetches of the old copy since the last snapshot are lost.

The raw daily counts are public, in downloads.csv on the repo's stats branch, and anyone can query the same counters through GitHub's API.