Download websites that use Plausible

About Plausible

Most analytics installations are inertia. A tag went in when the site launched and nobody has revisited the decision since. Plausible is different, because putting it on a site takes a deliberate act of replacement and there is usually a reason attached to it.

The reasons narrow the population in a useful way. Operators choose this Analytics tool because they want traffic measurement without cookies, without personal data collection and therefore without a consent banner interrupting every first visit, or because they want a script light enough not to show up in performance budgets. So a domain running it has generally thought explicitly about privacy posture, page weight or both. Independent publishers, developer tools, agencies, nonprofits and privacy conscious European businesses cluster heavily here. For a company selling consent management or audience level retargeting, the same list is a negative signal, because these sites have already opted out of the model those products depend on.

Licensing explains the shape of adoption. Plausible Analytics distributes the product under AGPL v3, a copyleft licence strong enough to require anyone offering a modified hosted version to publish their changes, and the codebase is written in Elixir. The result since 2019 has been two populations running the same software: subscribers to the managed service, and organisations running their own instance on their own infrastructure. Each population is a real deployment, but only one of them is a paying customer, and nothing visible in a page reliably tells them apart.

That split creates the most important caveat on this page. Self hosted and proxied installations commonly serve the script from the site's own domain under a renamed path, specifically so that content blockers and network filters do not strip it. Those deployments are close to invisible to any external scan, which means our count leans toward sites loading the standard hosted script and misses an unknown but meaningful share of the self hosted base. The number below is a floor with a known direction of error rather than an estimate of true adoption.

As of September 2026 we detect the tool on 17,263 sites, and the interesting uses of that list are all comparative. Analytics vendors use it for displacement research, to see which sites dropped a heavyweight tracker and what else changed on those pages at the same time. Privacy researchers use it to measure how far cookieless measurement has actually spread by sector and by market. Sales teams selling to the privacy conscious segment use it because self selection has already done the qualification work. None of that is available from checking domains individually.