
Bolt.new Setup: How to Use Bolt
Go from an idea to a published app in 10 minutes. Nothing to install, nothing to configure. This walkthrough covers the whole flow, checked against Bolt's official docs and live pricing in August 2026.
Open Bolt.new FreeQuick Answer: Bolt.new setup
There is nothing to install. Open bolt.new in a desktop browser, sign in with Google, GitHub, or email, type a description of the app you want, and Bolt builds and runs it in the browser. One click on Publish puts it on a free .bolt.host URL. The free plan includes 300K AI tokens a day (1M a month); Pro is $25 a month as of August 20, 2026.
Prerequisites
- A modern desktop browser (Chrome, Firefox, Safari, Edge)
- An internet connection
- A Bolt.new account (free, sign in with Google, GitHub, or email)
- An idea for what you want to build
Zero install required
Go to bolt.new
Open bolt.new in your browser. You get a clean screen with a large prompt box in the center and a Build Now button. That is the entire product surface until you type something.
No download page, no installation wizard, no dependency management. The full development environment, dev server included, runs inside the browser tab.
Sign Up (Free)
Sign in with Google, GitHub, or email. Signing up saves your projects and activates the free tier. What the free plan actually includes, per the live pricing data we track (verified August 20, 2026):
- 300K AI tokens per day, capped at 1M per month
- Public and private projects
- Website hosting on a free .bolt.host address
- Databases included, 10MB file uploads, Bolt branding on published sites
Pro is $25/mo: 10M tokens per month with no daily limit, unused tokens roll over for one month, custom domains, no branding, 100MB uploads. Teams is $30 per member. Full breakdown on our Bolt pricing page.
Token strategy
Describe Your App
Type a detailed description of what you want and press Build Now. The more specific you are, the better the first build. A good prompt:
Build a recipe management app with these features:
- A home page showing recipe cards in a responsive grid
- Each card shows the recipe image, name, prep time, and difficulty
- Clicking a card opens a detail page with ingredients and steps
- A form to add new recipes with image upload
- Search and filter by cuisine type
- Use React with Vite, Tailwind CSS, and React Router
- Store data in localStorage for now
- Modern, clean design with warm colorsCompare that with "Make a recipe app." The short version leaves everything to interpretation, and you will spend more tokens correcting the result than you saved by typing less.
Web app or mobile app?
Watch It Build
Bolt starts generating immediately. You will see four things working at once:
- File tree: on the left, the project structure builds in real time.
- Code editor: in the center. Click any file to read what was written.
- Terminal: at the bottom, dependencies install and the dev server starts automatically.
- Preview: on the right, a live preview you can click around as soon as it loads.
A first build typically lands in one to a few minutes depending on complexity. Bolt handles package installation, bundler configuration, and server startup on its own.
Preview and Test
Interact with the preview like a user would: click buttons, fill forms, navigate between pages. Use the device toggle at the top of the preview to check tablet and mobile layouts before you invest in more features.
Open in a new tab
Get the Vibe Coding Cheat Sheet
Best tool for every use case + pricing + pro tips. One page, zero fluff. Plus weekly updates on new tools.
Refine with Follow-Up Prompts
Your first build will not be perfect, and that is the intended workflow. Iterate with specific follow-ups:
Make the header sticky with a blur backdrop effect.
Add a loading spinner while recipes are being filtered.
Change the color scheme to use indigo instead of blue.Each follow-up has full context of your existing app, and Bolt modifies only the files that need to change. When you want to discuss direction rather than change code, switch to Plan mode: it answers and designs without editing the project, and costs fewer tokens than Build mode.
Publish
When you are happy with the app, press Publish. Bolt hosts the app itself and gives you a live address on a free .bolt.host domain. Publishing is available on the free plan; no Netlify, Vercel, or hosting account is involved.
Publishing takes well under a minute, and the URL is shareable immediately. Remember it is a snapshot: later edits stay in the editor until you publish again.
Custom domains
Share, Export, Keep Building
Your app is live and the code is yours, for any purpose including commercial use. From here you can:
- Export to GitHub: push the project to a repository for version control and further development in other editors.
- Download the source: get a zip of the complete project to run locally or deploy elsewhere.
- Keep iterating: reopen the project anytime and prompt for new features or fixes.
Outgrowing Bolt?
The 3 Settings That Actually Matter
1. Plan mode vs Build mode
The toggle that controls your token burn. Build mode spends tokens on every code update; Plan mode discusses without editing and costs less. Think in Plan, execute in Build. This single habit stretches the free tier further than anything else.
2. Agent selection
Bolt lets you pick the agent that powers your builds. The standard agent handles most work; save the heavier max option for genuinely complex tasks, because it costs more tokens for the same prompt. Matching agent to task is free money.
3. Connectors and context
Connectors add external services into Bolt's context, and everything in context costs tokens on every prompt. Bolt's own efficiency docs say it plainly: turn on connectors only when you need them, remove unused files, and clear the context when Bolt seems confused about the state of your project.
Troubleshooting: Where Builds Get Stuck
The preview is blank or shows an error page
Ran out of tokens in the middle of a build
Bolt keeps rewriting things you did not ask it to touch
Each follow-up prompt burns more tokens than expected
Published the app but the live URL shows an old version
The app works in preview but breaks after publishing
What to Build First
Personal Landing Page
Tell Bolt: "Build a personal portfolio site with a hero section, about me, project gallery, and contact form. Use a modern gradient design." Published in under 5 minutes.
Expense Tracker App
Prompt: "Build an expense tracker with categories, date filtering, a pie chart for spending breakdown, and local storage persistence." Bolt handles the full app and chart library setup.
AI-Powered Quiz App
Prompt: "Create a trivia quiz app that generates questions using an AI API, tracks scores, shows a leaderboard, and has timed rounds." Test Bolt's ability to integrate external APIs.
Bolt.new Tips from Power Users
Front-load your prompt
The initial prompt matters most. Include the tech stack, features, pages, and design preferences upfront. It is much easier to get a good first build than to retrofit features afterward.
Plan mode for thinking, Build mode for changes
Plan mode discusses your project without editing it and uses fewer tokens. Work out the approach there, then switch to Build mode to execute. Questions asked in Build mode are the most expensive way to think.
Check the terminal for errors
Bolt shows a terminal panel with build output. If the preview looks broken, check the terminal for error messages. Paste the error back into the chat and Bolt will fix it.
Export to GitHub for more control
Once your app reaches a certain complexity, export the code to a GitHub repo. From there, you can continue in Cursor, Claude Code, or any other editor with full version control. You own the code.
Name your stack explicitly
Mention frameworks in the prompt: "Use React with Vite and Tailwind CSS" or "Use Next.js with the App Router." Bolt builds JavaScript-based stacks, and being explicit avoids a framework you did not want.
Test on mobile early
The preview has a device toggle for mobile and tablet views. Test responsive layouts early. It is easier to prompt for mobile fixes while the context is fresh.
When to Use Bolt vs an IDE
| Use Bolt When | Use an IDE When |
|---|---|
| Prototyping a new idea quickly | Working on an existing large codebase |
| Building a landing page or simple app | Building something with complex backend logic |
| You want zero setup overhead | You need custom dev tooling and debugging |
| Sharing a quick demo or proof-of-concept | Working with a team using git branching |
| You are a non-developer exploring ideas | You need fine-grained version control |
Ready to build with Bolt?
For the fuller picture, read our Bolt review or put it head to head with Lovable in the live duel.
Built something? See what it's worth or submit it to our showcase.
Learn More About Bolt
Bolt.new Setup FAQ
Is Bolt.new free to use?
Do I need to install anything to use Bolt.new?
How do I set up Bolt.new?
What is the difference between Plan mode and Build mode?
How do I publish an app from Bolt.new?
What can I actually build with Bolt.new?
What happens when I run out of tokens?
Can I export my code out of Bolt.new?
Is Bolt.new better than Lovable?
Stuck at 80 percent? We take over half-finished builds.