Builder.io's Visual Editor lets a team that already has a React or Next.js codebase hand routine page and content changes to non-developers, without moving the codebase into Builder. Developers register the components that already exist in the app. Builder becomes the place to compose pages from those components and publish content changes without a code deploy. It is a content layer next to your codebase, not a replacement for it.
What does registering a component actually do?
Registering a component makes an existing React component available in the editor. A developer calls registerComponent() so the component can "appear in the Visual Editor as a custom block" (Builder.io, "Register Custom Components"). Registration also defines which props are editable: "If you have a prop you'd like to make editable in the Visual Editor, be sure to define an input for it" (same source). Once registered, the component shows up in the editor's Insert tab. Someone without a coding background can drag it into a page and adjust its registered inputs, and nothing beyond what the developer exposed.
Builder keeps a map of registered component names to references. Content is stored as JSON with a blocks field listing which components to render and with what props (Builder.io, "How Builder Works"). Your app renders that JSON by walking the blocks and instantiating the matching registered components. The component code, behavior, and styling all stay in your repository. Builder says it "integrates with your front-end code, not with your hosting platform, and pushes content to your site or app using APIs or generated code. You control your site, code, and hosting" (same source).
How does publishing work?
Content in Builder moves through a draft-and-publish cycle, not a code deploy. Builder's steps are: "Go to a draft content entry, or create a new one," "Update text, styles, and more within the content entry," then "Click the Publish button" (Builder.io, "Publish your content"). Publishing takes effect at the data layer right away: "Publishing a content entry makes it accessible to standard API calls and should make it visibly accessible on your web application, if integrated correctly" (same source).
"If integrated correctly" matters. Your app has to pull from Builder's Content API and point at the right preview or production URL for a published change to show up. Publishing in Builder's dashboard does not trigger a new deploy of your app.
What does Builder's AI do, and what does it need first?
Builder ships two different AI features that solve different problems.
Visual Editor AI works inside the content-editing flow you already have. Builder describes it as handling "various tasks, such as generating and editing content, styling components based on style guides, and adding interactivity by connecting content to data or responding to user actions" (Builder.io, "Generate content with Visual Editor AI"). It works only with what is already registered: it "can use your Space's registered design tokens, custom components, templates, and Symbols" (same source). Builder states the dependency directly: "For Visual Copilot to have something to work with, you must have a selection of custom components" (same source). With no registered components, AI generation has little to work with. This is the same registration step described above, not a separate setup.
Visual Copilot is a Figma-facing product: an AI Figma-to-code plugin that converts a selected Figma design into React, Vue, Svelte, Angular, or other framework code. For a team with a component library, Builder says "this feature in Visual Copilot uses AI to map reusable components in your Figma file to those in your code repository and generates code using your existing components when you have them" (Builder.io, "Introducing Visual Copilot"). That component-mapping capability is "currently available only through a private beta program for organizations with maintained design systems and component libraries" (same source), so do not assume it is turned on by default. It is a design-to-code generator you run once per design, not an ongoing content-editing tool like Visual Editor AI.
What stays in code, and what moves into Builder?
| Stays in your codebase | Moves into Builder |
|---|---|
| Component code, logic, styling internals | Which components appear on a given page, and in what order |
| Hosting and deployment (Netlify, Vercel, AWS, etc.) | The registered inputs' values (text, images, links) for each page |
| Which props are exposed as editable inputs | Draft/publish state and content history for those entries |
| Build pipeline and framework choice | AI-generated content and styling, scoped to registered components/tokens |
Who is Builder.io for?
Builder.io fits a team that already has developers, a component library, and a reason to let non-developers ship pages without a deploy. Builder's page for marketing teams describes the split: developers handle "system integrations with existing tools," "approved components and templates," and "brand governance frameworks," while marketers "create landing pages, campaign pages, site updates, and reusable sections in the Visual Editor" within that structure (Builder.io, "Marketing Teams"). The page also names roles, locales, and permissions as part of the model, so it assumes cross-functional teams rather than one person doing every job.
It stops fitting when there is no codebase. A solo site owner with no developer has no React or Next.js app to register components against, so Builder has nothing to sit beside. If you have AI-generated app code from Bolt, v0, or Lovable and you are turning it into an owned codebase, our guide on moving an AI builder project into your own codebase covers that earlier step. Builder.io's job starts once the codebase and its components exist.
What should I use if Builder.io is the wrong fit?
Start with the output you need. These categories solve different jobs.
| Your actual need | Category to evaluate |
|---|---|
| Let non-developers compose pages from approved components in an existing app | A visual content layer such as Builder.io |
| Give developers a starting code draft from a design | A code-export tool, followed by code review and normal deployment |
| Publish a designed marketing site without creating a codebase | A hosted builder or a design-to-publish tool |
| Let an outside coding agent propose changes to an owned repository | A repository workflow with narrow access, review, tests, and separate publish approval |
Do not choose a content layer only because it has a visual editor. Confirm that you already have the components, an integration owner, a preview environment, and publishing controls. If you do not have a codebase, compare hosted-site tools instead. If you need portable code, test the generated files and the deployment path.
What are Builder.io's real limitations here?
- Registration is an ongoing developer task. Every component a non-developer should use in the Visual Editor must be registered with explicit editable inputs first. Nothing is picked up automatically from your source tree.
- The AI features depend on the same registration. Visual Editor AI and Visual Copilot only work with components, tokens, and templates your team has registered. An unregistered part of your design system is invisible to Builder's AI, not just to a human editor.
- A correct publish still depends on your integration. Content is visible "if integrated correctly," so a broken preview URL, a stale SDK version, or a misconfigured Content API call can leave a published change invisible on your site even though Builder shows it as live.
- It does not touch your hosting. Builder delivers content through an API or generated code. Your deploy pipeline, uptime, and hosting bill stay what they were.
- It is a content API, not a general coding-agent route. If you want an outside AI tool such as Claude or ChatGPT to edit your site directly, see how ChatGPT, Claude, Codex or Cursor can edit an existing website.
Example (hypothetical): A Next.js team registers a PricingSection component with plan, price, and features as editable inputs. For a pricing update, a growth marketer opens that content entry in the Visual Editor, edits the price and feature list through the registered inputs, and clicks Publish. No code change and no deploy are needed. The updated section appears on the live pricing page because the app's Content API integration already points at Builder's production endpoint. If the team later wants an AI-generated first draft of a new landing page section, they ask Visual Editor AI to build it from the same registered PricingSection and other approved components, then a marketer edits the result before publishing. This is illustrative only, not a test we ran.
How do I check the setup before I rely on it?
- Confirm each component you want non-developers to edit is registered, with the specific props exposed as inputs, not just present in your codebase.
- Confirm your app's preview URL points at your current deployed environment, and that your production URL is correct before anyone publishes for real.
- Test one draft entry end to end: edit it, publish it, then load the live page to confirm the change appears.
- If you use Visual Editor AI or Visual Copilot, confirm the components or Figma mappings you expect it to use are registered first. An empty result usually means nothing is registered yet, not that the AI failed.
- Set roles and permissions before you give access to a non-developer, scoped to content editing rather than account or integration settings. The narrow-access principle in how to give an AI agent access to your website applies just as well to a human collaborator's Builder role.
Builder.io does not ask a React or Next.js team to give up their codebase. It asks them to register the components worth exposing, then hands page composition and publishing to people who are not writing code. It is built for a team that already has developers and a component library to point at.