Question 1

v0 switched to token billing and capped the free plan? Is this new?

Accepted Answer

v0 has been relatively stable over the last 90 days. v0 has eased its constraints recently. Low recent constraint volatility — few meaningful restrictions in the last 12 months.

Question 2

Why is this happening — is it the tool or me?

Accepted Answer

If v0 runs out far sooner than it used to, the metering changed under you rather than your usage ballooning. In May 2025 every plan moved to token-based credit metering: instead of a flat monthly message count, you're billed per input and output token from a monthly credit pool, so longer prompts and larger generations cost more and iterative work drains the pool fast — one user reported spending over thirty-five dollars in a single day on what had previously cost twenty for the whole month. The free plan was also quietly capped at roughly seven messages a day on top of a small monthly credit budget, and it arrived with no changelog or announcement, which is why it can feel like your account broke; it didn't. Then in January 2026 the twenty-dollar Premium tier closed to new users and began sunsetting, so a new solo developer's cheapest paid step is now Team at thirty dollars a user, about fifty percent more. Watching the token counter within a session separates metering from behavior: a handful of long generations burning most of your credits is the per-token model working as designed. Hitting a wall on free after only a few messages is the daily cap instead — confirmed when access returns on the daily reset while your monthly credits may still show a balance. So keep prompts tight, break large builds into smaller generations, and check the estimated cost of heavy work before committing. On free, plan around the roughly seven-message ceiling or upgrade for sustained work; and because Premium is gone for new users, price the jump to Team against how many tokens your projects actually consume rather than against the old flat twenty-dollar mental model.