Builder compatibility matrix
How each supported builder behaves in the conversion engine. Scores reflect measured fidelity across our permanent regression fixtures, not marketing claims.
13 of 13 builders shown
| Builder | Framework | ZIP | GitHub | Pages | Images | Assets | SEO | Animations | Forms | WordPress | Score | Success | Known limitations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Lovable | React + Vite + Tailwind | Yes | Yes | Excellent | Excellent | Excellent | Excellent | Good | Good | Excellent | 96–99 | 98% | Backend features and authenticated areas are not converted. |
| Framer | Framer static export (HTML/CSS/JS) | Yes | — | Excellent | Excellent | Good | Good | Fair | Fair | Good | 88–94 | 92% | Runtime-driven interactions and CMS relationships need manual rebuilding. |
| Bolt.new | Vite / React / Astro (varies per project) | Yes | Yes | Very good | Very good | Very good | Good | Good | Good | Very good | 88–96 | 93% | Projects with server routes need those removed before export. |
| Cursor AI | Any (React, Next.js, Vue, static) | Yes | Yes | Excellent | Excellent | Excellent | Very good | Good | Good | Excellent | 90–98 | 95% | Server-rendered features must be removed or made static. |
| Claude (Artifacts & Projects) | React / static HTML | Yes | Yes | Good | Good | Good | Fair | Good | Fair | Very good | 85–93 | 90% | Single-artifact exports often lack navigation and SEO metadata. |
| Google AI Studio | React / Vite / static | Yes | Yes | Very good | Good | Very good | Fair | Good | Fair | Very good | 84–93 | 89% | Runtime AI features are not portable to a static theme. |
| Replit | Node / React / static (varies) | Yes | Yes | Very good | Very good | Very good | Fair | Very good | Good | Very good | 86–95 | 91% | Backend routes and Replit DB features are not converted. |
| Webflow | Webflow static export (HTML/CSS/JS) | Yes | — | Excellent | Excellent | Excellent | Excellent | Good | Good | Excellent | 92–98 | 96% | CMS, Ecommerce and Memberships need to be rebuilt in WordPress. |
| Base44 | React application export | Yes | Yes | Good | Good | Good | Fair | Good | Fair | Good | 82–91 | 87% | Platform data and auth layers must be removed before export. |
| V0.dev | Next.js + React + Tailwind | Yes | Yes | Very good | Very good | Excellent | Very good | Good | Good | Very good | 88–96 | 92% | Server-side Next.js features have no static equivalent. |
| React (Vite / CRA) | React SPA | Yes | Yes | Excellent | Excellent | Excellent | Very good | Very good | Good | Excellent | 90–98 | 95% | Content that only exists after an API call is not captured. |
| Next.js | Next.js App or Pages Router | Yes | Yes | Very good | Very good | Excellent | Excellent | Good | Good | Very good | 88–96 | 92% | Any server-only feature must be replaced before export. |
| Static HTML | HTML / CSS / JavaScript | Yes | Yes | Excellent | Excellent | Excellent | Excellent | Excellent | Very good | Excellent | 94–100 | 98% | Server-side includes have to be flattened into plain HTML. |
How to read the score
- 100 — perfect: every page, image, link and component matched the baseline.
- 99 — excellent: cosmetic differences only.
- 98 — minor issues: a few assets or animations need a manual touch.
- 95–97 — fidelity issues worth reviewing before launch.
- below 95 — treated as a failed conversion and blocked from release.
Something scoring lower than expected?
Most fidelity loss comes from remote images, JavaScript-only navigation or missing routes — all fixable before you export.