Download websites that use Howler.js

About Howler.js

Sound on the web is a minority behavior, and the libraries that produce it identify a specific kind of site. Howler.js is a JavaScript audio library that wraps the browser audio interfaces and smooths over the differences between them, and a page that loads it intends to play something: a game, a soundboard, an interactive explainer, a language course, a media player or a kiosk screen. Ordinary content sites do not need it.

Narrowness is the point of this list. A general purpose library tells you little, because everyone uses it. An audio library segments the web by intent, and it does so more cleanly than a category label ever could. Browser game studios, e-learning publishers, interactive agencies and accessibility researchers all want the same population and cannot get it any other way, because no directory of the web is organized by whether a page makes noise.

Howler.js carries the MIT license and is published as an open source project rather than sold by a vendor, which changes the commercial reading in two ways. There is no vendor customer list this data could stand in for, so the extract is the only enumeration available. And adoption is a pure engineering choice made by whoever wrote the front end, uncolored by procurement, resale or hosting defaults, which makes it a cleaner signal about the developers than about the business.

The version distribution is the part worth studying. As of October 2026 we see the library on 713 sites across 21 distinct versions, with 2.2.4 the release we encounter most often. A spread that wide on a library first released in 2013 is characteristic of self-hosted front end dependencies. Nobody updates an audio library on a shipped project unless something breaks, copies are frozen into build output, and old releases persist for as long as the pages carrying them do. Version therefore works as a proxy for when the front end was last rebuilt, which is a more interesting question than which audio library someone picked.

Detection has boundaries worth stating. We identify the library from its filename, path and code fingerprints in delivered assets. Bundled and minified builds, where the library is compiled into a single application file under a different name, can hide it, and version strings are stripped by the same process. Undercounting is therefore real and concentrated in exactly the modern toolchains that bundle everything, so the count is a floor and the version data covers only installations where the version survived.

What the downloadable list answers is the shape of a population, not the status of a domain. A lookup tells you one site plays audio. The file tells you how many do, which countries and top level domains they sit in, how far behind the current release the population runs, and whether the group is growing as browser based games and interactive media grow or shrinking as bundlers erase the evidence.