Your AI website,
inside WordPress.

Yes. Every new account starts with 2 free conversions - no credit card required. Sign up, upload your first HTML file, and see what comes out before paying anything.

Any static HTML file works. Builderverse is optimized for AI-generated designs from tools like Claude, Google Stitch, ChatGPT, and Gemini, but any clean static HTML will convert. One important tip: if you use Claude Design, explicitly prompt it for “pure HTML, no bundler, no React” - its default export wraps the design in a self-extracting bundle that the converter can’t parse.

Yes. Builderverse generates templates specifically for Bricks Builder, a premium WordPress page builder. We are not affiliated with Bricks Builder in any way. You’ll need a recent Bricks version (2.0 or later is recommended).

Usually under 15 seconds. You upload, we process, and the download is ready.

Builderverse handles the heavy lifting - layouts, typography, styles, images, fonts, and script references. Think of the result as a production-ready starting point, not a pixel-perfect final product. Complex custom JavaScript or interactive widgets may need manual tweaks in Bricks.

Builderverse hands you Bricks’s structural primitives (text, div, section, image, svg, link, heading, button) with your HTML structure, classes, and styles preserved 1:1. It does not produce Bricks’s specialty widgets like Form, Menu, Slider, Accordion, Counter, Tabs, Image Gallery, or any of Bricks’s other widget abstractions. Each of those ships its own opinions about markup and styling, which would conflict with whatever your AI tool generated. Instead you get a clean, editable Bricks template that mirrors your source.

These elements are intentionally hidden in the Bricks editor, same as they're hidden on a real site until a user clicks the trigger. For content edits (text, links, icon swaps) use the structure panel on the right side of the Bricks editor: hidden elements are still selectable there. For visual layout edits, the source design opens these via design-specific toggle classes (`open`, `active`, `show`) or JavaScript functions. Simple drawers only need one class added via Bricks → Class field; composite menus may need several states activated at once. The activation logic is in the included `page-scripts.html`, or you can ask your AI assistant for a short snippet that replicates the open state. Just remove any temporary classes before publishing.

No. Every account starts with 2 free conversions. After that, credits are available in your dashboard - 5 for $29 or 15 for $59. One-time purchases, no recurring charges. Credits never expire. Builderverse is still early; we may introduce recurring plans later, but anything you’ve bought stays in your account.

One credit = one HTML upload. With a clean, well-prepared HTML file, that’s typically one finished Bricks template - so 5 credits can mean 5 ready-to-use websites. Working with AI-generated HTML sometimes means a couple of attempts to dial in the prompt or structure, and that’s just part of the workflow - your 2 free conversions are there to find what works before you buy credits.

Font links, scripts, and external libraries are auto-detected and ready to paste into Bricks header scripts. Tailwind CSS is compiled into a local stylesheet so your styles work without the Play CDN. Externally hosted images (Unsplash, Pexels, etc.) keep their original URLs and continue to load in WordPress. Local image paths are listed in the README - you’ll upload those to your Media Library manually.

Yes. You own everything you export from Builderverse - client projects, agency work, resale, all fair game. We don’t claim any rights to your converted templates.

Your HTML files and conversion results are stored while your project exists so you can re-download them. You can delete projects at any time from your dashboard. We don’t use your files for training, analysis, or anything beyond running the conversion.

Builderverse is built for static HTML from AI generators (Claude, Stitch, ChatGPT, Gemini). Framework exports (Framer, Webflow, Next.js, Vercel-deployed React apps), dynamic web apps, or JavaScript-heavy interactions aren’t the target use case and aren’t supported - they use their own layout engines, design tokens, and runtime logic that don’t translate cleanly to Bricks. If you run into issues with a supported file, contact us - we’ll troubleshoot together and try to make it right. As a rule, we don’t issue refunds: not for buyer’s remorse, not for files that fall outside the supported scope. That’s why every new account starts with 2 free conversions - so you can see exactly what you get before paying.