cd /news/ai-products/github-copilot-pricing-change · home topics ai-products article
[ARTICLE · art-20023] src=github.com pub= topic=ai-products verified=true sentiment=· neutral

GitHub Copilot Pricing Change

GitHub has implemented usage-based billing for all Copilot plans, replacing previous flat-rate pricing. Users who exceed their included AI credits can enable additional spending by updating their budget, though individual users may face consumption limits based on usage patterns, billing history, and account verification status. The company plans to remove these temporary spending restrictions in the coming weeks while it monitors user behavior under the new model.

read9 min publishedJun 3, 2026

Copilot News and Announcements #

All GitHub Copilot plans are now on usage-based billingHello GitHub Community, Usage-based billing is now in effect for all GitHub Copilot plans. Please refer to our ## Frequently Asked Questions## Can I buy as much additional usage as I want?After you consume your included AI Credits, you can enable additional spend by updating your budget to keep using Copilot. However, we may limit how much additional usage users on individual plans can consume based on their usage patterns, billing history, and verification states for their GitHub account. When you hit the limit, Copilot features that require additional AI credits will . You can either wait for the next billing cycle or upgrade to a higher plan tier to continue using Copilot. We recommend upgrading to the next plan for more included usage and higher additional usage limits. ## What are the additional usage limits? How much additional usage can users purchase?The limits increase by plan, so the limits for users on a Pro+ plan will generally be higher than those for users on a Pro plan. They also vary depending on a user’s usage patterns, billing history, and verification states for their GitHub account. These limits are subject to change, and you’ll see an in-product notification when you hit a limit. ## How will we know when we hit an additional usage spending limit?You will get an in-product notification when you hit the additional usage spending limit. ## Why can’t we purchase as much additional usage as we need without upgrading to a more expensive plan?Additional usage spending limits are a temporary measure to mitigate abuse while we observe user behavior under the new billing model. We intend to pull these back in the coming weeks, at which point you will be able to purchase additional usage without upgrading your subscription. ## Why do the spending limits vary? Why are some users treated differently?Limits vary by plan tier and account signals, including usage patterns, billing history, and verification state, to protect service reliability and prevent abuse. ## How exactly are you determining the amount of a user’s additional usage spending limit? What's the specific criteria?We look at a variety of factors, including usage and payment history with GitHub. We can’t disclose specifics, as it would give bad actors more details to work with to circumvent our safeguards. ## Will we always have to upgrade to a more expensive plan when we hit an additional usage spending limit?No, we are working on solutions for allowing users to purchase as much additional usage as they need without upgrading to a more expensive plan. That said, our subscription tiers are designed to deliver more value as they increase in cost. ## If I upgrade to a more expensive plan but then decide to downgrade, what does that look like? Are there any restrictions on when I can downgrade?You can downgrade at any point. The downgrade will be a “delayed downgrade” where you will stay in the current, more expensive plan until your next billing cycle. Then you will be charged for the downgraded plan and the lower included usage will take effect the next calendar month. Please note that if you upgrade from a Student plan to a paid plan, downgrading will take you to a Free plan and you will need to reapply for Student plan. ## You said you’d loosen restrictions once usage-based billing is in effect, but sign-ups for new users are still d. What’s going on?We understand the frustration. Usage-based billing is now in effect, but we’ve needed additional time to put safeguards in place to ensure a reliable experience for all users. We plan to re-enable new sign-ups for all Copilot plans in the coming weeks. ## What does it look like in practice to upgrade? Can you give an example of what the flow looks like?Once you hit an additional usage spending limit, you can upgrade to the next plan to continue using Copilot’s full set of features (code completions and next edit suggestions remain unlimited for all paid plans). By upgrading, you will be paying a prorated amount of the next plan’s cost based on your billing cycle. Your accrued additional usage will be charged during your next billing cycle. For example, once you hit the $29 additional usage spending limit on Copilot Pro and decide to upgrade, you will pay a prorated amount of the $39 Copilot Pro+ cost and receive $70 worth of AI Credits that are currently included with the Copilot Pro+ plan. On your next billing cycle, if you stay on Copilot Pro+, you will pay the full $39 for Copilot Pro+, the $29 in additional usage from Copilot Pro, and any additional usage from Copilot Pro+. A similar experience applies from Copilot Pro+ to Copilot Max with the corresponding costs. ## When can I sign up for Copilot Max?Copilot Max is ## Will you continue to offer flex AI Credits after the current promotion ends?Flex allotments may vary from month to month. They’re designed to adapt as the economics of AI evolve, including model pricing, new models, and improvements in efficiency. ## Why should I pay GitHub API prices when I can just go pay the model provider directly?Copilot gives you a single subscription across every model family we support, including OpenAI, Anthropic, Google, xAI , with model availability varying by plan— without managing separate API keys, billing relationships, or rate limits with each provider. You get one bill, one set of usage controls, and access to all of it across VS Code, the Copilot CLI, the Copilot SDK, Copilot Code Review, and tools like OpenCode — without configuring each one separately. For a lot of developers, the value isn't just "access to a model." It's that Copilot is deeply integrated into the tools they already use: pull requests, code review, the editor, the terminal. That integration work, including the context from your repo, your PR diff, your open files, and more, is what turns a model call into something more useful. ## Will users continue to see the same level of restrictive rate limiting we’ve seen over the past few months?We’ve loosened rate limits considerably, and users should not experience them with normal use. ## Can I set up budgets at the user-level for my organization?Yes, admins can now set a universal budget for users or override for specific sets of users. As users approach their budgets, admins will receive email notifications and can adjust budgets anytime from their billing settings. See our budget management | #

Beta Was this translation helpful?

Give feedback.

Replies: 164 comments 274 replies #

| So the answer is basically: if you hit your limit too quickly, you should upgrade and pay more? I get why GitHub moved to usage-based billing, but the numbers feel way off compared to the previous system. I had only two short sessions in the VS Code extension, with maybe 2–4 prompts total, and somehow that already consumed 210.5 AI Credits/Tokens/Whatever. Under the old model, that kind of usage would barely make a dent in my monthly quota. Now it feels like a handful of normal interactions can burn through a noticeable percentage of the month's allowance. What worries me, and Honestly, this feels like the kind of change that pushes people to look at other providers or even go directly to the model vendors instead of using Copilot as their main AI tool. More transparency around how credits are consumed in real-world VS Code workflows would go a long way. |

Beta Was this translation helpful?

Give feedback. #

| My GitHub account is associated with Fu-Jie, and I have been a long-time annual subscriber. My annual membership was originally set to expire in approximately two months. Earlier today (June 1, 2026), I clicked the "Refund" button in my account settings out of curiosity—not with the intention of immediately cancelling. I expected this action would lead to a confirmation page, not process the refund directly. However, the refund was executed immediately without any secondary confirmation prompt. I believe this is a design flaw in the refund workflow. Any action affecting payment and subscription status should include an explicit confirmation step to prevent unintended consequences from accidental clicks or exploratory actions. The absence of this basic safeguard led to the unexpected cancellation of my membership. To clarify: My request is not about renewal, but about the value of my current active contract. My existing membership had not yet expired and still had nearly two months of service remaining. Given recent changes to GitHub's billing policies, the terms and benefits under my current contract hold unique value during this remaining period. Once refunded and cancelled, renewing would not provide the same conditions. Given the above, I request that my original membership status and expiration date be restored, and I strongly recommend that your team improve the refund process by adding a necessary confirmation step. I look forward to your reply. |

Beta Was this translation helpful?

Give feedback. #

| one afternoon pro+ limit 85% |

Beta Was this translation helpful?

Give feedback. #

Beta Was this translation helpful?

Give feedback. #

| Dumbest decision ever.... |

Beta Was this translation helpful?

Give feedback. #

| Hm, wondering if there will be similar changes for the many Copilot variants in M365 in the future. |

Beta Was this translation helpful?

Give feedback. #

| I had faith in you.. Honestly, I regret not taking the refund offer you made. I genuinely think you're going to lose at least 80% of your client base. This is so ridiculous. It's far better to pay in real money and not by token. The base usage is ridiculously low. |

Beta Was this translation helpful?

Give feedback. #

| I'm using VS Code with GitHub Copilot and I chose LLM GPT 5.4 Mini, but the platform is deducting the cost of Gemini 3.5 Flash, and because of that, my credits are disappearing without me using them. |

Beta Was this translation helpful?

Give feedback. #

| How in the hell can 1 prompt which last month would barly cost a cent, now take up $4.51. this is ununsable and needs rolling back. |

Beta Was this translation helpful?

Give feedback. #

| So why has the Pro plan reduced its usage limit by almost 100 times compared to before? I also discovered that the |

Beta Was this translation helpful?

Give feedback. #

| In case anyone is curious on the value comparison, this is what I am seeing on the $10 plan using GPT-5.4: The 100 credits is an upper estimate of what I have been seeing if you assume larger prompts. I have seen as low as 10 credits and as high as 60 so far today. On average I seem to hover around 33 credits per prompt. |

Beta Was this translation helpful? Give feedback.

── more in #ai-products 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/github-copilot-prici…] indexed:0 read:9min 2026-06-03 ·