Why you might cancel GitHub and what it means for your workflow
GitHub is the world's largest platform for version control and collaborative software development, serving millions of developers and thousands of enterprises. If you pay for a GitHub subscription-whether Pro, Team, or Enterprise-you're paying for features like private repositories, advanced security scanning, GitHub Copilot, and team management tools. Canceling your subscription stops all recurring charges and downgrades your account to GitHub's free tier, though your repositories and data remain accessible under free-tier restrictions.
You might cancel for legitimate reasons: your project budget has shrunk, your team has migrated to a self-hosted solution, or you've consolidated your development tools. Whatever drives your decision, understanding the legal framework and the precise cancellation procedure protects your interests and prevents unintended billing. Yafee is here to walk you through each step with authority and clarity.
Common reasons developers and teams cancel GitHub
Cost control is the dominant reason users cancel GitHub subscriptions. Monthly or annual fees compound across multiple team members, and when project scope changes or budgets tighten, subscriptions become the first target for reduction. Additionally, teams migrate to competing platforms such as GitLab, Gitea, or Bitbucket when those alternatives better match their feature set or pricing model. Authentication failures, account access issues, and unmet expectations from paid features like Copilot also trigger cancellation requests. Some users report that auto-renewal charges continued even after they attempted to downgrade, underscoring the importance of formal, documented cancellation.
What happens when you cancel GitHub
- Your subscription downgrades to GitHub Free (no charge)
- Paid features-private repositories, GitHub Actions minutes, Copilot-become unavailable immediately
- Billing stops at the end of your current billing cycle (monthly or annual)
- Your account, repositories, and commit history remain intact and downloadable
- Team members lose access to organization-level paid features
GitHub subscription plans and your billing obligations
Your cancellation procedure depends on which plan you hold and whether you bill as an individual or organization owner.
Subscription tiers and billing structure
| Plan type |
Monthly cost (USD) |
Annual cost (USD) |
Best for |
Cancellation method |
| GitHub Free |
$0 |
$0 |
Solo developers, open-source |
No billing; optional account deletion |
| GitHub Pro |
$6 |
$48 (saves $24/year) |
Individual developers |
Self-service cancellation in Settings |
| GitHub Team |
$21 per user |
$231 per user |
Small teams (3+ developers) |
Organization owner cancels in billing |
| GitHub Enterprise |
Custom pricing |
Custom pricing |
Large organizations, compliance needs |
Contact account manager or support |
| GitHub Copilot Pro |
$20 individual |
N/A (monthly only) |
AI-assisted code completion |
Cancel separately from account plan |
Locating your billing information and renewal date
Before you cancel, identify your current plan and next billing date. Log into your GitHub account, click your profile picture in the top-right corner, select Settings, then navigate to Billing and plans. You will see your current plan name, renewal date, payment method, and usage charges. If you manage a team or organization, verify whether you hold the billing role (organization owner or billing manager). GitHub allows only account owners and billing administrators to cancel subscriptions, so team members must ask their organization owner to initiate cancellation.
Your legal position and consumer protection rights
In the United States, your right to cancel a recurring subscription is protected by the Restore Online Shoppers Confidence Act (ROSCA), which requires companies to obtain express informed consent before charging you and to honor cancellation requests within a specific timeframe. Additionally, many states have enacted their own negative-option laws that strengthen consumer protections further. Yafee advises all users to understand that these federal and state laws place the burden on GitHub to acknowledge your cancellation promptly and confirm the cessation of billing.
Your legal position under federal and state law
The Restore Online Shoppers Confidence Act (ROSCA): This federal law (15 U.S.C. § 7704) requires that GitHub obtain your express informed consent before charging you for any subscription. Once you cancel, GitHub must stop billing you within one billing cycle and must acknowledge your cancellation promptly. If GitHub continues to charge you after cancellation, you have the right to dispute the charge with your credit card company or bank and to file a complaint with the Federal Trade Commission (FTC).
State negative-option laws: California, New York, Virginia, and other states impose stricter requirements on subscription services. For example, California's Automatic Renewal Law requires clear, conspicuous terms before you enroll and mandates that cancellation be "as easy as" signup. If GitHub fails to honor your cancellation request within the required timeframe, you can file a complaint with your state attorney general's office.
What this means in practice: GitHub cannot charge you after you submit a valid cancellation request. If billing continues, you have grounds to dispute the charge through your payment method and to escalate the matter to the FTC or your state's consumer protection authority. Yafee recommends that you keep a dated copy of your cancellation request as evidence.
How to cancel your GitHub subscription step by step
GitHub offers multiple cancellation methods depending on your account type and plan tier.
Step 1: verify your account ownership and billing role
Only the account owner (for Pro) or organization billing manager (for Team) can cancel a subscription. If you manage a team account, confirm that your role is "Owner" or "Billing Manager" in the organization settings. If you lack this permission, contact your organization owner and ask them to initiate the cancellation. This step prevents accidental cancellations and ensures that the right person authorizes the change.
Step 2: navigate to your billing settings and review your plan
- Log into GitHub with your account credentials
- Click your profile picture in the top-right corner
- Select Settings from the dropdown menu
- In the left sidebar, click Billing and plans
- Review your current plan, renewal date, and payment method
- Take a screenshot or note your renewal date for your records
Step 3: initiate the cancellation request online
GitHub allows you to downgrade or cancel your subscription directly through the web interface, which is the fastest method and provides immediate confirmation.
- In Billing and plans, locate your current subscription under "Plan"
- Click Edit or Change plan next to your subscription
- Select Free from the available tier options
- GitHub will display a confirmation message that your plan will downgrade at the end of your current billing cycle
- Confirm the downgrade by clicking Downgrade or Cancel subscription
- GitHub will send you a confirmation email within minutes; save this email as proof of cancellation
Step 4: cancel GitHub copilot separately (if applicable)
If you subscribe to GitHub Copilot Pro or Copilot for your organization, you must cancel it separately from your main plan subscription. Canceling your GitHub Pro plan does not automatically cancel Copilot.
- In Settings, navigate to Billing and plans
- Scroll to the "Subscriptions" section and locate GitHub Copilot
- Click Edit next to Copilot
- Select Cancel Copilot subscription
- Confirm your cancellation request
Step 5: request cancellation via email for enterprise or disputed billing
If you hold an Enterprise plan or if your online cancellation attempt fails, contact GitHub Support through email. This creates a formal record of your cancellation request and ensures that your request is tracked by GitHub's billing team.
- Send an email to [email protected] or through the GitHub Support portal (support.github.com)
- Include your full name, GitHub username, account email, and current plan tier
- State clearly: "I request cancellation of my GitHub [Plan Name] subscription effective immediately" or "at the end of my current billing cycle"
- Attach a screenshot of your billing page showing your current plan and renewal date
- Request a confirmation email acknowledging receipt of your cancellation request
- GitHub's billing team typically responds within 2-3 business days
Step 6: confirm cancellation and verify billing has stopped
After submitting your cancellation, verify that GitHub has honored your request by checking your next billing date and payment method status.
- Return to Settings > Billing and plans after 5-10 minutes
- Confirm that your plan now shows GitHub Free or Free
- Verify that there is no upcoming billing date listed (or the date has changed to "None")
- Check your email for a cancellation confirmation from GitHub
- Monitor your bank statement or credit card for the next 1-2 billing cycles to confirm no charges appear
What happens after you cancel your GitHub subscription
Your account transitions smoothly to GitHub's free tier, and you retain full access to your repositories and data.
Immediate changes after cancellation
- You lose access to paid features: private repositories remain, but collaborators and branch protection rules may be limited
- GitHub Actions usage limits revert to free-tier allowances (2,000 minutes per month for private repositories)
- GitHub Copilot suggestions cease if you had Pro or Copilot subscriptions
- Organization teams lose advanced security and compliance features
- Your repositories and commit history remain fully accessible and downloadable
Billing confirmation and refunds
GitHub does not refund partial months if you cancel mid-cycle. Instead, your cancellation takes effect at the end of your current billing period. If you were charged an annual fee upfront and wish to cancel early, contact GitHub Support to request a prorated refund. Yafee recommends requesting this in writing so you have documented evidence if GitHub refuses.
Downloading your data before losing access
Before your free-tier limitations take full effect, back up your repositories and project data. You can export your GitHub data by using Git command-line tools to clone all repositories locally or by using GitHub's data export tools. Navigate to Settings > Data exports to request a full export of your account data, which GitHub will prepare and email to you within a few days.
Timeline and what to expect
Understanding the cancellation timeline prevents confusion and helps you plan your workflow transition.
Cancellation timeline for individual plans (Pro)
| Timeline |
What happens |
Your action |
| Day of cancellation |
You submit cancellation; GitHub acknowledges and shows plan downgrade to Free |
Save confirmation email; take screenshot of billing page |
| End of current billing cycle |
Your subscription downgrade becomes effective; final charge appears on statement |
Monitor your statement; confirm no further charges occur |
| 30-60 days after |
Free-tier feature limits may apply to private repositories or collaborators |
Download repositories; migrate to alternative platform if needed |
| 90+ days after |
GitHub may disable unused free accounts; notification sent before deletion |
Log in periodically or request permanent deletion via Settings |
Cancellation timeline for team and organization plans
Team and Enterprise cancellations may take longer because organization billing managers and account managers must coordinate. If you manage a team, allow 5-7 business days for GitHub's billing department to process your cancellation request. Enterprise cancellations may require written agreement between you and a GitHub account manager and can take 10-14 business days.
Common mistakes to avoid when canceling GitHub
Most cancellation failures stem from simple oversights that are entirely preventable with the right checklist and awareness.
Mistake 1: confusing account deletion with subscription cancellation
Canceling your subscription downgrades your plan to Free; it does not delete your account. If you want to permanently delete your GitHub account and all associated data, you must explicitly request account deletion in Settings > Account > Delete your account. This is irreversible and removes all repositories and commit history. Yafee advises most users to cancel their subscription first and download their data before requesting full account deletion.
Mistake 2: failing to cancel GitHub copilot separately
Downgrading your main plan does not automatically cancel Copilot Pro or Copilot Team subscriptions. Many users discover duplicate charges weeks or months after thinking they had canceled completely. Always check the "Subscriptions" section in Billing and plans and explicitly cancel Copilot if you have it enabled.
Mistake 3: canceling without verifying your billing role
If you are not the account owner or billing manager on a Team or Enterprise account, your cancellation request will be rejected. Before you attempt cancellation, log into your organization settings and confirm your role. If you lack permission, request that your organization owner initiate the cancellation on your behalf.
Mistake 4: not documenting your cancellation request
Screenshot your billing page before and after cancellation. Save all confirmation emails from GitHub. If a dispute arises and GitHub continues to charge you after cancellation, these documents prove that you submitted a timely, valid cancellation request. This documentation is essential if you need to dispute charges with your credit card company or file a complaint with the FTC.
Mistake 5: canceling during a promotional period or trial
If GitHub offered you a discounted or trial rate, canceling mid-trial may trigger charges or lock-in periods. Review your subscription terms in Billing and plans before canceling. If you are unsure whether early cancellation carries penalties, contact GitHub Support first to confirm.
Refunds and dispute resolution
GitHub's refund policy is straightforward but must be handled carefully if you believe you were overcharged.
GitHub's refund policy
GitHub does not refund prorated amounts for mid-cycle cancellations. Your subscription remains active until the end of your billing period (month or year), and you are charged the full amount for that period. However, if you request cancellation more than 30 days before your renewal date, some Enterprise contracts allow for prorated refunds. Contact GitHub Support in writing if you believe you are entitled to a refund.
Disputing unauthorized charges with your bank or credit card company
If GitHub continues to charge you after you submit a valid cancellation request, do not simply accept the charge. Initiate a chargeback or dispute through your credit card company or bank within 60-120 days of the charge. Provide your bank with:
- A dated screenshot of your GitHub cancellation confirmation
- Copies of emails confirming your cancellation request
- Your billing statement showing the unauthorized charges
- A written statement explaining that you requested cancellation and GitHub failed to honor it
Your bank or credit card company will investigate and may reverse the charges in your favor. This process typically takes 30-45 days, and Yafee strongly recommends pursuing this remedy if GitHub's support team does not respond within 5 business days of your cancellation request.
Escalating to the federal trade commission if GitHub ignores cancellation
If GitHub continues to bill you despite multiple cancellation requests and your bank declines the dispute, file a complaint with the Federal Trade Commission (FTC) at reportfraud.ftc.gov. The FTC enforces ROSCA and other consumer protection laws against deceptive billing practices. Provide the FTC with all documentation of your cancellation requests and denied refunds. The FTC can force GitHub to refund you and to cease unlawful billing practices.
Checklist before and after cancellation
Use this checklist to ensure your cancellation is complete and your billing has truly stopped.
| Before cancellation |
After cancellation |
| Verify your account ownership or billing manager role |
Confirm plan now shows "Free" in Billing and plans |
| Screenshot your current plan and renewal date |
Verify no upcoming billing date is listed |
| Download all repositories and project data |
Save GitHub's cancellation confirmation email |
| Check for active GitHub Copilot subscriptions |
Monitor your credit card for 2-3 billing cycles; confirm no charges appear |
| Export account data via Settings > Data exports |
Contact GitHub Support if unexpected charges appear; file dispute with bank if needed |
If your online cancellation fails or if GitHub does not acknowledge your request within 3 business days, escalate immediately using the channels below.
Primary GitHub support channels
GitHub Support portal: Visit support.github.com and select "Billing and payments" > "I want to cancel my subscription." GitHub's support team will respond within 2-3 business days.
Email billing support: Send your cancellation request to [email protected] with your full name, GitHub username, and account email. Keep a copy for your records.
GitHub corporate address (for formal written requests):
GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, CA 94107
United States
You may send a formal cancellation letter via certified mail if you wish to create an irrefutable record of your request. Include your account email, GitHub username, and explicit request to cancel your subscription effective immediately or at the end of your current billing cycle.
Federal trade commission complaint (if GitHub refuses to cancel)
If GitHub fails to honor your cancellation request or continues billing after cancellation, file a complaint with the FTC at reportfraud.ftc.gov. The FTC enforces ROSCA and will investigate repeated or willful violations. Provide all documentation of your cancellation attempts and any unauthorized charges.
State attorney general complaint (if you reside in california, new york, or virginia)
California, New York, and Virginia have state-level negative-option laws that provide additional protections. File a complaint with your state's attorney general if GitHub violates these laws. Links to state AG offices are available at naag.org.
Key takeaways and next steps
Canceling your GitHub subscription is straightforward when you follow the correct procedure and document each step. You have strong legal protections under the Restore Online Shoppers Confidence Act and state negative-option laws, which require GitHub to honor your cancellation promptly and to cease billing immediately. Do not delay if unexpected charges appear after cancellation; contact your bank or credit card company and file a dispute, then escalate to the FTC if necessary.
Take these actions today to protect yourself:
- Log into your GitHub account and verify your billing role (owner or billing manager)
- Screenshot your current plan, renewal date, and payment method
- Download all repositories and export your account data
- Navigate to Billing and plans and click to downgrade to Free
- Cancel GitHub Copilot separately if applicable
- Save your cancellation confirmation email and billing page screenshot
- Monitor your credit card statement for 60-90 days to confirm no further charges occur
Yafee has helped thousands of consumers cancel unwanted subscriptions and recover overcharges by providing clear, legally grounded guidance. If you encounter resistance from GitHub or discover unauthorized charges, return here for escalation strategies or contact the FTC directly. Your consumer rights are protected, and Yafee remains your trusted resource for contract clarity, cancellation procedures, and billing disputes.