// troubleshooting guide · bolt.new
Bolt.new Site Shows 404 After Publishing
- Status
- Fixed in latest version
- platforms:
- Web
- updated:
- November 15, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · bolt-new/site-shows-404-after-publish3 FIXES
// quick answer
Static hosting needs HTML output and an SPA redirect rule. Ask Bolt to build static or prerendered output and add a redirect so refreshing non-home routes works.
Most likely fix: Build as static HTML
How to fix it
// try these in order, the most common fix is first
FIX 1Build as static HTML
- 01Ask Bolt to use SPA mode or prerendering
- 02Publish again
Did this fix it?FIX 2Add a redirect rule
- 01Ask Bolt to add /* /index.html 200 in a _redirects file (or netlify.toml)
- 02Publish, then Update
- 03Refresh a non-home page to confirm
Did this fix it?FIX 3Build output directory not found
- 01Paste the error in chat and ask Bolt to fix the build
- 02Publish again; contact support if it persists
Did this fix it?
Symptoms
Home page works but other routes 404, or the site shows only 404 pages.
Why it happens
- C-01Server-rendered framework with no HTML output
- C-02Single-page app routes missing a redirect rule
- C-03No build output directory
// this guide also covers
- bolt.new 404 after publish
- bolt.new page not found refresh
- bolt.new no build output directory
Still not working?
If Bolt.new keeps failing, you're not alone. See every Bolt.new problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Lovable Stuck in an Error Loop (Lovable)
Replit Workspace Not Loading (Replit)
Cursor High Load Error (ERROR_RESOURCE_EXHAUSTED) (Cursor)
Bubble Workload Units Running Out Too Fast (Bubble)
GitHub Copilot Proxy and Certificate Errors (GitHub Copilot)