Home / Blog / Cost and billing
Is GitHub Actions free? Pick your plan, repository and runner and see what you pay
Is GitHub Actions free? Public repositories, self-hosted runners and each plan's included dollars, dated and sourced, with a tool that works out your case.
Yes for public repositories on GitHub’s standard runners, and for self-hosted runners today. In a private repository each plan includes a monthly dollar amount of usage: $12 on Free, $18 on Pro and Team and $300 on Enterprise Cloud, which is 2,000, 3,000 and 50,000 minutes on a standard Linux runner. Past that you pay per minute, or are blocked if there is no payment method on file. Our GitHub Actions cost guide has the rates.
- Standard GitHub-hosted runners are free in public repositories and use none of your included amount.
- Private repositories draw on a dollar amount: $12 on Free, $18 on Pro and Team, $300 on Enterprise Cloud.
- At $0.006 a minute that is 2,000, 3,000 and 50,000 standard Linux minutes.
- Self-hosted runners are free today; the $0.002 a minute charge announced for 1 March 2026 was postponed.
- With no payment method, usage is blocked once the included amount is gone. Larger runners always need one.
That is the whole answer for most projects. The rest of this page is the detail that changes it: the runner you pick, the plan you are on, what a minute of each kind draws from the allowance, and the one charge GitHub announced and then put on hold. Every GitHub figure is read from GitHub’s own pages and dated, because these are figures that move.
Does GitHub Actions cost money for you?
- 3,000 minutes at $6 per 1,000 is $18.00.
- GitHub Free includes $12.00, so $6.00 is charged. The first 2,000 minutes are covered.
GitHub charges usage to the repository owner, so as we read it every private repository the same owner has draws on one included amount.
A budget can stop spending before the included amount is used or a bill is run up: GitHub says spending may be limited by one or more budgets.
Artifact storage and the 10 GB Actions cache are separate allowances and are not in this figure.
GitHub’s figures, read 2026-11-17. This runner: $0.006 a minute. Minutes are billed minutes: each job is rounded up to a whole minute.
It works from GitHub’s own rates and allowances, the ones in the table below, and it says what it leaves out. It does not know your budgets, how many of the included dollars your other repositories have used, or what your artifact storage costs. For a bill built from your own workflow, use the calculator.
How many GitHub Actions free minutes do you get?
GitHub does not give you a number of minutes. It gives you a dollar amount, and every job draws it down at the rate of the runner it used. So the number of free minutes depends on the runner. This table does the division for the three standard runners most people use.
| Plan | Included a month | Linux 2-core at $0.006 | Windows 2-core at $0.010 | macOS at $0.062 | Artifact storage |
|---|---|---|---|---|---|
| GitHub Free | $12 | 2,000 | 1,200 | 193 | 500 MB |
| GitHub Pro | $18 | 3,000 | 1,800 | 290 | 1 GB |
| GitHub Team | $18 | 3,000 | 1,800 | 290 | 2 GB |
| GitHub Enterprise Cloud | $300 | 50,000 | 30,000 | 4,838 | 50 GB |
| runners.io | 3,000 minutes | 3,000 at $0.004 | 1,200 at $0.010 | Not offered | Not sold by us |
Our row counts minutes, not dollars: 3,000 minutes a month are included, a Windows minute counts as 2.5 of them, and past them a 2 vCPU Linux minute is $0.004. We do not offer macOS. Jobs start once a card is on file.
Read on the date this post was last checked from GitHub’s billing page and rate table. Three details change the count. GitHub’s rate table says it rounds the minutes and partial minutes each job uses up to the nearest whole minute, so a 61-second job uses two. GitHub charges usage to the owner of the repository, so as we read it every private repository an owner has draws on the same amount. And a 1-core ubuntu-slim minute is $0.002, so the same $12 buys 6,000 of them. The 10 GB Actions cache is a separate allowance and is not in the table.
Is GitHub Actions free for public repositories?
Yes, on the standard runners. GitHub says use of its standard GitHub-hosted runners is free and unlimited on public repositories, and it does not use up the included amount. They are also free for GitHub Pages and Dependabot. A public repository gets a bigger machine too: 4 CPUs and 16 GB of memory on a standard Linux or Windows runner, where a private repository gets 2 and 8.
Larger runners are the exception. GitHub says they are billed for public repositories, and that they require a valid payment method. They are available to organisations and enterprises on Team and Enterprise Cloud.
Is GitHub Actions free for private repositories?
Free up to the included amount, then billed. Every standard GitHub-hosted runner in a private repository draws from the account’s included usage at its own rate, and that includes the ARM64 runners (see our post on them). A repository that runs 40 jobs a day of three minutes each, 30 days a month, uses 3,600 billed minutes of Linux. On Free the $12 covers the first 2,000, and the other 1,600 cost $0.006 each, which is $9.60. Put your own numbers in the tool above. Our per-minute rate for every size, beside GitHub’s, is on the GitHub Actions runner pricing page.
On Pro or Team the same 3,600 minutes are covered up to 3,000, and the other 600 cost $3.60. On Enterprise Cloud, where $300 covers 50,000, they cost nothing. That is why the runner and the number of minutes matter more than the plan: on Windows the Free amount lasts only 1,200 minutes.
Are self-hosted runners free?
GitHub charges nothing for them today, and its billing page lists self-hosted runner usage as free. You pay for the machines. GitHub announced on 16 December 2025 a $0.002 per minute platform charge on self-hosted runner usage in private repositories from 1 March 2026, then added an update: “We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.” We found no new date when this post was last checked. That is a status, not a forecast. The self-hosted cost post covers what you do pay.
GitHub offers larger runners to organisations and enterprises on the Team and Enterprise Cloud plans. They are billed, in public repositories too, at the rates in GitHub’s table.
What happens when the free minutes run out?
It depends on whether there is a payment method on the account. With none, GitHub says usage is blocked once you consume the included amount, so workflows stop running until you add one. With one, additional use is charged to it, and spending may be limited by one or more budgets. A budget is the control to set if a runaway matrix worries you: see the limits post for what else has a ceiling.
How to stay inside the free amount
Because the included amount is dollars, the way to make it last is to use fewer, shorter, cheaper jobs. Five things move the number, and each is arithmetic on the figures above.
Count jobs, not seconds. A job rounds up to a whole minute, so ten jobs of 20 seconds bill ten minutes, and one job doing the same work bills one. A workflow made of many tiny jobs is the most expensive shape, and our run-less post shows how to cancel, skip and merge them.
Know what a matrix costs. Every leg is a job, up to 256 per matrix, and a Windows leg draws down about 1.7 times what a Linux leg does. The matrix post has an expander that counts them before you push.
Use the cheapest runner that does the job. GitHub describes its single-CPU runners as a lower-cost option for lightweight operations, and the 1-core ubuntu-slim minute is $0.002, a third of a standard Linux minute. In our view labelling, linting and short checks fit it. Builds do not.
Remember that the amount is shared. GitHub charges usage to the repository owner, so as we read it a busy repository can use what a quiet one would have had. And set a budget: GitHub says that with a payment method on file, spending may be limited by one or more budgets, which is how a mistake stops at a number you chose.
If you would rather not count minutes at all, a public repository on standard runners costs nothing, and the calculator prices a private one from your own run history.
What changed in 2026
Two things, both from the 16 December 2025 announcement. GitHub cut the price of its hosted runners by up to 39 per cent, depending on the machine, on 1 January 2026. A standard Linux 2-core minute is $0.006 on its rate table today. And it planned the self-hosted charge above, then postponed it. A lot of what is written about whether Actions is free still describes the older prices or the postponed charge as if it were in force. The dated log of GitHub’s pricing changes keeps the order straight, and the rates post has the full table by size and platform.
Sources
- GitHub Actions billing (docs.github.com)
- Actions runner pricing (docs.github.com)
- GitHub-hosted runners reference (docs.github.com)
- Update to GitHub Actions pricing (GitHub changelog, 16 December 2025) (github.blog)
- GitHub Actions new pricing: self-hosted runner price increase (GitHub roadmap) (github.com)
- Actions limits (docs.github.com)
Frequently asked questions
Is GitHub Actions free for public repositories?
Yes, on standard GitHub-hosted runners: GitHub says their use is free and unlimited in public repositories, and it does not reduce your included amount. Larger runners are billed in public repositories too.
How many free GitHub Actions minutes do I get?
None as such. Private repositories get a dollar amount: $12 on Free, $18 on Pro and Team, $300 on Enterprise Cloud. At $0.006 a minute that is 2,000, 3,000 and 50,000 standard Linux minutes.
Does GitHub Actions cost money for self-hosted runners?
Not today. GitHub lists self-hosted runner usage as free. It announced a $0.002 a minute charge from 1 March 2026 and postponed it with no new date, and you still pay for the hardware they run on.
What happens when the free minutes run out?
With no payment method on the account, GitHub blocks usage once the included amount is consumed. With one, further use is charged to it, and spending may be limited by budgets.