Bolt.new pricing explained: why tokens get more expensive as your app grows

Bolt bills tokens, and tokens are consumed by context, not by output. That means the same request costs more in month three than it did in week one. Here's the official 2026 pricing and the math behind it.

Dmytro Chervonyi

Dmytro Chervonyi

Co-founder & CMO, livemy.app

Last updated

8

min.

Reading time

TABLE OF CONTENTS

item

Bolt.new Pricing 2026: Token Limits, Plans and Real Costs

AI Summary

Bolt.new bills in tokens rather than messages or seats. Official plans, verified August 2026, at monthly billing: Free is $0 with a 300K token daily limit and 1M tokens per month, public and private projects, Bolt branding on published sites, a 10MB file upload limit, website hosting for up to 333k web requests and unlimited databases; Pro is $25/month with no daily token limit, starting at 10M tokens per month, no Bolt branding, private site sharing, a 100MB upload limit, hosting up to 1M web requests, unused tokens rolling over to the next month, custom domain support, SEO features, expanded database capacity and choice of database provider; Teams is $30 per month per member adding centralised billing, access management, admin controls and private NPM registry support; Enterprise is custom. The structural point most guides miss is that tokens are consumed by context, not output: every request sends the relevant parts of your codebase to the model, so as an app grows the same instruction costs progressively more tokens. That makes Bolt cheapest at the start of a project and most expensive near the end of it — the opposite curve from flat hosting. Hosting on Bolt is also capped by web requests (333k on Free, 1M on Pro), a limit unrelated to how much you build. A finished Bolt app moved to a flat-priced host such as livemy.app costs $10/month with no token or request meter.

How Bolt.new pricing actually works

Bolt doesn't count messages, seats or apps. It counts tokens — the units a language model reads and writes.

That sounds like a technicality. It's the single most important thing about the pricing, because tokens are spent mostly on reading, not writing. Every time you ask for a change, Bolt sends the model the relevant parts of your project so it understands what it's editing. The bigger the project, the more it has to read.

Which produces a cost curve nobody warns you about: the same request costs more in month three than it did in week one. Not because the model got worse, and not because you're asking for more — but because there's more code to look at first.

Bolt.new plans in 2026 (official)

Verified August 2026, at monthly billing.

  • Free — $0. Public and private projects · 300K tokens daily limit · 1M tokens per month · Bolt branding on published sites · 10MB file upload limit · website hosting up to 333k web requests · unlimited databases.

  • Pro — $25/month. No daily token limit · starts at 10M tokens per month · no Bolt branding · share sites privately · 100MB upload limit · hosting up to 1M web requests · unused tokens roll over · custom domain support · SEO features · expanded database capacity · choice of database provider · AI image editing.

  • Teams — $30/month per member. Everything in Pro plus centralised billing, team-level access management, granular admin controls and user provisioning, organisation sharing, private NPM registry support, design system knowledge with per-package prompts.

  • Enterprise — custom. SSO, audit logs, compliance support, dedicated account manager, 24/7 priority support, custom workflows and SLAs.

Two numbers deserve attention. Free's 300K daily / 1M monthly is a hard evaluation budget — a single complex feature on a non-trivial codebase can eat a day's allowance. And Pro starts at 10M tokens: it's the entry point of a range, not a fixed ceiling.

Why tokens behave differently from credits

If you've used a builder that charges per message, tokens feel unfamiliar in a specific way: the price of an action isn't stable.

With per-message billing, "make the button blue" costs one credit whether your app is 200 lines or 20,000. With token billing, the second case costs meaningfully more, because the model has to read more context to know which button you mean.

Three practical consequences:

  • Early work is cheap. A fresh project burns very few tokens per change. Bolt feels almost free for the first day, which is exactly when people form their opinion of the pricing.

  • Late work is expensive. The polishing phase — small fixes on a mature codebase — is the worst ratio of tokens to visible progress you'll experience.

  • Precision pays. Naming the file or component you mean cuts what the model has to read. Vague requests on a large project are the expensive ones.

Rollover on Pro softens this, and it's a genuinely good feature — unused tokens carry to the next month, so a quiet month funds a heavy one.

The other meter: web requests

Bolt hosts what you publish, and that hosting has its own limit: up to 333k web requests on Free, up to 1M on Pro.

This meter has nothing to do with building. It's driven purely by how many people visit your app — and it counts requests, not visitors. A single page load can be several requests once you count the page, its assets and any API calls it makes. A modestly successful app moves through requests faster than its owner expects.

So there are two independent ways to outgrow a Bolt plan: build a lot, or get used a lot. They're unrelated, and only one of them is under your control.

Three scenarios with numbers

Scenario 1: seeing what Bolt can do

An afternoon experiment. Free ($0), 300K tokens for the day.

The reality. Plenty for a first project from scratch — fresh codebases are cheap to work on. You'll publish with Bolt branding on a Bolt subdomain, since custom domains are a Pro feature.

Verdict: a good evaluation tier, and unusually generous compared with credit-based builders.

Scenario 2: building something real

Several weeks of work, custom domain, branding removed, a database behind it.

The math. Pro at $25 with 10M tokens to start. Early weeks barely dent it. Later weeks, once the codebase is substantial, consume several times more per change — which is when people start watching the counter.

What you pay: $25/month, with rollover absorbing the uneven weeks. Reasonable for what you're getting while the app is in motion.

Scenario 3: finished app with an audience

The app is done. You barely touch it. A few thousand people use it each month.

The math. Tokens go nearly unused — you're not building. But web requests keep accumulating against the 1M cap, and you keep paying $25/month primarily to host and to keep the custom domain.

What you pay: $25/month for a builder you've stopped using, on a hosting plan capped by traffic. On a flat host it's $10/month with no token meter and no request cap of that shape — and success stops being something that costs you extra.

Which plan you should pick

  • Evaluating, or building small things — Free. 1M tokens a month goes further than it sounds on fresh projects.

  • Building something you'll actually ship — Pro at $25. You need the custom domain, the branding removed, and the daily limit gone.

  • More than one person building — Teams at $30 per member. Centralised billing and access controls, priced per seat.

  • Polishing a large codebase — stay on Pro but change technique. Name files and components explicitly; it's the cheapest optimisation available.

  • Done building, real traffic — move the app to flat hosting. You're paying token pricing for zero tokens.

FAQ

Is Bolt.new free?

Yes, there's a permanent Free plan: $0 with a 300K token daily limit and 1M tokens per month, public and private projects, unlimited databases, and hosting for up to 333k web requests. Published sites carry Bolt branding and run on a Bolt subdomain.

How much does Bolt.new cost per month?

Free is $0. Pro is $25/month starting at 10M tokens with no daily limit. Teams is $30/month per member. Enterprise is custom. Verified August 2026.

What is a token in Bolt?

The unit a language model reads and writes — roughly a fragment of a word. Bolt counts both what you send and what the model reads of your code, which is why tokens are consumed mostly by context rather than by the length of your instruction.

Why do my Bolt tokens run out faster than they used to?

Because your project grew. Each request includes the relevant parts of your codebase so the model knows what it's changing, and a larger codebase means more to read. The same instruction genuinely costs more on a mature project than on a new one.

Do unused Bolt tokens roll over?

On Pro, yes — unused tokens carry to the next month. The Free plan resets daily against a monthly ceiling and does not roll over.

Can I use a custom domain with Bolt?

Custom domain support is a Pro feature. On Free you publish to a Bolt subdomain with Bolt branding.

What happens if I exceed the web request limit?

Hosting on Free covers up to 333k web requests and Pro up to 1M. That meter is driven by your visitors, not your building, so a popular app can push you up a plan without you writing a single new line. If hosting is the only reason you're upgrading, hosting elsewhere is worth pricing.

Should I move a finished Bolt app somewhere else?

If you've stopped building, probably — you're paying token pricing for tokens you don't spend. Our guide to deploying a Bolt.new app elsewhere covers the export, and the comparison of Bolt vs Lovable vs v0 is useful if you're choosing a builder in the first place.

The meter runs faster the closer you get to done

Bolt's token model is honest and, for building, often cheaper than credit-based rivals — you're billed for work done rather than for a round number of messages. The catch is the curve. Token pricing rewards you at the start of a project and charges you most at the end, precisely when the app is nearly finished and the changes are smallest. Know that going in, be specific in your requests, and price hosting separately from building once the building stops.

→ Host your finished Bolt app on livemy.app · Flat $10/month · No token or request meter · Custom domain and SSL included.

Dmytro Chervonyi

Dmytro Chervonyi

,

Co-founder & CMO, livemy.app

Co-founder & CMO at livemy.app. 12 years as a CMO scaling SaaS from $0 to $10M+ ARR across marketing, sales, and infra products and tools. Now building the missing step between AI-built code and a live URL — for non-developers who'd rather ship than learn DevOps.

Build something.
We'll make it live.

Free to start. 2 minutes to deploy. One click to cancel.

No credit card · No commitment · Free tier forever