Article
Can You Reach China Without an ICP Filing? Hybrid Architecture Paths and Trade-offs
September 28, 2026
TL;DR
- The ICP filing attaches to mainland hosting. Sites not hosted in mainland China have a lower ICP requirement, but most mainland-hosted commercial sites need the filing.
- Outside the mainland you stay cross-border: 2–8+ s TTFB, 15–30+ s page loads. Offshore CDNs without mainland edge nodes do not fix it.
- A hybrid path — global stack plus a China-facing edge — can go live while entity and filing work progresses in parallel. The license question follows the product, not the hosting location.
Your site needs to work for visitors in mainland China. The first question that surfaces is usually: do we need an ICP filing? It is really two questions. First, what does the filing obligation attach to? Second, what does it cost to stay outside the mainland and still serve Chinese users?
This article lays out the decision. It covers what triggers the filing, what performance looks like on each path, and how a hybrid architecture lets you ship a China-facing experience while entity and filing work progresses. For the full performance diagnosis, see why your website is slow in China.
What actually triggers the ICP filing
The ICP filing (Bei'an, 备案) is mandatory for most websites hosted on mainland servers. If your origin and edge both sit outside mainland China, the ICP requirement is lower than for a mainland-hosted site.
This is the core of the question: the filing attaches to hosting location, not to the act of reaching Chinese users. A site hosted outside the mainland can be visited from China without a filing, but it pays a performance cost. A site hosted inside the mainland needs the filing — operating without one risks domain blocking and enforcement.
One framing note before the paths. Choosing to host outside the mainland is a legitimate architecture decision with a measurable performance cost. It is not a workaround for operating a mainland-hosted site without a filing — that path risks domain blocking and enforcement. If you later move hosting inside the mainland, the filing obligation applies at that point. The three paths below are weighed as architecture choices, each with its compliance footprint stated.
The filing timeline is typically 2–4 weeks with complete documents and a qualified entity. For the phase-by-phase breakdown, see the ICP filing timeline.
The performance cost of serving China without an ICP filing
If your origin stays outside mainland China, every request from a Chinese visitor crosses the international transit links between mainland networks and servers abroad. Three causes stack: congested cross-border transit, DNS resolution outside the country, and filtering by the Great Firewall.
The numbers are concrete. Global-only TTFB from China runs 2–8+ seconds before any other asset downloads. Full page loads on cross-border sites often reach 15–30+ seconds. Many users bounce before the first pixel appears.
An offshore CDN without mainland edge nodes does not change this. The edge has to be inside the country for a CDN to cut the cross-border hop. Caching assets on offshore CDN nodes does not touch the transit path. Image compression and VPNs do not fix it either.
For the full diagnosis — blocked APIs, DNS round trips, and what does and does not help — see why your website is slow in China.
Path 1: global-only, accept cross-border latency
The simplest option is to keep your current global stack and accept the cross-border performance profile. No mainland hosting. No ICP filing. No entity setup in China.
This path is defensible when China traffic is a small share of your audience and page speed there carries no commercial weight. It is the wrong choice when China is a primary market and conversion depends on load time.
What you get: zero filing overhead, zero entity overhead, no infrastructure changes. What you give up: sub-second TTFB, reliable third-party script loading, and pages that load in seconds rather than tens of seconds. Third-party APIs — Google Maps, YouTube, global font hosts, payment gateways — remain blocked or unreliable behind the firewall.
Path 2: hybrid — keep the global stack, add a China path
The hybrid path keeps your global website and adds a China-facing edge layer. Content is authored once in your global CMS and delivered through two paths: the existing global path for the rest of the world, and a China path for visitors on mainland networks.
Many brands add a China path — mainland CDN with edge caching on China networks, localized pages, and replaced APIs — without replacing the global site. The hybrid architecture removes the cross-border hop for served assets: the edge sits on the same networks as visitors, and CDN configuration covers static assets, media, and cache policies tuned for China ISPs.
The China path can go live while the broader China plan — entity setup, ICP filing, full deployment — progresses in parallel. This is the key sequencing advantage: you do not need to wait for the filing to finish before Chinese visitors get a usable experience. The China path still has prerequisites — China CDN requirements.
What it changes: you add a China-facing edge layer, replace blocked third-party dependencies (maps, video, payment APIs), and tune DNS and cache policies for China networks. What it defers: full origin migration and the complete filing workflow can proceed on their own timeline.
For the infrastructure details, see our hybrid China acceleration service.
Compliance trade-offs before you choose
The hosting decision and the compliance decision are related but separate. Three trade-offs shape the choice.
License trigger follows the product, not the hosting location. The ICP license (ICP证) applies to commercial online platforms and paid services. The trigger is what your product does, not where it is hosted. A marketplace or paid platform needs to assess the license regardless of whether the origin sits in Shanghai or Singapore. For the full comparison, see ICP filing vs ICP license.
A Hong Kong entity is not a filing holder. A Hong Kong company alone does not satisfy the filing-holder requirement. If you later move hosting to the mainland, the filing must sit with a mainland-registered company or qualifying partner — typically a WFOE. Hosting in Hong Kong today does not change that when you migrate tomorrow. For what actually changes between a Hong Kong origin and a mainland one — filing scope, performance, migration cost — see Hong Kong vs mainland server: what actually changes. For the entity rules, see WFOE vs Hong Kong company.
Mainland migration is a scheduling constraint. If the hybrid path is a stepping stone to full mainland hosting, plan the filing timeline early. Filing submission and review typically takes 2–4 weeks with complete documents and a qualified entity, but earlier phases — entity setup, hosting selection, document preparation — add time before submission. The filing is a scheduling constraint, not a blocker, when you plan for it. For the phase-by-phase view, see the ICP filing timeline.
Decision table
The table below summarizes the three paths on the factors that matter most.
| Global-only | Hybrid (global + China path) | Full mainland | |
|---|---|---|---|
| ICP requirement | Lower if not hosted in CN | Mainland components require filing | Filing usually required |
| Typical TTFB from China | 2–8+ s | <1 s with tuning | <1 s with tuning |
| Third-party APIs | Often blocked | Replaced or proxied | Replaced or proxied |
Which path fits your situation
The hosting and compliance decision changes shape depending on what your China operation needs to do first. The matrix below maps eight common situations to the recommended path and the first thing to verify before you act.
| Your situation | Recommended path | First verification step |
|---|---|---|
| Marketing site that must load in China; no filing, no entity | Hybrid interim: dependency replacement and offshore-only edge now; start entity and filing in parallel | Run the 10-point China readiness checklist |
| E-commerce checkout for mainland visitors | Full mainland path: WFOE holds the ICP filing and the mainland merchant account; run the license assessment | Confirm the mainland-registered entity qualifies for the WeChat Pay mainland merchant path |
| WeChat Mini Program ambitions | Web hybrid meanwhile: the program needs its own filing (error 86369); one filed entity underpins program, domain filing, and merchant account | Confirm the administrator holds a mainland ID for face verification |
| Already hosted in Hong Kong or on an offshore edge | Outside the mainland: no ICP filing, but the 2–8+ s cross-border cost stands; PSB filing instead of ICP for outside-mainland-only acceleration; a Hong Kong entity still cannot hold a future filing | Per-carrier TTFB from mainland test points, never averaged |
| Budget-constrained; China traffic small today | Global-only is defensible while China carries no commercial weight; read the full cost frame before committing | Measure current China TTFB before deciding the traffic share is small |
| Compliance-averse enterprise — minimal mainland footprint | Keep origin offshore (global-only or offshore-only edge with PSB filing); the license trigger still follows the product, so assess anyway | Classify the product against the license trigger |
| Long-term: full mainland migration planned | Hybrid as the stepping stone: entity first — no filing work starts before registration; five phases in order; plan the timeline early | Run the ICP filing timeline estimator |
| Global CDN (Cloudflare) user told to “just add China” | A gated add-on, not a filing bypass: Enterprise plan + separate subscription + JD Cloud content vetting; apex ICP filing or license required first | Confirm the apex ICP filing or license exists before requesting vetting |
Note: the matrix sits on top of a licensing split. Only MIIT-licensed operators may run mainland edge nodes; the operator license and the site-level ICP filing are separate instruments — your CDN vendor holds the license, your company holds the filing.
FAQ: Reaching China Without an ICP Filing
Can visitors in China reach a site without an ICP filing?
Yes, if the site is hosted outside the mainland. The ICP requirement is lower for sites not hosted in CN. But visitors will experience 2–8+ s TTFB and 15–30+ s page loads. Offshore CDNs without mainland edge nodes do not fix the cross-border transit problem.
Does hosting outside the mainland remove all compliance obligations?
No. The license trigger is what your product does, not where it is hosted. A paid platform or marketplace still needs to assess whether an ICP license applies. And if you later move hosting to the mainland, the filing obligation applies at that point.
Can we launch a China-facing path before the ICP filing is done?
Yes. The China path can go live while entity setup and filing work progress in parallel. Mainland-hosted components of the path require the filing, so plan the filing alongside the build — not after it.
Is a Hong Kong entity enough to hold the filing when we move mainland?
No. A Hong Kong entity alone does not satisfy the filing-holder requirement. The filing must sit with a mainland-registered company or qualifying partner — typically a WFOE. Plan the entity structure before the hosting migration, not after.
Is Hong Kong hosting a way to avoid the ICP filing?
Yes for the filing — the obligation attaches to mainland hosting, so hosting outside the mainland removes it. The cross-border performance cost still stands: 2–8+ s TTFB and 15–30+ s page loads. For outside-mainland-only acceleration, a PSB filing applies instead of an ICP filing. And a Hong Kong entity still cannot hold the filing when you later move mainland — that takes a mainland-registered entity.
What actually breaks on a global-only site in China?
Third-party APIs — Google Maps, YouTube, global font hosts, payment gateways — are blocked or unreliable behind the firewall. Full page loads on cross-border sites often reach 15–30+ seconds. Many users bounce before the first pixel appears. The site itself may be reachable, but the experience feels broken.
Do offshore CDNs, image compression, or VPNs fix the slowness?
No. An offshore CDN without mainland edge nodes does not touch the cross-border hop — the edge has to be inside the country. Image compression misses the transit path entirely. A VPN shifts the burden onto every individual visitor and is not a fix for a business audience.
Can we add a China path without replacing our global site?
Yes. Content is authored once in the global CMS and delivered through two paths — the existing global path for international visitors, and a China path for visitors on mainland networks. The global stack stays in place. Prerequisites still apply: mainland-hosted components need the filing, and blocked dependencies get replaced.
Which third-party dependencies does the China path replace?
Maps to Amap or Baidu Maps, video to domestic hosts, payments to WeChat Pay. Audit the full list via the network tab from a mainland session — classify each call as works, slow, or blocked, and treat the blocked ones as architecture decisions.
How do we verify the China path works from inside China?
Run per-carrier tests on Telecom, Unicom, and Mobile via mainland test-point services (boce.com, 17ce.com, ping.chinaz.com). Record the timestamp, network type, first-render time, and TTFB for each run. Never average across carriers: China's three major carriers route traffic differently, and a site that loads acceptably on one may time out on another.
Does going hybrid mean we can skip the entity and filing permanently?
No. Mainland-hosted components require the filing, and the obligation applies when hosting moves to the mainland. The license trigger follows the product, not the hosting location — a paid platform still needs to assess the license regardless of where the origin sits. The hybrid path is a stepping stone, not a permanent bypass.
What does the China path cost?
The filing service itself is free — the cost is calendar time: 2–4 weeks with complete documents and a qualified entity. Entry hosting bundles on both vendors are subscription-only. CDN basic fees are billed by traffic, peak bandwidth, or monthly 95th-percentile, with the Chinese mainland as its own billing region. For the full cost frame, see what mainland hosting actually costs.
Next steps
The decision is yours: accept cross-border latency, add a China path alongside the global stack, or move hosting fully to the mainland. Each path has a clear performance profile and a clear compliance footprint.
We can help you map the trade-offs to your product, timeline, and entity structure. Start with the hybrid China acceleration service for the infrastructure path, or the ICP compliance service for the filing and entity work. If you want a full picture first, run the 10-point China readiness checklist to see where your stack stands today.
Email hello@chinagateway.pro to talk through the decision.
Related articles
ICP Filing for Foreign Companies: Step-by-Step Timeline
The 2–4 week filing window and where it sits in your launch.
Why Your Website Is Slow in China (and What Fixes It)
What staying offshore costs: 2–8+ s TTFB, 15–30+ s loads.
ICP Filing vs ICP License: Which One You Need
The license trigger follows the product — offshore or on the mainland.
Mapping the trade-offs to your product and timeline?
We weigh global-only, hybrid, and full mainland paths against your stack — and align the infrastructure with entity and filing work. About our ICP compliance service.
hello@chinagateway.pro