Short answer: run eas build --platform ios --local (or --platform android) in your Expo project. EAS runs the same build steps on your machine instead of Expo's servers and leaves an IPA, APK or AAB in your project folder. iOS builds need a Mac with Xcode. Local builds don't use your hosted build quota.
What you need
- Node and EAS CLI:
npm install -g eas-cli, theneas login. - For iOS: a Mac with Xcode and its command line tools, CocoaPods and fastlane.
- For Android: a JDK and the Android SDK and NDK, with
ANDROID_HOMEset. - An
eas.jsonwith at least one build profile.
Running a build
# iOS release build using the "production" profile
eas build --platform ios --profile production --local
# Android
eas build --platform android --profile production --local
EAS CLI still handles credentials. With remote credentials it downloads your distribution certificate and provisioning profile from Expo for the build; with credentialsSource: "local" it reads them from credentials.json.
When the build finishes, the path of the artifact is printed. Submit it with eas submit --platform ios --path ./build.ipa, or upload it yourself.
What local builds don't support
Expo's documentation lists these limits:
- One platform at a time.
--platform allis not available. - No build cache.
- EAS environment secrets aren't injected. Set them as environment variables on your machine.
- Tool versions in
eas.jsonare ignored. Fields such asnode,yarn,cocoapods,ndkandimagedescribe Expo's hosted machines. Locally you get whatever is installed, so keeping Xcode and Node up to date is your job.
When local builds make sense
| Situation | Hosted EAS Build | Local build |
|---|---|---|
| No Mac available | Works | iOS not possible |
| Occasional builds | Simple, within the free tier | More setup than it's worth |
| Many builds a day | Queue time and usage add up | Starts at once, no usage fees |
| Debugging a failing build | Read logs after the fact | Inspect the machine directly |
| Signing keys must stay on your hardware | Stored with Expo | Possible with local credentials |
The usual pattern for a team is a shared Mac, often a Mac mini, that everyone builds on. What is missing from plain eas build --local on that Mac is everything around the build: a queue, logs your teammates can read, somewhere to download the result and a way to send it to the stores.
Running EAS local builds for a team
VenelX Studio wraps that workflow. It detects Expo projects on the Mac, runs EAS local builds or plain Xcode and Gradle builds from a browser, queues them per Mac and streams the logs. Finished builds can be shared with an install link or sent to TestFlight and Google Play, and Studio reads the submit profiles in your eas.json to fill in tracks and app IDs.
You don't have to choose one or the other. Many Expo teams keep hosted EAS for EAS Update and the occasional build, and move the daily volume to a Mac they own. For a fuller comparison, see VenelX Studio vs EAS Build.