GitHub Actions Won't Charge You (Probably)

4 minute read Published: 2025-12-16
GitHub Actions Won't Charge You (Probably) cover

If you received an email from GitHub about upcoming pricing changes for GitHub Actions, you might be wondering: "Are they going to start charging me for something that was free?" The short answer: It depends on what you're using, but for most people, the news is actually good.

Let me break down what's changing in plain language, so you can understand how it affects your projects.


The Big Question: Is GitHub Actions Still Free?

Yes—for public repositories, GitHub Actions remains completely free. If you're using GitHub Actions in public repositories (like open-source projects), nothing changes. You can continue using it without any charges.

This is important because many developers and organizations rely on GitHub Actions for open-source projects, and GitHub has committed to keeping that free.


What's Actually Changing?

GitHub is making two main changes, both scheduled for 2026:

1. Price Reductions (January 1, 2026)

Good news: GitHub is reducing prices for GitHub-hosted runners in private repositories by up to 39%, depending on the machine type you use.

If you're currently paying for GitHub Actions in private repositories, your costs will go down. This is a straightforward price cut—no catch.

2. New Platform Charge for Self-Hosted Runners (March 1, 2026)

This is the one that might affect you: GitHub will introduce a new $0.002 per-minute "cloud platform" charge for self-hosted runners.

Wait—what's a self-hosted runner? If you're using your own servers or machines to run GitHub Actions (instead of GitHub's cloud infrastructure), those are self-hosted runners. Most individual developers and small teams use GitHub-hosted runners, so this won't affect them.

Important details:

  • This charge only applies to self-hosted runners (your own machines)
  • The charge is $0.002 per minute (that's 0.2 cents per minute)
  • Even with this charge, it still counts against the minutes already included in your GitHub plan

What does that last point mean? If you have a GitHub plan that includes 2,000 minutes per month, and you use 500 minutes on self-hosted runners, you'll pay the $0.002/minute charge, but those 500 minutes still count toward your 2,000-minute allowance. You're not being double-charged.


Quick Reference: Pricing Summary

Here's a simple breakdown of what's changing:

TypeStatus After Update
Public repo GitHub-hosted✅ Still free
Private repo GitHub-hosted🔻 Price reduced (up to 39%)
Self-hosted runners💲 $0.002/min platform charge
Enterprise Server customers✅ No change

What This Means for You

  • Public repositories: No change—still free
  • Private repositories (GitHub-hosted): You'll pay less—prices dropping up to 39%
  • Self-hosted runners: New $0.002/min charge (~$0.12/hour). Calculate based on your usage
  • Enterprise Server: No changes

Why the Change?

GitHub hasn't provided detailed reasoning, but the new charge for self-hosted runners likely reflects the infrastructure costs of managing the platform, security, and integration features that make self-hosted runners work seamlessly with GitHub Actions—even when the actual compute happens on your machines.

The price reduction for GitHub-hosted runners suggests GitHub is optimizing their infrastructure and passing those savings to customers.


What Should You Do?

  1. Check your usage: If you're using self-hosted runners, review how many minutes you typically use per month to estimate the new cost.

  2. Review your plan: Make sure you understand what's included in your current GitHub plan (free, Pro, Team, or Enterprise).

  3. Calculate impact: For self-hosted runners, multiply your monthly minutes by $0.002 to see the additional cost. For example:

    • 1,000 minutes/month = $2.00/month
    • 5,000 minutes/month = $10.00/month
  4. Consider alternatives: If the new charge significantly impacts your costs, you might want to evaluate whether self-hosted runners are still the best option, or if GitHub-hosted runners (which are getting cheaper) might work for your needs.


The Bottom Line

For most users, these changes are either neutral (public repos stay free) or positive (private repo prices go down). The only group that will see new charges is those using self-hosted runners, and even then, the charge is relatively small.

The key takeaway: GitHub Actions isn't going away, and it's not suddenly becoming expensive. The changes are targeted and mostly beneficial. If you're concerned about costs, take some time to review your usage patterns and plan accordingly before the changes take effect in 2026.


Further Reading