Home / Blog / Cost and billing
Why do macOS and Windows minutes cost more than Linux on GitHub Actions?
GitHub does not say why macOS and Windows minutes cost more. The rates, what the January 2026 cut changed, and what Apple's licence adds, with fact and inference kept apart.
GitHub does not say why. Its billing page says only that jobs on Windows and macOS runners “cost more to run than jobs on Linux runners”, at rates set by operating system and processing power, and its rate page prints the prices: $0.006 a minute for 2-core Linux, $0.010 for 2-core Windows (1.7 times) and $0.062 for standard macOS (10.3 times). Anything beyond those figures is inference, and this post keeps the two apart. Our GitHub Actions cost guide has the rates.
- GitHub does not say why: its billing page states only that Windows and macOS jobs cost more than Linux ones.
- A standard macOS minute is $0.062, 10.3 times a $0.006 Linux 2-core minute; a Windows minute is $0.010, 1.7 times.
- The 1 January 2026 cut moved Windows from 2.0 to 1.7 times Linux, and macOS from 10.0 to 10.3 times.
- Apple's macOS licence limits macOS to Apple hardware and sets a 24-hour minimum for CI leases: our inference, not GitHub's reason.
- Run non-Apple work on Linux, filter macOS workflows by path, keep one macOS leg in a matrix and set timeouts.
What does a macOS or Windows minute cost today?
A standard macOS minute is 10.3 times a 2-core Linux minute, and a Windows minute is 1.7 times. These are the rates on GitHub’s Actions runner pricing page, read on the date this post was last checked. The page prints no effective date. The last two columns are our arithmetic on its rates.
| Runner | Per minute | Times a Linux 2-core minute | Extra over a Linux 2-core minute |
|---|---|---|---|
| Linux 1-core, x64 (ubuntu-slim) | $0.002 | 0.3 | -$0.004 |
| Linux 2-core, x64 | $0.006 | 1.0 | - |
| Linux 2-core, arm64 | $0.005 | 0.8 | -$0.001 |
| Windows 2-core, x64 | $0.01 | 1.7 | $0.004 |
| Windows 2-core, arm64 | $0.01 | 1.7 | $0.004 |
| macOS 3-core or 4-core (M1 or Intel) | $0.062 | 10.3 | $0.056 |
| macOS 12-core, x64 (larger runner) | $0.077 | 12.8 | $0.071 |
| macOS 5-core, arm64, M2 Pro (larger runner) | $0.102 | 17.0 | $0.096 |
The multiple matters most where you least see it, which is the included allowance. GitHub states a plan’s included compute as a dollar amount, and each job draws it down at the rate of the runner it used, so the same amount buys far fewer macOS minutes than Linux ones. Standard runners in public repositories are free and draw nothing down.
| Plan | Included a month | Linux 2-core minutes | Windows 2-core minutes | macOS standard minutes |
|---|---|---|---|---|
| Free | $12 | 2,000 | 1,200 | 193 |
| Pro | $18 | 3,000 | 1,800 | 290 |
| Team | $18 | 3,000 | 1,800 | 290 |
| Enterprise Cloud | $300 | 50,000 | 30,000 | 4,838 |
Did the gap change on 1 January 2026?
Yes, a little. GitHub cut hosted-runner rates by up to 39 per cent from 1 January 2026, and the cut was not the same size everywhere, so the multiples moved. Windows fell further than Linux and now costs 1.7 times a Linux minute instead of 2.0. macOS fell a little less than Linux, so its multiple rose from 10.0 to 10.3. The rates before and after are from GitHub’s roadmap item for the cut, and the new ones match the rate page today.
| Runner | Per minute before | Per minute after | GitHub's change | Times Linux before | Times Linux after |
|---|---|---|---|---|---|
| Linux 2-core | $0.008 | $0.006 | -25% | 1.0 | 1.0 |
| Windows 2-core | $0.016 | $0.01 | -38% | 2.0 | 1.7 |
| macOS 3-core or 4-core | $0.08 | $0.062 | -23% | 10.0 | 10.3 |
GitHub says the new $0.002 per minute platform charge is “already included” in the reduced hosted-runner rates, so the rates above are all-in and nothing is added on top. The pricing post has the whole rate table and the dated log has every change since 1 January 2025.
What does GitHub say about why?
Four things, and none of them is a reason for the size of the gap. This is what we found GitHub documenting, read on the date this post was last checked.
“Each type of runner hosted by GitHub has a per-minute rate that is determined by the operating system and processing power.”
First, that sentence and the one after it, which gives the example that Windows and macOS jobs “cost more to run than jobs on Linux runners”. Second, the rate page states no reason, no multiplier and no effective date. Third, GitHub’s runner reference says macOS runners “are hosted in GitHub’s own macOS cloud”. Fourth, it says that in periods of high demand macOS jobs may take longer to start, and that GitHub “monitors macOS usage and plans capacity to meet demand over time”. The third and fourth are facts about how macOS capacity is run, and GitHub does not link either to the price.
What might explain the macOS premium?
What follows is our reading of terms Apple publishes. We could not find GitHub saying which terms it operates under, or that these are the reason for its rate. It is context, not an explanation.
The macOS Tahoe 26 licence agreement permits macOS only on Apple-branded computers: it does not allow you to “install, use or run the Apple Software on any non-Apple-branded computer”. Nothing in it restricts Linux in that way, and whether that lowers or raises anyone’s costs is our guess, not GitHub’s.
The same agreement has a section for renting macOS out for continuous integration, which it calls “Permitted Developer Services”. A lease must be for “a minimum period of twenty-four (24) consecutive hours”, and during it the lessee must have “sole and exclusive use and control” of the Apple software and the hardware it is on. That is a rule about leasing macOS to a customer, and we do not know that it describes GitHub’s own arrangement. What it shows is that renting out macOS minutes is a different business from renting out Linux ones, in ways that are public.
For Windows we found no published rule that sets it apart in the same way, and GitHub gives no reason for its 1.7 times. We would rather leave that blank than guess.
How do I spend fewer macOS and Windows minutes?
Ten minutes on a standard macOS runner bills $0.62, and the same ten minutes on a 2-core Linux runner bills $0.06. Across 400 runs that is $248.00 against $24.00. So the saving is in what you send to macOS and Windows, in this order.
1. Run on Linux whatever does not need Apple or Windows. Linting, unit tests of logic that does not touch the platform, formatting and packaging checks all give the same answer on Linux. Keep the macOS or Windows job for the build, the platform-specific tests and the signing.
2. Run the macOS job only when the files it builds change. A separate workflow with a paths filter does that. The macOS workflow below runs only for Swift sources, tests and the package file, and the Linux workflow beside it runs on every pull request.
# .github/workflows/swift-tests.yml
name: swift-tests
on:
pull_request:
paths:
- "Sources/**"
- "Tests/**"
- "Package.swift"
concurrency:
group: swift-tests-${{ github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
test:
runs-on: macos-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@v7
- run: swift test
# .github/workflows/lint-and-unit.yml
name: lint-and-unit
on:
pull_request:
concurrency:
group: lint-and-unit-${{ github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
lint:
runs-on: ubuntu-slim
timeout-minutes: 10
steps:
- uses: actions/checkout@v7
- run: ./ci/lint.sh
unit:
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@v7
- run: ./ci/unit-tests.sh
We checked both files with actionlint 1.7.12 and did not run them: the paths, scripts and Swift package are placeholders for yours. There is one trap in the first. As GitHub’s troubleshooting page for required status checks puts it, a workflow skipped by path filtering leaves its checks in a “Pending” state and blocks merging, so do not make a path-filtered macOS workflow a required check.
3. Keep one macOS leg in a matrix. A matrix multiplies its axes, and a macOS leg costs 10.3 times a Linux one. Test every language version on Linux and the newest on macOS, as the pricing post works through.
4. Cancel superseded runs and set a timeout on every job. Both files above do. A job with no timeout-minutes can run up to 360 minutes, which on a standard macOS runner is $22.32, against $2.16 on Linux.
5. Remember each job rounds up on its own. GitHub rounds the minutes of each job up to a whole minute, so splitting a ten-minute macOS job into five jobs of 2 minutes 10 seconds bills 15 minutes, not about 11. The post on running less has the changes that reduce the minutes in the first place, and the runner size guide says when a bigger runner saves money. To price your own month, the calculator takes your minutes, and the team minutes post shows how to estimate them. Our Windows Server runners for GitHub Actions page has the 2 vCPU rate a minute.
Sources
- Actions runner pricing (docs.github.com)
- GitHub Actions billing (docs.github.com)
- GitHub-hosted runners reference (docs.github.com)
- GitHub Actions new pricing: hosted runner price drop (GitHub roadmap) (github.com)
- Pricing changes for GitHub Actions (GitHub Insights) (github.com)
- Troubleshooting required status checks (docs.github.com)
- Workflow syntax for GitHub Actions (docs.github.com)
- Software licence agreement for macOS Tahoe 26 (Apple) (apple.com)
Frequently asked questions
Why do macOS minutes cost more than Linux on GitHub Actions?
GitHub does not say. Its billing page says only that Windows and macOS jobs cost more than Linux ones, at rates set by operating system and processing power. A standard macOS minute is $0.062 against $0.006 for 2-core Linux. Any reason beyond that is inference.
How much more is a macOS or Windows minute than a Linux minute?
On GitHub's rate page, as last checked, a standard macOS minute is $0.062, 10.3 times a 2-core Linux minute at $0.006, and a 2-core Windows minute is $0.010, 1.7 times. A 12-core macOS larger runner is $0.077.
Did the price gap change in 2026?
A little. After the January 2026 cut, Linux is $0.006, Windows $0.010 and macOS $0.062. Windows fell from 2.0 to 1.7 times Linux, and macOS rose from 10.0 to 10.3 times, because Linux fell 25 per cent and macOS 23.
Does Apple's licence explain the macOS price?
It may, but GitHub has not said so. Apple's macOS licence allows macOS only on Apple-branded computers, and for leasing it to others for continuous integration it sets a 24-hour minimum lease with sole use of the machine. We do not know whether GitHub works under those terms.
How do I reduce macOS and Windows minutes?
Run lint and logic tests on Linux, put the macOS job in its own workflow with a paths filter, keep one macOS leg in a matrix, cancel superseded runs and set timeout-minutes. Do not make a path-filtered workflow a required check.