Download websites that use Bootstrap Icons

About Bootstrap Icons

Few front-end dependencies leave behind as clear a timestamp as an icon set pinned to a fixed URL. Across the sites where a release string is readable we separate 108 distinct builds of Bootstrap Icons, and the build a site serves is usually the build that was current on the day the page was assembled. Icon libraries do not get upgraded. Nobody reopens a working template to advance an icon font by a point release, because the glyphs that were already there still draw correctly.

The version column therefore carries more information than the presence flag. A site reporting 1.11.3 is not telling you that it is maintained. The site is telling you roughly when its layout was put together and that nothing since has forced a rebuild. For a researcher hunting frozen front ends, or an agency trying to locate the sites it built and never revisited, the release string is the interesting field and detection itself is only the filter that produces the candidate list.

Bootstrap Icons arrived in 2020 as a package separate from the framework it belongs to, which puts a hard floor under the age of any page carrying it. Under the MIT terms there is no license server, no account and no vendor relationship, so the library spreads by copy and paste rather than by procurement. A site that loads it very likely also uses the Bootstrap layout system, and the pairing tends to indicate a hand-assembled or agency-built template rather than a hosted site builder, since builders ship icon tooling of their own.

As of September 2026 we detect Bootstrap Icons on 1,605,912 sites, with United States accounting for 1,096,037 of them and .com the suffix that recurs across the rest. Country here reflects where sites are hosted and registered rather than where an audience sits, and the concentration describes the market for small commercial websites more than it describes any preference among developers.

Detection has a limit worth stating plainly. When the icons are compiled into a site bundle, renamed by a build step or self-hosted under a generic asset path, the glyphs still render but the library is no longer identifiable, and the site is missed. Sites behind serious asset pipelines are underrepresented as a class, and the version field is absent more often than it is wrong. A number drawn from public markup is a floor rather than a census, and the bias runs in a known direction: the more sophisticated the build, the less likely the site appears here at all.

A per-domain lookup answers whether one site loads the library. A downloadable list answers questions that exist only in aggregate. Which domains are pinned to releases from a particular window, which hosting providers concentrate them, which portfolios of unrelated sites share one frozen template and therefore one builder. Inventory questions need a file, because checking domains one at a time never reveals the shape of the population you are checking.