Running on Builder.io?

Builder.io models or Figma sync misbehaving? We sort it out.

Builder.io is powerful, which is another way of saying it has many ways to come apart. Visual edits that override React components in ways nobody expected, symbols that override each other across pages, and Figma imports that lose half the layout on the way across. We bring the model schema, the symbols and the registered components back into agreement.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

builderio-publish.log

mismatched

What it is

Builder.io at a glance

Builder.io is a visual headless CMS that lets marketers and designers edit live pages against your real components, with an API-driven backend you consume from Next.js, Remix, Gatsby, Qwik, Shopify Hydrogen, Angular or raw HTML. It is used by teams that want a page builder on top of their own design system rather than a separate frontend.

The product includes a Figma-to-code bridge called Visual Copilot, A/B testing, edge personalization and a flexible content model. Pricing is based on content entries, seats and personalization volume. Builder.io is based in San Francisco and was founded in 2019 by Steve Sewell.

Type
Visual headless CMS with Figma-to-code
First released
2019
License
Proprietary SaaS, usage based pricing
Maintained by
Builder.io, Inc.
Typically used for
Marketing pages against a design system, A/B testing, personalization, Figma to production flow

The honest version

Builder.io pros and cons

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

Where Builder.io is strong

  • Edits happen against your real componentsA marketer can drop a ProductCard that is the actual registered React component, not a lookalike. What they see is what ships.
  • Figma-to-code is genuinely usefulThe Visual Copilot bridge turns Figma frames into Builder blocks that respect your design tokens, which closes a gap most CMSs leave open.
  • Headless by defaultYou render pages in your framework of choice, so performance, auth and routing are not forced into a vendor-shaped box.
  • A/B testing and personalization built inVariations and audience targeting are a dropdown rather than a separate Optimizely integration.
  • Edge delivery is fastContent is served from an edge CDN with short TTLs and client-side hydration that avoids the usual CMS lag.

Where Builder.io bites

  • Model schema changes are brittleRename a field and every page using it breaks silently. The editor shows a warning if you are lucky and a blank block if you are not.
  • Symbol overrides cascade in surprising waysAn override on one page can shadow the parent symbol's updates. Teams spend hours trying to understand why a global change does not land.
  • Registered component driftAdd a prop to a React component without updating the Builder registration and you get a silent mismatch. The visual editor shows the old shape and renders the new one.
  • Costs scale with content and personalizationEntry counts, seat counts and personalization requests stack quickly, and the step changes between tiers are large enough to notice at renewal.
  • The preview flow is fragileDraft previews rely on a live URL that your framework serves correctly with the correct CORS headers. Auth-protected staging environments often break preview, and the error messages are not clear.
  • Vendor lock-in is realContent lives in Builder's shape, and moving it to Contentful or Sanity requires a mapping pass and a rebuild of the editor surface.

Sound familiar?

Common Builder.io problems we fix

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

Model 'page' schema mismatch

Pages break after a schema change

A field was renamed, its type changed, or its validation tightened. Existing entries do not auto-migrate, so pages render with missing blocks until each is opened and saved.

Entries migrated, schema in step

Symbol 'site-header' overridden in 3 pages

Global symbol changes do not land everywhere

A header updated in the main symbol does not propagate to pages that have an override. The marketer sees the new header on most of the site and the old one on three pages, and nobody can work out why.

Symbol overrides deliberate, not accidental

Figma import: FRAME nested 11 deep

Figma import produces unusable output

A Figma file with deep nesting, non-auto-layout frames, or missing component definitions produces Builder output that is half a page. The Visual Copilot assumes auto-layout and fails on free positioning.

Figma that imports cleanly

Registered component 'ProductCard' missing prop 'variant'

Registered components are out of date

A prop added in React but not mirrored in the Builder registration. The editor cannot set it, and the component renders with a default the marketer did not choose.

Registry that matches the real code

Preview URL for draft not reachable

Draft previews do not load

The preview iframe is blocked by CORS, the staging URL is behind basic auth, or the preview token is not being forwarded by your framework's router.

Preview that works for the editor

Edge personalization cookie missing

Personalization falls back to default

A caching layer stripping cookies, or an edge function that runs before the personalization script sets one. The variation never fires and every user sees the control.

Personalization reaching the segment

Webhook signature verification failed

Webhooks are failing silently

A signing secret rotated in Builder but not in your handler, or a redeploy that reset an environment variable. Content changes are not invalidating caches downstream.

Webhooks signed and verified

What we do

Builder.io help, from setup to upkeep

Call us for one broken symbol, or let us own the Builder.io integration alongside your frontend.

Rescue
Schemas mismatched, symbols cascading in strange ways, or a Figma import that refuses to come across. We untangle it in the right order.
Component registry
React, Next.js or Qwik components registered properly, with input types, defaults and nested blocks so the editor sees what the code sees.
Figma-to-code pipeline
Design files structured for Visual Copilot, auto-layout applied, component instances named consistently, and the import path tested before every launch.
Personalization and A/B
Segments defined against real traffic, variations wired through the edge correctly, and analytics joined back to your warehouse.
Managed Tech
Ongoing watch on schema drift, webhook health, registry upgrades alongside your frontend releases, and a person to call when the editor goes blank before a campaign 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 Builder.io alongside something else?

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

Questions

Builder.io questions

Something else? Call+1 737 727 7327

Why do my Builder.io symbols behave differently on different pages?

Overrides cascade in an order that is not always obvious. A symbol edited in one page silently shadows the parent's updates for that page only. The fix is to audit which pages have overrides, decide which were intentional, and clear the rest. We walk through the symbol tree and give you a map of where the differences live.

Should we use Builder.io, Contentful or Sanity?

Each solves a different shape. Builder.io is visual-first and shines when marketing wants to edit pages against your real design system. Contentful and Sanity are stronger for structured content with many content types and editorial workflows. We give an honest view based on the team doing the editing, not the framework the engineers prefer.

Why does our Figma import lose half the page?

Usually because the design is not built for auto-layout. Visual Copilot assumes frames with auto-layout, named component instances, and reasonable nesting depth. Free positioning, nested groups and hidden layers produce output that looks unusable. Prep the Figma file first and the import quality jumps.

Can we move off Builder.io without a rebuild?

Partially. The content can be exported and mapped to another CMS, but the editor surface, the symbols and the overrides do not translate. Teams that want portable content usually treat Builder.io as a frontend editing layer, not a long-term content store.

How does Builder.io handle personalization at scale?

Variations and audiences are evaluated at the edge, with cookies setting the segment. The traps are caching layers that strip cookies, and edge functions ordered incorrectly so personalization runs on a stale cache key. We trace the request from browser to edge and fix the order.

How much does Builder.io help cost?

The quote costs nothing. Share the account, the models and what is drifting, and we come back with a figure before any work begins.

Free estimate

Builder.io giving you trouble?

Send us the account, the models that are drifting and the component registry. A real 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.