Bolt.new Not Working? Common Errors & Fixes

Bolt spends tokens on every prompt and on its full project context, so big projects and fix loops drain allowances. Use Plan mode, specific prompts, Version History and clear context.

Bolt error loops come from repeating automatic fixes. Stop clicking Attempt fix, switch to Plan mode, ask for logging and error handling, or revert in Version History.

When Bolt tokens run out, free users can still edit in Code view, paid users can upgrade or reload. Free tokens reset daily and monthly; paid tokens on renewal.

This error means project files exceed 100MB, usually from images or videos. Delete unused media, then move the rest to external storage and use URLs.

If Bolt fails to publish to Netlify, run the build, download the project and deploy it manually via Netlify drag and drop. Check status.bolt.new first.

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.

Check status.bolt.new, then confirm the Supabase URL and keys match the intended project and fix RLS. Re-add environment secrets on the host if you exported.

Reauthorize the GitHub app from the Bolt homepage. If one GitHub account is linked to two Bolt accounts, remove the link from the old account first.

API calls from server functions fail when secrets are missing or CORS headers are wrong. Add secrets via the database icon and check Access-Control headers.

Open the sidebar, click your account name, Subscription, then Cancel subscription under Billing details. It takes effect next billing period; subscriptions are non-refundable per the Terms.