Cursor is the most popular AI code editor on the market, and its pricing is usually the first question developers ask before switching. Since moving to a usage-based model, the plan names are simple but what you actually pay depends on how heavily you use AI models. This guide keeps the background brief and focuses on what matters: every Cursor plan in 2026, how the credit-based billing works, what drives your real cost, and how to choose the right plan for your workload.
What is cursor?
Cursor is an AI-first code editor, built as a fork of VS Code, that puts an AI assistant at the center of how you write software. It keeps the familiar VS Code interface and extension compatibility, then adds AI autocomplete, a chat that understands your whole codebase, and agents that can make multi-file changes on their own. In short, it is a normal editor with a coding AI wired into every action.
How Cursor Works
Under the hood, Cursor routes your requests to foundation models from OpenAI, Anthropic, and Google rather than running its own. Tab completions suggest code as you type, Auto mode lets Cursor pick a cost-efficient model for routine work, and you can manually select premium models like Claude or GPT for harder tasks. Agent mode runs multi-step, multi-file operations autonomously, and Max mode expands the context window so the model can reason over more code at once. Because every request is ultimately a model API call, your cost is tied to which model you use and how much work you ask of it, which is exactly what the pricing model below reflects.
How Cursor Pricing Works in 2026
This is the part that trips people up, so it is worth understanding before looking at the plans. In June 2025 Cursor moved from a fixed request-based model to usage-based billing, and the structure has stayed that way since. The formula is simple:
Cursor cost = a fixed monthly fee (which includes a pool of usage credits equal to the plan price) + any on-demand overages billed in arrears.
Every paid plan comes with a monthly credit pool roughly equal to its subscription price. Pro, for example, includes about $20 of model usage. You draw down that pool as you use AI, and the rate of depletion depends entirely on which model you pick and how heavy the request is.
What uses credits, and what does not
Tab completions are unlimited on paid plans and use minimal credits.
Auto mode, where Cursor selects a cost-efficient model, is effectively unlimited on paid plans and does not draw from your credit pool at full model price, so it is the cheapest way to work.
Manually selecting premium models such as Claude Opus, GPT-5, or Gemini Pro draws from your credit pool based on that model's API pricing and the size of the request.
Agent mode runs several model calls per task, so multi-step, multi-file operations consume credits for each step and file processed.
Max mode expands the context window (up to 1M tokens on some models) so the model reasons over more code, which costs more credits per request.
The token rates behind a request
When usage is metered, Cursor bills against your credits at flat per-token rates regardless of the underlying model, then premium model selection scales how many tokens a task consumes.
Cursor measures AI usage in tokens, and its metered billing is based on three token categories. Input tokens and cache writes cost $1.25 per million tokens, which covers the code, prompts, and context you send to the model. Output tokens cost $6.00 per million tokens, making them the most expensive part of a request because they represent the code, explanations, or responses generated by the AI. Cache reads cost just $0.25 per million tokens, allowing Cursor to reuse previously processed context at a much lower cost than sending the same information again.
In practical terms, this means that long AI-generated responses are typically more expensive than the prompts you send. Tasks involving large codebases, extensive context windows, or verbose outputs will consume credits faster, while cached context helps reduce costs by avoiding repeated processing of the same information.
Because requests are backed by model APIs, your effective cost mirrors the providers' own rates. Our Claude pricing 2026, ChatGPT pricing 2026, and Google Gemini API pricing guides show what the models inside Cursor cost at source.
Overages, annual billing, and students
When you exhaust your monthly credits, you can either upgrade to a higher tier or enable pay-as-you-go overage billing at the same API rates to keep working without interruption.
Annual billing saves roughly 20 percent across paid tiers, bringing Pro down to about $16 per month.
Verified students can get a year of Cursor Pro free with a school email, and a one-week Pro trial is included for everyone.
Cursor Pricing Plans 2026
Cursor offers five individual and team tiers plus custom Enterprise. The only real difference between Pro, Pro+, and Ultra is the size of the credit pool; the features are the same.
Cursor offers six pricing tiers in 2026, each designed for a different type of user. The Hobby plan is completely free and includes limited Agent requests and Tab completions, making it suitable for developers who are evaluating Cursor or coding only occasionally.
The Pro plan costs $20 per month and includes approximately $20 worth of usage credits, along with unlimited Tab completions and Auto mode. It is the most popular option for developers who use Cursor daily.
For heavier AI usage, Pro+ costs $60 per month and provides three times the usage allowance of Pro across OpenAI, Claude, and Gemini models. It is aimed at developers who regularly work with frontier AI models and would otherwise incur overage charges on the Pro plan.
The Ultra plan is priced at $200 per month and includes 20 times the usage of Pro, along with priority access to new features. It is intended for full-time AI-native developers who spend most of their day working inside Cursor and frequently use agents and large-context models.
For organizations, the Teams plan costs $40 per user per month. It provides Pro-level AI usage along with administrative capabilities such as SSO, centralized billing, shared rules, and team management features. It is best suited for teams of three or more developers.
Finally, Enterprise pricing is customized based on organizational requirements. It includes pooled usage, audit logs, SCIM provisioning, advanced security controls, and compliance features, making it suitable for large organizations with governance and regulatory requirements.
Hobby (Free)
A genuine free tier, not a trial. You get limited Agent requests and limited Tab completions with no credit card, plus a one-week full Pro trial when you start. It is enough to evaluate Cursor or to cover light, occasional coding.
Pro ($20/month)
The plan most developers should choose. It unlocks unlimited Tab completions, unlimited Auto mode, extended Agent limits, access to frontier models, MCPs, skills, hooks, and background or cloud agents, along with about $20 of included model usage. For anyone who codes daily, Pro pays for itself if it saves even an hour of work a month.
Pro+ ($60/month)
Pro+ adds no new features; it simply triples your usage, giving 3x the credits of Pro on all OpenAI, Claude, and Gemini models. Cursor recommends it as the sweet spot for active developers who use frontier models regularly and would otherwise rack up overages on Pro.
Ultra ($200/month)
Ultra gives 20x the usage of Pro plus priority access to new features. At this price it is infrastructure spend rather than a productivity subscription, built for developers who live in Cursor all day, run background agents continuously, and rely on frontier models for large-context work.
Teams ($40/user/month)
Teams gives each seat Pro-equivalent AI access plus organizational features: shared chats, commands, and rules, centralized billing, usage analytics, org-wide privacy mode, role-based access control, and SAML or OIDC SSO. The $20 per-seat usage premium over an individual Pro plan is the price of administrative control and shared context.
Enterprise (Custom)
Everything in Teams plus pooled usage across the organization, invoice and purchase-order billing, SCIM seat management, an AI code tracking API and audit logs, granular admin and model controls, and priority support. It is for large organizations with compliance, security-review, or procurement requirements.
What Changed in June 2026
Cursor updated its Teams plan in June 2026 and estimates the changes lower costs for about 90 percent of teams. They took effect immediately for new customers and from July 1, 2026 for renewing customers.
Two usage pools per seat. The Standard Teams seat now splits usage into a Composer/Auto pool (first-party Cursor models, including Composer 2.5) and a separate Third-Party API pool (Claude, GPT, Gemini). That gives every seat much more headroom at the same $40 price.
A new Premium seat. At $120 per month (5x the usage of Standard for 3x the cost), it is built for developers running agents all day, and Cursor expects it to cover 99 percent of heavy users for a full month without overages. Teams can mix Standard and Premium seats freely.
Better controls. Improved admin controls and rebuilt spend alerting, with a usage dashboard that shows how close you are to each limit.
What Drives Your Cursor Cost
Two developers on the same plan can see very different effective costs, because cost is set by model choice and request size, not by the plan alone. The biggest drivers are:
Model selection. Premium models like Claude Opus or GPT-5 consume far more credits than lightweight models or Auto mode.
Agent usage. Each agent step is a separate model call, so multi-step tasks add up quickly, roughly a few cents per call.
Max mode and large context. The more code you load into context, the more tokens you pay for on every request.
Output length. Output tokens cost several times more than input, so verbose generations cost more.
This is the same dynamic that governs any model-backed tool, where usage growth quietly outpaces the sticker price. Our LLM cost optimization guide and our note on the true cost of tokens explain why.
How to Choose the Right Cursor Plan for Your Work
The most common mistake is starting on Ultra just in case. Match the plan to how you actually work, then move up only when you consistently exhaust a tier's credits. Use the table as a quick guide.
If you're simply evaluating Cursor or coding for fewer than 10 hours a week, the Hobby plan ($0) is the best choice. It offers real functionality without requiring a credit card and is sufficient for testing the editor or handling occasional development work.
For developers who use Cursor as their primary editor for two to four hours a day, Pro ($20/month) is typically the right fit. Unlimited Tab completions and Auto mode cover most day-to-day coding workflows, and the included usage credits are usually enough for regular development.
If you're on Pro and consistently incur $20–$40 in monthly overage charges, moving to Pro+ ($60/month) makes more financial sense. The plan includes three times the usage allowance of Pro, making it cheaper than repeatedly paying overages.
For developers who still exceed Pro+ limits and accumulate more than $140 in monthly overages, Ultra ($200/month) becomes the better option. With twenty times the usage of Pro, it's designed for full-time, AI-native development workflows that rely heavily on agents and premium models.
Teams with three or more developers that need centralized billing, SSO, and shared rules should choose Teams ($40 per user/month). It is the only tier that provides the administrative controls and collaboration features required for managing multiple users.
Within organizations, developers who run agents heavily throughout the day may benefit from Teams Premium ($120 per seat/month). It provides five times the usage of a standard Teams seat, helping avoid unpredictable overage charges for power users.
Finally, companies that require compliance features, audit trails, pooled usage, and enterprise governance should choose Enterprise (custom pricing). This tier is built for large organizations that need advanced administrative controls, security, and audit logging.
The simple rule Start on Pro. Watch your usage dashboard for a full billing cycle. If you finish the month with credits to spare, stay on Pro. If you are rationing agent requests near month-end or paying $20 to $40 in overages, move to Pro+. Only step up to Ultra if Pro+ still feels limiting after a full cycle. For teams, the $20-per-seat premium over individual Pro plans buys centralized billing, SSO, and shared context, which is worth it the moment you have three or more developers.
How to Reduce Your Cursor Costs
Default to Auto mode for routine completions and simple generation, since it does not draw from your credit pool at full price.
Reserve premium models for tasks that genuinely need deep reasoning or multi-file changes.
Use Max mode only when the task truly needs a larger context window, and trim context to what the model actually needs.
Be deliberate with agents; multi-step, multi-file runs draw credits for every step and file.
Commit annually for about 20 percent off, and watch the usage dashboard so you upgrade or cap overages before they surprise you.
If Cursor sits inside a larger AI and cloud bill, fold it into the same budgeting discipline you use elsewhere, as covered in our token budgeting framework and FinOps for AI token and GPU costs guides.
Conclusion
Cursor pricing in 2026 is straightforward once you understand that you are buying a credit pool, not a fixed number of requests. Hobby is a real free tier, Pro at $20 is the right home for most working developers, Pro+ and Ultra exist for the minority who exhaust those credits, and Teams adds the administrative layer organizations need. The amount you actually pay comes down to model choice, agent usage, and context size, so lean on Auto mode, reserve premium models for hard problems, and let your usage dashboard, not guesswork, decide when to upgrade.
Top comments (0)