Table of Contents
Cursor Pricing July 2026: All 6 Plans ($0 to $200/Month) and Which One to Pick
Pro at $20/month is the right call for most working developers, per cursor.com/pricing. For teams, the July 1, 2026 restructure changed the math enough that any budget decision made before that date deserves a second look: Standard seats now ship with two separate usage pools, and a new Premium seat at $120/user gives power users a predictable cost ceiling instead of a month-end bill surprise, per Cursor's June 1 Teams pricing post.
Six tiers now run from $0 to $200/month for individuals (per cursor.com/pricing), plus two seat types for teams and a custom Enterprise tier. Here is exactly what each costs, what you get, and who should pick it.
All 6 tiers at a glance (2026-07-03)
Prices from cursor.com/pricing and Cursor's June 1 Teams pricing post, fetched 2026-07-03.
| Plan | Monthly | Annual (per mo) | Best for |
|---|---|---|---|
| Hobby | Free | Free | Trying Cursor, light side projects |
| Pro | $20 | Not published | Daily professional use, 10+ hrs/week |
| Pro+ | $60 | Not published | Heavy Composer users who hit Pro's ceiling |
| Ultra | $200 | Not published | Full-time agent runners, CI pipelines |
| Teams Standard | $40/user | $32/user | Most dev team members |
| Teams Premium | $120/user | $96/user | Power users who spike on-demand spending |
| Enterprise | Custom | Custom | 25+ seats, compliance, invoice billing |
Annual pricing for individual plans (Pro/Pro+/Ultra) is not published on the live pricing page as of 2026-07-03. Teams annual rates ($32 and $96) come from Cursor's June 1 blog post.
Hobby (free)
Hobby is genuinely usable. The current cursor.com/pricing page lists "limited Agent requests" and "limited Tab completions" without specific numbers. Cursor dropped the older 2,000-completions framing, so the live description today is deliberately vague.
Start here, build something real, and notice where Cursor throttles you. No credit card required. If you are evaluating Cursor before proposing it to your team, Hobby gives you enough runway to form an opinion on tab completion and basic Composer tasks.
The upgrade signal is obvious when it comes: Cursor cuts you off mid-Composer session, or the features you actually want (frontier model access, cloud agents, MCPs) are locked. At that point, per cursor.com/pricing, $20 for Pro is an easy call.
Pro ($20/month)
Pro is where most professional developers land, per cursor.com/pricing. Per cursor.com/docs/account/pricing, it includes two usage pools that reset monthly: a generous Auto + Composer pool for Cursor's first-party models, plus $20 worth of API budget for third-party frontier model requests (Claude, GPT-4o, Gemini). Beyond usage, Pro unlocks frontier model access, MCPs, skills and hooks, cloud agents, and Bugbot on usage-based billing.
Twenty dollars of third-party API budget covers a reasonable amount of Composer work. Run long multi-file agentic tasks exclusively on Claude or GPT-4o and that pool thins out fast. When it runs out, on-demand billing kicks in at standard API rates, billed in arrears. That is not a problem if you watch the dashboard; it becomes one if you don't.
Pro fits anyone using Cursor as their primary editor 10+ hours a week. The productivity gain on tab completion alone tends to cover the cost before you factor in Composer.
Pro+ ($60/month)
Pro+ runs $60/month and includes $70 in API usage per month, per cursor.com/docs/account/pricing. That is 3.5x the API pool of Pro at 3x the monthly price.
Cursor says in the pricing FAQ: "We recommend Pro+ for daily agent users." The qualifying question is whether you actually are one. A developer who tabs through autocomplete suggestions and occasionally runs a Composer task is not the target. Pro+ is for someone running Composer for 20-30 minutes at a stretch, handling multi-file refactors, or running cloud agents that chain several model calls.
Breakeven math: if you are on Pro and your on-demand overages average more than $40/month, Pro+ is cheaper. Under $10/month in overages, stay on Pro. Most developers who hit the ceiling two or three times per month find Pro+ pays for itself by the third billing cycle.
Ultra ($200/month)
Ultra includes $400 in API usage per month, per cursor.com/docs/account/pricing. That is 20x Pro's pool.
Most developers do not need this plan. Ultra makes sense for someone running Cursor as a full-time agent platform: automated pipelines via the Cursor SDK, CI-integrated code review at scale, or a developer whose Pro+ on-demand charges are consistently high enough that the monthly Cursor tab reliably clears $200, per cursor.com/docs/account/pricing.
A quick check: pull your last two months of on-demand charges and add them to your current plan cost. If that total exceeds $200, Ultra is a budget cap with a real payoff. If it doesn't, it is not.
Cursor calls Ultra suitable for "agent power users," per cursor.com/pricing. Most developers who think they need it actually need Pro+.
Teams Standard vs Premium ($40 vs $120/user/month)
This is the July 1 change that makes every pre-July Cursor teams comparison stale.
Per Cursor's June 1 blog post, every Teams seat now ships with two separate pools of included usage:
- Composer and Auto pool - reserved for Cursor's first-party models and the Auto routing mode
- Third-Party API pool - usage from frontier models like Claude, GPT-4o, and Gemini
Standard seats stay at $40/user/month ($32 annual), per cursor.com/blog/teams-pricing-june-2026. Standard now carries "significantly more usage, with no change in cost" because of the new dual-pool structure. Standard is the right seat for most dev team members who use Composer as part of their daily workflow but are not running extended agent tasks.
Premium seats cost $120/user/month ($96 annual) and include 5x the usage of Standard at 3x the cost, per the same post. Cursor says Premium's Composer pool covers a full month of heavy agent usage for 99% of users. The audience is the small slice of any team that drives most of the on-demand charges. Per Cursor's Developer Habits Report (cited in the June 1 blog post), usage follows a power-law distribution: a handful of people generate most of the cost.
Teams can mix seat types freely. The practical approach: start everyone on Standard, run one billing cycle, look at who is triggering on-demand charges, and upgrade those people to Premium. Per cursor.com/blog/teams-pricing-june-2026, for a 5-person team with two heavy Composer users and three moderate ones, two Premium seats plus three Standard seats runs $360/month. That is often cheaper than five Standard seats plus unpredictable on-demand overages.
One Teams feature worth calling out: Bugbot. Per Cursor's June 10 changelog, Bugbot now completes reviews in about 90 seconds on average, down from about 5 minutes. It finds 10% more bugs per review (0.62 per review vs. 0.56 before), and costs about 22% less per run. Bugbot is included in Teams and Enterprise plans. For any team that wants automated code review on every PR, that improvement makes the Teams tier noticeably more useful than it was 30 days ago.
On the SpaceX deal: SpaceX agreed to acquire Cursor for $60 billion in stock, with the deal expected to close in Q3 2026, per TechCrunch's June 16 report. The June 1 Teams pricing restructure was announced two weeks before the acquisition and has nothing to do with it. What is not confirmed: whether post-close model access for Claude and GPT stays exactly as-is once the xAI/SpaceX stack takes over. Teams on annual contracts should factor that open question into their planning.
Enterprise (custom pricing)
Enterprise adds pooled usage across all seats, invoice/PO billing, SCIM seat management, repository/model/MCP access controls, auto-run and network controls, audit logs, service accounts, an AI code tracking API, and priority support, per cursor.com/pricing. Contact sales makes sense at 25+ seats, when compliance requires an audit trail, or when finance needs invoice billing rather than card billing.
Teams Standard/Premium already includes SAML/OIDC SSO, centralized billing, the admin dashboard, and team-wide privacy mode. The Enterprise jump is mostly about governance at scale: pooled usage instead of per-seat caps, and the access controls regulated industries need.
Which plan to pick
Solo developer: start on Hobby, upgrade to Pro when Cursor throttles you. Pro at $20/month, per cursor.com/pricing, covers daily professional use for most people. Move to Pro+ only if you are running extended Composer sessions and you see on-demand charges accumulating. Ultra is for full-time agent work.
Teams: default everyone to Standard, then audit after one billing cycle. Cursor's admin dashboard shows per-user consumption split across both pools, per cursor.com/blog/teams-pricing-june-2026, so the Premium upgrade decision becomes a data call rather than a guess. A mix of Standard and Premium seats usually comes out cheaper than all-Standard plus on-demand.
The July 1 restructure is a net win for teams. More included usage at Standard pricing, a predictable ceiling at Premium, and per-user visibility that was not there before. Any team that was on Standard and hoping on-demand charges would stay small now has the tools to manage it properly.