Bolt.new Problems & Issues
Real user-reported problems, complaints, and limitations for Bolt.new. Based on analysis of 14 signals.
Overall score: 52/100
Issues by Category
Bolt.new tokens burn fast on larger projects
Because the project context is sent with each prompt, token use per request grows with project size. Users report monthly allowances being used up in a small number of prompts on bigger apps. Typical for projects past the prototype stage.
Tokens spent on planning and thinking with no code change
Reviewers on Trustpilot report tokens consumed on plans or processing that never produced the requested change, with no automatic restoration.
No refunds: Bolt subscriptions are non-refundable
The Terms of Service say subscriptions are non-refundable. Users who lost tokens to errors or crashes report difficulty getting restored tokens or money back.
Tokens vanish when you cancel
Allocated and rollover tokens are lost when the billing cycle ends after cancelling. Rollover tokens also expire after two months.
Token reloads only for the highest Pro tier or annual plans
Buying extra tokens is restricted, so people on lower monthly tiers must upgrade instead of topping up.
Error-fix loops waste tokens
Clicking Attempt fix repeatedly can spend tokens without solving the problem, and Bolt's own docs warn against repeating it. Users describe millions of tokens lost chasing one bug, often authentication or setup.
Sessions crash or stall near completion
Trustpilot reviewers describe sessions ending abruptly or failing near the end of a build, losing work and tokens.
Supabase connection and credentials problems
Users report Supabase credentials reverting to the wrong database, RLS rules that expose or hide data, and connection errors after export and re-import.
Netlify publish fails or breaks after forking
Publishing can fail at the Netlify step, and forking a project creates a new Netlify site so the old connection and custom domains are lost.
Project too large to publish (100MB limit)
Publishing fails when project files exceed 100MB, usually due to images and videos stored in the project. Media must move to external storage.
Prototype ceiling: complex apps get brittle
Reviews say Bolt is great for first versions but the AI rewrites large files for small fixes and breaks working features as the app grows.
Slow or unhelpful support, reply to few complaints
Trustpilot shows 78% 1-star ratings (2.0/5 from 217 reviews) and Bolt replying to about 12% of negative reviews. Some users do praise support.
Generated apps ship with weak security by default
AI-generated Supabase apps can have disabled RLS or missing policies, exposing data until fixed.
Setup and npm install failures in new projects
Some users burn tokens just getting a basic project running, with npm install failures a common trigger.
Regret Patterns
Common reasons users regret choosing Bolt.new.
Out of tokens mid-project
Monthly allowance is gone before the app is finished because of fix loops.
Paying for tokens that fixed nothing
Tokens spent on attempts that did not solve the error, with no refund.
Outgrowing the prototype
Changes start breaking working features as the app grows.
Surprise cancellation token loss
Allocated and rollover tokens disappear at the end of the cycle.
Insecure default database setup
RLS missing or wrong, noticed only after launch.
When Bolt.new Breaks Down
Specific scenarios where Bolt.new fails or underperforms.
Apps with many files and large context
Each prompt carries more context, so tokens per request rise.
Authentication and OAuth setup
Common source of long fix loops and token burn.
Projects with large media files
Publishing blocked above 100MB.
Server-rendered frameworks
Bolt hosting needs static HTML, so SSR apps publish as 404 pages until converted.
Forked or duplicated projects
Netlify site and custom domains disconnect.