Downgrade do plano da sua conta

About downgrades

When you downgrade your personal account, organization, or enterprise account's subscription, pricing and account feature changes take effect on your next billing date. Downgrading your plan does not affect other subscriptions or usage-based billing for your account. For more information, see How does upgrading or downgrading affect the billing process?.

Downgrading your personal account's plan

If you downgrade your personal account from GitHub Pro to GitHub Free, the account will lose access to advanced code review tools on private repositories. For more information, see GitHub’s plans.

1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
2. In the "Access" section of the sidebar, click Billing and plans, then click Plans and usage.
3. Under "Current plan", use the Edit drop-down and click Downgrade to Free.
   
4. Read the information about the features your personal account will no longer have access to on your next billing date, then click I understand. Continue with downgrade.

If you published a GitHub Pages site in a private repository and added a custom domain, remove or update your DNS records before downgrading from GitHub Pro to GitHub Free, to avoid the risk of a domain takeover. For more information, see Managing a custom domain for your GitHub Pages site.

Downgrading your organization's plan

Organization owners and billing managers can access or change billing settings for an organization.

After an organization's plan is downgraded, the organization will lose access to any functionality that is not included in the new plan. If an advanced feature, such as GitHub Pages, is not available for private repositories in your new plan, consider whether you'd like to retain access to the feature by making affected repositories public. For more information, see Setting repository visibility.

Downgrading from GitHub Enterprise Cloud disables any SAML settings. If you later purchase GitHub Enterprise, you will need to reconfigure SAML.

1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
2. In the "Access" section of the sidebar, click Organizations.
3. Next to the organization, click Settings.
4. If you are an organization owner, in the "Access" section of the sidebar, click Billing and plans.
5. Under "Current plan", use the Edit drop-down and click the downgrade option you want.
   
6. Read the information about the features your organization will no longer have access to on your next billing date, then click I understand. Downgrade my organization.

Downgrading an organization's plan with legacy per-repository pricing

Organization owners and billing managers can access or change billing settings for an organization.

If your organization is using a legacy per-repository billing plan, you can switch to per-user pricing at any time. You will not be able to switch back to repository pricing once you've upgraded to per-user pricing. For more information, see Upgrading your account's plan.

1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
2. In the "Access" section of the sidebar, click Organizations.
3. Next to the organization, click Settings.
4. If you are an organization owner, in the "Access" section of the sidebar, click Billing and plans.
5. Under "Subscriptions", next to your current plan, select the Edit dropdown menu and click Edit plan.
6. Under "Billing/Plans", next to the plan you want to change, click Downgrade.
7. Enter the reason you're downgrading your account, then click Downgrade plan.

Removing paid seats from your organization

To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see:

• Removing a member from your organization
• Converting an organization member to an outside collaborator
• Managing an individual's access to an organization repository

1. In the upper-right corner of any page on GitHub, click your profile photo, then click Settings.
2. In the "Access" section of the sidebar, click Organizations.
3. Next to the organization, click Settings.
4. If you are an organization owner, in the "Access" section of the sidebar, click Billing and plans.
5. Under "Current plan", next to your current plan, select the Edit dropdown menu, then click Remove seats.
6. Under "Remove seats", select the number of seats you'd like to downgrade to.
7. Review the information about your new payment on your next billing date, then click Remove seats.

Downgrading your enterprise account's plan

Enterprise accounts are only available with GitHub Enterprise, so it's not possible to downgrade an enterprise account to another plan.

If you want to stop paying for GitHub Enterprise altogether and your company pays via invoice, contact GitHub's Sales team. If you have a self-serve enterprise account, an enterprise account owner must remove or delete all organizations from the enterprise first. Removing an organization from an enterprise automatically downgrades the organization to GitHub Free. See Removing organizations from your enterprise.

Once all organizations have been removed or deleted, an enterprise owner can delete the enterprise account to cancel the GitHub Enterprise subscription. See Deleting an enterprise account.

Removing paid seats for your enterprise account

Enterprise owners and billing managers can manage billing for an enterprise account.

1. In the top-right corner of GitHub, click your profile photo.

2. Depending on your environment, click Your enterprise, or click Your enterprises then click the enterprise you want to view.

3. At the top of the page, click Settings.

4. Under Settings, click Billing.

5. Under "Payment information", click Manage seats.

   

6. In the "User licenses" section, under "Total Seats", enter a number of seats.

   

7. Click Update seats.

Further reading

• GitHub’s plans
• How does upgrading or downgrading affect the billing process?
• About billing on GitHub.
• About per-user pricing