This review is based on documented features, verified pricing, and community sentiment — not hands-on testing. See how we research →
Bolt.new has generated over 1 million websites. That's not a marketing claim — it's the benchmark for what browser-native AI app generation can do at scale. Built on StackBlitz's WebContainer technology (Node.js running in the browser, no server round-trips), Bolt generates full-stack React applications from natural language prompts with zero local setup.
January 2026 saw a 40% performance improvement in build speed. Bolt Cloud V2 added built-in databases, authentication, file storage, and edge functions — transforming it from a code generator into a more complete development platform. The honest question in 2026 is no longer whether Bolt works. It clearly does. It's whether the token consumption model makes it cost-effective for your specific use case.
This review covers Bolt's documented capabilities across the use cases people actually reach for it — MVPs, landing pages, internal tools, dashboards, and design-to-code handoffs — based on verified features, current pricing, and community feedback from developers and non-technical builders alike.
Bolt has grown well past its original "prompt to app" pitch. Here's what the platform actually covers now, feature by feature.
This is the core technology, and it's worth understanding because it explains almost everything else about Bolt. WebContainers are StackBlitz's invention: a full Node.js runtime that executes entirely inside your browser tab. No cloud round-trips, no local setup, no Docker. The file system, terminal, package manager, and dev server all run client-side. That architecture is the reason generation feels fast — there's no server in the middle of every keystroke. It's also a genuine technical differentiator that most competitors don't share.
Bolt lets you choose the model behind each task. Claude Opus 4.6 is the default, with GPT-4o and Gemini 1.5 Pro available as alternatives. You can pick the best model for the job — one for reasoning-heavy logic, another for speed. That flexibility is rare in the app-builder category, where most tools lock you to a single provider. For teams that care about model choice, it's a real reason to look at Bolt over Lovable.
Upload a Figma design file and Bolt generates runnable React code from it. For designers and the developers who inherit their work, this shortens the handoff considerably — you're starting from a working component tree instead of redrawing the layout by hand. It's one of Bolt's clearest advantages over Lovable, which has no equivalent.
The 2026 release added built-in databases, authentication, file storage, edge functions, analytics, and hosting. You no longer need a separate Supabase account to ship something with a backend — Bolt covers the standard needs in-platform. This is the change that moves Bolt from "code generator" toward a more complete development platform.
You can switch out of build mode and into a planning conversation. Describe what you want, talk through the architecture, and settle the requirements before any code is generated. On complex projects this matters more than it sounds — it's the single most effective way to keep Bolt from going off the rails and burning tokens on the wrong thing.
From inside Bolt, one click gives you a live URL with SSL. For teams that want to move the project into a local environment afterward, there's GitHub export. So the deploy story works both for "ship it now" and "hand it to engineering."
Bolt can generate images directly from text prompts — useful for placeholder art and simple visual assets without leaving the tool. It's available on paid plans and enabled in settings under Add-on features.
Underneath the AI layer is a real editor: file system, terminal, package manager, and live preview, all in the browser tab. If you want to read and edit the generated code directly — not just prompt at it — you can, which is more than some competitors allow.
Token consumption is Bolt's most consistent community complaint, and it's worth explaining clearly because it's the thing most likely to surprise you. The issue is structural. Bolt syncs the entire codebase on every interaction, which means a 50-file app costs significantly more per message than a 5-file app. The more your project grows, the more each instruction costs — even when the change you're asking for is small.
The specific pain shows up in normal workflows: building an MVP iteratively, making design revisions, debugging errors the AI itself generated. All of these consume tokens at rates that catch Pro users off guard. You don't feel it on a quick landing page. You feel it on day three of an ambitious build.
The mitigation is real, though, and most people skip it. Use Discussion Mode before you start generating, and plan the architecture upfront. A well-planned Bolt session uses roughly 3–5x fewer tokens than an iterative trial-and-error approach, because you're not paying to regenerate the same files while the AI figures out what you actually meant.
For a rough sense of scale: a simple landing page uses minimal tokens. A full-stack app with authentication, a database, and 10+ pages can exhaust a Pro monthly allocation on a single complex project. Budget for that reality before you commit to building something large on Bolt alone.
Because the whole codebase syncs on each message, your per-interaction cost climbs as the project does. There's no fixed "this prompt costs X" you can plan around — the same instruction is cheap on a small app and expensive on a large one. Planning in Discussion Mode is the closest thing to a cost control Bolt offers.
The most consistent warning from developers who've used Bolt extensively is what they call the "70% wall." The first 70% of a project — scaffolding, UI components, standard CRUD, authentication — Bolt handles well and fast. The remaining 30% — custom business logic, complex state management, edge-case debugging — is where the AI struggles and you need either developer intervention or a willingness to accept limitations.
For prototypes and MVPs where 70% is enough to prove the concept, that's not a problem — it's the whole value. For production applications that have to be maintained and extended, plan for a developer to finish the work. This isn't unique to Bolt; every tool in the category hits a version of the same wall. But it sets expectations correctly: Bolt is a prototyping and MVP engine, not a replacement for an engineering team on a production system.
Bolt's Figma import is one of its most-searched features, and for the right use case it's genuinely useful. Upload a Figma design file and Bolt generates functional React components that preserve layout, spacing, and styling. The translation isn't always pixel-perfect, but for designer-to-developer handoffs on MVPs and prototypes, it eliminates a lot of manual rebuild work.
The limitation is the same one you'd expect: complex interactive states, custom animations, and advanced component logic still need a developer's hands after the import. Treat the Figma import as a strong starting point rather than a finished product — a way to skip the tedious first pass, not to skip engineering entirely. Among browser-based builders, it's the feature that most clearly separates Bolt from Lovable.
Pricing verified June 2026. Bolt runs a token-based model across four tiers.
| Plan | Price | What you get |
|---|---|---|
| Free | $0 | Limited tokens per month, access to Claude Opus 4.6, no credit card required. Useful for testing and simple projects. |
| Pro | $25/mo | $20/month billed annually. Higher token allocation, all models, Bolt Cloud features, priority generation. |
| Teams | $30/user | Collaboration features, shared projects, admin controls. |
| Enterprise | Custom | Volume tokens, security and procurement support. |
Token consumption is not fully transparent, and that's the honest caveat on every tier. Complex multi-file apps with frequent iterations consume tokens faster than simple projects. Bolt syncs the entire codebase on each interaction — that's what drives the unpredictability. Using Discussion Mode to plan before building significantly reduces wasted token consumption, and it's the closest thing to a budgeting lever the pricing model gives you.
January 2026 brought a 40% build performance improvement. Bolt Cloud V2 launched with built-in databases, authentication, file storage, and edge functions. Figma import was added. Claude Opus 4.6 became the default model. AI image generation was added to paid plans.
The three browser-based builders people compare most often each lean in a different direction. Bolt optimizes for speed and model flexibility, Lovable for design-first MVPs on a Supabase backend, and Replit for learning and transparent, multi-language code. Here's how they line up on the features that tend to decide it.
| Bolt.new | Lovable | Replit | |
|---|---|---|---|
| Best for | Speed, Figma-to-code, multi-model | Design-first MVPs, Supabase | Learning, multi-language, transparent code |
| Technology | WebContainers (in-browser Node.js) | React + Supabase | Cloud IDE + Agent |
| Multi-model | ✓ Claude/GPT/Gemini | ✗ Claude only | ✓ Multiple |
| Figma import | ✓ 2026 | ✗ | ✗ |
| Built-in database | ✓ Bolt Cloud V2 | ✓ Supabase native | ✓ |
| See the code | ✓ Full browser IDE | Limited | ✓ Full IDE |
| Free tier | ✓ Limited tokens | ✓ 5 credits/day | ✓ Limited |
| Starting price | $25/month | $25/month | $25/month |
| One-click deploy | ✓ Netlify | ✓ | ✓ |
| Best audience | Developers + technical founders | Non-technical founders | Learners + multi-language |
For a fuller breakdown of the category, see our guide to the best AI app builders in 2026. If you want to keep working in an existing codebase rather than start fresh in a browser, Cursor is the more natural fit — none of these three are built for that.
Ease of use scores high because there's zero local setup, it's browser-native, and Discussion Mode reduces off-rails generation — it only gets steeper on genuinely complex projects. Features are the standout: WebContainers, multi-model support, Figma import, Bolt Cloud V2, one-click Netlify deploy, GitHub export, and AI image generation add up to one of the deepest feature sets in the category. Value takes the hit, and it's almost entirely the token model — the free tier is limited, complex projects exhaust credits fast, and the $25/month Pro tier is competitive against Lovable but only if you manage consumption. Integration is strong across Supabase (external), Netlify (native), GitHub export, Figma import, and multi-model APIs. Support and docs rest on a solid StackBlitz foundation with a strong community — r/vibecoding alone has 89K members — but the token-consumption documentation is the weak spot, and it's the exact area users most need clarity on.
Limited tokens per month. No credit card required.
Try Bolt.new Free →Bolt fits a specific kind of builder very well, and frustrates another kind just as reliably. Here's the honest split.
Bolt.new is among the strongest browser-native app builders available, and the 1M+ websites generated back that up. Going from a text prompt to a live, deployed full-stack application without leaving the browser is a real advantage for early-stage product work — and the WebContainer architecture is why it feels faster than the alternatives. The 2026 additions, Figma import and multi-model support especially, widen Bolt's lead for design-to-code workflows.
The token model is the thing to manage. On complex projects it surprises most users, and the 70% wall means production polish still needs a developer. Plan in Discussion Mode, watch your consumption, and keep expectations honest about where the AI stops. Do that, and for the core use case — fast MVPs and design-to-code at $25/month — Bolt delivers.