This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.
Deploy your first Expo Router and React app
Edit page
Learn how to deploy your Expo Router and React apps to Expo Hosting.
Deploy your first web app with an AI agent
Paste this into Claude, Cursor, Codex, or another agent.
Deploy the web version of my Expo Router project to Expo Hosting. Use https://docs.expo.dev/eas/hosting/get-started.md as the source for each command. 1. Check that EAS CLI is installed and up to date. If it is not, run `npm install -g eas-cli`. 2. Check that I am logged in with `eas whoami`. If I am not, stop and ask me to run `eas login` or to set `EXPO_TOKEN`. Do not print a token. 3. If the project does not have an Expo Services project ID, ask me before you run `eas init`. 4. Read `web.output` in the app config. If it is not set, ask me to choose `single`, `static`, or `server`, and set it. The `server` output is for projects with API routes or server functions. 5. Run `npx expo export --platform web`. The command writes the export to the dist directory. 6. Ask me for a preview subdomain name, for example `my-app` for `https://my-app.expo.app`. Run `eas deploy --non-interactive --dev-domain <name>`. If the command says that the preview URL is already set, run `eas deploy --non-interactive` without `--dev-domain`. If the command says that the name is taken, ask me for another name. 7. Do not run `eas deploy --prod` unless I ask for a production deployment. 8. Give me the deployment URL and the dashboard link from the command output. Tell me which commands you ran.
Expo Hosting is a react hosting service that allows you to deploy an exported Expo web build to a preview or production URL.
This guide will walk you through the process of creating your first web deployment.

Set up Expo Hosting for your Expo Router web project, create your first deployment, and get a preview URL up and running.
2 requirements
2 requirements
1.
Expo Hosting is available to anyone with an Expo account, regardless of whether you pay for Expo Services or use the Free plan. You can sign up at expo.dev/signup.
Paid subscribers can create more deployments, have more bandwidth, storage, and requests, and may set up a custom domain. Learn more about different plans and benefits at Expo pricing.
2.
Don't have a project yet? It's quick and easy to create a "Hello world" app you can use with this guide. Run the following command to create a new project:
1
Install the latest EAS CLI
EAS CLI is the command-line app you will use to interact with Expo Services from your terminal. To install it, run the command:
You can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version.
We recommend using
npminstead ofyarnfor global package installations. You may alternatively usenpx eas-cli@latest. Remember to use that instead ofeaswhenever it's called for in the documentation.
2
3
Prepare your project
For your app config file's expo.web.output, decide whether to set it to either single, static, or server.
single: Exports your Expo app to a single-page app with only oneindex.htmloutputstatic: Exports your Expo app to a statically generated web appserver: Supports server functions and API routes as well as static pages for your app
Don't worry if you're not sure which output mode you need, you can always change this value later and re-deploy.
4
Now publish your website to Expo Hosting:
The first time you run this command, it will:
- Prompt you to connect an Expo Services project if you haven't done so yet
- Ask you to choose a preview subdomain name
A preview subdomain name is a prefix used for the preview URL of your app. For example, if you choose
my-appas your preview subdomain name, your preview URL would look something like this:https://my-app--or1170q9ix.expo.app/, and your production URL would be:https://my-app.expo.app/.
Once your deployment is complete, the CLI will output a preview URL for where your deployed app is accessible, as well as a link to the deployment details on the Expo dashboard.