I ran out of Bolt tokens and my app is not finished. What now?
Short answer: First, stop prompting. Bolt, an AI tool that builds web and mobile apps from plain-language prompts, counts tokens (small pieces of text it reads and writes), and most of the burn comes from re-reading your whole project on every message. You have four moves: wait for the reset, edit the code yourself for free in Code view, buy more tokens or move up a plan, or export the project and hand the last 30 percent to a developer. If you are stuck in a loop of failed fixes, more tokens will only feed the loop, so export and get a person to look.
Your Bolt budget is gone, the app is maybe 70 percent done, and you need to know whether to wait, pay more, or stop and hand it off.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
What actually happened to your tokens
Bolt's help center says tokens are how Bolt measures the work an agent does. It spends them when it reads your prompt, reads your project files, plans, and writes code. Here is the part that surprises people: most of the usage comes from Bolt reading and syncing your project files, so a bigger project costs more per message. Your tenth feature costs more tokens than your first, even if the prompt is the same length.
That is why a budget that felt huge on day one disappears near the end. The app got bigger, and every message got more expensive.
As of November 2026, Bolt's pricing page lists these plans. Check the page for current numbers before you decide anything.
| Plan | Price | Tokens |
|---|---|---|
| Free | $0 | 300K a day, 1M a month, no rollover |
| Pro | $25 a month (monthly billing) | No daily limit, starts at 10M a month, unused tokens roll over |
| Teams | $30 a month per member | Pro features plus team controls, tokens not shared between members |
Your four options right now
1. Wait for the reset
On the Free plan, the daily 300K limit resets every day and does not carry over. The monthly 1M resets on the 1st. On a paid plan, tokens reset on your renewal date, at the same time of day your billing period renews, not at midnight. In Bolt, open the Subscription page, then Billing and usage, and look for the line that says when your next refill happens.
One catch from the help center: if you cancel a paid plan mid-month after already using more than 1M tokens, you do not get the Free allowance right away. You wait for the next month.
2. Edit the code yourself, which costs no tokens
Bolt's help center says that editing files in Code view does not use tokens, and that if you hit the daily limit you can still make direct edits for free. Two more things cost nothing: Version history (an undo button that restores an earlier state of the project) and the Publish button. Use them instead of asking Bolt to do the same job by prompt.
If you cannot read code, you can still use this for small things, such as changing a line of text, a color value or a price you typed in.
3. Buy more tokens or change plan
Bolt says the most cost-effective way to get more tokens is to upgrade to a higher plan. Token reloads, a one-off purchase, are only offered if you are on the highest individual monthly Pro plan or any annual Pro plan. Reloaded tokens do not expire. The price per reload depends on your plan, and you see it on the Billing and usage page when you click Reload tokens. Check that screen for your own price.
4. Export and get a person to finish it
This is the right move when the budget is spent and the remaining work is hard, not just long. More on how to decide below.
Keep paying Bolt, or pay a person?
Here is a worked example with made-up numbers, so you can see the shape of the decision. Say your app needs three things: a working login, a payment step and an admin screen. You are on Pro at $25 a month. You spend two extra months of plan fees, so $50, plus one reload you decide to buy. That looks cheap, and when the work is plain it is.
Now say the login fails on a real phone, Bolt's automatic fix tries four times, and each try costs tokens and makes something else break. Your real cost is not the $25. It is your own evenings, and a project that gets bigger and more fragile with every attempt. At that point a fixed-price finish by a developer can be cheaper than the loop. For reference, Blur Studio fixes and finishes start around $1,500, but get two or three quotes from anyone you consider, and ask what is included.
My rule of thumb:
- Keep going with Bolt if the remaining work is more of the same kind of thing (new pages, text changes, extra fields) and the last few prompts worked on the first try.
- Hand it off if the same error has survived three attempts, if the bug is about logins, payments or data, or if you are about to launch to real customers.
My longer guide on whether AI can finish a half-built app or you need a developer covers this decision in more detail, and how much vibe coding really costs shows where the money goes. (Vibe coding means building software by describing it to an AI.)
The stop rule for the retry loop
Bolt's own token guide warns against clicking Attempt fix over and over. Each attempt uses tokens, and a second click sometimes works, but a fifth click almost never does. Here is the rule I would follow:
- Allow two automatic fix attempts on any one error.
- After the second, stop. Do not prompt "try again" or "fix it properly."
- Switch to Plan mode. Bolt says Plan mode uses fewer tokens because it talks through the problem without writing code. Ask it to explain what it thinks is wrong, in plain words.
- Ask Bolt to add detailed logging around the broken area. Bolt's help center suggests this for error loops, because the next error message then carries real information.
- If you now have a clear cause, make one narrow fix. If you still do not, export and get help.
Also use Version history to roll back a change that made things worse. Restoring does not cost tokens.
If you keep building, make tokens last
These come straight from Bolt's help center page on token efficiency:
- Plan first. Use Plan mode to decide, then Build mode to write.
- Pick the right agent. The Standard agent suits average tasks. The Max agent uses more tokens for complex ones. Using Max for a simple change wastes tokens.
- Be specific. Name the file or function instead of asking about the whole app.
- Add features one at a time and test after each.
- Turn on connectors (links to outside tools) only when you need them, since they add to what Bolt reads.
- Clear context and trim the project. Delete unused files and split large ones.
Export and handoff checklist
Do this before you contact anyone, and do it even if you plan to keep using Bolt. It protects you. (More on getting code out of any builder in how to export code from an AI app builder.)
- Download the project. On a desktop, click the project title, then Download. You get a zip of your files. This does not work on a phone.
- Connect GitHub. GitHub is a service that stores code with a full history of changes. Bolt's GitHub integration backs up your code outside Bolt and keeps it synced. Most developers want a GitHub link, not a zip.
- Export your data. If your app uses Bolt's built-in database, Bolt's help center says you can export row data as CSV or JSON from the database Tables view. If you connected your own Supabase (a database and login service), your data already lives there. Bolt also lets Pro and Teams plans claim a Bolt database into your own Supabase account.
- List your keys. Write down every outside service the app uses (payments, email, maps) and where each key is stored. Do not paste keys into emails.
- Write a one-page brief. What the app does, what works, what is broken, the exact error messages, and a screenshot of each broken screen.
- Note your hosting. Where is the live version? Which domain? Who owns that account? See hiring a Bolt developer for what a developer will ask.
What to ask a developer, and red flags
- Ask for a fixed price for a written list of what is finished, not an open hourly meter.
- Ask who owns the code and accounts when they are done. The answer must be you.
- Ask what they will test, and on which devices.
- Red flag: they want to rebuild everything before they have opened the code.
- Red flag: they ask for your Bolt login instead of a GitHub invite.
If you are weighing other tools instead, see Bolt.new alternatives. Switching tools resets the clock but not the underlying problem.
How I'd approach this
I would do three things, in this order. First, stop spending tokens today, and download the project and connect GitHub, so you hold a copy no matter what happens next. Second, write down the list of what is left, and sort it into plain work and risky work. Plain work (text, layout, extra fields) you can finish yourself with Plan mode and careful prompts. Risky work (logins, payments, anything touching customer data) I would not leave to a loop of automatic fixes.
Third, put a price on the risky part. If the quote to finish it is a small multiple of what you have already spent on tokens, pay it. You are buying back your time and a launch date. If a developer cannot tell you what is wrong after reading the code for an hour, that is also useful to know before you pay for a month of more tokens.
Questions people ask
How many tokens does Bolt give on the Free plan?
As of November 2026, Bolt's pricing page lists 1 million tokens a month with a daily limit of 300,000 on the Free plan. Free tokens do not roll over. If you hit the daily limit, direct edits in Code view are still free. Check Bolt's pricing page for current numbers.
Do unused Bolt tokens roll over?
On paid plans, yes. Bolt's help center says unused tokens stay valid for two months from the start of the billing cycle in which you received them, as long as your subscription is active. They are used oldest first. Free plan tokens do not roll over.
Can I buy more Bolt tokens without changing my plan?
Only on certain plans. Bolt says reloads are available if you are on the highest individual monthly Pro plan or any annual Pro plan, and reloaded tokens do not expire. Bolt also says upgrading to a higher plan is the most cost-effective way to get more tokens. See the vibe coding cost guide for how costs add up.
Why did one small change use so many tokens?
Bolt says most usage comes from reading and syncing your project files, so larger projects use more tokens per message. Using the Max agent for a simple task, asking for changes across the whole app, and repeated automatic fix attempts all add to it.
Can I keep working in Bolt after I hit the limit?
Not by prompting. You can still edit code in Code view, use Version history to roll back, and click Publish, none of which use tokens. Prompts need tokens, so you wait for a reset, reload, or upgrade.
When should I stop and hire a developer instead?
When the same error survives two or three fix attempts, when the problem involves logins, payments or customer data, or when you are close to launch. My guide to finishing a half-built app walks through the decision.
More in this topic: Problem solving: AI-built and no-code apps (26 guides) →