Does Storyblok Work in China? Data Residency, PIPL & an Offshore Content API
Storyblok is a headless CMS: it stores each space's content in one offshore region — Europe, the US, Canada or Australia — with no mainland-China region, serves it through a content API that crosses the border, and leaves the ICP filing on the public site you build on top. A compliance-first look at the two doors.
Does Storyblok work in China?
Whether you can use Storyblok in mainland China is a data-residency and cross-border-API question before it is a speed one. Storyblok is a headless CMS: it holds the content your site is built on — and any personal data your content models carry — and serves it through a live content delivery API. Where that content is stored, and where the API answers from, is what China's law responds to.
Storyblok's own server-location FAQ says “Hosting of content is within Europe, the United States of America, Canada, or Australia,” distributed globally on AWS CloudFront. None of those four regions is in mainland China, so any content model holding personal data about China users is kept outside the mainland — a cross-border transfer of personal information PIPL governs. And because Storyblok is a backend behind a frontend you build and host, the ICP filing question lands on the public mainland site you run, not on Storyblok itself. The table below pairs Storyblok's own wording with the rule each line triggers.
This is a risk picture, not a verdict — what applies turns on what your models hold, how much of it is personal, and who your users are. Our China team can map your Storyblok exposure with you →
Compliance snapshot
- ! Reachable through a global edge, but Storyblok's content API answers from an offshore region — Europe, the US, Canada or Australia
- ✕ No mainland-China region exists: every hosting region Storyblok offers is outside the mainland
- ! Content models holding personal data of China users keep it offshore — a PIPL cross-border transfer
- ! The ICP filing attaches to the public site you build on Storyblok, not to the headless backend
- ✓ An ICP-filed, in-country delivery path can sit in front of your site — no rebuild, no migration off Storyblok
What Storyblok's own documentation says about China
| Fact | Primary source |
|---|---|
| Storyblok stores each space's content in one region you choose, and every region it offers is offshore. Its own server-location FAQ states “Hosting of content is within Europe, the United States of America, Canada, or Australia,” and that customers “can choose whether the data should be hosted in Europe, Canada, Australia, or the US” — a choice “only available on the Premium and Elite plans.” None of those regions is in mainland China, so the content your site is built on is stored outside the mainland. | Storyblok — Where are your servers (or AWS sites) located? (storyblok.com), retrieved 2026-10-07 |
| If your content models hold personal data, that data is held offshore. A headless CMS stores more than marketing copy — content models commonly carry author profiles, user-generated content, comments, and form- or personalization-style entries that can be personal information. Collected from people in China and kept in an offshore Storyblok region, that is a cross-border transfer of personal information under PIPL: the handler — you, Storyblok's customer, not Storyblok — must give notice, obtain separate consent, and satisfy one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). | PIPL Chapter III, Articles 38–43 |
| There is no region toggle that keeps the content on Chinese soil. For 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)). Because Storyblok publishes no mainland-China region — only Europe, the US, Canada and Australia — keeping your China users' content and personal data in-country means running that storage on infrastructure inside the mainland, a separate arrangement from your Storyblok space. | PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| Reaching it is the easy half — the live API still crosses the border, and the ICP question is about your site. “Storyblok and its main infrastructure use AWS CloudFront to distribute globally,” so published reads can be served from an edge cache; but draft and preview requests, personalized or uncached reads, and every write still resolve against the offshore region across the border — a round trip a plain edge cache does not remove. The ICP filing (State Council Order No. 292; MIIT Order No. 33) attaches to the public mainland website or app you build on top of Storyblok and its in-country hosting resource — not to the headless CMS itself. | Storyblok — Where are your servers (or AWS sites) located? (storyblok.com), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the deciding question about Storyblok is not how fast a page paints — it is where the content your site is built on is stored, and where the API that serves it answers from. Storyblok is a headless CMS: a live content backend your frontend calls on every request, not a bundle of files you can simply park at an edge. It answers both questions in its own documentation, and both answers point offshore. Reaching Storyblok from inside China is rarely the hard part; the licensing footing and the data residency are the exposure.
Storyblok in China at a glance
| What decides it | In Storyblok's own terms |
|---|---|
| Where your content lives | “Hosting of content is within Europe, the United States of America, Canada, or Australia.” Each space's content sits in the single region you pick — and no region is inside mainland China. |
| How it's delivered | “Storyblok and its main infrastructure use AWS CloudFront to distribute globally.” Published reads can come from an edge cache; draft, preview, personalized and write queries still resolve against the offshore region across the border. |
| Choosing a region | Customers “can choose whether the data should be hosted in Europe, Canada, Australia, or the US,” a choice “only available on the Premium and Elite plans.” Every available region is offshore. |
| Serving the public | The site you build on Storyblok and serve to mainland visitors needs an ICP filing tied to a mainland hosting resource. As a headless backend with no mainland region, Storyblok offers no ICP-filing footing of its own — the filing lands on your site. |
| Your data on Storyblok | Personal data in content models about Chinese users is stored offshore — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that an offshore region cannot meet. |
No mainland region, so the ICP question lands on your site
Storyblok hosts each space’s content in a single region you choose, and in its own words “Hosting of content is within Europe, the United States of America, Canada, or Australia.” Customers “can choose whether the data should be hosted in Europe, Canada, Australia, or the US,” a choice Storyblok notes is “only available on the Premium and Elite plans.” Every one of those regions is offshore; not one is in mainland China.
That geography settles the licensing question before performance enters it. A public-facing website served 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 must attach to a hosting resource physically inside the mainland. Storyblok is a headless backend with no mainland region, so there is nothing on Storyblok to file against — and because your frontend is a separate application you build and host, the filing lands on that public site, not on the CMS. “We already run on Storyblok” does not carry into China: reaching the content API is not the same as being cleared to operate a mainland site.
A live content API, not a bag of static files
A headless CMS is dynamic by nature: your site asks Storyblok for content on request, rather than shipping a fixed set of files. Storyblok states that it and its “main infrastructure use AWS CloudFront to distribute globally,” so published reads can be answered from an edge cache close to the user. But draft and preview content, personalized or uncached reads, and every write still travel back to the offshore region where the space lives — a cross-border round trip that an edge cache in front of a foreign origin does not remove. This is why “just put a CDN on it” under-answers the China question for a headless stack: caching the fast public reads leaves the dynamic path crossing the border, and leaves the ICP and data-residency facts untouched.
Your China users’ content stays offshore
Model anything that holds personal data in Storyblok — author profiles, account records, user-generated content, comments, form entries — and for China users that personal information lives in Europe, the US, Canada or Australia, outside the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, Storyblok’s customer, not Storyblok — 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 none of Storyblok’s four regions can satisfy.
This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both depends on what your content models hold, how much personal data you keep, and who your users are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep authoring in Storyblok. We add the piece a headless CMS with no mainland region cannot: compliant, ICP-filed delivery from inside the mainland, set in front of the public site you already run — no rebuild, no second codebase, and no move off Storyblok. Our China team maps your ICP and data-residency obligations against your entity and the personal data your content models hold, then stands up the in-country delivery — and, where the law requires it, the in-country storage — a lawful China presence needs, while your Storyblok spaces stay exactly where they are.
Related reading:
Frequently Asked Questions
Does Storyblok store Chinese users' content and data in China?
No. Storyblok hosts each space's content in the single region you pick, and the regions it offers — Europe, the United States, Canada and Australia — are all outside mainland China. So the content your site is built on, and any personal data your models hold about China users, is kept offshore.
Do I need an ICP filing to use Storyblok in China?
The ICP filing does not attach to Storyblok — it is a headless backend. It attaches to the public mainland website or app you build on top of it. Serve that site to mainland visitors from inside China and it needs an ICP filing tied to a mainland hosting resource, and Storyblok has no mainland region to provide one. Whether your particular setup triggers the filing is a risk to confirm with counsel, not a given.
Can 21YunBox help make our Storyblok setup compliant in China?
Yes. Our China team can assess your PIPL cross-border and data-residency exposure for the personal data your content models hold, and stand up compliant, ICP-filed in-country delivery — and, where the law requires your China users' data to stay on the mainland, in-country storage — in front of the site you already run, so you keep building on Storyblok. Get in touch to work through your specific case.
