Visual editor will not load the preview
The front end sets X-Frame-Options or a strict Content Security Policy that blocks the Storyblok iframe. Editors see a broken frame and cannot click to edit.
Preview loading under the editor domain
Running on Storyblok?
Storyblok sells itself on the visual editor, and the visual editor is also the thing that stops working first. We take over spaces where the preview iframe refuses to connect, where the bloks on the live site have drifted from the component schema in the Management API, or where a Next.js front end is throwing 500s on draft previews that nobody can reproduce locally.
What it is
Storyblok is a headless content management system founded in 2017 in Linz, Austria, built around a visual editor that renders the live front end inside an iframe and lets editors click directly onto the component they want to change. Content is modelled as nested bloks, which are typed components defined in the Management API and composed inside a story.
The platform exposes a Content Delivery API, a Management API, a GraphQL endpoint, a webhook system for publish and workflow events, and SDKs for Nuxt, Next.js, SvelteKit and most mainstream frameworks. It competes with Contentful, Sanity and newer entrants, and leans into the visual editing experience as the differentiator editors notice first.
The honest version
No technology is all upside. This is where Storyblok earns its place and where it tends to cause trouble.
Sound familiar?
The Storyblok problems that bring people to us, and what you have once each one is fixed.
The front end sets X-Frame-Options or a strict Content Security Policy that blocks the Storyblok iframe. Editors see a broken frame and cannot click to edit.
Preview loading under the editor domain
A new blok was added in the UI but no React or Vue component was written, or the mapping from technical name to component was never updated. Any page using the blok falls over.
Every blok mapped and rendered
Fields added, renamed or deleted directly in production, with no corresponding migration applied to staging. Content exported from one space fails to import into another.
Schema managed as code
A deploy that reused the preview token, or an API call that forgot the version parameter. Visitors see drafts, SEO sees drafts, and the editor is surprised.
Draft and published strictly separated
A static site build that should kick off on publish but the endpoint is returning errors, or the signing secret is wrong, so retries pile up and content stays stale on the CDN.
Webhooks firing reliably
A migration script, a content import from Contentful or a backfill job that fires requests as fast as they return. Half the operations succeed, the rest need to be re-run.
Batching and backoff in the client
Draft mode produces different HTML than the server did, because fetching is not consistent between the server and client paths. Editing a page triggers a client-side crash.
Draft and live paths consistent
A page is only translated in some languages, the translated_slugs field is empty for the others, and the front end falls back to the default slug, which produces wrong canonicals.
Translations mapped across all locales
What we do
Call us for one broken editor, or hand us the whole space.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Nine times out of ten it is the preview iframe being blocked. The front end sends X-Frame-Options deny or a Content Security Policy that forbids frame-src app.storyblok.com, so the editor loads a blank frame. The fix is to permit the Storyblok editor origin only on the preview deployment, plus making sure the bridge script actually loads on draft pages.
Take the component definitions out of the UI and into a repository through the Management API, make changes by pull request, and apply them to each space with a script. Editors edit content; developers edit schema. Draft and production environments then evolve the same way staging and production do in a regular application.
The common causes are a receiver that returns a non-2xx status on the signing failure path, a build hook URL copied from a stale environment, and Storyblok queuing retries that silently stop after a while. We log every incoming webhook, verify the signature against the shared secret properly, and make the receiver idempotent so safe retries do no harm.
Yes. We work out the component model in Storyblok first, map every Contentful content type or Sanity schema onto bloks, import content in batches that respect the Management API rate limits, and port any custom rich text renderer. The front end is the piece that needs the most rewriting, because the two APIs do not look alike.
Next.js draft mode plus the Storyblok bridge is the current recommended pattern. Draft mode sets a cookie that your fetchers read and switch the API version to draft, the bridge script listens for editor messages and refreshes the page, and the production build does not fetch draft content. We set it up so editors see changes immediately and public visitors never do.
The quote is free. Describe the space, the front end framework, and the problem you are seeing, and we come back with a number before we touch anything.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: