How Much Does Cursor Cost?

Published on February 20, 2026 | Prices Last Reviewed for Freshness: March 2026
Written by Alec Pow - Economic & Pricing Investigator | Content Reviewed by CFA Alexander Popinker

Cursor is an AI-assisted code editor that bundles chat, code edits, and agent-style workflows inside the IDE. What you pay depends on two things: the subscription tier and how much metered model usage you burn through each month.

Cursor pricing has a fixed monthly fee, plus an included usage allowance on paid plans. After that included pool, extra usage can add to the bill depending on plan and workspace settings. Cursor has also changed how “Auto” counts over time, so the renewal date can matter as much as the plan name in Cursor’s pricing docs.

TLDR: Cursor starts free, paid tiers start at $20 per month, and teams typically budget $40 per seat monthly before extra usage.

• Free plan is $0, Teams is $40 per user per month, Enterprise is custom on Cursor’s pricing page.
• Cursor Pro includes $20 of monthly agent usage, Pro Plus includes $70, and Ultra is positioned as the top individual tier.
• Cursor said it moved Pro from request-based limits to $20 included usage, and tied “Auto” to unlimited model access when selected (as described in its July 4, 2025 post) on its June 2025 pricing update.
• Cursor said that at the next billing renewal after September 15, “Auto” for individuals would contribute to included monthly usage at token rates (Aug 12, 2025) in its August 2025 update.
• Each Teams seat costs $40 per month and comes with $20 per month of included usage allocated per user in the Teams pricing doc.

How Much Does Cursor Cost?

Cursor’s paid individual plans are built around a monthly subscription plus an included usage pool. In Cursor’s account pricing documentation, Pro includes $20 of monthly API agent usage, with Auto and composer-style usage described as generous alongside it. That structure is what changed the buying math in 2025: instead of counting requests, the plan is framed as a credit pool that maps to underlying model costs.

A practical way to read that is “Pro is the entry paid seat.” If you mainly use tab completion and occasional chat prompts, you can often stay inside the included pool. If you run agents to refactor multiple files, ask the tool to search a large repo, or repeatedly regenerate code, you can hit the included usage faster. That is why Cursor’s own explanation of the shift leaned on the idea that harder tasks can consume far more tokens than simpler ones.

Many buyers also compare Cursor with other coding assistants before they commit. If you are weighing tool spend across a stack, it helps to line up monthly seat costs side by side with common alternatives. We have separate articles for GitHub Copilot costs and Microsoft Copilot costs, which can act as a sanity check when you set internal budget caps.

Cursor plans explained

Cursor splits into an individual side and a business side. Individuals start on a free tier at $0, then move up to paid plans that add more usage and fewer limits. Organizations typically choose Teams at $40 per seat monthly, then step into Enterprise when they need pooled usage, invoice workflows, or tighter admin controls. The public pricing page lists Free, Teams, and Enterprise, and also calls out Bugbot add-on pricing that sits beside the core editor subscription.

The feature split also matters for budgeting. Teams is not just “Pro times many people.” It adds shared team billing, usage analytics, role-based access, and single sign-on options listed on the same page. Enterprise layers in pooled usage, invoice and purchase order billing, SCIM seat management, and audit-style tooling. If you only need a seat for one developer, those admin features can be dead weight. If you need policy controls for dozens of seats, they are often the point of the upgrade, not a bonus.

Pro Plus and Ultra

Cursor created higher individual tiers for people who burn through more agent usage. In its docs, Pro Plus includes $70 of monthly API agent usage, which is a larger included pool than Pro’s $20. Ultra is positioned as the highest tier for individuals, built for users who want a much larger allowance and stable predictability on the seat.

The reason these tiers exist is visible in Cursor’s own public post about the 2025 shift: it argues that a single hard request can cost much more than a routine one because long-horizon tasks spend more tokens. In that framing, the tier ladder is a way to sell a bigger included pool to the small slice of users who drive the bulk of inference spend.

If you want a third-party summary of the tier sticker prices, Vantage’s breakdown lists individual subscription rates as Hobby free, Pro at $20 per month, and Ultra at $200 per month, and it also lists Team at $40 per month in its plan summary. Treat third-party tables as a shortcut, then verify against Cursor’s own docs before purchasing.

Teams and Enterprise

Teams is the plan most small engineering groups end up on because it adds centralized billing and admin features while keeping a predictable per-seat price. Cursor’s Teams pricing documentation states the base seat price at $40 per month, and it also states each seat comes with $20 per month of included usage that is allocated per user and does not transfer between members.

That “allocated per user” detail is easy to miss and can shape what you pay in practice. If you have one very heavy user and four light users, you may not be able to lend unused included usage to the heavy user on Teams. Enterprise is where Cursor advertises pooled usage for the organization, which can reduce waste when usage is uneven across seats, along with invoice and purchase order workflows that larger orgs often require.

Enterprise also leans into governance features that show up in procurement checklists. Cursor’s public pricing page lists invoice and PO billing, SCIM seat management, and audit log tooling as Enterprise features. Those features can carry real internal cost savings if your current tooling forces manual seat management and weak offboarding controls, but they also push you into talk-to-sales pricing.

Usage credits, Auto

Cursor’s paid plans are not unlimited everything in the way many older SaaS tools were. The plan includes a monthly usage allowance, and the product can meter usage against that pool. Cursor’s July 4, 2025 blog post states it moved Pro from request-based pricing to $20 included usage and described unlimited usage of models when Auto is selected, with Auto routing across frontier models based on capacity.

Then Cursor published another update on Aug 12, 2025 that changed how Auto behaves at renewal time. It stated that at the next billing renewal after September 15, Auto for individuals would contribute to included monthly usage at token rates. In plain terms, that means someone who leaned heavily on Auto could see a different monthly spend pattern after the renewal cutoff.

This is also where cheap plan comparisons can go wrong. One tool can be a flat seat fee, another can be a seat fee plus metered usage with top-ups. If you are buying multiple subscriptions, keep a single sheet that tracks seat fees, included usage, and the policy that kicks in after the included pool. ThePricer’s pricing walk-through for Perplexity Pro is a good reminder that two tools can share the same sticker price and still behave very differently in real spend once limits and allowances enter the picture.

Hidden costs and add-ons

There are also operational costs that show up as time, not line items. A team plan may require SSO setup, role design, and admin reporting. Enterprise adds invoice and PO workflows that may be required by procurement even if the engineering group would happily pay by card. Cursor’s billing documentation points users to the dashboard to manage subscriptions and invoices, which hints at where finance and IT will spend time during rollout and renewals in its billing docs.

Finally, metered usage can turn a stable seat fee into a variable monthly bill. Cursor’s blog posts emphasize token-based costs and changes in how Auto counts. That is a real budget issue for teams that run heavy multi-file edits, large codebase queries, or agent loops for hours. The clean fix is policy: set internal guardrails on who can run long agent sessions, and review usage after the first month before you scale seat count.

Mini cases

Mini case 1, solo developer: A single developer who wants a predictable paid seat starts on Pro at $20 per month and aims to keep usage inside the included $20 monthly agent allowance described in the docs. Their base subscription is $20 monthly, and the metered part becomes relevant only if their workflow consumes more than the included pool.

Mini case 2, heavy agent user: A power user who burns through the included Pro pool quickly looks at higher tiers. Cursor’s docs list Pro Plus at an included $70 monthly usage allowance, which can reduce the frequency of top-ups compared with Pro. The trade is a higher subscription fee, set by Cursor, plus the same budgeting question: how far does the included pool go in your repo and model mix.

Mini case 3, five-person team: A small team chooses Teams at $40 per seat monthly for centralized billing and admin controls. The docs say each seat includes $20 monthly usage allocated per user, so the team has five separate $20 pools rather than one shared pool. Their base seat bill is $200 per month ($40 × 5 = $200) before extra usage and before any add-ons.

A worked total example

Worked total example (itemized): A startup licenses Teams for 8 developers and adds Bugbot for code review coverage. Teams seats are $40 per user per month, so the seat subtotal is $320 monthly ($40 × 8 = $320). Bugbot is $40 per user per month on Cursor’s pricing page, so the add-on subtotal is another $320 monthly ($40 × 8 = $320). Base monthly tool spend becomes $640 ($320 + $320 = $640) before any extra usage beyond included pools.

Computed insight 1: If you compare a Pro seat at $20 per month with an Ultra seat at $200 per month shown in third-party summaries, the annual sticker difference is $2,160 per year ($200 × 12 = $2,400, $20 × 12 = $240, $2,400 – $240 = $2,160). That gap only makes sense if the larger included allowance and stability prevent enough extra usage charges or time loss to cover it.

Computed insight 2: Teams can double your seat fee versus individual Pro on paper, because Teams is $40 per seat monthly and Pro is $20 per month in common summaries. For 10 developers, that difference is $200 more per month for Teams seats alone ($40 × 10 = $400, $20 × 10 = $200, $400 – $200 = $200). What you buy with that delta is admin tooling and policy controls listed under business plans, not more included usage per user, since the Teams doc describes per-user included usage rather than a shared pool.

Cursor’s sticker price is only half the budget story. The other half is how your team’s prompts and agent runs map to the included usage pool.

Buying checklist

Start by deciding if you are buying as an individual or as an organization. If you need centralized billing, policy controls, SSO, and usage reporting, Teams is the natural starting point at $40 per seat monthly. If you need pooled usage, invoice workflows, and SCIM, Enterprise is the path Cursor highlights.

Next, map your usage pattern to the included usage amounts. Cursor’s docs list included monthly usage for paid tiers, and the Teams doc explains that included usage is per user and does not move between members. That single rule can decide whether Teams is cost-efficient for uneven teams, or whether Enterprise pooled usage is worth a sales quote.

Finally, plan for governance as soon as you buy multiple seats. Cursor’s AI Code Tracking API documentation describes a way to track AI-generated contributions and accepted AI code across repos. That kind of reporting does not change the sticker price, but it can reduce waste by showing where adoption is high, where it is low, and where teams are running up usage without shipping output in its AI code tracking API doc.

Article Highlights

• Cursor has a free tier at $0, and Teams is listed at $40 per user per month, with Enterprise priced by sales quote.
• Paid plans include a monthly usage pool, with Pro described as including $20 of monthly agent usage and Pro Plus including $70 in the docs.
• Cursor’s July 2025 post describes the shift to $20 included usage and explains why token-heavy tasks can change what users pay month to month.
• Cursor’s Aug 2025 post ties Auto usage changes to renewals after September 15, which can affect bills for heavy Auto users.
• Teams includes $20 per seat monthly usage allocated per user, and that pool does not transfer between teammates.

Answers to Common Questions

Is Cursor free?

Yes. Cursor lists a Free plan at $0 on its pricing page, with paid business tiers starting at $40 per seat monthly and Enterprise priced by sales quote.

What is the difference between Pro and Teams?

Teams is built for organizations and adds centralized billing and admin controls, while individual plans focus on a single seat. Cursor’s Teams documentation also says each seat includes $20 monthly usage allocated per user and that it does not transfer between members.

Does Auto affect what I pay?

Cursor’s public posts in 2025 discuss changes to how Auto is treated, including a renewal-based update after September 15 where Auto contributes to included monthly usage at token rates. If you use Auto heavily, your renewal date can change how quickly you burn through included usage.

How do teams control spend?

Most teams start by standardizing who can run long agent sessions, reviewing usage after the first billing cycle, and limiting add-ons to the groups that use them. On larger rollouts, governance tooling like AI code tracking and audit-style controls can help spot waste early.

Is Enterprise worth it?

Enterprise is mainly for organizations that need pooled usage, invoice workflows, SCIM, and tighter security and admin controls. If those requirements are in your procurement checklist, Enterprise can be the only plan that fits even if the sticker price is higher.