Back to blog
GuideFlutteriOSXcodeCI/CDCodemagicWindows

Flutter iOS Build Without a Mac: 4 Ways That Work in 2026

November 15, 20269 min readby Macyou Team

You can write a Flutter app on Windows or Linux, but you cannot build its iOS version there. Flutter’s release guide says “Xcode is required to build and release your app”, and Xcode runs only on macOS, so the flutter build ipa command has to run on a Mac somewhere. That Mac does not have to be yours. It can belong to a CI service that runs macOS for you (Codemagic, GitHub Actions or Xcode Cloud), or it can be a cloud Mac that you rent and use like your own. Prices and limits of other companies’ products below were checked on 15 November 2026.

What needs a Mac and what does not

Flutter’s install guide covers Windows, macOS, Linux and ChromeOS, so you write the Dart code and build the Android version on your PC. The iOS side is different. The same release guide adds: “You must use a device running macOS to follow this guide.” Three steps are tied to a Mac:

  • Building. Flutter’s docs say flutter build ipa produces an Xcode build archive (.xcarchive) and an App Store app bundle (.ipa). The command calls Xcode, and the Xcode system requirements page lists which macOS and which Macs Xcode needs.
  • Signing. An iOS app has to be signed before it can be installed on a real device or published. To publish on the App Store, Flutter’s guide says you must first enroll in the Apple Developer Program, which costs $99 a year.
  • Uploading. Flutter’s guide lists three ways to send the build to App Store Connect: Apple’s Transporter app for macOS, the xcrun altool command with an App Store Connect API key, or Xcode itself. All three run on a Mac.

So none of the routes below removes the Mac. They change whose Mac it is and who looks after it.

Four ways to run the iOS build

RouteWhose Mac runs the buildWhat you set upPrice, checked 15 November 2026Limits
CodemagicCodemagic’s Mac mini machinesA codemagic.yaml file and an App Store Connect API key500 free macOS M2 minutes a month for individuals, then $0.095 a minute on M2 or $0.114 on M4Builds only, no screen. One build at a time on the free plan, and a build can run for 120 minutes at most
GitHub Actions macOS runnersMacs hosted by GitHubA workflow file that you write, plus your own signing setupFree on standard runners in public repositories. Private: $0.062 a minute, with $12 a month of included compute on GitHub Free, about 193 macOS minutesBuilds only, no screen. The standard macOS runner has a 3 core M1 processor and 7 GB of memory
Xcode CloudApple’s build machinesA script that installs Flutter on each build, and a workflow created in Xcode25 compute hours a month included with the Apple Developer Program, then 100 hours for $49.99 a monthApple says to use Xcode for the first setup, so you need a Mac at least once
A cloud Mac you rentA dedicated Mac that only you useXcode, Flutter and CocoaPods, installed by youMacyou M4 Mac mini, 16 GB: $99 a month, or $80 a month billed annuallyBilled by the month or the year, so it costs more than CI when you build only a few times a month

Option 1: Codemagic

Flutter’s continuous delivery page lists Codemagic first among the CI options that have Flutter support built in. Codemagic’s Flutter guide describes the build in a codemagic.yaml file in your repository. Its example runs on a Mac mini M2 machine and builds the app with flutter build ipa. The same guide says Codemagic can publish the build to App Store Connect for beta testing with TestFlight, and that you have to create the app record in App Store Connect first.

Codemagic’s plan for individuals includes 500 free build minutes on macOS M2 machines every month. After that a minute costs $0.095 on M2 or $0.114 on M4. A solo developer who runs 30 builds a month at 15 minutes each uses 450 minutes, which costs $0 because it fits inside the free minutes. Teams can pay per minute or buy the fixed price plan at $3,990 a year.

The limits: the free plan is for one user and runs one build at a time, and a single build can run for 120 minutes at most. You get logs and an app file, not a Mac screen, so you cannot open Xcode or the Simulator to look at a problem.

Option 2: GitHub Actions macOS runners

GitHub hosts macOS runners in its own macOS cloud, and a job asks for one with a label such as macos-latest. The standard runner behind that label has a 3 core M1 processor and 7 GB of memory. GitHub gives you the Mac and nothing Flutter specific: you write the workflow that gets the Flutter SDK, runs the build, signs the app and uploads it. Flutter’s continuous delivery page shows fastlane as the tool for that and names GitHub Actions among the systems it works with.

Standard runners are free in public repositories. In a private repository a macOS minute costs $0.062, and GitHub rounds every job up to a whole minute. GitHub Free includes $12 of compute a month and GitHub Pro $18, so the Free plan covers about 193 macOS minutes. The same 450 minutes a month cost about $16 on GitHub Free after the included compute.

GitHub does not charge for minutes on self hosted runners, and a Mac that you rent can be one. iOS CI with GitHub Actions on a dedicated Mac shows that setup.

Option 3: Xcode Cloud

Apple describes Xcode Cloud as a continuous integration and delivery service built into Xcode and designed for Apple developers. Apple’s Xcode Cloud page does not mention Flutter, but Flutter’s continuous delivery page has an Xcode Cloud section. It asks for Xcode 13.4.1 or higher and an Apple Developer Program membership, and it has you add a script at ios/ci_scripts/ci_post_clone.sh. That script runs after Xcode Cloud clones your repository: it installs Flutter with git, runs flutter precache --ios and flutter pub get, installs CocoaPods with Homebrew and runs pod install. Apple says each build environment is temporary and is destroyed when the build completes, so the script does this on every build.

What Xcode Cloud does not do is start without a Mac. Flutter’s steps create the workflow in Xcode (Product > Xcode Cloud > Create Workflow), and Apple’s documentation says: “Use Xcode to initially configure your project or workspace to use Xcode Cloud.” After that first setup, Apple says you can edit workflows and start builds from the App Store Connect website. So from a PC you need a Mac once, borrowed or rented, and then builds run in Apple’s cloud.

The Apple Developer Program membership includes 25 compute hours a month, and Apple sells more as monthly plans, starting with 100 hours for $49.99. How those hours are counted is covered in Xcode Cloud pricing explained.

Option 4: a cloud Mac you rent

A cloud Mac is a real Mac in a data center that you reach from your PC. Because it is a whole Mac, you get what the CI services leave out: Xcode on a screen, the Simulator, and a place to work out why a native plugin or a signing step fails. The ways to see a simulator from a PC are compared in iOS Simulator on Windows.

Macyou is one example. You rent a dedicated physical Mac mini or Mac Studio by the month or by the year, one customer per machine. Your macOS account is an administrator with sudo, and you install Xcode, Flutter and CocoaPods yourself; Xcode is not preinstalled. You connect over SSH with a key and see the full screen in Screen Sharing or any VNC viewer on Windows or Linux, over the same secure connection. There is no desktop in the browser. The Mac is ready about 5 minutes after payment is confirmed and runs 24/7. The M4 Mac mini with 16 GB costs $99 a month, or $80 a month billed annually, and the price does not depend on how many builds you run.

The limits: billing is monthly or annual, so for two or three builds a month the free minutes of a CI service cost less. You also look after the machine yourself, which includes updating Xcode and Flutter.

Steps on the cloud Mac

  1. Connect from your PC over SSH, and open the Mac’s screen in a VNC viewer when you need Xcode’s windows.
  2. Install Xcode. Flutter’s iOS setup guide then has you run sudo sh -c 'xcode-select -s /Applications/Xcode.app/Contents/Developer && xcodebuild -runFirstLaunch' and accept the licence with sudo xcodebuild -license. Both need sudo, which your administrator account has. xcodebuild -downloadPlatform iOS downloads iOS platform support and the Simulator runtimes.
  3. Install the Flutter SDK for macOS and add its bin folder to your PATH. Install CocoaPods, which Flutter’s guide asks for when plugins use native iOS code.
  4. Run flutter doctor. Flutter’s docs say you need checkmarks for Flutter and for the platforms you plan to target, so here the Xcode line has to pass.
  5. Clone your project and run open ios/Runner.xcworkspace. In Xcode, sign in with your Apple ID and select your team under Signing & Capabilities. Flutter’s guide says the “Automatically manage signing” setting is on by default and is sufficient for most apps.
  6. Run flutter build ipa. The archive lands in build/ios/archive/ and the app bundle in build/ios/ipa/.
  7. Upload the .ipa with Transporter, with xcrun altool, or from Xcode, then install the build on your iPhone through TestFlight.

Code signing without a Mac

Signing is the step that differs most between the routes, so it helps to know what each one asks of you. All of them need an Apple Developer Program membership.

  • An App Store Connect API key is created on the App Store Connect website, under Users and Access, so any browser will do. Codemagic recommends giving the key the App Manager role and warns that the key file can be downloaded only once.
  • Codemagic: once that key is added, Codemagic’s docs say you can generate a new Apple Development or Apple Distribution certificate in its team settings and fetch provisioning profiles from the Apple Developer Portal. The docs also note that Apple limits the number of Apple Distribution certificates to 3.
  • GitHub Actions: nothing is automatic. Flutter’s fastlane steps create a distribution certificate in the Apple Developer account, select it in Xcode, and recommend fastlane’s Match to keep certificates in sync across machines. The same page recommends testing the build and deployment locally before moving to a cloud system, so plan a session on a Mac for the first setup. On the CI side the credentials go into encrypted variables.
  • A cloud Mac: you sign in to Xcode with your Apple ID and let Xcode manage signing, as on any Mac.

Testing on a real iPhone with TestFlight

Flutter’s iOS setup guide attaches the iPhone to a USB port on your Mac and says that to send your app to a physical iOS device, even for testing, you must establish trust between your Mac and the device. A PC cannot do that, and a cloud Mac sits in a data center where you cannot plug in your phone. From a PC the way onto a real iPhone is TestFlight.

The build service or the cloud Mac uploads the build to App Store Connect, and you install it with Apple’s TestFlight app. Apple says testers use the TestFlight app to view the invite and install the beta, and that you do not need to keep track of device identifiers (UDIDs) or provision tester profiles. Up to 100 members of your team can be internal testers, and you can invite up to 10,000 external testers once App Review has approved your first build for TestFlight.

For day to day work that means: Android on your PC while you write the app, the Simulator on a cloud Mac when you need to see iOS, and TestFlight for the real phone.

Which one to pick

  • A few builds a month of an app with common plugins: Codemagic, inside the free minutes.
  • Your code is on GitHub and you are comfortable writing build scripts: GitHub Actions.
  • You can get to a Mac once for the setup and want Apple’s own CI: Xcode Cloud.
  • You work on the iOS version most days, or you have to debug native code and signing in Xcode: a cloud Mac.

The same question for other frameworks, native Swift included, is answered in Xcode on Windows, and for React Native in React Native iOS build without a Mac. Every Mac we rent is on the pricing page.

Rent a dedicated M4 Mac mini

Questions

Can I build a Flutter iOS app on Windows?

Not on the Windows PC itself. Flutter’s release guide says Xcode is required to build and release the app and that you must use a device running macOS. You write the app on Windows and run the iOS build on a Mac that a CI service or a cloud Mac provider runs for you.

Can I build a Flutter iOS app for free without a Mac?

The build minutes can be free: Codemagic gives individuals 500 macOS M2 minutes a month, and GitHub does not charge for standard runners in public repositories. Signing the app and using TestFlight still need the Apple Developer Program at $99 a year.

Does Xcode Cloud work with Flutter?

Yes, with extra setup. Flutter’s docs give a script that installs Flutter and CocoaPods after Xcode Cloud clones your repository. Apple says to use Xcode for the first configuration of Xcode Cloud, so you need a Mac for that step.

Can I test a Flutter app on my iPhone from Windows?

Yes, through TestFlight. A CI service or a cloud Mac builds and uploads the app, and you install it on your iPhone with the TestFlight app. Running the app on the phone straight from your editor needs the phone attached to a Mac.

Sources

All checked on 15 November 2026.