Does Netlify work in China?
Whether Netlify works in China is an ICP, reachability and data-residency question — not a speed one. Netlify is excellent global edge hosting, but its network sits outside the mainland, and that one fact sets both answers that matter for a China audience.
In its own documentation Netlify describes simplifying "building for the web on our global CDN" — a worldwide edge network you reach from offshore, with no point of presence inside mainland China. Two things follow for a public China-facing site. It is served from outside the country, so there is no licensed in-country host for an ICP filing (备案) to attach to; and every mainland visitor's request — their real IP, request logs, and any form or analytics data — crosses the border, which China's Personal Information Protection Law governs as a cross-border transfer. The table below sets Netlify's own wording against the rule each door triggers.
This is a risk picture, not a verdict — what applies turns on whether you serve the public in China and the personal data your site collects. Our China team can map your Netlify hosting and data exposure with you →
What actually decides whether you can run Netlify in China
| Fact | Primary source |
|---|---|
| In Netlify's own words, it runs on a global CDN with no mainland-China presence. Netlify describes simplifying "building for the web on our global CDN (Content Delivery Network) so you can focus on building your project and reaching your goals without managing infrastructure" — a worldwide edge network you reach from offshore, with no point of presence inside mainland China. So a China-facing Netlify site is reachable but served from outside the country, which sets both compliance doors below. | Netlify Docs — What is Netlify?, retrieved 2026-10-08 |
| A public mainland site needs an ICP filing, and an offshore Netlify host has nothing to file against. Under State Council Order No. 292 (Article 4) and MIIT Order No. 33, an ICP filing (备案) attaches to a hosting resource physically inside mainland China and to a mainland legal entity. Netlify's edge is offshore, so there is no in-country resource for the filing — the door is the hosting location, not Netlify's build or deploy. | State Council Order No. 292 (Measures for the Administration of Internet Information Services), Article 4; MIIT Order No. 33 |
| Served offshore, a mainland visitor's data leaves the country — a cross-border transfer under PIPL. At minimum a visitor's real IP address and request logs, and more if the site carries forms, logins or analytics, leave the mainland when Netlify serves them from its offshore edge. PIPL governs that transfer (Chapter III, Articles 38–43: notice, separate consent, and one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification). For a CIIO or large-volume handler, personal information collected in China must be stored inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). | PIPL Chapter III, Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The weight of that duty scales with volume and role, not with choosing Netlify. Under the CAC's March 2024 Regulations on Promoting and Regulating Cross-border Data Flows, a non-CIIO transferring fewer than 100,000 individuals' non-sensitive personal information in a calendar year is exempt from the security assessment, the standard contract and certification — which is why the ICP footing, not the data threshold, is usually the first thing to settle. | CAC — Regulations on Promoting and Regulating Cross-border Data Flows, March 2024 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
Netlify is one of the best places in the world to build and ship a modern web project, and nothing here asks you to leave it. For a mainland-China audience, though, the deciding question about Netlify is not how quickly it paints — it is where the site it serves is allowed to operate and where your visitors’ data is allowed to go. Netlify answers the first half in its own documentation: it runs on a global CDN, a worldwide edge network with no presence inside mainland China. So a public Netlify site is reachable from the mainland yet served entirely from outside it, which leaves it with no footing for the ICP filing a public mainland site requires and turns the data it collects from Chinese users into a cross-border transfer China’s law governs. The reachability is real; the licensing and the data residency are the exposure.
The short version is a partnership, not a replacement: Netlify stays your host and build pipeline, and a compliant, ICP-filed presence inside the mainland sits in front of it for Chinese visitors. Below is what Netlify documents about its own network, the ICP door an offshore edge structurally cannot hold, and how China’s Personal Information Protection Law treats the data a China-facing site collects — in Netlify’s own words and China’s own law, so you can take it to counsel rather than to a benchmark.
Netlify in China at a glance
| What decides it | In Netlify's own terms — and China's own law |
|---|---|
| Where it runs | Netlify runs on a global CDN — in its own words you build “on our global CDN” and ship “without managing infrastructure.” That edge network is worldwide, and none of it sits inside mainland China; a China-facing site is served to the mainland from offshore. |
| Who holds the ICP footing | An ICP filing attaches to a hosting resource physically inside mainland China and to a mainland legal entity. A site served from Netlify's offshore edge has neither — there is nothing in-country to attach one to. |
| Serving the public | A site shown to mainland visitors from inside China needs an ICP filing tied to a mainland hosting resource. Netlify offers no such in-country host of its own, and cannot file on your behalf. |
| Your visitors' data | Served offshore, a mainland visitor's real IP, request logs and any form or analytics data leave the country — a cross-border transfer PIPL governs, even for a mostly static site. |
| Is it reachable? | Reachable, not blocked — but reaching the mainland from an offshore edge is a delivery fact, not a compliance one. It creates neither an ICP filing nor in-country data residency. |
A global edge with no mainland host, so no footing for an ICP filing
Netlify does not ask you to think about servers, and for a global audience that is the point. In its own words it simplifies “building for the web on our global CDN (Content Delivery Network) so you can focus on building your project and reaching your goals without managing infrastructure” — a worldwide edge network that serves each visitor from a nearby node. That design is close to ideal almost everywhere. What it is not is inside mainland China: none of that global CDN sits in the mainland, so a China-facing Netlify site is served to visitors there from offshore.
That geography settles the licensing question before performance ever enters it. A public-facing website delivered to mainland visitors from inside China turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, and that filing has to attach to a hosting resource physically located in the mainland and to a mainland legal entity. Netlify’s edge is offshore, so there is simply nothing on Netlify to file against. That is where “we already ship on Netlify” runs out: reaching China is not the same as being cleared to operate there, and no deploy setting or custom domain creates the in-country host a filing needs.
Reachable is not the same as compliant
A Netlify site is not something China categorically blocks — it is reachable. But reachability is the delivery half of the question, and it is the half that misleads. Whether or not a page loads cleanly for a mainland visitor, it is served from Netlify’s offshore edge, and serving it there gives you neither an ICP filing nor in-country data residency. A static build helps delivery, because a pre-rendered page has no server round trip to pay — but it still references offshore edges, fonts and scripts, so it is only as reachable as those offshore dependencies, and it is no closer to compliant. Those two gaps are facts about where hosting sits and where data lands, not latency you can tune away.
Your China visitors’ data still crosses the border
Serve a Netlify site to China from its offshore edge and your visitors’ personal information — at minimum their real IP addresses and request logs, more if the site carries forms, logins or analytics — leaves the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, Netlify’s customer, not Netlify — must give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty no offshore edge can satisfy. A mostly static marketing site sits lighter here than a data-heavy app, but the compliant design answers the question the same way.
This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both depends on what you serve, how much personal data you hold, and who your users are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep building and shipping on Netlify exactly as you do today — same Git-driven deploys, same previews, same global edge. 21YunBox adds the one piece a global host with no mainland presence cannot: compliant, ICP-filed delivery from inside the mainland, set in front of the site your Netlify build produces — no rebuild, no second codebase, and no move off Netlify. Our China team maps your ICP and data-residency obligations against your entity and your data volumes, handles the ICP filing, and stands up the in-country delivery and storage a lawful China presence needs, while Netlify stays your host and source of truth.
Related reading:
