GitHub Actions included minutes by plan, and what overage costs

Each GitHub plan comes with a monthly allowance of Actions minutes for private repositories. This page lists the allowances, explains what a minute beyond them costs, and shows the bill for a few workloads using the calculator.

Included minutes and storage per plan

Included usage per plan. Figures last checked on 2026-10-05. Source: GitHub Docs, GitHub Actions billing.
PlanIncluded minutes per monthArtifact storageCache storage per repository
GitHub Free2,000500 MB10 GB
GitHub Pro3,0001 GB10 GB
GitHub Free for organizations2,000500 MB10 GB
GitHub Team3,0002 GB10 GB
GitHub Enterprise Cloud50,00050 GB10 GB

Artifact storage is shared with GitHub Packages. GitHub Team also includes 75 GB of custom image storage and GitHub Enterprise Cloud 150 GB. The seat prices of the plans themselves are not in this site's data and are not part of any figure on this page.

What the included minutes cover

The two GitHub pages read on the checked date list no minute multiplier. In this site's calculator, one minute on any standard runner therefore uses one included minute, whatever the operating system. If GitHub publishes a different rule elsewhere, it is not reflected here.

There is no separate overage price

When the allowance is used up, GitHub charges each further minute at the per-minute rate of the runner it ran on. The price of going over therefore depends on where your jobs run.

Standard runner rates. Prices last checked on 2026-10-05. Source: GitHub Docs, Actions runner pricing.
Standard runnerRate per minute beyond the allowance1,000 minutes beyond the allowance (calculator output)
Linux 1-core (x64)$0.002$2.00
Linux 2-core (arm64)$0.005$5.00
Linux 2-core (x64)$0.006$6.00
Windows 2-core (x64 or arm64)$0.01$10.00
macOS 3-core or 4-core$0.062$62.00

The last column is the calculator's result for a GitHub Free account that runs 3,000 minutes in a month on that one runner (30 jobs a day, 5 minutes each, 20 working days), which is 1,000 minutes more than the plan includes.

Worked example: the same workload on each plan

A private repository runs 25 jobs per working day, 8 minutes each, 20 working days a month, all on the Linux 2-core runner. That is 500 jobs and 4,000 billable minutes a month.

Calculator output from prices last checked on 2026-10-05.
PlanIncluded minutesMinutes beyond the planOverage cost per monthPer year
GitHub Free2,0002,000$12.00$144.00
GitHub Pro3,0001,000$6.00$72.00
GitHub Team3,0001,000$6.00$72.00
GitHub Enterprise Cloud50,0000$0.00$0.00

The difference between plans is only the size of the allowance. Moving from GitHub Free to GitHub Team removes 1,000 billed Linux minutes here, worth $6.00 a month; whether that is worth the plan's seat price is a separate question this page cannot answer, because seat prices are not in its data.

Worked example: the same minutes on a dearer runner

Keep the GitHub Free account and the 4,000 minutes, but change the runner. On Linux 2-core the 2,000 minutes beyond the allowance cost $12.00 a month. On Windows 2-core they cost $20.00. On the standard macOS runner they cost $124.00 a month, or $1,488.00 a year. The allowance is the same number of minutes in each case; what changes is the rate applied to everything after it.

When a month mixes runners, the bill depends on which jobs happened to use up the allowance. The calculator's headline figure spreads the included minutes over the runners in proportion to their minutes and shows the lowest and highest possible bill next to it. The billing guide has a worked mix.

Storage overage is separate

Storage prices. Prices last checked on 2026-10-05. Source: GitHub Docs, GitHub Actions billing.
Storage beyond the included allowancePrice per GB per month
Shared storage (artifacts and GitHub Packages)$0.25
Actions cache$0.07
Custom image storage$0.07

As an example, 20 GB of cache beyond the allowance comes to $1.40 a month in the calculator's what-if. The free estimate on this site covers minutes only and leaves storage out.

Three questions to ask before you count on the allowance

  1. Is the repository private? If it is public and uses standard runners, the allowance is not touched.
  2. Do any jobs use larger runners? Those minutes are billed in full and should be added on top.
  3. How short are your jobs? Each one is rounded up to a whole minute, so many very short jobs use the allowance faster than their real run time suggests.

Check your own plan. Pick your plan in the calculator, enter your jobs and runner mix, and it shows the included minutes consumed, the minutes beyond the plan and the overage per month and per year.

More guides