Bolt.new is an AI app builder from StackBlitz that runs a complete Node.js development environment in the browser. It generates full-stack applications from prompts, installs packages, runs servers, and shows live previews - with no local setup required.
Best for: Developers and technical builders who want a real in-browser dev environment with package and server control, and zero local setup.
Not ideal for: Completely non-technical users who never want to see code, or teams building very large projects where token costs accumulate quickly.
Bolt.new is StackBlitz’s AI app builder, and its defining feature is that it runs an entire Node.js environment inside the browser using WebContainer technology. This means the AI can do things most browser-based builders cannot: install npm packages, run development servers, execute build steps, and manage a real file system - all client-side, with nothing to install locally.
The result is a tool that sits closer to a real development environment than a no-code generator. You describe an app, Bolt generates the code in real time, and you watch it build with live previews. This review explains how Bolt works, breaks down its token-based pricing model, and covers where the in-browser approach helps and where it costs you.
What is Bolt.new?
Bolt.new is a browser-based, AI-powered full-stack development environment. It combines a frontier AI model with StackBlitz’s WebContainers, which run Node.js directly in the browser. From a single prompt, Bolt scaffolds a project - commonly a React or Next.js application built with Vite - and can install dependencies and run the app without leaving the tab.
Because the AI has control over a genuine environment, it can manage the full lifecycle of an app: creating files, installing libraries, running the dev server, and preparing for deployment. This ‘AI with environment control’ model is what differentiates Bolt from generators that only produce static code for you to run elsewhere.
Key features
- In-browser Node.js environment WebContainers run a full Node toolchain in the browser, so the AI can install npm packages and run servers with no local setup.
- Real-time code generation Bolt writes and edits files live, with an integrated editor and a preview pane that updates as the app builds.
- Full-stack scaffolding Projects are generated with modern frameworks such as React, Vite, and Next.js, and Bolt can wire up backend pieces and integrations.
- Direct file and terminal access Unlike no-code tools, you can open and edit any file directly and work with the project as real code.
- One-click deployment Generated apps can be deployed directly, and projects can be exported or pushed to GitHub for ongoing work.
How it works in practice
You begin with a prompt and Bolt scaffolds the project, installs dependencies, and starts a dev server - all visible in the browser. From there you iterate by chatting with the AI or editing files directly. Because the environment is real, you can verify that the app actually runs rather than relying on a static preview.
The most important practical detail is how token usage scales. Bolt syncs your project’s file system to the AI on each message, so larger projects consume more tokens per request. Keeping projects focused, and being deliberate about when you invoke the AI versus editing code yourself, is the main lever for controlling cost.
Output and code quality
Bolt produces standard, framework-idiomatic code - typically React or Next.js with Vite - that developers can read, extend, and maintain. Because you have direct file access and a running environment, it is straightforward to inspect and correct the output as you go, which is an advantage over tools that hide the code.
The trade-off is that getting the most out of Bolt benefits from some technical comfort. The tool gives you a real environment with real complexity, and while non-technical users can build with it, the experience and the ability to debug improve significantly if you understand the underlying stack.
Integrations and deployment
Because Bolt runs a full Node environment, it can work with any npm package, which makes its integration surface very broad - you are not limited to a fixed set of supported services. Backends and databases can be wired in as code, and projects can connect to external APIs like any standard application.
Deployment is available directly from Bolt, and GitHub export provides a path to continue development locally or deploy through your own pipeline. This flexibility suits developers who want to start fast in the browser but retain the option to move the project into a conventional workflow.
Limitations to be aware of
The token model is the principal limitation. Costs scale with project size and request frequency, and because pricing is variable per request, spend can be harder to predict than a flat per-message model. Free and paid plans have monthly token allotments, with paid tokens rolling over for an additional month.
Running a full environment in the browser also imposes occasional limits - very large or resource-intensive projects can strain WebContainers. For most web apps this is not an issue, but it is worth knowing that the in-browser approach has practical boundaries that a local environment would not.
Pricing
Bolt.new uses a token-based model rather than a per-message one. Tokens are consumed per request, with larger projects using more tokens because the file system is synced to the AI. Paid tokens roll over for one additional month. For plan limits, the daily cap and top-ups, see Bolt.new pricing and tokens explained.
| Plan | Price | What it includes |
|---|---|---|
| Free | $0 /mo | Explore the environment and build small apps.; 1 million tokens per month; 300,000 token daily limit; Full in-browser dev environment; Live preview and editing |
| Pro | $25 /mo | For active solo builders.; 10 million tokens per month; Token rollover for one extra month; Option to buy more tokens; Deployment and GitHub export |
| Teams | $30 /member/mo | For collaborating teams.; Per-member monthly token allotment; Team collaboration features; Centralised billing; Tokens are not shared between members |
| Enterprise | Custom | For larger organisations.; Custom token volumes; Priority support; Advanced security and controls |
Higher token tiers above Pro are available for heavier usage. Because consumption depends on project size and prompt frequency, monitor your token burn early to estimate ongoing cost. Verify current limits on Bolt’s pricing page.
Pros and cons
Pros
- Runs a genuine Node.js environment in the browser - install packages, run servers, no setup
- Direct file and terminal access gives developers real control
- Works with any npm package, so the integration surface is very broad
- Standard framework output (React/Next.js/Vite) is readable and maintainable
- Token rollover softens the impact of variable usage
Cons
- Token costs scale with project size and can be hard to predict
- Larger or resource-heavy projects can strain the in-browser environment
- Gets the most value when the user has some technical background
- Variable per-request pricing makes budgeting less straightforward than flat plans
Common questions
How does Bolt.new pricing work?
Bolt uses a token-based model. The free plan includes 1 million tokens per month (with a 300,000 daily limit), Pro is $25/month for 10 million tokens, and Teams is $30 per member per month. Tokens are consumed per request and paid tokens roll over for one additional month.
Why does Bolt use so many tokens?
Bolt syncs your project’s file system to the AI on each message so it has full context. The larger your project, the more tokens each request consumes. Keeping projects focused and being deliberate about when you prompt the AI helps control usage.
Is Bolt.new good for non-developers?
Non-technical users can build with Bolt, but the tool exposes a real development environment with real complexity. The experience - especially debugging - is significantly smoother for users with some understanding of the underlying stack.
Can I deploy and export apps from Bolt?
Yes. Bolt offers one-click deployment, and projects can be exported or pushed to GitHub so you can continue development locally or deploy through your own pipeline.
What is the difference between Bolt.new and Lovable?
Bolt is code-first and runs a real in-browser dev environment with direct file access, favouring developer control. Lovable is more guided, auto-provisions a Supabase backend, and leans toward non-technical users. Bolt suits technical builders; Lovable suits founders who want a managed full-stack result.
Verdict
If Bolt’s token use or browser editor is what is pushing you out, our Bolt.new alternatives guide matches each replacement to the reason for leaving and includes Bolt’s own token-saving steps.
Bolt.new occupies a distinctive position among AI app builders: it gives you a real, AI-controlled development environment in the browser rather than a managed no-code experience. For developers and technically comfortable builders, that control - direct file access, any npm package, a running server - is a genuine advantage over more constrained tools.
The token model is the thing to plan around. Costs rise with project size and request frequency, so Bolt rewards focused projects and deliberate prompting. If you value control and a real environment over a fully managed flow, and you keep an eye on token burn, Bolt is a capable and flexible choice. The free tier is enough to learn how its usage scales for your kind of project.