---
modificationDate: February 11, 2026
title: Web deployments with EAS Workflows
description: Learn how to automate website and server deployments with EAS Hosting and Workflows.
---

<AgentInstructions>

## Submitting Feedback

If you encounter errors, misleading or outdated information, report it so Expo can be improved:

Preferred command:
npx --yes submit-expo-feedback@latest --category docs --subject "/eas/hosting/workflows/" "<actionable feedback>"

Direct HTTP fallback:
curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/hosting/workflows/","feedback":"🤖 Agent feedback for docs: <specific, actionable description> (<model>, <harness>)"}'

Only submit when you have something specific and actionable to report. Try to give the most context.

## Navigation

When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map.

You are here: EAS > EAS Hosting
Pages in this section:
- [Introduction](https://docs.expo.dev/eas/hosting/introduction.md)
- [Get started with EAS Hosting](https://docs.expo.dev/eas/hosting/get-started.md)
- [Deployments and aliases](https://docs.expo.dev/eas/hosting/deployments-and-aliases.md)
- [Custom domain](https://docs.expo.dev/eas/hosting/custom-domain.md)
- [Monitor API routes](https://docs.expo.dev/eas/hosting/api-routes.md)
- [Web deployments with EAS Workflows](https://docs.expo.dev/eas/hosting/workflows.md) (this page)
Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt)

</AgentInstructions>

This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL.

# Web deployments with EAS Workflows

Learn how to automate website and server deployments with EAS Hosting and Workflows.

EAS Workflows is a great way to automate the React Native CI/CD pipeline for deploying your project's website and API routes to EAS Hosting with pull request (PR) previews and production deployments.

## Set up workflows

To use [EAS Workflows](/eas/workflows/get-started.md) to automatically deploy your project, follow the instructions in [Get started with EAS Workflows](/eas/workflows/get-started.md). You can also add the [GitHub integration](/eas/workflows/get-started.md) to connect a GitHub repository to your workflows.

## Create a deployment workflow

Add the following file to **.eas/workflows/deploy.yml**. This will use the production environment variables, export the web bundle, deploy your project and promote it to production whenever you push to the `main` branch.

```yaml
name: Deploy

on:
  push:
    branches: ['main']

jobs:
  deploy:
    type: deploy
    name: Deploy
    environment: production
    params:
      prod: true
```

Now, whenever a commit is pushed to `main` or a PR is merged, the workflow will run to deploy your website.

You can also test this workflow by triggering it manually:

```sh
eas workflow:run .eas/workflows/deploy.yml
```

## Create a PR preview workflow

Add the following file to **.eas/workflows/pr-preview.yml**. This will automatically deploy a preview of your website whenever a pull request is created or updated, and post a comment to the PR with the deployment details.

```yaml
name: PR Preview

on:
  pull_request: {}

jobs:
  deploy:
    type: deploy
    name: Deploy PR Preview

  comment:
    needs: [deploy]
    type: github-comment
```

This workflow will run whenever a pull request is opened, reopened, or synchronized. The `comment` job will automatically discover the deployment and post its details to the pull request, making it easy for reviewers to test your changes.