How to Use Bolt.new | Build Websites and Web Apps with AI in the Browser

Bolt.new is an AI-powered builder for creating websites, web apps, and prototypes directly in the browser. You describe what you want to build, Bolt generates the project, and you can preview, edit, run, and iterate without setting up a local development environment first.

This guide explains what Bolt.new is, how to use it, how to write better prompts, when it fits better than other AI app builders, what to check on pricing, and how to review generated apps before publishing.

Table of Contents

1. What Bolt.new Is
2. What You Can Build with Bolt.new
3. How to Use Bolt.new
4. How to Write Better Prompts
5. When Bolt.new Is a Good Fit
6. Pricing and Tokens
7. Safety Checks Before Publishing
8. Summary

What Bolt.new Is

Bolt.new is a browser-based AI development tool from StackBlitz. It lets you prompt, generate, run, edit, and deploy web projects without starting from a local terminal setup.

The key idea is that Bolt is not only a mockup generator. It is built around an in-browser development environment, so it can create app files, install packages, run code, and show a live preview as you work.

That makes it useful for moving from an idea to a working prototype quickly. It also means the output still needs technical review if you plan to publish it or use it with real users.

What You Can Build with Bolt.new

Bolt.new is strongest when you want to build and test a web project quickly.

Compared with v0 by Vercel, Bolt.new is more focused on full project execution in the browser. v0 is often better when the main goal is UI and React component generation.

Compared with Lovable, Bolt.new feels closer to a development workspace. Lovable is attractive for app flow creation through chat, while Bolt is useful when you want to see and work with the generated project more directly.

How to Use Bolt.new

The basic workflow is:

1. Open Bolt.new.
2. Describe the website or app you want to build.
3. Review the generated project and preview.
4. Ask Bolt to add, remove, or fix features.
5. Check the files and dependencies.
6. Test the main user flow.
7. Decide whether to publish, export, connect a repository, or rebuild parts manually.

Start with a small version. A single screen or one main workflow is easier to review than a full SaaS platform.

For example:

"Build a simple invoice calculator for freelancers. It should let users enter hourly rate, hours, tax rate, and discount, then show subtotal, tax, and total. Keep it responsive and do not add login, database, or payments yet."

This prompt limits the scope, defines the inputs, explains the output, and prevents Bolt from adding unnecessary complexity.

How to Write Better Prompts

Good Bolt.new prompts are specific about users, screens, behavior, and constraints.

Include these details when relevant:

• Who will use the app
• The main problem it solves
• Pages or screens needed
• Inputs and outputs
• Data that should be saved
• Features to avoid in the first version
• Preferred design tone
• Whether backend, database, or authentication is needed
• Any framework or library preference

The safest prompt pattern is: purpose, user, first workflow, data, constraints. If you ask for everything at once, the generated project becomes harder to debug and easier to misunderstand.

Follow-up prompts should be narrow. "Add a CSV export button to the results table" is better than "make this more professional."

When Bolt.new Is a Good Fit

Bolt.new is a good fit when you want to test a web app idea quickly and are comfortable reviewing generated code.

It works well for:

• Startup MVPs
• Small internal tools
• Product demos
• Landing pages with interactive sections
• Learning projects
• Frontend-heavy experiments
• Early validation before hiring or building fully

It is less ideal when the hardest parts are compliance, advanced permissions, payment logic, sensitive data, long-term maintainability, or complex backend architecture. In those cases, Bolt can still help with a prototype, but production work needs a proper review process.

Pricing and Tokens

Bolt.new uses a token-based usage model, and the details can change. Official pricing currently lists a free plan with token limits and paid plans such as Pro and Teams with higher monthly token allowances and additional features.

Before relying on Bolt.new for repeated work, check:

• Daily and monthly token limits
• Whether private projects are included
• File upload limits
• Hosting and web request limits
• Branding on published sites
• Custom domain support
• Database and backend features
• Whether unused tokens roll over
• Team collaboration needs

The practical risk is iteration cost. A vague prompt can burn tokens through repeated fixes. Planning the first version before you prompt is usually cheaper than asking Bolt to discover the product with you.

Safety Checks Before Publishing

Before publishing anything generated by Bolt.new, review it as real software.

Check these points:

• Are API keys, tokens, or secrets hidden?
• Are form inputs validated?
• Is user data stored safely?
• Are admin-only actions protected?
• Does the app behave correctly on mobile?
• Are loading and error states handled?
• Are dependencies necessary and current?
• Does the app still work after a fresh reload?
• Are paid services or external APIs creating unexpected costs?

AI-generated apps can look convincing while still having weak security or broken edge cases. If the project handles personal data, payments, customer records, or business operations, get a technical review before launch.

Summary

Bolt.new is a strong AI builder for creating websites, web apps, and prototypes directly in the browser. It is useful when you want to move quickly from idea to running project without local setup.

Use it by starting small, writing prompts with clear users and workflows, checking token usage early, and reviewing generated code before publishing. Bolt can accelerate the first build, but production responsibility still belongs to the person launching the app.