Cursor pricing: current and legacy plans, usage limits and extra charges

Published on November 7, 2026 by Steven Jones

Cursor pricing changed in October 2026. New customers now buy Cursor through The X Subscription, starting at $8 per month for Plus or $30 for Premium. Existing subscribers may still have the older $20 Pro, $60 Pro+ or $200 Ultra plan. Those older prices are not necessarily outdated for the people who still pay them.

The expensive misunderstanding is assuming that every paid plan includes Claude, GPT and Gemini usage. Under the new plans, the included allowance is for Cursor models and is shared with Grok. Third-party models cost extra from the first request. This guide separates the two plan families, traces charges by model and mode, and shows how to decide whether to keep an existing subscription. We checked prices and rules on 7 November 2026.

First, identify which Cursor pricing system you have

What your account shows	Your pricing system	Where usage and extra charges appear
Free, Plus, Premium, Super or Ultra under The X Subscription	New plans: one weekly pool for Cursor models, shared with Grok	Usage and prepaid credit at grok.com/dashboard; billing at grok.com/dashboard/billing
Hobby, Start, Pro, Pro+, Ultra, Teams Standard or Teams Premium	Legacy Cursor: two monthly pools on eligible paid tiers	Cursor dashboard, including the Spending tab and on-demand charges
An older allowance expressed in a number of requests	Earlier legacy request-based pricing	Check your account’s request allowance and whether a selected model requires Max Mode

The name Ultra appears in both families, but the entitlements differ. Check your billing dashboard rather than identifying the plan by name or an old receipt. This also explains why two developers can show different, legitimate Cursor prices on the same day.

---

---

Current Cursor subscription prices: what $8, $30, $100 and $200 actually buy

The X Subscription	Published monthly price	Included Cursor-model usage	Third-party models in Cursor
Free	$0	Limited	Unavailable
Plus	$8	Base weekly pool	Unavailable
Premium	$30	4x the Plus pool	API list price, paid separately
Super	$100	15x the Plus pool	API list price, paid separately
Ultra	$200	50x the Plus pool	API list price, paid separately
Teams	$30, $100 or $200 per paid seat	Matches each seat’s tier	API list price, plus an eligible team token charge

Prices are in US dollars, excluding applicable tax such as UK VAT. Annual billing may produce a different checkout total. The published multipliers describe relative usage, not a fixed number of Claude requests or a guaranteed dollar credit.

Upgrading from Premium to Super does not include a Claude allowance. It buys a larger weekly pool for Cursor models such as Grok and Composer. If nearly all your paid activity uses a named Claude or GPT model, calculate the separate model bill before paying for a higher tier.

Legacy Cursor Pro pricing can still be valid

Legacy plan	Existing plan price	How included usage works
Hobby	Free	Limited free usage
Start, India only	₹649/month, tax included	Cursor Models pool only
Pro	$20/month	Cursor Models and Other Models pools
Pro+	$60/month	Larger allowances in both pools
Ultra	$200/month	Larger allowances in both pools
Teams Standard	$40/user/month	Two monthly pools per paid seat
Teams Premium	$120/user/month	Five times Standard usage per seat

For legacy Pro, Pro+, Ultra and Teams customers, Other Models is a separate included monthly allowance for third-party models. It is consumed at the selected model’s API rate. Cursor Models covers Grok and Composer. These pools reset monthly with the account’s billing cycle, and unused usage does not roll forward.

For many existing developers, this is the financial reason to stay put. A $20 Pro renewal with third-party usage included can be more valuable than a new $30 Premium subscription when you buy the same third-party usage separately. Team administrators should also remember that legacy allowances are assigned per seat, not freely transferable between colleagues.

Model-and-mode billing matrix: which pool pays for a request?

Model or mode	The X Subscription	Legacy usage-based Cursor plan
Named Grok or Composer model	Weekly included pool; prepaid credit after exhaustion	Monthly Cursor Models pool; on-demand after exhaustion if enabled
Named Claude, GPT or Gemini model	Premium or above: prepaid credit at API list price from the first request	Monthly Other Models pool; then on-demand if enabled
Auto Cost mode (formerly classic Auto)	Bills as a Cursor-model request against the weekly pool, whatever model serves it	Bills against the Cursor Models pool
Auto Balance or Intelligence, on Teams and Enterprise with Cursor Router	Cursor-model route uses weekly pool; third-party route uses prepaid credit	Cursor-model route uses Cursor Models; third-party route uses Other Models
Subagent explicitly using a third-party model	Third-party prepaid charge, even if the parent chat shows Auto or Grok	Draws from Other Models, then eligible on-demand usage
Your own supported provider API key	Provider bills model usage directly; eligible team requests may still incur Cursor’s token charge	Provider bills directly; eligible legacy team requests may incur Cursor’s token charge

On Teams and Enterprise, eligible third-party requests also carry the Cursor Token Rate of $0.25 per million tokens, covering input, output and cached tokens. It does not apply to individual plans, Cursor models or Cost mode. Certain third-party models with sufficiently low cache-read prices are exempt. Check the routed model and request-level charge rather than assuming the word Auto determines the bill.

A further exception applies to older request-based subscriptions: Max Mode can be charged at the model’s API rate plus 20%. Do not apply that rule to modern usage-based plans, where this older Max Mode pricing does not apply.

Weekly resets, prepaid credit and monthly invoices are different things

The new weekly pool refreshes on the date shown in the Grok usage dashboard. It is shared across eligible activity in Cursor, Grok Chat, Imagine, Voice and Grok Bot. Using image generation elsewhere on the subscription can therefore reduce the Cursor-model capacity left for coding. The Grok API, however, is billed separately and does not consume that pool.

Prepaid credit is not included in usage. It pays for named third-party models immediately and for Cursor models after the weekly pool runs out. Credit bought as a top-up does not refresh each week; Cursor currently says it expires 365 days after purchase if unused. Top-ups are charged to your payment method when bought, including when Auto Top-up triggers.

Legacy plans instead reset both included pools monthly. Additional usage is invoiced in arrears when on-demand billing is enabled. On-demand is off by default for legacy individual Pro, Pro+ and Ultra accounts, but on by default for legacy Teams. That team default deserves checking before letting several agents run unattended.

Worked Cursor cost example: the usage bill and the cash bill

Assume a new Premium subscriber selects Claude Sonnet 5.5 directly for 20 agent requests in a month. For each request, assume 200,000 uncached input tokens and 40,000 output tokens. Cursor currently lists Sonnet 5.5 at $2 per million input tokens and $10 per million output tokens.

One request: (200,000 ÷ 1,000,000 × $2) + (40,000 ÷ 1,000,000 × $10) = $0.80.

Twenty requests: 20 × $0.80 = $16 of third-party usage. Add the $30 Premium subscription, and the economic cost is $46 before tax.

But suppose the developer buys a $20 prepaid top-up. Their cash charges are $30 for Premium plus $20 for the top-up, or $50 before tax, while $4 of credit remains for future usage. Confusing credit purchases with credit consumption makes invoice reconciliation unnecessarily difficult.

For a Teams Premium seat using the same eligible model and token quantities, 4.8 million total tokens would also add $1.20 in Cursor Token Rate charges, making the illustrative consumption cost $47.20 before tax. These figures exclude cache reads and writes, other agent calls, regional pricing adjustments and any tax. Real agent runs may contain many model requests, not just the visible conversation turns.

Your search, your sources

Make DIY AI a preferred source

See more of our reporting in Google Top Stories, AI Overviews and AI Mode.

Add DIY AI on Google

When migrating makes financial sense, and when it does not

Switching from an eligible legacy Cursor subscription to The X Subscription is optional and permanent. You can’t simply restore the old plan after migration. Cursor has not announced a fixed compulsory migration date for existing customers, so a valid legacy renewal should not be treated as an error. The migration flow for an existing paid Cursor account offers Premium and above, rather than treating the $8 Plus tier as a direct Pro replacement.

Make the decision from your last full month’s usage, not the new plan’s headline price:

1. Record your current legacy subscription fee and the actual value consumed from Other Models.
2. Estimate what those same third-party requests would cost as prepaid usage under Premium, Super or Ultra.
3. Check how often you use Grok or Composer, and whether Grok apps would compete for your new shared weekly pool.
4. For teams, compare paid seat tiers, the additional token rate and who can approve top-ups.

As a simple illustration, imagine a $20 legacy Pro account that currently covers $15 of third-party requests from its included allowance. The equivalent new Premium month would cost $30 plus $15 in model consumption, or $45, before tax. This is a hypothetical workload, not a claim about every account’s allowance. Conversely, someone mostly using Grok or Composer may benefit from the larger new pool and additional Grok features.

Migration can also generate a final invoice for uninvoiced legacy on-demand usage and prorated refunds for eligible unused subscriptions. You may need to cancel an Apple App Store subscription separately. Review the checkout summary and account-linking details before confirming.

Set spending controls before starting long agent runs

On The X Subscription, open grok.com/dashboard/billing and find Additional usage credits. Leave Auto Top-up switched off unless automatic purchases are deliberate. Set a Monthly additional usage limit for the amount of paid model usage you are willing to consume.

There is a subtle trap: that limit measures usage consumed, not the amount of prepaid credit you buy. Purchasing $20 of credit does not itself use $20 of the cap. A $10 consumption cap can stop further paid requests even if you have unused credit. Enforcement isn’t instantaneous, so don’t treat it as an absolute real-time safeguard.

On legacy plans, use the Cursor dashboard’s Spending tab to disable on-demand usage or set its monthly limit. For Teams, restrict who can alter usage settings. Raising a legacy limit mid-cycle can also make previously credited excess usage billable. If predictable expenditure is more important than uninterrupted agents, keep overages off and accept that requests may pause at the allowance boundary.

Which Cursor plan should you choose?

New customer using Grok or Composer: start with Plus if its feature restrictions suit your work; choose Premium or higher only when you need the larger pool, cloud agent features or named third-party models. New customer relying on Claude or GPT: budget at least Premium plus measured token usage; Super and Ultra do not make those requests free.

Existing legacy subscriber: keep the plan until your account’s real model mix shows migrating is worthwhile. Team: compare per-seat charges, paid token routing and shared credit controls before choosing a tier.

If you are deciding between editors rather than billing systems, read our Claude Code vs Cursor comparison, our Windsurf vs Cursor comparison and the best AI coding tools guide. For model rates and entitlement changes, consult Cursor’s official Models & Pricing documentation.