Download websites that use ECharts

About ECharts

A charting library is one of the more informative things to find in a page, because it says the page renders data rather than describing it. ECharts is loaded when something on the site draws lines, bars, maps or heatmaps in the browser from values fetched at runtime, which usually means a dashboard, a monitoring view, a public statistics portal or the reporting screen of an application. Sites that only publish prose and images do not carry it.

Origin explains part of the footprint. The library was created inside Baidu and later donated to Apache Software Foundation, and open governance under a permissive licence changed who was able to use it. Apache 2.0 terms let commercial vendors embed the library inside their own products without obligation, so a meaningful share of detections belong to a shipped product rather than to a bespoke build by the site owner.

Version data is unusually informative here. Because the library is a dependency the site itself serves, whether self-hosted or pinned on a content delivery network, the version travels with the site instead of updating silently on a vendor's server. Across the population we observe 29 distinct versions as of October 2026, with 5.4.3 appearing more often than any other. The tail behind that leading version is the interesting part, because a front-end dependency nobody upgrades is a maintenance signal and, for some releases, a known-vulnerability signal.

Detection carries a bias anyone sizing the market should know about. We can see the library when it arrives as a recognisable file, from a delivery network or from a predictable path in the site's own assets. When a build tool bundles and minifies it into a single application file, the identifying strings can vanish, and the site runs the library without us being able to prove it. Modern applications are exactly the ones most likely to bundle, so the count leans toward simpler integrations and understates sophisticated ones.

Two forces pull against each other in that picture. The documentation and community around the project have a strong presence in Chinese-language development, while attribution follows where a site is hosted and registered, so the geographic column describes where the sites live rather than where the developers who chose the library work. First released in 2013, the library has had long enough for both patterns to settle.

The reason to want the list rather than a lookup is that every interesting question here is comparative. Which visualisation library a market has settled on, whether adoption is shifting between them, which analytics and business intelligence platforms ship one inside their embedded dashboards, and which versions are still in the field, are all questions about a population. Competing library maintainers, embedded analytics vendors, developer tool marketers and security teams tracking client-side dependencies each need the full set of domains, joined to whatever else those domains run.