By Partly fixable yourself. Settings and build fixes, one to two hours.
- How serious
- Medium
- Fix it yourself?
- Partly, some steps need a developer
- Typical cost
- €99–$990 for a single fix (prices)
- Top rated for Bolt
- Afterbuild Labs · 10.0/10
What you see. You clicked Publish in Bolt with Netlify as the host, and the deploy fails or never shows a working site.
Why it happens
Bolt builds your project inside the browser and hands the output folder to Netlify. Several things can break that handoff. Bolt's help lists a project over 100MB, usually media files, and the error Could not find a build output directory to publish, which means the build did not produce the dist or build folder Bolt expected. The Hosting Provider dropdown also only appears while the project is unpublished and your Netlify account is connected.
On the Netlify side, the usual failures are warnings treated as errors because Netlify sets CI=true, a file name whose case differs from the import, and peer dependency conflicts during install. Netlify also cannot host your database or server code, so an app that relies on a backend inside Bolt will build but then fail at runtime. Netlify's own advice is to make sure the build works before blaming the host.
Fix it yourself
- In Bolt, click the gear icon, then All project settings → Applications and confirm Netlify is connected. Then under Domains & Hosting set Hosting Provider to Netlify.
- Download the project and check its size. Remove unused images and video or move them to external storage. Bolt caps publishes at 100MB.
- If the error names a missing build output directory, ask Bolt in chat to fix how the project builds, then click Publish again.
- In Netlify, open the deploy log and find the first red line. For warnings failing the build, set the build command to
CI='' npm run build. For peer dependency errors, add anNPM_FLAGSvariable with--legacy-peer-deps. - Check the publish directory in Project configuration → Build settings. For Vite projects it is
dist. - As a fallback, run the build, click Download, and drag the output folder onto Netlify's manual deploy page.
When to get an engineer
Hire when the build passes but the live site cannot reach its backend, when your app stores data or secrets that need a server, or when the log shows errors inside the code rather than the settings. Send the deploy log, the project download and your Netlify site name. A single fix is €99–$990 and takes about 2 days. Moving the backend to a proper host is a bigger job in the $300–$25,000 band. See our Bolt guide.
Top-rated companies for Bolt apps
Ranked by our score: published prices, scope of work, AI tools named, timing and a low-risk first step. How we score.
- 1Afterbuild Labs10.0/10Best for: A check before launchFree first step · from $49
- 2Redlab10.0/10Best for: A full rescue by one team that keeps buildingFree first step · from $490
- 3Vibe Code Rescue (Lev Arakelyan)9.0/10Best for: A one-off check and a cleanupFrom $299
Check these
The code lives in a Git repository you own
Connect GitHub or export the project. If the builder account is lost, the product should not be.
Secrets live in the host's environment settings
Keys belong in environment variables on the server, not in the repository or in front-end code.
Dependencies are current and audited
Run npm audit. Critical advisories in packages you ship should be fixed before launch.
No secret keys reach the browser
Open your live app, then DevTools, Sources, and search the loaded JavaScript for sb_secret_, sk_live_, sk-proj- and sk-ant-. Older Supabase keys are long tokens starting with eyJ: decode the middle part of each on your own machine, and if it contains "role":"service_role", your secret key is public. A publishable or anon key in the browser is expected.
Questions
Should I host on Bolt or Netlify?
Bolt's help says Netlify cannot host databases or traditional backends, so projects that need them should stay on Bolt hosting. A front end with a Supabase backend works on either.
I forked the project and lost the Netlify link. Why?
Bolt says forking or duplicating drops the Netlify connection. Reconnect it, which creates a new Netlify site, and repoint any custom domain.
Sources: Bolt: Netlify for hosting; Bolt: Publishing issues; Netlify: Build troubleshooting tips; Netlify: Vite on Netlify.