Netlify and China — what works, what doesn't
Netlify mirrors the Vercel profile in China — no mainland coverage. Here is the practical remediation ladder.
Netlify is a clean place to ship a frontend. The China question is the same one we ask of any overseas-hosted platform: does it reach mainland users acceptably, and what can you do without abandoning the platform you like?
What generally works
Static pages and assets served from Netlify’s overseas edges do load from the mainland, but with higher and less predictable latency than a domestic origin. For lightweight marketing sites with few third-party dependencies, the result can be acceptable.
Where the edges are
The recurring failures are not Netlify itself — they are the bundled dependencies: fonts, analytics, auth widgets, and embeds that phone home to blocked domains. And anything that requires an ICP filing cannot be solved by hosting choice alone.
The remediation ladder
The options mirror the Vercel playbook:
- Static export to a China-reachable CDN for the China-facing surface.
- A China proxy layer in front of the existing deployment.
- Hosting the China-facing components separately, on a filed domain.
Measure first — the right rung on the ladder is specific to your app and your dependency set.
