How do you make a website work in mainland China?
Treat it as two independent gates, not one speed problem: the site has to be delivered fast enough from inside mainland China, and it has to carry a valid ICP filing — and the arrangement that passes the first gate is the same one that triggers the second.
Delivery from inside the mainland is what removes the congested, filtered border crossing, and in-country delivery is exactly what the ICP filing regime binds to — so any arrangement that avoids the filing is one that keeps the latency. The filing also needs a mainland China legal entity to stand behind it and attaches to whoever actually serves the traffic, not only your domain. The sections below separate the two gates, walk the four delivery paths, and show where a compliant in-country delivery layer lets your existing platform stay the source of truth.
Which path fits turns on your entity, your content and who your users are — a risk map to work through with counsel, not a one-size verdict. Our China team can map your path with you →
What actually decides it — the two gates, and the rules each one rests on
| Fact | Primary source |
|---|---|
| The filing is a permission to operate, set by State Council Order No. 292. Article 4 of the Measures for the Administration of Internet Information Services (互联网信息服务管理办法, 国务院令第292号) puts commercial services under a license (许可) and non-commercial ones under a filing (备案), and states plainly: “未取得许可或者未履行备案手续的，不得从事互联网信息服务” — without the license or the filing, you may not provide the service. That is the legal gate behind “anything served from inside mainland China needs an ICP filing.” How ICP filing works → | Measures for the Administration of Internet Information Services, State Council Order No. 292 (promulgated 2000-09-25), Article 4 — Cyberspace Administration of China, retrieved 2026-10-07 |
| The filing attaches to whoever serves the traffic, not only your domain. MII Order No. 33 (非经营性互联网信息服务备案管理办法), Article 18, provides that “互联网接入服务提供者不得为未经备案的组织或者个人从事非经营性互联网信息服务提供互联网接入服务” — an access-service provider may not carry a site that has not filed. So the filing has to name the provider actually delivering the traffic: you cannot launch first and file later through a compliant mainland provider, and a filing whose named provider no longer serves the site can be cleared as an inactive “empty-shell” record. Move delivery and the filing has to move with it. Why the filing and the hosting are one decision → | Measures for the Administration of the Record-Filing of Non-Operational Internet Information Services, MII Order No. 33 (effective 2005-03-20), Article 18 — State Council Gazette on gov.cn, retrieved 2026-10-07 |
| The filer has to sit inside mainland China — the hard blocker for a foreign company. Order No. 33 scopes filing to “在中华人民共和国境内的组织或个人” (organizations or individuals within PRC territory, Article 5) and is made to the provincial communications authority where the filer is domiciled (Article 3). In practice the filing system expects a mainland address, a mainland contact and, for a company, a Chinese business license, so a foreign entity with no mainland presence has no eligible party to file in its name. The statute sets a territorial test rather than naming a “local company” rule, so treat the entity question as one to confirm with counsel for your structure. What the filing binds to → | MII Order No. 33, Articles 3 and 5 (territorial scope) — State Council Gazette on gov.cn, retrieved 2026-10-07 (the “foreign company needs a mainland entity” point reflects filing-system practice, not a verbatim statutory clause) |
| Serving the mainland from offshore keeps the border crossing — and that crossing is a personal-data export under PIPL. Leave the origin outside the mainland and your mainland visitors’ personal information is sent abroad on every request. PIPL Article 38 requires a cross-border transfer to rest on one of a set of legal bases — a CAC security assessment, CAC-accredited certification, or the CAC standard contract — and Article 39 requires separate consent plus specific notice to the individual. For a critical-information-infrastructure operator, or a handler above the CAC volume threshold, Article 40 requires domestically collected personal information to be stored in China and to pass a CAC security assessment before any export (the Cybersecurity Law carries a parallel localization duty — Article 37 in the 2016 text, renumbered Article 39 in the version effective 2026-01-01). So the offshore setup that leaves the latency can also be the one that carries cross-border and data-residency risk — a risk to assess with counsel, not a verdict. How cross-border data rules apply → | Personal Information Protection Law (NPC, Chairman’s Order No. 91, effective 2021-11-01), Articles 38–40, bilingual text via China Justice Observer, retrieved 2026-10-07; Cybersecurity Law Art 37 (2016) / Art 39 (effective 2026-01-01) |
Sources verified by the 21YunBox compliance team on 2026-10-07.
There are two gates, and they are independent
Almost every plan for serving mainland China treats this as one problem — make the site faster — and it is two. They are separate gates, they are failed separately, and passing one tells you nothing about the other.
Gate 1 — performance. Your origin sits outside mainland China, so every request crosses a border that is congested and filtered. The symptom users report is not “slow” but inconsistent: the same page is tolerable in the morning and unusable in the evening.
Gate 2 — the filing. Anything actually served from inside mainland China requires a valid ICP filing, and that filing requires a mainland China legal entity.
The trap is in how they interact. The fast path and the filed path are the same path. Delivery from inside China is what removes the border crossing — and it is also precisely what triggers the filing requirement. So the arrangements that avoid the filing are, without exception, the ones that keep the border crossing.
That is why a setup can be genuinely fast and still be the wrong answer for an enterprise: speed achieved outside the filing regime is speed you do not have permission to keep.
Gate 1: why the border crossing is the whole problem
A CDN’s job is to put a copy of your content physically closer to the user. That works everywhere in the world, and it works in China only if the points of presence are actually in China.
This is where most plans quietly fail. Hong Kong and Singapore feel close on a map and sit on the far side of the Great Firewall. Serving mainland users from there does not shorten the crossing; it just moves where the crossing ends.
Three things then break, separately:
- The crossing itself — high and, more importantly, variable latency.
- The domain can be filtered — platform-provided subdomains are more exposed than a custom domain on the same infrastructure.
- Everything the page pulls in fails on its own schedule — fonts, consent banners, analytics, embedded video, form endpoints. The page can “mostly load” and still convert nothing, because on a lead-capture site the form is the conversion event.
Point 3 is the one that surprises teams. A CDN accelerates what you own. It does nothing for the dozen third-party services your page calls, and those have no mainland presence either.
Gate 2: what the filing actually binds to
Three properties of the ICP filing decide most project schedules, and all three are commonly discovered late.
It is triggered by where the server is, not by who you are. A site hosted entirely abroad needs no filing — which is also exactly why it is slow.
It requires a mainland China legal entity. A foreign company cannot file in its own name. This is the single most common hard blocker, and it is a company-structure problem rather than a technical one.
It is bound to your hosting/access provider, not only to your domain. Moving delivery to a new provider means updating the filing to name that provider. A filing left without a current provider is not merely stale — it can be reclassified as an “empty shell” and cancelled.
That last property is why “we already have an ICP” is not the reassurance it sounds like. The filing has to match the infrastructure that is actually serving the traffic today.
The four paths, compared on both gates
| Passes Gate 1 (performance) | Passes Gate 2 (filing) | Effect on your global stack | |
|---|---|---|---|
| Do nothing, tune what you can | No — border crossing remains | Not applicable — nothing served in China | None |
| Near-shore CDN (Hong Kong / Singapore) | Partly — static assets only; APIs and forms still cross | Not applicable — and that is the point people miss | None |
| Rebuild a separate site inside China | Yes | Yes — you hold the filing | A second codebase and content workflow, permanently |
| China delivery layer over the existing build | Yes | Yes — filing attaches to the delivery layer | None — your existing platform stays the origin |
Near-shore is the option most teams try first and the one that disappoints most reliably. It is attractive precisely because it needs no filing, and it needs no filing precisely because it never enters China.
The rebuild genuinely works and is genuinely expensive — not in infrastructure but in operations. A second codebase, a second content workflow, and a marketing team that publishes twice and has to remember which market gets what.
So do we need a CDN, or something else?
If your site is static, your audience is tolerant, and nothing on the page calls a third party, a China-capable CDN plus your own filing is a complete answer. That is a real scenario and it is worth saying so.
It stops being a complete answer when any of these are true, which for an enterprise site is usually all of them:
- The page calls services that are blocked or slow in China — analytics, fonts, consent, video, marketing-automation forms.
- Content is dynamic or personalised, so caching a copy is not enough.
- You have no mainland entity, so the filing has no one to attach to.
- Delivery is changing, so an existing filing has to be updated in step with it.
Where 21YunBox sits
We are the layer that passes both gates without changing your global platform. Your existing CMS, build pipeline and publishing workflow stay exactly as they are and remain the source of truth. We put compliant delivery inside mainland China in front of them, rewrite the blocked third-party calls individually so the conversion path completes, and our compliance team holds or updates the ICP filing so that the technical and regulatory halves match.
That last clause is the part worth checking in any proposal you receive, from us or anyone else: a filing made against the wrong infrastructure has to be redone, and it sits on the critical path.
Link: China ICP License for Websites
Frequently Asked Questions
Our site is already fast in China — do we still need an ICP filing?
Quite possibly, and the two questions are separate. Being reachable is Gate 1; the filing is Gate 2, and it is triggered by delivering from inside mainland China, not by how the page performs. If the speed comes from an arrangement that never enters the mainland — a near-shore edge in Hong Kong or Singapore, say — you have sidestepped the filing by keeping the border crossing, which is also why that speed tends not to hold for APIs, form submissions and dynamic content. Durable in-country performance and the filing arrive together.
We already hold an ICP filing from years ago — are we covered?
Only if it names the infrastructure serving your traffic today. The filing binds to the access provider as well as the domain (MII Order No. 33, Article 18), so moving delivery means updating the filing to name the new provider, and a filing whose provider no longer serves the site can be cleared as an inactive record. An old filing is worth verifying against your current setup rather than assuming it still stands.
Can 21YunBox help make our site work in mainland China?
Yes. We put compliant delivery inside mainland China in front of your existing CMS and build pipeline — which stay the source of truth — and rewrite the blocked or unreliable third-party calls individually so the conversion path completes end to end, while our compliance team holds or updates the ICP filing so the technical and regulatory halves match. For teams with no mainland entity, that filing can sit with us rather than waiting on a Chinese subsidiary. We map your PIPL cross-border and data-residency exposure for your entity, data and users first. Get in touch to work through your case.
