GitHub Actions larger runners: price per minute

Larger runners give a job more cores, memory and disk, at a higher per-minute rate. The question this page answers is when the bigger machine is worth it: how much shorter a job has to get before the bill goes down instead of up. The figures are the ones this site's calculator uses.

Three rules that differ from standard runners

GitHub's Actions runner pricing reference, read on 2026-10-05, states three things about larger runners:

• Included minutes cannot be used for them. Every minute is billed from the first one.
• They are not free for public repositories.
• They are only available to organizations and enterprises on the GitHub Team or GitHub Enterprise Cloud plans.

Per-minute prices, x64

Each doubling of cores a little less than doubles the Linux rate. The arm64, macOS and GPU runners have their own prices; the runner pricing page lists all of them.

Worked example: does the 8-core runner pay for itself?

An organization runs 20 jobs per working day, 22 working days a month, 440 jobs. On the Linux 4-core runner each job takes 20 minutes: 8,800 minutes, all billed. The calculator's full version gives $105.60 a month ($1,267.20 a year).

What happens on the Linux 8-core runner depends entirely on how much faster the job gets:

If the job really halves to 10 minutes, the bigger runner saves $8.80 a month ($1,161.60 a year instead of $1,267.20) and every run finishes sooner. At 11 minutes it already costs slightly more than the 4-core runner, and at 14 minutes it costs a good deal more. Because the 8-core rate is a little under twice the 4-core rate, the job has to get close to twice as fast before the move is free.

Paying more for faster feedback can still be the right choice. The point is to know the price: here, a job that only drops from 20 to 14 minutes costs over a quarter more per month.

Worked example: against the standard runner

The step from a standard runner to a larger one costs more than the rates suggest, because the included minutes stop applying. Suppose the same 440 jobs take 40 minutes each on the standard Linux 2-core runner, in a private repository on GitHub Team. That is 17,600 minutes; 3,000 are included and 14,600 are billed at $0.006, which comes to $87.60 a month. The 4-core larger runner at $105.60 finishes each job in half the time in this example and costs more, since none of its 8,800 minutes are covered by the plan.

For a public repository the gap is wider still: the standard runner is free there and the larger runner is not.

How to decide

• Measure before you move. Run the job a few times on the larger runner and note the real duration. Builds that are limited by downloads or by a single thread gain little from more cores.
• Compare whole minutes. Each job is rounded up to a whole minute, so use rounded job lengths on both sides.
• Count what the included minutes were worth. If your standard-runner usage fits inside the plan today, any larger-runner minute is new spending.

More guides

• GitHub Actions ARM runners cost versus x64
• GitHub Actions runner pricing per minute by OS and size
• Self-hosted versus GitHub-hosted runners
• How to reduce GitHub Actions minutes