Guides

GitHub Actions macOS Runner Cost: What iOS CI Costs in 2026

Abhishek Ray · November 9, 2026

A standard GitHub Actions macOS runner costs $0.062 a minute, and every job is rounded up to the next whole minute. The larger macOS runners cost $0.077 (12-core Intel) and $0.102 (5-core M2 Pro) a minute. Standard runners are free in public repositories; in a private repository, a 10-minute iOS test job costs $0.62 each time it runs, and your plan’s included usage ($12 to $18 a month on most plans) covers fewer than 300 macOS minutes.

Below are the current rates from GitHub’s docs, what happened to the old 10x “minute multiplier”, worked examples for a real iOS workload, and how Xcode Cloud, Codemagic, a self-hosted Mac and a per-minute cloud Mac compare. I checked every price on November 9, 2026.

Disclosure: I make macbox, one of the options at the end. For the main example in this guide, it’s not the right tool, and I’ll show why.

GitHub macOS runner pricing in 2026

These are GitHub’s per-minute rates from its runner pricing page, with the hardware from its runner reference and larger runner reference:

Runner Labels Hardware Per minute Per hour
Linux 2-core (for comparison) ubuntu-latest 2 CPU $0.006 $0.36
macOS standard, arm64 macos-latest, macos-15, macos-26, xcode-27 3 CPU (M1), 7 GB RAM $0.062 $3.72
macOS standard, Intel macos-15-intel, macos-26-intel 4 CPU, 14 GB RAM $0.062 $3.72
macOS large (larger runner) macos-latest-large, macos-26-large 12 CPU Intel, 30 GB RAM $0.077 $4.62
macOS xlarge (larger runner) macos-latest-xlarge, macos-26-xlarge, xcode-27-xlarge 5 CPU M2 + 8 GPU, 14 GB RAM $0.102 $6.12

A few rules decide what you actually pay:

  • Rounding. “GitHub rounds the minutes and partial minutes each job uses up to the nearest whole minute.” A job that takes 4 minutes 5 seconds bills 5 minutes. It’s per job, so a workflow split into three small macOS jobs pays the rounding three times.
  • Failures count. GitHub’s own example: a 10-minute workflow that fails after 5 minutes and then succeeds on a re-run costs 15 minutes.
  • Public repositories. “The use of standard GitHub-hosted runners is free” in public repositories. Larger runners are not: “Larger runners are not free for public repositories.”
  • Larger runners need a paid org. They’re “only available for organizations and enterprises using the GitHub Team or GitHub Enterprise Cloud plans”, and they need a payment method on file.

macOS costs about ten times Linux per minute ($0.062 against $0.006). So on an iOS project that runs both, one macOS minute costs as much as ten Linux minutes, and the Mac jobs dominate the bill unless they’re a small share of the minutes.

The price came down this year. On January 1, 2026, GitHub cut hosted runner prices “by up to 39%” (changelog). The standard macOS rate went from $0.080 to $0.062, and the two larger macOS runners from $0.120 and $0.160 to $0.077 and $0.102. If a blog post quotes $0.08 a minute, that’s the pre-2026 rate.

What happened to the macOS minute multiplier?

If you remember “macOS minutes count 10x”, you’re remembering the old model. Until late 2025, GitHub’s docs said jobs on “Windows and macOS runners hosted by GitHub consume minutes at 2 and 10 times the rate that jobs on Linux runners consume”. Plans came with free minutes: 2,000 a month on Free, 3,000 on Pro and Team, 50,000 on Enterprise Cloud. Under the multiplier, a 10-minute macOS job ate 100 of them. The docs dropped the multiplier for per-minute prices in December 2025, and kept the minute quotas until late October 2026.

GitHub’s billing docs now describe it differently. Each runner has a dollar rate, and your plan includes a dollar amount of compute each month:

Plan Included compute per month macOS minutes that buys at $0.062
GitHub Free (personal or org) $12 193
GitHub Pro $18 290
GitHub Team $18 290
GitHub Enterprise Cloud $300 4,838

In GitHub’s words: “The included compute usage is expressed as a monetary amount, not a fixed number of minutes or other usage units.” The numbers line up with the old quotas. $12 buys 2,000 Linux minutes at $0.006, and under the old 10x multiplier 2,000 minutes bought 200 macOS minutes; now $12 buys 193. So the multiplier didn’t go away so much as turn into a price. The rough rule still holds: a macOS minute costs about what ten Linux minutes do.

That included amount is shared. Linux jobs, other runners and, per the same page, Copilot code review on private repos draw from it too, so in practice there may be less of it left for macOS than the table shows. Without a payment method on file, jobs stop when it runs out.

Worked example: a 10-minute iOS test job, 20 times a day

Take a typical small team: an iOS app whose build-and-test workflow takes 10 minutes on a standard macOS runner, triggered 20 times a day by pushes and pull requests, every day for a 30-day month. Private repository, GitHub Team.

  • 20 runs × 30 days = 600 runs
  • 600 runs × 10 minutes = 6,000 macOS minutes
  • 6,000 × $0.062 = $372.00
  • Less Team’s $18 of included compute: $354.00 a month, if nothing else used it

Weekdays only (22 days) would be 4,400 minutes, $272.80 before the $18.

The same workload on the larger runners, if they took the same 10 minutes:

  • 12-core large: 6,000 × $0.077 = $462.00
  • M2 Pro xlarge: 6,000 × $0.102 = $612.00

They won’t take the same 10 minutes, and that’s the only question that matters for larger runners. The xlarge costs 1.65 times as much per minute, so before rounding it only saves money if it finishes in under about 61% of the time (0.062 ÷ 0.102 = 0.608). With whole-minute rounding, your 10-minute job ($0.62) has to bill 6 minutes or less on the xlarge (6 × $0.102 = $0.612), and 8 minutes or less on the 12-core large (8 × $0.077 = $0.616). At 6 minutes 1 second, the xlarge bills 7 minutes and costs more. Run the job on both for a week and look at the timings before switching. I haven’t timed them myself, so I can’t tell you which way your project will go.

If the repository is public, the standard-runner version of all this costs $0. That’s a real reason to keep an open-source iOS project on GitHub Actions and not think about it further.

Two limits are worth knowing before you scale up. Standard plans can run at most 5 macOS jobs at once (Enterprise: 50), shared between standard and larger runners (limits). And any GitHub-hosted job stops at 6 hours.

Cheaper alternatives for iOS CI

Here’s the same 6,000-minute month on the other options I checked:

Option How it bills Cost for 6,000 minutes a month
GitHub standard macOS runner $0.062/min, rounded up per job $372.00 ($354.00 after Team’s $18)
GitHub macOS xlarge $0.102/min $612.00 at the same job time
Xcode Cloud Compute hours; 25 included with the developer program $49.99/month if it fits in 100 compute hours (not measured)
Codemagic, pay as you go $0.095/min on an M2 Mac mini $570.00
Codemagic, fixed price Unlimited, per year $3,990/year, $332.50/month
Self-hosted Mac runner GitHub charges nothing The Mac (from $899) plus your time
macbox $0.05 per Mac minute while a job runs Over its daily limit; see below

Xcode Cloud

On list price, Xcode Cloud looks like the cheapest option at this volume. The Apple Developer Program (99 USD a year, which you need to ship to the App Store anyway) includes “25 compute hours/month”. More costs $49.99 a month for 100 hours, $99.99 for 250 and $399.99 for 1,000. Our 6,000 GitHub minutes are 100 hours, so if the same work used 100 Xcode Cloud compute hours, it would be $49.99 a month against GitHub’s $354. I haven’t run this workload on Xcode Cloud, and its hours aren’t the same unit as GitHub’s minutes.

Read Apple’s definition of a compute hour before you count on that: “running 5 tests of 12 minutes each equals one compute hour.” Every test task counts, so testing on more device types adds hours: close to three times as many for three devices, if the tests take about as long on each. It’s also Apple’s own workflow, set up from Xcode, with results in Xcode and App Store Connect. That’s fine for many teams, and annoying if the rest of your CI lives in GitHub. It can send builds to TestFlight.

Codemagic

Codemagic charges $0.095 a minute for an M2 Mac mini and $0.114 for an M4, which is more per minute than GitHub. Individuals get 500 free M2 minutes a month (one build at a time). The fixed plan, $3,990 a year for unlimited M2 use, comes to $332.50 a month, paid as one $3,990 annual purchase. Against GitHub Team after its $18 of included compute, it wins once you’re past about 5,650 macOS minutes a month (($332.50 + $18) ÷ $0.062 ≈ 5,653).

A self-hosted Mac runner

GitHub doesn’t charge for self-hosted runners: the billing docs list “Self-hosted runners” under usage that “remains free”. GitHub had announced a $0.002-a-minute platform fee for self-hosted runners starting March 2026, then postponed it “to take time to re-evaluate our approach”, with no new date. Watch for it, but today you pay nothing to GitHub.

So the cost of a self-hosted Mac runner is the Mac. Apple lists the Mac mini from $899, which is about two and a half months of the $354 bill above. That’s only the purchase price against the GitHub bill; GitHub charges nothing per minute, but power, hosting and your time aren’t free. What you take on is the admin: someone installs each Xcode release, keeps simulator runtimes and disk space under control, applies macOS updates, keeps the machine powered and online, and cleans up between jobs. Your capacity is the number of Macs you own. For a team running thousands of macOS minutes a month with someone willing to do that work, a Mac mini or two on a shelf is often the cheapest answer. For a solo developer running a few hundred minutes, it’s a lot of upkeep to save $20.

A rented Mac works as a self-hosted runner too; I compared monthly and per-day Mac rentals in Rent a Mac.

Where a per-minute cloud Mac fits (and where it doesn’t)

macbox is a cloud Mac for coding agents. Claude Code, Codex, Cursor or a person at a terminal runs macbox build, macbox test or macbox screenshot, the project goes to your own macOS VM with Xcode 27, and the result comes back to the terminal. It costs $0.05 per Mac minute, in whole minutes, and the leftover part of a minute is free, so a job under a minute costs nothing. You pay only while a build, tests, a screenshot or a live session runs; uploading, queueing and starting the VM are free.

It doesn’t fit the 20-a-day CI workload above. Each account has a daily limit of 180 Mac minutes, and that workload needs 200. Even without the limit it would come to $300 a month (6,000 × $0.05), less than GitHub’s $354 but about six times the Xcode Cloud list price. It also can’t do a lot of what a release pipeline does: no code signing, no TestFlight or App Store upload, no physical devices, and no React Native, Flutter or Expo.

Where it fits is the loop before CI: an agent or a developer on Linux, Windows or a cloud sandbox who needs a Mac many times an hour for short jobs. Here are real runs from our test logs, on a small SwiftUI app with 4 unit tests and 5 XCUITests.

A build from a fresh Ubuntu 24.04 container, on October 29, 2026:

$ macbox build
macbox: Sending 6 files (8 KB) from /work/tally
...
Build Succeeded
macbox: build dd7a37b0d61c868a (Tally, built 09:19:04)
macbox: build succeeded in 32s (under a minute, not billed). Job dd7a37b0d61c868a.

The unit tests:

$ macbox test --only-testing TallyTests
...
PASS TallyTests.CounterTests testIncrementAddsOne (0.00s)
PASS TallyTests.CounterTests testIncrementUsesStep (0.00s)
PASS TallyTests.CounterTests testResetReturnsToZero (0.00s)
PASS TallyTests.CounterTests testStartsAtZero (0.00s)
macbox: test succeeded in 1m7s (billed 1 minute, 4 tests passed). Job 46987318cd1a4307.

The whole suite, run on October 27 by Claude Code on Linux after it wrote the UI tests (shortened from its exact command, which also piped the output through tail):

$ npx -y macbox test
...
PASS TallyUITests.TallyUITests testCancellingResetKeepsCount (12.94s)
PASS TallyUITests.TallyUITests testConfirmingResetClearsCount (10.53s)
PASS TallyUITests.TallyUITests testStartCountLaunchArgument (11.48s)
PASS TallyUITests.TallyUITests testTappingPlusOneTwiceShowsTwo (34.13s)
PASS TallyUITests.TallyUITests testTypingStepChangesIncrement (11.27s)
macbox: test succeeded in 3m9s (billed 2 minutes, 9 tests passed). Job e040148e027593bb.

And one UI test on its own:

$ npx -y macbox test --only-testing TallyUITests/TallyUITests/testConfirmingResetClearsCount
...
PASS TallyUITests.TallyUITests testConfirmingResetClearsCount (16.12s)
macbox: test succeeded in 1m27s (billed 1 minute, 1 tests passed). Job ea0cdb17f4ec2ae5.

Those four jobs billed 0 + 1 + 2 + 1 = 4 minutes, $0.20. Note the full suite: 3m9s on the clock, 2 minutes billed.

For a rough sense of the difference in billing rules, price the same four clock times the GitHub way, each rounded up: 1 + 2 + 4 + 2 = 9 minutes × $0.062 = $0.558, about 56 cents. Treat that as an illustration, not a benchmark. I didn’t run these jobs on GitHub, where each would also spend time on checkout and setup. The point is the rules: GitHub bills the whole job and rounds up; macbox bills only the run and drops the partial minute. For many short jobs, that adds up. For one long nightly job, it barely matters.

The full XCUITest walkthrough is in XCUITest tutorial, and setting this up for cloud agents like Codex cloud or Claude Code on the web is in iOS builds from cloud agents. If you’re on Linux and wondering what runs where, see Xcode on Linux.

Which should you use?

  • Open-source iOS app: GitHub Actions standard macOS runners. They’re free in public repos and nothing else here beats free.
  • Private app, mostly builds and tests, Apple-only stack: price Xcode Cloud first. If our example fits in 100 compute hours, that’s $49.99 against about $354 on GitHub; try it on your project to see how many hours it really uses.
  • Private app, a pipeline already in GitHub Actions, a few hundred macOS minutes a month: stay. The included $18 on Team covers about 290 minutes; past that, a 10-minute run costs 62 cents, and moving your pipeline costs more time than it saves money.
  • Thousands of macOS minutes a month and someone happy to look after a Mac: a self-hosted runner. A Mac mini costs about what two and a half months of our example GitHub bill do, before power and upkeep.
  • Considering larger runners: time your job on them first. In our 10-minute example, the xlarge has to bill 6 minutes or less, and the large 8 or less, to save money.
  • An agent or developer who needs a Mac in short bursts, from Linux, Windows or a cloud sandbox: a per-minute cloud Mac like macbox, alongside CI rather than instead of it. Signing and TestFlight stay in CI.

FAQ

How much does a GitHub Actions macOS runner cost?

$0.062 per minute for the standard 3-core M1 or 4-core Intel runner, $0.077 for the 12-core Intel larger runner, and $0.102 for the 5-core M2 Pro larger runner. Each job is rounded up to a whole minute. Standard runners are free in public repositories.

Is there still a 10x minute multiplier for macOS?

Not in GitHub’s current docs. Usage is priced per minute in dollars and drawn from a dollar amount of included compute ($12 on Free, $18 on Pro and Team, $300 on Enterprise Cloud). The ratio is about the same as before: $0.062 for macOS against $0.006 for Linux.

How many free macOS minutes does GitHub give you?

In public repositories, standard macOS runners are free with no stated cap. In private ones, the included compute buys about 193 macOS minutes on Free, 290 on Pro and Team and 4,838 on Enterprise Cloud, if nothing else uses it.

Are larger macOS runners worth it?

Only if they cut your job time enough. Before rounding, the M2 Pro xlarge needs under about 61% of the standard runner’s time and the 12-core large under about 80%; for a 10-minute job, that means billing 6 and 8 minutes or less. They need a Team or Enterprise Cloud plan and are billed even in public repositories.

Does GitHub charge for self-hosted Mac runners?

Not today. A $0.002-a-minute fee was announced for March 2026 and then postponed with no new date. You still pay for the Mac and the time to maintain it.

What’s the cheapest way to run iOS CI?

Free GitHub runners if the repo is public. For a private app, Xcode Cloud’s 25 included hours and $49.99 100-hour plan are the lowest list prices here, if your workload fits in those hours. At high volume, a self-hosted Mac mini is often cheaper, if you can maintain it.