Bolt.new Netlify Deployment Problems: What to Check

Netlify can be a good deployment target for Bolt.new projects, but a working preview does not guarantee a working Netlify deployment. The most common issues are build settings, missing environment variables, redirects, routes, Supabase config and runtime errors that appear only on the live URL.

Check the build command and output directory

If Netlify cannot build the app, confirm the command and publish directory match the generated framework. A wrong command can fail immediately, while a wrong output directory can build successfully but publish the wrong files.

If you want the project checked end to end, see Bolt.new app repair.

If Netlify, the app build and connected services all look plausible, narrow the deployment fault before making several changes at once.

Check environment variables in Netlify

Netlify has its own environment variable settings. Supabase URL, anon key, API URLs and other values must exist there too. A project can work in Bolt.new preview and fail on Netlify because production variables were never added.

Check redirects for client-side routing

If the home page works but direct links return 404, Netlify may need redirect rules for a single-page app. Do not rewrite the whole router until you have checked hosting redirects.

Check blank screens and runtime errors

A successful Netlify deploy can still show a blank screen. Open the live URL console. Missing assets, failed imports, undefined environment values and route errors often show up immediately.

Check Supabase and auth domains

If the app uses Supabase auth, add the Netlify URL and final custom domain to the relevant redirect settings. If this is the main issue, the Bolt.new auth guide gives the focused checks.

When the deployment is urgent

If a client launch or live workflow is blocked, collect the Netlify deploy log, live URL, preview URL and last change. For time-sensitive outages, use emergency website fixes.

Checklist

• Check Netlify build command and publish directory.
• Check Node version if the build requires it.
• Add production environment variables.
• Check redirects for client-side routes.
• Inspect live console and network errors.
• Check Supabase and auth domain settings.

Conclusion

Most Bolt.new Netlify deployment problems come from the gap between preview and production. Diagnose that gap first, then repair the specific setting or code path that fails.

Netlify checks before changing code

Before editing the app, check Netlify settings. Confirm the deploy is using the expected branch, build command, publish directory and environment variables. Check whether the failed deploy used a cached build or a different Node version from the one Bolt.new expected.

If the app uses client-side routing, test a direct visit to an internal route. A 404 on refresh often points to missing redirect rules rather than broken React routes. If the app loads but connected features fail, check environment variables and Supabase domains next.

What to send for Netlify repair

Send the deploy log, build settings, live URL, preview URL, any redirect file, first console error and a note about which routes or connected services fail live.