Download websites that use Mapbox GL JS

About Mapbox GL JS

A map is one of the few things on a web page that arrives with a running bill attached. Rendering tiles costs the site owner money on every load, which makes Mapbox GL JS on a page evidence of a deliberate, budgeted decision rather than a component somebody inherited because the theme included it. Front end libraries in general are weak commercial signals. A metered rendering engine is not one of them.

The decision usually indicates that the business has geography inside its product. Store locators, property listings, delivery and logistics tracking, travel and booking, field service, asset monitoring and any dashboard that plots points on a base map all converge on the same requirement, which is vector tiles drawn in the browser with custom styling and data driven layers. The Maps category on this site collects everything from a static image embed to a full rendering engine, and the engines are the part with real budget behind them. A company that pays to put an interactive map on its site is a company whose customers ask where.

As of September 2026 we detect Mapbox GL JS on 49,041 sites. United States accounts for 24,563 of them and .com covers most of the addresses, which fits a product sold through developer channels to companies already used to paying for infrastructure by usage. Mapbox released the library in 2015, wrote it in JavaScript and published the open source releases under a BSD license, although the terms attached to later versions have changed over time and anyone depending on the licensing position should check the specific release they ship.

Churn is the commercial reason to want the population rather than a single lookup. Map providers compete on price per load and on the terms attached to caching, offline use and derived data, and pricing changes have moved sizeable groups of sites between providers before. A list of every site running one engine, refreshed between scans and compared against the equivalent list for competing engines, shows migration while it is happening. Checking a domain shows a state and never a direction.

The limits deserve to be direct. The library is normally bundled into an application build, minified and sometimes renamed, so detection depends on identifiable strings surviving that process and the count should be read as a lower bound. No version breakdown appears here for the same reason, because a bundled build usually carries no readable release marker. And a map on a page says nothing about whether the account behind it sits on a free allowance or an enterprise contract, so the list sizes an audience rather than a spend.