Download websites that use VideoJS

About VideoJS

Video is expensive to put on a website. Somebody has to shoot it, store it, pay for the bandwidth and keep it playing on every browser and phone that turns up. A page with a real video player on it is a page somebody invested in, which makes the player a sharper business signal than most of the tags sitting next to it.

VideoJS is the piece that handles the playback. Created in 2010 and maintained by its contributors under a corporate sponsor, a role now held by Mux, it is an open source JavaScript player released under Apache 2.0 that wraps the browser's own video element, smooths over the differences between browsers, and adds captions, playlists, adaptive streaming and a plugin interface for advertising and analytics. Publishers, broadcasters, course platforms, marketing sites and documentation portals all reach for it for the same reason: video that has to work everywhere without a native application.

Because the player ships as a file inside a page, versions accumulate. We record 126 versions, with detections clustering around 8.23.3. Client-side libraries get pinned into themes, bundles and page builders, and they are usually replaced only when the surrounding product is rebuilt, so a site can serve an ageing player while the rest of the page looks current. For a security or maintenance audit the version is the interesting column, because a player runs in the visitor's browser and carries every flaw it shipped with.

As of September 2026 we detect VideoJS on 10,832 sites. Knowing that one domain uses it is rarely worth much alone. A downloadable list is what allows the question to be asked properly: which industries standardised on an open source player instead of a hosted service, which countries and domain endings concentrate video-heavy sites, what advertising, captioning and analytics tools appear beside the player, and how many installations are old enough to be worth an approach. Streaming platforms, CDN and encoding vendors, captioning and accessibility companies and advertising technology firms all read the same rows for different reasons.

The honest caveat is bundling. When a player is compiled into build output and renamed, the fingerprint can disappear, so our count runs below reality. Detection also tells you which player renders the video, not where the video is stored or who serves it, and a site can load the player from a shared template on pages that carry no video at all.