Running on Storyblok?

Storyblok visual editor refusing to load? We clear the backlog.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

storyblok-preview.log

still broken

What it is

Storyblok at a glance

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.

Type
Headless, visual content management system
First released
2017
License
Proprietary SaaS
Maintained by
Storyblok GmbH
Typically used for
Marketing sites, multi-brand content, e-commerce product content, multi-language web projects

The honest version

Storyblok pros and cons

No technology is all upside. This is where Storyblok earns its place and where it tends to cause trouble.

Where Storyblok is strong

  • The visual editor is a real selling pointEditors click on the hero image on the live page and the component opens in the side panel, which is far closer to how non-developers expect to work than a tree of fields in the abstract.
  • Nested bloks compose cleanlyComponents can contain other components as typed children, so a page is a tree rather than a flat bag of fields. Section layouts, grids and nested cards all map onto this without hacks.
  • Multi-language is well supportedField-level translation, folder-level translation and translated slugs are all available, and the Content Delivery API respects them so front ends do not have to re-implement locale logic.
  • Good SDKs for the modern JS ecosystemThe Next.js and Nuxt SDKs cover draft mode, the bridge, and preview toggling with minimal glue, and the React component for rendering bloks is small enough to read in an afternoon.
  • Versioned content is a first-class conceptDraft and published versions are separate on the API, and the cv parameter lets you cache aggressively without serving stale drafts in production.

Where Storyblok bites

  • Visual editor requires a public preview URLThe iframe renders a real preview of your site, which means hosting a preview environment that Storyblok can reach and that honors the bridge. Behind strict corporate networks or VPNs this becomes work.
  • Schema drift is easyComponents can be edited in the UI by anyone with permission. If the front end code and the component schema are not in version control together, you find out they differ when content breaks in production.
  • Rate limits are strict on Management APIBulk imports, migrations, or a chatty content model generation script hit the limit quickly, and the reset is not instantaneous. Backfills need batching and backoff from the start.
  • Rich text rendering is your code to ownThe rich text format is JSON, and the resolver function that turns it into HTML or React is on your side. Teams that treat it as a black box eventually hit a field that renders nothing.
  • Pricing is per team and per featureThe plan structure adds up quickly once you want more seats, more environments or SSO, and the enterprise tier is the only one with some deliverability features that smaller competitors ship by default.
  • The Nuxt and Next.js SDKs have evolving APIsMajor version bumps of the SDKs have changed the patterns for draft mode and the visual editor bridge more than once, so upgrades are not quite the no-op you hope for.

Sound familiar?

Common Storyblok problems we fix

The Storyblok problems that bring people to us, and what you have once each one is fixed.

X-Frame-Options prevents preview

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

component not found: 'hero_banner'

Front end crashes on a component it does not know about

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

422: component schema does not match

Schema has drifted between environments

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

draft content fetched in production

Unpublished content is leaking to live

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

webhook /story_published: 500

Publish webhooks never trigger a rebuild

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

Management API: Rate limit reached

Bulk operations keep hitting the rate limit

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

Hydration mismatch after preview toggle

Next.js hydration breaks in the editor

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

translated slug missing

Multi-language URLs are broken

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

Storyblok help, from rescue to steady state

Call us for one broken editor, or hand us the whole space.

Rescue
A preview iframe that will not render, a space where the schema has drifted, or a publish that does not trigger a build. We get content moving again.
Schema as code
Component definitions pulled out of the UI and into a repository so the front end and the CMS stay honest to each other, with migrations rather than manual field edits.
Front end integration
Next.js, Nuxt or SvelteKit wired up with draft mode, the bridge, cache busting on cv, and a render for the rich text format that handles every field type you have.
Multi-language and multi-space
Field or folder-level translation, translated slugs, and multiple spaces for brand variations, set up so editors are not fighting the model.
Content migration
Moving from Contentful, Sanity or a bespoke CMS into Storyblok, with the content model worked out first, bulk imports batched against the rate limits, and references kept intact.
Managed Tech
Schema change review, SDK upgrades, webhook monitoring, and a team on call when the editor stops working the morning of a product launch.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Storyblok alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Storyblok questions

Something else? Call+1 737 727 7327

Why can editors not use the visual editor on our Storyblok space?

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.

How do we stop the Storyblok schema drifting between environments?

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.

Why do our Storyblok webhooks never trigger a build?

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.

Can you migrate us from Contentful or Sanity to Storyblok?

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.

How do we handle draft previews on Next.js with Storyblok?

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.

How much does Storyblok help cost?

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

Storyblok giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.