Bolt.new deployment guide · reviewed September 25, 2026
Bolt.new app won’t deploy? Check which step failed
A broken preview, a failed Bolt publish and a failed build on another host are different problems. Identify where the failure happens first, then follow the matching checks before changing providers.
Step 1
The preview is blank
This can be a browser or WebContainer issue before the app reaches hosting. Try a Chromium-based browser and temporarily check whether an extension or VPN is blocking Bolt.
Step 2
Bolt Publish fails
Read the error shown after Publish. If the generated .bolt.host address works but your custom domain does not, check the domain status and DNS settings before rebuilding.
Step 3
An external host build fails
Use that provider’s build log. The first specific error usually points to a missing dependency, environment setting or build configuration.
Check an external-host build log
Paste a redacted log to check for common build failures. This browser-based checker does not connect to Bolt or your hosting account, and it does not upload or save the text.
Only common build errors are recognized. This is a first check, not a complete code review.
0 / 16,000Analysis runs in this browser and the text is not saved or uploaded. Remove API keys, passwords, tokens and private URLs before pasting logs.
How this checker works
Find the first useful clue.
- It looks for common build failures such as missing packages, environment settings, TypeScript errors and output folders.
- It runs on this page. No AI service or hosting account is connected.
- It does not change your project. Review the suggested checks and confirm them in your code and host settings.
Where are you deploying?
Publishing inside Bolt
Bolt’s built-in hosting publishes a project to a .bolt.host address. Bolt’s help center says all users can publish there; custom domains are available to paid users. If the generated address works but your custom domain does not, check the domain status and DNS records before rebuilding the app.
Deploying to Vercel, Netlify or another provider
Treat the external deployment as its own project. Confirm that the host sees the right repository and project folder, uses the build command declared by the app, and has the required environment variables. A Vite frontend can be deployed to Vercel, but server features and connected data services still need a compatible setup.
The site loads, but login or saved data fails
That points to a production service or configuration check, not necessarily a failed frontend build. Verify the production database, authentication callback URLs and environment settings. A hosting change does not automatically move the Bolt database. Bolt warns that replacing a database connection can cause data loss, so make a backup and follow its migration instructions first.
Bolt database connection and migration guidanceShould you move a Bolt app to another host?
Keep it on Bolt when…
- the current app publishes successfully and Bolt’s built-in services fit its needs;
- you want to manage hosting, domains and the app’s database in the Bolt workflow;
- the available domain and plan terms work for your project.
Compare external hosts when…
- you need a particular runtime, provider account or deployment workflow;
- your app already uses services outside Bolt and you want to manage them together;
- you have checked the code, database, secrets, commercial terms and full cost of moving.
If you decide to move, first sync or back up the project, deploy a copy, and verify its pages, sign-in, data writes and custom domain before switching visitors to it.
Related launch help
Official references
Provider information reviewed September 25, 2026. Percent to Prompts is independent and does not currently earn commission from the providers mentioned.