GitHub Actions runner pricing: why macOS minutes cost 10x
GitHub Actions runner pricing is per minute, and the price depends on the runner. A macOS minute costs $0.062. A Linux minute costs $0.006. That is about 10 times more. In October, $111 of my $582 Actions bill was macOS, from only 1,797 minutes. Here is why Mac minutes cost so much, and 4 ways I cut them.
GitHub Actions runner pricing per minute
These are GitHub's list prices for the standard hosted runners in private repos, past the free minutes in your plan:
| Runner | Price per minute | vs Linux |
|---|---|---|
Linux (ubuntu-latest) | $0.006 | 1× |
Windows (windows-latest) | $0.010 | about 1.7× |
macOS (macos-latest) | $0.062 | about 10× |
Larger runners cost more per minute. Standard runners are free for public repos. GitHub keeps the current numbers on its runner pricing page, so check it before you budget.
What GitHub Actions minutes cost in real life
Prices per minute look tiny. They add up fast. Say one iOS build takes 10 minutes, and your team runs it 30 times a day:
- 10 minutes × 30 runs × 22 work days = 6,600 minutes a month.
- On macOS: 6,600 × $0.062 = about $409 a month.
- The same minutes on Linux: about $40.
GitHub also rounds every job up to a whole minute. A 10-second check still costs a full minute.
Why macOS minutes cost 10x
It comes down to hardware. Apple lets macOS run only on Apple computers, and each Mac may run at most 2 extra copies of macOS in virtual machines. So GitHub can't pack Mac jobs onto big shared servers the way it does with Linux. It needs racks of real Macs, and it gives each job its own.
Mac jobs are also long. Xcode builds, simulators and code signing take minutes, not seconds. So a high price meets long jobs, and the bill climbs fast.
What it did to my bill
Our GitHub Actions bill went from $3 in August 2025 to $582 in October 2026. Coding agents push code all day, and every push runs CI.
macOS was a small slice of the minutes, but $111 of the bill. And that was with builds only. I wasn't running any iOS tests yet, because each test run would have cost even more. That is a bad trade. You should never skip tests to save on CI.
4 ways to cut macOS minutes
1. Run only Mac work on a Mac
Lint, format checks, backend tests and docs builds don't need macOS. Move them to Linux, at a tenth of the price. Then make the Mac job wait for them, so a lint error stops the run before the costly part starts.
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: make lint
ios:
needs: lint
runs-on: macos-latest
steps:
- uses: actions/checkout@v4
- run: xcodebuild -scheme App build
2. Cancel old runs with concurrency
Push twice in a row, and the first run keeps going. Nobody looks at its result. With coding agents, this happens all day. Add GitHub Actions concurrency with cancel-in-progress, and a new push stops the old run.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
Keep it off deploy workflows. There, a new push could stop a deploy halfway. Use it on build and test workflows only.
3. Skip runs with a paths filter
A README fix should not start an iOS build. Add a paths filter, so the Mac workflow runs only when app code changes.
on:
pull_request:
paths:
- 'ios/**'
- 'Package.resolved'
One catch: if this workflow is a required check, a pull request that skips it waits forever for a result. Keep it out of required checks, or add a small job that always runs and reports for it.
4. Run Mac jobs on a Mac you own
Self-hosted runners have no per-minute price on GitHub today. Many of us already have a Mac on the desk that sits idle at night. Register it as a self-hosted runner and change one line:
runs-on: [self-hosted, macOS, ARM64]
A few things keep it healthy. Start the runner with --ephemeral, so every job gets a new runner, and wipe its work folder and DerivedData after each job. A new runner alone does not clean the disk. Install it as a service, so it comes back after a restart. Turn off sleep. And watch the disk, because Xcode fills it fast. At my October macOS bill, a base Mac mini ($899) pays for itself in about 8 months. If you already own the Mac, you save from day one.
I got tired of babysitting my own runner, so I built Codemany to do that part: a fresh runner for every job, updates and disk cleanup on its own. You can also do it all by hand with the steps in our Mac runner guide. For the full picture of GitHub Actions pricing, see how to cut GitHub Actions costs.
Questions
What is GitHub Actions runner pricing per minute?
At GitHub's list prices, a standard Linux runner is $0.006 a minute, Windows $0.010 and macOS $0.062. Larger runners cost more. Check GitHub's runner pricing page for current numbers.
Why are macOS runners so expensive on GitHub Actions?
macOS may only run on Apple hardware, with at most 2 virtual machines per Mac, so GitHub needs real Macs for every job. Mac jobs are also long, so the minutes add up.
Are macOS minutes free for public repos?
Yes. Standard GitHub-hosted runners, macOS included, are free for public repos.
Do self-hosted runners cost money on GitHub Actions?
Not per minute today. GitHub announced a $0.002 a minute charge for self-hosted runners in December 2025, then postponed it with no new date. You pay for your own machine.
Related
Read next: GitHub Actions pricing and cost, slow macOS jobs, running out of minutes, iOS and Xcode builds, AI agents and CI costs and the savings calculator
Start a 14-day trial No card needed. $20 a month for 2 machines after that.