Cursor Pricing in 2026: Plans, Costs, and What You Actually Get

Quick answer: As of August 2026, Cursor has a free Hobby tier at $0, Pro at $20/month, Pro+ at $60/month, Ultra at $200/month, and Teams at $40/user/month, with custom Enterprise pricing. The headline subscription prices look simple, but Cursor no longer sells a fixed number of requests. Since June 2025 each plan includes a pool of AI model usage billed against real API costs, so your actual monthly cost depends on which models you run and how heavily you use them - Pro's $20 buys roughly $20 of frontier-model usage before overages kick in. That shift is why some heavy users saw effective costs jump sharply, and why controlling spend now matters more than picking a tier. Prices change often; always check cursor.com/pricing before you commit.

Cursor is the AI code editor from Anysphere, and for most of its rise it sold the simplest thing in the world: $20 a month for a bucket of "fast" premium requests. You knew what you were getting. Then in mid-2025 the model underneath the price changed, the price tag on the box did not, and a lot of loyal users opened their bill to a number they did not recognize.

This guide is the honest version. What every plan costs today, what the 2025 change actually did, how the new usage billing works, what drives your bill up, how to keep it down, and - the question the pricing page will never answer for you - whether Cursor Pro is worth it for the way you actually work.

What Are Cursor's Pricing Plans in 2026?

Here is the full lineup, straight from the official Cursor pricing page as of August 2026. Read the "what you get" column more carefully than the price, because that is where the real cost lives now.

Two things on this table matter more than the numbers themselves.

First, the "included usage" figures for the higher tiers are approximate and get quoted differently across sources. Cursor's own page frames Pro as "$20 of frontier model usage per month," and third-party analysts peg Pro+ and Ultra at roughly $70 and $400 of usage respectively. Treat the multiples (3x, 20x) as the reliable part and the exact dollar values as a moving target.

Second, an annual commitment typically knocks about 20 percent off, and unlimited Auto mode is the quiet load-bearing feature of every paid plan. Auto lets Cursor pick a capable model at heavily discounted rates and does not draw down your frontier-model allowance. If you mostly live in Auto, your bill is basically the sticker price. If you insist on hand-picking Claude Opus for every prompt, it is not.

What Changed With Cursor's Pricing in 2025, and Why Did People Get Upset?

The short version: in June 2025, Cursor stopped counting requests and started counting compute, and it did the rollout badly enough to owe its users a public apology.

Before the change, Pro was a request-based plan. You got a fixed monthly allowance of fast premium requests and then slower fallback usage after that. Per Cursor's own June 2025 pricing post, "there was a limit of 500 requests per month, with Sonnet models costing two requests." One prompt, one or two requests, easy to reason about. The flaw, from Cursor's side, was that a request is a request whether it burns a few hundred tokens or a few hundred thousand - so a cheap edit and a massive multi-file agent run cost the company wildly different amounts but the user the same.

The new model prices what you actually consume. Pro now includes "unlimited usage of Tab and models in Auto" plus "$20 of frontier model usage per month at API pricing," with more available at cost beyond that. Heavier models, longer context, and MAX mode eat that allowance faster; light work barely touches it. In principle it is fairer. In practice, for people doing exactly the agentic, long-context work Cursor is best at, the effective price of that work went up - by a lot in the worst cases.

The backlash was less about the model and more about the surprise. Users on predictable flat plans logged in to find variable bills, ran out of allowance after a handful of prompts on the newest models, and in some documented cases saw effective costs climb many times over. A detailed timeline of the episode describes an initially defensive response that only later turned into real remediation. The specific communication failure Cursor admitted to was leaving users thinking "unlimited usage" covered every model when it only ever meant Auto.

To its credit, Cursor owned it. Co-founder Michael Truell wrote that "our recent pricing changes for individual plans were not communicated clearly, and we take full responsibility," and the company offered to refund unexpected charges racked up between June 16 and July 4, 2025, pointing affected users to a dedicated support address. If you want the operator's-eye view of the product itself beyond the billing drama, our Cursor review for 2026 covers whether it is still the editor to beat.

How Does Cursor's Usage-Based (Credit) Billing Actually Work?

Here is the mental model that makes your bill predictable. Every paid plan is a subscription plus a bucket of included model usage. You spend that bucket at the underlying API rates of the models you run, and when it is empty you either stop, upgrade, or pay overages at the same rates.

The single biggest lever is Auto versus a hand-picked model:

• Auto mode is unlimited on every paid plan and runs at deeply discounted rates. Per CloudZero's breakdown, Auto uses rates on the order of $1.25 per million input tokens and $6.00 per million output tokens, and crucially it does not drain your frontier allowance. This is the default for a reason.
• Manually selecting a frontier model - Claude Sonnet or Opus, GPT-5 class, Gemini - draws from your included usage at that model's full API price. The gap between the cheapest and most expensive choice can be roughly 25x for the same task.

On top of model choice sit three multipliers that quietly accelerate spend: MAX mode (bigger context windows, more tokens per call), long conversations (every turn re-sends the accumulated context, so a sprawling chat gets more expensive with each reply), and task framing (pointing an agent at your whole repo when a single file would do). Overages, when you hit them, are billed at API rates with no markup - Cursor is not marking up tokens, it is passing through what the model providers charge it.

The practical upshot: your bill is not really set by which tier you bought. It is set by how disciplined you are about models, mode, and context inside that tier. Which is exactly what the next section is about.

What Drives Your Cursor Bill, and How Do You Control It?

If your Cursor cost is unpredictable, it is almost always one of the drivers below. Each one has a direct control. This table is the one to bookmark.

The through-line is simple: Cursor's expensive path and its cheap path do the same job for most work. A guide like Finout's cost-cutting tips lands on the same handful of moves, because the physics do not change - tokens are the unit, and models, mode, and context are the three dials that set how many you burn.

If you find yourself fighting the meter constantly, that is a signal worth heeding. It may mean your workload is heavier than a $20 plan is priced for, or it may mean a flat-rate competitor fits your usage pattern better. We map those trade-offs in Cursor vs Windsurf for 2026 and in the broader Cursor alternatives roundup.

Is Cursor Pro Worth It? Who Should Pay and Who Should Stay Free

Cursor Pro at $20/month is worth it for the developer who writes code most days, leans on autocomplete and Auto mode, and reaches for a frontier model only when a task genuinely needs one. For that profile, the value is real and the bill is boringly predictable - you spend most of your time in unlimited Tab and Auto, and the included frontier allowance covers the occasional heavy lift. If you are that person, stop reading and just buy it.

The free Hobby tier is the right call for two groups: people evaluating whether Cursor fits their workflow at all, and light or occasional users whose needs the limited Agent allowance already covers. There is no shame in staying free. If you are not hitting the limits, paying $20 to not hit them harder is money lit on fire.

Pro+ at $60 and Ultra at $200 are for a narrower crowd: people whose work is dominated by long-context, multi-file agent runs on premium models, where the extra 3x or 20x allowance is cheaper than paying the same usage as overages on Pro. Do the arithmetic before you upgrade. If you are consistently blowing through Pro's allowance mid-month, Pro+ can genuinely be the cheaper option, not the pricier one. If you are upgrading on a hunch, you are likely overpaying.

The honest edge cases are worth naming. If you prefer a terminal-first, agent-driven workflow over an editor, the calculus is different - we compare that head-to-head in Claude Code vs Cursor. If you are a non-developer trying to ship a real product rather than write code, Cursor's usage meter and the "last 20 percent" of production hardening are the wrong fight to pick, and there are better-fit options in our best vibe coding tools for 2026 guide. And if a metered bill you cannot fully predict is itself the dealbreaker, that is a legitimate reason to look at flat-rate tools even if Cursor is technically the stronger editor.

One caveat that applies to every number in this piece: AI coding pricing is unusually volatile, tied directly to model provider costs that keep moving. Cursor has changed its model once publicly and adjusts allowances quietly more often than that. Whatever tier you pick, glance at cursor.com/pricing and your own usage dashboard on a cadence, not once.

Where Creatr Fits

Everything above assumes you want to be the person in the editor - picking models, watching the meter, and carrying the work from prompt to production yourself. Cursor is an excellent tool for exactly that, and if writing and shipping your own code is the point, it belongs in your stack.

Creatr is for the other case. We build, host, and run production-grade software for you: the first build ships in 24 hours, there are humans in the loop rather than a usage meter you have to manage, and you own the code outright. Where a tool like Cursor hands you a faster way to do the work, Creatr hands you the finished, running result - which matters most when the hard part is not writing the first 70 percent but hardening and operating the last 30, the authentication, the integrations that fail gracefully, the hosting that stays up.

We will not pretend Creatr is the answer for everyone. If you are a developer who loves being in the editor and wants maximum control over every model call, a Cursor subscription is a better fit than delegating the build, and you should buy it. Creatr earns its place when you would rather describe the outcome than operate the tooling, when you want software delivered and running instead of a faster IDE to run yourself, and when owning working code beats renting the time to write it. If that is the shape of what you need, start with Creatr. If it is not, use the tables above to right-size your Cursor plan and keep the meter honest.