Global service map
. Regenerated with each Chinaready Landscape publish.
Quick answer: CanvasJS is a client-side JavaScript charting library, so nothing about it is blocked — charts render in the browser and never call a server. Chinaready marks it Limited for one reason: if you load it from its overseas CDN, the script arrives slowly or stalls for mainland users. Self-hosting the library file on a China CDN fixes that outright and is the shortest path if you are happy with CanvasJS. The reason teams still switch is licensing — CanvasJS is commercial — so the China-origin, permissively licensed libraries Apache ECharts and AntV G2 are the usual replacements. Availability in China: Limited.
Availability in China: Limited
Charting libraries are the easiest category on this site to get right, because there is no service dependency to replace — the code runs in the visitor's browser. Only two things actually matter for China.
If your page loads CanvasJS from an overseas CDN, mainland visitors wait on a cross-border request for a script that blocks your charts from rendering. Bundle the library with your application assets or serve it from a China CDN alongside them, and the problem disappears. This applies to every JavaScript library on the page, not just charts — the same fix covers Bootstrap, jQuery, and web fonts loaded the same way.
CanvasJS is commercially licensed. That is often the real trigger for switching, especially for teams building a China product with a domestic engineering team, where an open-source library with Chinese documentation is easier to staff and maintain.
| Library | What it is | Best fit |
|---|---|---|
| Apache ECharts | Apache-licensed charting library donated by Baidu to the Apache Software Foundation, with a very wide chart-type catalogue, Canvas and SVG renderers, and first-class Chinese documentation | The default first evaluation. Broadest coverage and the safest choice for a China-facing dashboard or data-heavy page |
| AntV G2 | Grammar-of-graphics charting library from Ant Group's AntV suite, MIT licensed, composable rather than chart-type-per-config | Teams who want to compose visualisations from primitives, or who already use Ant Design |
| AntV F2 | Mobile-first sibling of G2, built for small screens and WeChat Mini Program canvases | Charts inside Mini Programs and mobile web, where bundle size and touch interaction matter most |
Because there is no backend, a migration is a rewrite of chart configuration objects and nothing more — no data residency question, no new vendor contract, no ICP implication. Budget for the config rewrite and for re-testing interactions and responsive behaviour. Check chart-type coverage against what you actually render before committing, and compare bundle size if the page is performance-sensitive; ECharts is feature-rich and correspondingly larger unless you build a custom bundle.
Options named here are alternatives-page orientation candidates for research — Chinaready does not add them as Explore / Landscape product tiles.
Mapped China-ready candidates
CanvasJS is reachable from mainland China, but its commercial license and overseas CDN delivery make it an awkward default for China-hosted front ends. Apache ECharts, AntV G2, and AntV F2 are China-origin, Apache-2.0 or MIT licensed charting libraries that can be self-hosted or served from a domestic CDN. Confirm chart-type coverage and bundle size before migrating.
CanvasJS is reachable from mainland China, but its commercial license and overseas CDN delivery make it an awkward default for China-hosted front ends. Apache ECharts, AntV G2, and AntV F2 are China-origin, Apache-2.0 or MIT licensed charting libraries that can be self-hosted or served from a domestic CDN. Confirm chart-type coverage and bundle size before migrating.
CanvasJS is reachable from mainland China, but its commercial license and overseas CDN delivery make it an awkward default for China-hosted front ends. Apache ECharts, AntV G2, and AntV F2 are China-origin, Apache-2.0 or MIT licensed charting libraries that can be self-hosted or served from a domestic CDN. Confirm chart-type coverage and bundle size before migrating.
Yes, functionally. CanvasJS is a client-side JavaScript charting library, so it renders entirely in the browser and never calls a server that could be blocked. Chinaready marks it Limited only because loading it from an overseas CDN is slow or stalls for mainland visitors. Self-hosting the library file on a China CDN, or bundling it with your application assets, resolves that completely.
Chinaready Landscape currently maps CanvasJS to Apache ECharts, AntV G2, AntV F2. Apache ECharts is the usual default — Apache-licensed, originally from Baidu, now an Apache Software Foundation project, with a very wide chart-type catalogue and first-class Chinese documentation. AntV G2 from Ant Group is MIT licensed and takes a grammar-of-graphics approach, and AntV F2 is its mobile-first sibling for small screens and WeChat Mini Program canvases. These are research candidates rather than one-to-one endorsements.
Licensing, usually. CanvasJS is commercially licensed, while Apache ECharts and the AntV libraries are Apache-2.0 or MIT and free to self-host. Teams building a China product with a domestic engineering team also find an open-source library with Chinese documentation easier to staff and maintain. If neither applies to you, self-hosting CanvasJS on a China CDN is a perfectly reasonable answer.
Mechanical rather than architectural. There is no backend involved, so there is no data residency question, no new vendor contract, and no ICP implication — the work is rewriting chart configuration objects and re-testing interactions and responsive behaviour. Check chart-type coverage against what you actually render before committing, and compare bundle size if the page is performance-sensitive, since ECharts is feature-rich and correspondingly larger unless you build a custom bundle.
The same delivery problem affects every overseas-CDN asset on the page, so review the BootstrapCDN, Cloudflare CDN, and Google Fonts pages in the same pass — self-hosting or a domestic mirror fixes all of them together. Then use the Chinaready Guide for where front-end delivery sits in a China stack. If the path remains unclear, book a call with Chinaready.
