How plan changes affect billing
When you change your paid plan, the impact on billing depends on the type of change:
| Scenario | When is billing affected? | Is proration applied? | When does access change? |
|---|---|---|---|
| Upgrade plan | Immediate | Yes | Immediately |
| Downgrade or cancel plan | End of current cycle | No | End of current cycle |
| Add paid seats/licenses | Immediate (prorated) | Yes | Immediately |
| Remove paid seats/licenses | Next billing cycle | No | End of current cycle (unless access revoked) |
Key takeaways:
- Upgrades are billed and applied immediately.
- Downgrades and cancellations take effect only after the current billing cycle ends.
- Adding seats is prorated and grants immediate access.
- Removing seats takes effect in the next cycle, unless access is manually revoked.
Each account on GitHub is billed separately. Upgrading an organization account enables paid features for the organization's repositories only and does not affect the features available in repositories owned by any associated personal accounts. Similarly, upgrading a personal account enables paid features for the personal account's repositories only and does not affect the repositories of any organization accounts. For more information about account types, see Types of GitHub accounts.
Making a change to the GitHub plan for your personal account, organization, or enterprise account does not affect billing for use of GitHub features, such as Copilot or paid apps purchased in GitHub Marketplace.
For more information, see GitHub's plans and How GitHub billing works.