GitHub Actions runner pricing per OS and size

Every GitHub-hosted runner has its own per-minute rate. The tables below list the rates this site's calculator uses, grouped the way GitHub groups them: standard runners first, then larger runners by processor family. Each table carries the date its prices were read.

Standard runners

Standard runners are the ones you get from labels such as ubuntu-latest, windows-latest and macos-latest. In private repositories their minutes count against your plan's included minutes first; in public repositories they are free.

Larger runners, x64

Larger runners have more cores, memory and disk. GitHub's pricing reference says they are only available to organizations and enterprises on the GitHub Team or GitHub Enterprise Cloud plans, that included minutes cannot be used for them, and that they are not free for public repositories. Every minute is billed at the rate below.

Larger runners, arm64

Larger runners with a GPU

"Not listed" means the price list read on that date has no runner of that size for that operating system, not that it is free.

How to read the tables

• The operating system sets the base. Among the 2-core standard runners, a Windows minute costs more than a Linux minute, and the standard macOS runner costs about ten times the Linux 2-core rate.
• Size scales the rate, a little less than in proportion. Going from the Linux x64 4-core to the 8-core runner doubles the cores, and the rate goes from $0.012 to $0.022. A job that really finishes in half the time on twice the cores costs slightly less on the bigger machine; a job that does not speed up costs almost double.
• arm64 is cheaper at the same core count. At 16 cores, Linux arm64 is $0.026 a minute against $0.042 for x64. Whether your build runs as fast on arm64 is something only a test run tells you.
• Rounding still applies. Each job is rounded up to a whole minute on every runner, so short jobs on expensive runners are where rounding costs the most.

Worked example: the same jobs on each standard runner

A GitHub Team account with a private repository runs 40 jobs a day, 22 working days a month, 6 minutes per job: 5,280 minutes, of which 3,000 are included and 2,280 are billed. Putting all of them on one runner at a time, the calculator gives:

This assumes a job takes 6 minutes on every runner, which is rarely true: a 1-core machine is slower and a macOS build does different work. Use it to see the effect of the rate alone.

Worked example: a larger runner

Ten jobs a day on a Linux 16-core runner, 12 minutes each, 22 working days a month, is 2,640 minutes. Because included minutes do not apply, all of them are billed. On the x64 runner the calculator's full version gives $110.88 a month ($1,330.56 a year). On the arm64 runner of the same size it gives $68.64 a month ($823.68 a year). That cost comes on top of whatever your standard runners cost.

More guides

• How GitHub Actions minutes are billed
• Included minutes per plan and what overage costs
• GitHub Actions vs CircleCI cost
• GitHub Actions vs Buildkite cost
• How to reduce GitHub Actions minutes