Why More v0 Seats Do Not Mean a Shared Budget
v0 Plus costs $30 per seat, but each seat's $30 monthly credits stay individual. Use this worksheet to plan uneven team usage and shared top-ups.

v0 Plus costs $30 per user per month and includes $30 in monthly credits for that user. Business costs $100 per user and includes the same $30 per-user allowance. A team can share purchased credits, but one member cannot spend another member’s unused monthly allowance. If one person does most of the building, adding a quiet seat does not give the busy person another $30 to use. These are the current v0 plan prices and credit rules, read on November 16, 2026.
The useful way to budget is to write down each person’s likely v0 usage, subtract that person’s available credits, and total the uncovered amounts. The worksheet below uses an illustrative two-person team. It does not predict a bill or assume that every prompt costs the same.
What each seat includes
v0’s pricing page lists Free, Plus, Business and Enterprise. Its pricing documentation also describes Premium, but says that plan is being sunsetted and is unavailable to new users. Prices below are US dollars before applicable taxes. The credit column describes included v0 generation credit, not cash returned against the subscription fee.
| Plan | Published subscription price | Included credits | The decision it addresses |
|---|---|---|---|
| Free | $0 | Current new-user offer: $5 once; existing Free users keep $5 monthly | Explore within a seven-message daily limit; check your own offer in Billing |
| Plus | $30 per user per month | $30 monthly per user, plus $2 in daily login credits when eligible | Collaboration and access to all models |
| Business | $100 per user per month | $30 monthly per user, plus $2 in daily login credits when eligible | Plus features with training opt-out by default |
| Enterprise | Custom quote | Custom | Advanced controls such as SAML SSO and role-based access |
The Free offer deserves a check before you build a spreadsheet. The docs distinguish $5 one-time credits for new signups under the current offer from a $5 monthly allowance retained by existing Free users. The pricing page displays the current signup offer, and the Billing page shows which allowance applies to your account. Free also has a seven-message daily limit. Neither a new user’s one-time grant nor the daily message limit should be entered as a recurring paid-seat allowance.
Existing Premium subscribers have a different situation: the documentation lists $20 a month with $20 of included monthly credits, but says the plan is no longer offered to new users. Do not plan a new team around a Premium signup. If you already have it, check your actual account and migration terms before comparing it with Plus.
Business does not buy a larger monthly generation allowance than Plus: both list $30 per paid seat. Its higher subscription price pays for different account features, including training opt-out by default. Enterprise pricing and included credits are custom, so there is no honest public per-seat calculation for it. The plan table is a starting point; the relevant question for a paid team is how many seats need access and how much each will generate.
Individual credits are not the shared pool
The v0 pricing docs separate two balances on Plus, Business and Enterprise. Included monthly credits remain individual to each user. Purchased Shared Credit Pool credits can be used by the team, after a person’s individual monthly credits are exhausted. The pricing page also describes additional purchased credits as shared across the team. It does not say that buying another seat transfers that seat’s included monthly credits to a busy colleague.
This distinction matters when work is uneven. A manager may see two Plus subscriptions and $60 in monthly included credits, then assume either user can consume $60. The documentation describes two individual $30 allowances instead. If the first user needs $60 and the second needs $5 during a fresh billing period, the first is $30 over their own allowance while the second leaves $25 of theirs unused. You cannot erase the first user’s gap by subtracting the second user’s unused balance. Purchased shared credit may cover it, subject to the team’s actual balance and billing settings.
Credits also have different clocks. v0’s credit rules say unused monthly credits can roll into the next billing cycle but expire after 65 days. The $2 daily login credit for eligible Premium, Plus and Business users appears when they first use v0 that day in UTC; unused daily credit expires at 00:00 UTC and does not accumulate. Purchased credits expire one year after purchase. They remain in the balance when a subscription expires, but require an active paid plan to use. Check the expiration dates in Billing rather than treating all balances as a single permanent pool.
Model an uneven two-person month
The following is an illustrative planning scenario, not an observed v0 invoice. Suppose two Plus users start the period without rollover credits or a purchased pool. After accounting for any daily credits actually earned and applied, their net v0 generation usage is $60 for the frequent builder and $5 for the occasional reviewer. Those $60 and $5 are assumed usage amounts, not fixed prompt counts or claims about a typical team.
| Person | Plus seat price | Individual monthly allowance | Assumed net usage | Difference against own allowance |
|---|---|---|---|---|
| Frequent builder | $30 | $30 | $60 | $30 uncovered |
| Occasional reviewer | $30 | $30 | $5 | $25 unused |
| Team totals | $60 | $60 in separate allowances | $65 | $30 uncovered for the builder |
The arithmetic is per person: max(0, $60 - $30) = $30 for the builder; max(0, $5 - $30) = $0 for the reviewer. Their uncovered usage totals $30. The reviewer’s $25 left over is still theirs, subject to the monthly rollover and expiry rule. Adding $60 and $5 first, then subtracting a pooled $60, would produce a misleading $5 gap because the monthly allowances are individual.
If the team purchased and consumed exactly $30 of shared credits for this assumed gap, the planning cash outlay would be $60 for two Plus seats plus $30 for those credits = $90, before taxes. That is a worked example, not a statement about minimum purchase size, credit application order, or an actual bill. Daily credits, old rollover balances, purchased credits already on hand and model selection could change the amount you need to buy. The docs say generation pauses when available credits are used up, so verify the team’s settings before the busy member reaches zero.
Now compare a third Plus seat. It would add a $30 subscription and $30 of individual monthly credits for that third user. If the same person still does the $60 of generation, that extra seat does not close their $30 gap under the published credit rules. Buy a seat because another person needs access, collaboration or their own workload. Budget purchased shared credits against uneven usage separately. The site’s AI plan finder can help compare plan structures, but the account’s Billing page remains the source for its actual balances.
Model choice changes the credit burn
v0 charges for the input and output tokens processed, not a fixed number of dollars per message. The pricing page publishes these rates per million tokens. Its docs explain that input can include the prompt, chat history, source files and other relevant context, so a short new prompt can still have substantial input. Cached tokens have separate rates.
| Model | Input per 1M tokens | Cache write per 1M | Cache read per 1M | Output per 1M |
|---|---|---|---|---|
| v0 Mini | $0.20 | $0.25 | $0.02 | $1.20 |
| v0 Pro | $2.00 | $2.50 | $0.20 | $10.00 |
| v0 Max | $5.00 | $6.25 | $0.50 | $25.00 |
| v0 Max Fast | $10.00 | $12.50 | $1.00 | $50.00 |
For a simplified illustrative request with 100,000 uncached input tokens and 20,000 output tokens, v0 Pro’s listed rates give (100,000 / 1,000,000 × $2) + (20,000 / 1,000,000 × $10) = $0.40. At v0 Mini’s listed rates, the same token counts give $0.02 + $0.024 = $0.044. These calculations exclude cache writes and reads, images, any other billable work, and taxes. They are arithmetic at the published rates, not a test of a real request or a guarantee that two models produce the same output. The actual token counts and credit use belong in v0’s Usage view.
This is also why “$30 of credits” cannot be translated into a dependable number of prompts. More context and larger generated code increase token counts. If you compare v0 with direct model APIs, the DailyTech API price comparison explains the separate provider rate cards. Do not add a direct API bill to a v0 credit worksheet unless your workflow actually uses both services.
Check the bill before adding a seat
Start in v0 Usage and Billing. Usage groups credit consumption and activity by project or chat. On eligible team plans, Owners and members with the Billing role can review team-wide credit and activity by member or project. Billing shows the plan, credit balances, expiry dates, payment method and invoices. That is where you can replace the assumed $60 and $5 above with your own figures.
Write a row for each member. Record paid seat cost, individual monthly credits, any rollover balance and expiry, daily credit actually earned, generation use, and the purchased shared balance. For planning, calculate max(0, member usage after applicable credits - member's available individual monthly credits) for each member, then add those positive gaps. Use the account’s balance and charge history for the final number: published docs do not provide enough detail to promise a universal credit application order for every combination of grants and rollovers.
If a member is repeatedly over their own allowance while others leave most of theirs unused, another seat is unlikely to be the cleanest way to fund that member’s generation. If privacy requirements are the deciding factor, compare Business with Plus on those features separately; Business’s published monthly generation allowance is still $30 per user. If you only need to understand why two people can consume different credit amounts doing similar work, the Lovable timing example shows how a different builder’s daily grants change its bill. The Cursor and Copilot comparison covers yet another plan structure. Neither substitutes for v0’s own account usage data.
Finally, separate building in v0 from operating the app after deployment. v0’s pricing page says Free can deploy to Vercel, but it does not say that every hosting, database or AI service used by a deployed app is included in a v0 generation allowance. Check those services’ bills on their own terms. A v0 seat decision should be based on the work done in v0 and the account features the team needs.
Sources
- v0 Plans and Pricing: current plan prices, included credits, model rates and tax note.
- v0 Pricing documentation: individual and shared credit rules, Free eligibility, expiry, Usage and Billing.
- Vercel’s updated v0 pricing announcement: historical explanation of the move to token metering and context accounting; current plan decisions above use the live pricing and docs.
All pages read on November 16, 2026.
Free toolIs a monthly AI plan cheaper than paying per use?Compare for my usage

