EAS Build pricing in 2026: free builds, credits and what $19 buys

EAS Build pricing looks simple on the plan cards and gets harder once you read the small print about credits, build sizes and concurrency. This guide lays out what each Expo plan includes for builds, what a build costs after the credit runs out, and a few worked examples. Every price and limit below is as listed on expo.dev/pricing and docs.expo.dev on November 4, 2026. Expo changes these pages, so check them again before you decide.

A note on names

Expo's pricing page now says Expo Build, Expo Submit, Expo Update and Expo Workflows. The CLI is still eas-cli and most guides still say EAS. Expo Build (EAS Build) is the same product under both names.

The plans

Plan	Price	Builds	Queue, timeout and extras	Concurrency
Free	$0	15 Android and 15 iOS builds a month	Low priority queue, 45 minute timeout	5, up to 1 on macOS
Starter	$19/month plus usage	$45 of build credit	High priority, large workers, 2 hour timeout	5, up to 2 on macOS ($50 per extra, up to 5 extra)
Production	$199/month plus usage	$225 of build credit	SSO, priority support	15, up to 10 on macOS
Enterprise	Custom	Build credit starting at $1,000	Enterprise Support add-on	20, up to 15 on macOS

Every plan lists unlimited members. No annual price was shown on November 4, 2026. Expo's billing docs say the Free plan "cannot incur overage charges", so on Free you stop when the builds run out instead of getting a bill.

What a build costs after the credit

On paid plans, builds past the included credit are charged per build, by platform and worker size:

Platform	Medium worker	Large worker
Android	$1 per build	$2 per build
iOS	$2 per build	$4 per build

Expo Workflows, its CI, is billed per minute: Linux medium $0.018 and large $0.035, macOS medium $0.075 and large $0.150.

Credits do not roll over

Expo's usage based pricing docs say credits "reset at the start of the billing period and expire at the end of that billing period". A quiet month does not bank credit for a busy one. Plan around your busiest release month, not your average.

Worked examples

These are simple sums with the listed prices. They assume the credit is spent at the per build rates above. Your real bill depends on worker sizes, retries and how Expo counts each build, so treat them as estimates.

Solo developer, one app

If you build 10 iOS and 10 Android test builds a month, Free covers it at $0. The cost is time: Free builds use the low priority queue, and only one macOS build runs at a time. Our guide to builds stuck in the queue covers that part.

Small team on Starter

If every build were an iOS build on a medium worker at $2, $45 of credit would cover about 22 builds. On large workers at $4, about 11. If you do 30 iOS medium builds a month, that is $60 of builds, so about $15 past the credit, plus the $19 plan, about $34 in total. Add Android builds at $1 or $2 each on top.

When concurrency is the real cost

Starter runs up to 2 macOS builds at once. A third costs $50 a month, more than the plan itself. If your team often waits for iOS builds, check whether the wait is the queue or your own concurrency before you buy more.

Updates are priced separately

Expo Update (over the air updates) is priced by monthly active users: 1,000 on Free, 3,000 on Starter, 50,000 on Production, then $0.005 per extra user and $0.10 per GiB of bandwidth. If you ship updates to many users, that line can grow faster than builds. AppForShare does not host over the air updates, so this is not a cost we replace.

Where else the money goes

A build is only the first step. After it, a team still needs to get the build to testers, collect devices for iPhones, take feedback, check the build before the store, and handle the store listing and release. Expo covers some of this: internal distribution gives each build a link that is open for anyone with the URL, Expo Submit uploads to App Store Connect and Google Play, and Workflows can add TestFlight groups.

AppForShare is the layer after the build. It does not build apps on its own machines and it does not host updates. As listed on our pricing page:

AppForShare plan	Price	What EAS users usually add it for
Free	$0	Password protected links, feedback with screenshots, readiness check with Expo checks
Pro	$12/month	Channel link that always opens the newest build, Connect Expo webhook, CLI and CI uploads, iPhone onboarding link, store upload to TestFlight or a Play testing track
Team	$39/month, 5 seats, $6 per extra seat	Tester groups, access codes, private projects, TestFlight feedback in the inbox, Play crash and ANR rates, Play production drafts

One honest point: Expo lists unlimited members on every plan, including Free. AppForShare Free and Pro have 1 seat, and Team has 5. If your team wants many people in the dashboard at no cost, Expo is ahead there.

Ways to spend less on builds

• Ship JavaScript changes as updates. If only JavaScript changed and the runtime version is the same, an Expo Update can reach testers without a new build.
• Build one platform. If a fix only touches iOS, run --platform ios, not all.
• Build on your own machine. eas build --local runs the build on your computer. Expo's docs note no caching, no Expo secret environment variables and one platform at a time.
• Build on GitHub Actions. AppForShare GitHub builds (Pro and Team) have an Expo preset that runs npx expo prebuild and builds on your own GitHub Actions minutes. GitHub bills those minutes under your own GitHub plan. See GitHub Actions builds.

More for EAS teams: sharing eas build --local output and Expo EAS alternatives.

Common questions

Is EAS Build free?

The Free plan includes 15 Android and 15 iOS builds a month on a low priority queue, as listed on November 4, 2026. It cannot run up overage charges.

What does $19 buy?

Starter is $19 a month plus usage. It includes $45 of build credit, high priority builds, large workers, a 2 hour timeout and 3,000 update users.

Do unused credits carry over?

No. Expo's docs say credits expire at the end of each billing period.

Can I keep EAS Build and still use AppForShare?

Yes. Most EAS users keep building there and send internal builds to AppForShare. See AppForShare vs Expo EAS and the Expo internal distribution guide.

If your EAS plan already covers your builds, the cheaper fix may be on the sharing side. Create a free AppForShare account and upload your next EAS build to see the install page.