Free plan billing period
For the Free plan, the billing period starts on the first day of the calendar month.
Expo & React Native · all subjects
billing
34 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
Paid plan billing period
For all paid plans, the billing period starts from the subscription date of that plan.
Free plan free credits not transferable
Free plan credits cannot be transferred to another subscription plan. All paid plans provide credits to enable priority builds for EAS Build and broader access to EAS Update through more monthly active users and extra bandwidth.
Cannot downgrade paid plan to use free credits
If you are subscribed to a paid plan and use up your included EAS Build credits, additional builds are billed using usage-based pricing. You cannot downgrade to the Free plan to use the free build credits instead. If you cancel your subscription, the Free plan will take effect after your current billing period ends, and then you can use the Free plan's monthly quota subject to its limits and reset schedule.
Update billing information only reflects on next invoice
Updating billing information will only be reflected on the next invoice, not on the last invoice.
Annual payment available for Enterprise plans
Annual plans are available for Enterprise plan customers. Contact Expo for more information.
ACH or wire transfer payment for Enterprise annual plans
Enterprise plan customers on annual plans can pay by ACH (Automated Clearing House) as an alternative to credit card payments. Contact Expo for more information.
Expo does not store card information
Expo does not store card information. Stripe handles the payment system and stores payment information. See Stripe's security documentation for details on how Stripe handles security.
Reduce EAS Build usage with EAS Update and fingerprinting
Use EAS Update and development builds to test and deploy new code without creating a new build. For JavaScript-only changes, use a fingerprint via EAS Workflows to skip creating a new build and publish updates through EAS Update instead. This reduces the need for additional builds since JavaScript code changes more frequently than native code.
Refund request process
If a user subscribes to a plan from the wrong account, they can go to Receipts in the wrong account and initiate a request for a refund.
View usage estimate for next bill
To estimate the next bill, go to Billing and see the Usage section, which provides a summary of EAS Build usage based on resource class, EAS Update usage based on monthly active users and global edge bandwidth, and the amount spent for both.
Production plan features and pricing
The Production plan is designed for professional developers and small businesses. It provides reliable, production-grade services, monthly credits for high-priority builds on EAS Build, and higher limits for unique users, bandwidth, and storage for EAS Update. Exceeding limits or using up monthly credits results in usage-based pricing.
Enterprise plan features
The Enterprise plan is designed for organizations and enterprises with large projects requiring additional resources and dedicated support. It provides reliable, production-grade services, significantly higher monthly credits for high-priority builds on EAS Build compared to other plans, and higher limits for unique users, bandwidth, and storage for EAS Update. Exceeding limits or credits results in usage-based pricing.
EAS free access limits
Expo Application Services (EAS) offers free access to a limited quantity of low-priority builds on EAS Build and free updates with EAS Update. These free limits reset monthly.
Paid plans include credits for priority builds
Beyond the Free plan, paid subscription plans offer credits to enable priority builds for EAS Build and broader access to EAS Update through more monthly active users and extra bandwidth.
Subscriptions billed monthly worldwide
Subscriptions are billed monthly and are priced the same worldwide (pre-tax). Current plan details can be viewed at https://expo.dev/settings/billing under the Current Plan section.
Subscriptions can be cancelled anytime
Subscriptions can be cancelled at any time. Detailed cancellation information is available in the Manage Plans documentation.
Annual contracts available
Expo offers annual contracts on an as-needed basis. Customers should contact their customer support team to determine if an annual plan is suitable for their needs.
Exceeding plan limits triggers usage-based billing
Each paid plan has specific limits. Subscribers can exceed these limits and pay for additional usage through usage-based billing.
Starter plan pricing and credits
The Starter plan costs $19 per month and provides $45 of build credit for priority builds. It offers reliable, production-grade services, monthly credits for high-priority EAS Build, and the ability to exceed Free plan limits for EAS Update with usage-based pricing for overages.
Enterprise Support add-on features
The Enterprise Support add-on is available exclusively for new Enterprise plan subscribers, subject to availability. Key features include professional long-term support from Expo experts, direct communication channel support with a Service-Level Agreement (SLA), and a dedicated account manager.
Usage-based billing enabled for EAS Build and EAS Update
Expo applies usage-based billing for customers who exceed their plan allowances. Usage-based billing is enabled for EAS Build and EAS Update and is billed monthly. An estimate of existing usage and any overage charges is provided on the account's Billing page at expo.dev/settings/billing.
EAS Build pricing model and credits
For EAS Build, a flat fee is charged for an individual build executed at higher-priority levels, totaled monthly and charged at the end of the billing period or sooner if the plan is canceled. Builds that are canceled before any work is done are not charged. Starter, Production, Enterprise, and Legacy plan subscribers receive credits for EAS Build that can offset build costs. These credits are reset at the start of each billing period and expire at the end of that billing period.
EAS Build credit exceeded example (Production plan)
Example: A Production plan account with 20 medium Android builds at $1 each ($20), 10 large Android builds at $2 each ($20), 30 medium iOS builds at $2 each ($60), and 40 large iOS builds at $4 each ($160) equals $260 total. With the EAS Build Credit of $225 included, the subscriber pays $35 for 100 builds instead of $260.
EAS Update pricing comprises monthly active users and global edge bandwidth
Usage-based pricing for EAS Update comprises two metrics: monthly active users (MAU) and global edge bandwidth. Updated users reflect the number of unique users who download at least one update in a billing period. Global edge bandwidth represents the total bandwidth used beyond the subscription plan's base bandwidth allocation. If monthly active users exceed the plan's base MAU allocation, 40 MiB of global edge bandwidth is included for each additional user. A monthly active user counts only once per billing period regardless of how many updates they download. A user is considered a unique installation of an app on a device.
EAS Update usage example (Starter plan)
Example: A Starter plan subscriber deploys 20 updates of 5 MiB each to 10,000 users. The plan includes 3,000 monthly active users and 100 GiB per month. Overage charges are: 7,000 updated users at $0.005 per user = $35, and 603.13 GiB global edge bandwidth at $0.10 per GiB = $60.31, for a total of $95.31. Bandwidth calculation: 20 updates × 5 MiB × 10,000 users = 976.5625 GiB total used. Subtract 100 GiB included in plan and 273.4375 GiB included with 7,000 extra updated users (7,000 × 40 MiB) = 603.125 GiB billable.
EAS Update pricing for additional updates in same billing period
If a subscriber sends an additional update in the same billing period, they only pay for extra bandwidth used, not for additional monthly active users. Monthly active users are counted uniquely per billing period. Example: Sending a 21st update of 5 MiB to 10,000 users results in 1,025.39 GiB total bandwidth used. After subtracting the 100 GiB plan allocation and 273.4375 GiB for 7,000 extra users, 651.95 GiB is billable at $0.10 per GiB = $65.20.
Production plan EAS Update allocation
The Production plan includes 50,000 monthly active users and 1 TiB (1024 GiB) of bandwidth per month. This is sufficient for many applications before incurring overage charges.
Billing usage estimates may be delayed up to 24 hours
Billing estimates shown in the dashboard may be delayed by up to 24 hours (one day).
Monitor EAS Build and EAS Update usage in dashboard
To see the current billing period's usage summary, go to Billing > Usage at expo.dev/settings/billing. The usage summary displays information for EAS Build, EAS Update, and other services. Detailed EAS Build usage shows builds count and executed builds by platform and resource class. Detailed EAS Update usage shows updated users and global edge bandwidth details. Both detailed views allow viewing current or previous billing period data.
Usage notifications for EAS Build credit thresholds
Expo sends email notifications to account Owners and Admins when an account reaches 80% and 100% of the plan's included EAS Build credits. These notifications are enabled by default and can be managed from the Email notifications page in the EAS dashboard at expo.dev/settings/billing.
Optimize build usage with EAS Update and development builds
EAS Update and development builds can be used to test and deploy new code without creating an entirely new build, enabling faster iteration and reduced build usage. JavaScript code typically changes more frequently than native code; using EAS Update for JavaScript changes instead of building reduces unnecessary build usage. When using CI/CD for pre-production builds, automate building only when native code changes by using Expo Fingerprint to detect changes and only execute a build if native code has changed, otherwise publish an update.
Reduce development build count with shared testing builds
A development build can run any EAS Update that is compatible with its native runtime. When using EAS Update with multiple testing channels, testers or test devices can use the same development build, reducing the need for creating additional builds.
Optimize EAS Update bandwidth usage with asset selection
Assets can be included or excluded when using EAS Update to reduce the number of assets uploaded or downloaded from the updates server and global edge bandwidth used. Exclude assets that haven't been modified, such as unchanged images or videos. Excluded assets won't be uploaded to the update server and won't be downloaded by the app, but assets not part of an update must be included in the native build. If an app has already downloaded an asset that is part of a new update, the app will not re-download that asset and it will not add to bandwidth usage. Use `npx expo-updates assets:verify <dir>` to verify all required assets are included in the update.