This is for Copilot Pro and Pro+ on a personal account. If you get Copilot through your company, you can't cancel it yourself; ask your organization owner to remove your seat.

1. Sign in at github.com, click your profile picture in the top-right corner and choose Settings.
2. In the left sidebar, under Access, click Billing & licensing, then Licensing. On older accounts the page is called Plans and usage.
3. Find the GitHub Copilot section, open the Manage subscription drop-down and click Cancel subscription.
4. Confirm by clicking Cancel Copilot Pro (or Pro+).
5. You keep your current features until the billing cycle ends. After that, your account moves to the free Copilot plan and you won't be charged again.

Paying for GitHub Pro too? To drop it, go to Settings > Billing & licensing > Additional billing details, open the Edit drop-down under Current plan and click Downgrade to Free. The change applies on your next billing date.

If you upgraded to Copilot Pro inside the GitHub Mobile app on an iPhone or iPad, Apple bills you, so canceling on github.com won't stop the charges.

1. Open the Settings app on your iPhone and tap your name at the top.
2. Tap Subscriptions, then GitHub.
3. Tap Cancel Subscription and confirm.

Refunds for App Store purchases are handled by Apple at reportaproblem.apple.com, not by GitHub. Not sure where you subscribed? Check your receipt: an email from Apple means the App Store, an email from GitHub means github.com.

Cancel Copilot Business for the whole organization (organization owners only):

1. Click your profile picture, choose Organizations and select your organization.
2. Click Settings under the organization name.
3. In the sidebar, under Code, planning, and automation, click Copilot > Access. On the new billing platform it's under Billing & licensing > Licensing.
4. If GitHub asks you to finish setting up Copilot policies, click Go to policies and do that first.
5. Under Copilot Business is active in your organization, select Disabled, then click Confirm and remove seats. Removing every seat cancels the plan.

Downgrade GitHub Team to Free:

1. In the organization's Settings, under Access, click Billing & licensing. Only owners and billing managers see this page.
2. Under Current plan, open the Edit drop-down and pick the downgrade option.
3. Review the features you'll lose and click I understand. Downgrade my organization. The change applies on your next billing date.

If the organization is part of a GitHub Enterprise account, an enterprise owner has to remove it from the enterprise first. Enterprise contracts signed with GitHub sales usually need written notice before the renewal date.

Most companies overpay for GitHub because of Copilot seats that nobody uses, not because of the plan itself. Before you cancel, check who actually uses Copilot:

• Sort seats by last activity. In the organization's Settings > Copilot > Access, sort the list by last activity. People who haven't used Copilot in a month are easy savings.
• Download the activity report. The same page lets you export a CSV with each person's last activity date, so you can share it with team leads.
• Remove individual seats. Switch access to Enabled for: selected members, check the people who don't need Copilot and click Cancel seat. They stay in the organization; only the Copilot seat goes away.
• Former employees. Removing someone from the organization also removes their Copilot seat. Do this as part of offboarding so you don't keep paying for people who left.

A removed seat keeps working until the end of the billing cycle, and you stop paying for it from the next cycle. Subscope flags this automatically: it shows which GitHub Copilot seats nobody has used in 30 days, so you can cut seats with data instead of canceling for everyone.

Canceling Copilot doesn't touch your code. Repositories, issues, pull requests and Actions history stay exactly where they are. Copilot settings and chat history tied to your seat stop being available once access ends.

Downgrading an organization from Team to Free doesn't delete repositories either, but features that aren't in the free plan stop working. For example, GitHub Pages sites built from private repositories may go offline. You can make those repositories public to keep them running. If a Pages site in a private repository uses a custom domain, update or remove its DNS records before you downgrade so nobody can take over the domain.