Bolt.new not working? How to fix it and get unstuck
Last reviewed 3 November 2026
The preview is blank, the same error keeps coming back, and each attempt uses more tokens. Before you ask Bolt to try again, restore something that works and find out what you’re dealing with.
Check Bolt’s status page, try the preview in a fresh browser window, then restore the last good version from version history. Use Plan Mode to discuss the problem before changing any code, and keep each request small. If data, sign-in or payments keep breaking, get a developer to look.
First, rule out the simple causes
- Check Bolt’s status page. If there’s an incident, more prompts won’t help.
- Try the preview somewhere else. Reload, then try a private window or another browser with extensions off. If it works there, the problem is your browser and not your app.
- Save a copy. Download the project as a zip file or connect GitHub before you change anything else.
Go back to something that worked
Bolt saves versions automatically. Its version history, under View history, lets you preview, name and restore earlier points, and Bolt recommends it over other restore methods. You can also restore from a point in the chat. Name each version that works as you go, so you can find it again.
Restoring your project and restoring your data aren’t necessarily the same thing. If real customers are using a database, export the rows you care about first, from your database tables.
Stop the fix loop, and the token drain
- Use Plan Mode first. It lets you talk through the problem before Bolt writes any code.
- Describe what happened, not just “fix it”: what you clicked, what you expected, what happened, and the exact error.
- Make one change at a time, and test it before the next one.
- Keep the project’s context small. Bolt’s guides on token efficiency and managing context explain what uses tokens fastest. Large projects cost more per message.
What common problems usually mean
| What you see | Usually points to | Try first |
|---|---|---|
| No preview, or preview not loading | Your browser, or a code error from the last change | Try a clean browser window, then restore the previous version |
| Stuck on thinking or authenticating | A temporary problem, or a request that’s too large | Check the status page, reload, and split the request into smaller steps |
| Error 500 or internal server error | A failing server function or database request | Read the database and server function logs |
| Sign-in not working | Sign-in settings or redirect addresses | Review your authentication settings |
| Works in preview, broken when published | Settings or keys that differ on the live site | Compare the settings, and check the logs while you reproduce the problem |
| Tokens running out quickly | A large project, or repeated attempts at a fix | Stop retrying, restore, and plan before you build |
These are common patterns, not a diagnosis, and Bolt changes often. Bolt’s help centre has the current steps.
Check security before you go further
Bolt offers a project security audit on paid plans and a database security check on all plans. Bolt recommends running a check at least once before you publish, and says that using the button in the Publish menu avoids spending tokens. It’s a good start. Then test the app yourself with our security checklist, since a scan can’t tell you what your app should allow.
When to stop prompting and get help
- The same problem has come back after several attempts.
- Customers’ data, sign-in or payments are involved.
- You’re spending more tokens on repairs than on new features.
- You’re trying to get it into the App Store and it keeps getting rejected.
Your project is still useful. It shows exactly what you want, and developers can work from the code. See how we make AI-built apps ready for real customers.
Questions founders ask
Can I export my code from Bolt?
Yes. You can download a project as a zip file, or manage versions through GitHub. Export early, so you always have your own copy.
Why does Bolt use so many tokens?
Bolt’s guides explain that a project’s context affects what each message costs. Repeated fix attempts on a large project add up quickly, which is another reason to restore and plan first.
Can a developer take over a Bolt project?
Yes. A developer can work on the downloaded code or the GitHub repository in their own tools. We’d start by checking what’s worth keeping.