Download websites that use Three.js

About Three.js

Rendering a lit, textured, moving object inside a browser tab is something almost every visitor's machine can do and almost no website asks for. The pages that do ask are usually running Three.js, so a match here reads as a statement about intent and budget rather than as a routine dependency.

Three.js is a JavaScript library under the MIT license, published in 2010, that wraps WebGL so a developer can put real-time graphics into a page without writing shader code by hand. No content management system installs it by default and nobody adds it by accident. Presence means a deliberate decision, a developer able to execute it, and a budget that covered the extra work: a product configurator, a map, an architectural walkthrough, a browser game, a launch page for something the client wanted to feel expensive.

The population is commercially interesting out of proportion to its size. Agencies that build interactive work, WebGL and asset tooling vendors, rendering platforms and hiring teams looking for front-end engineers with graphics experience are all trying to identify the same set of domains. As of October 2026 we detect the library on 34,309 sites, with United States accounting for 28,040 of them and .com leading the domain breakdown, a distribution that follows agency and product-marketing spend rather than any regional technical preference.

Detection has two honest limits. Three.js is frequently bundled and minified into a site's own application code, and when a build strips the banner and renames the module our crawler cannot see it, so the count is a floor rather than a total. Running the other way, a page can load the library for a decorative background it barely uses, and the data cannot tell that apart from a full configurator. We publish no version breakdown for the same bundling reason, which means the list will not separate a current project from one frozen years ago.

A per-domain lookup answers whether one portfolio site uses the library. The downloadable list answers the question behind it: which companies in a given market have already paid for interactive graphics on the web and are therefore able to buy the next piece of it. Sorted by country and TLD and joined against the rest of the JavaScript graphics data, the population narrows quickly into something a search engine cannot reproduce, because nothing about a rendered scene appears in the page text a search engine indexes. The sites are found by what they load, not by what they say, which is the whole reason a technology dataset exists.