> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Regions

> Three regions to deploy in. How to pick one for your audience.

Streampixel runs in three regions. Each project lives in one region, picked when you create the project. Pick the region closest to most of your viewers — distance is the single biggest factor in how responsive the stream feels.

## Available regions

| Region       | Code           | Best for      |
| ------------ | -------------- | ------------- |
| US-East-1    | `us-east-1`    | North America |
| Europe       | `europe`       | EMEA          |
| Asia Pacific | `asia-pacific` | APAC          |

<Info>
  Region is set when you create a project and can't be changed in place. To move a project, create a new one in the target region and re-upload your build.
</Info>

## Choosing a region

| Your audience                       | Recommended region                              | Typical latency |
| ----------------------------------- | ----------------------------------------------- | --------------- |
| US / Canada / Mexico                | `us-east-1`                                     | 20–80 ms        |
| UK / EU / Africa / Middle East      | `europe`                                        | 20–80 ms        |
| India / SE Asia / Japan / Australia | `asia-pacific`                                  | 30–120 ms       |
| Globally distributed                | Pick the region closest to your largest segment | varies          |

<Tip>
  For globally distributed audiences, the simplest pattern is one project per region. Route viewers to the right share URL based on their location.
</Tip>

## What's shared across regions

Your account, dashboard, REST API, and billing are all global — same login and credentials no matter which region a project is in.

What's not shared: stream traffic, builds, and worker capacity all live in the project's region. A regional outage only affects projects in that region.

<Warning>
  There's no automatic cross-region failover today. If you need redundancy, run parallel projects in two regions and pick the right one client-side.
</Warning>

## Moving a project to a different region

<Steps>
  <Step title="Create a new project">
    In the dashboard, create a new project and pick the target region.
  </Step>

  <Step title="Re-upload your build">
    Submit the same `.zip` to the new project — via dashboard or [Upload File API](/resources/api-reference/upload-file-api).
  </Step>

  <Step title="Update embed URLs">
    Switch your iframe `src` or Web SDK `appId` to point at the new project.
  </Step>

  <Step title="Decommission the old project">
    Once traffic is fully cut over, delete the old project from the dashboard.
  </Step>
</Steps>

If you need help moving a production project — including preserving share URLs — contact support.

## Next steps

<CardGroup cols={2}>
  <Card title="Configuring your project" icon="sliders" href="/resources/quick-start-guide/configuring-your-project">
    Set worker counts, codecs, and timeouts.
  </Card>

  <Card title="Codec settings" icon="film" href="/resources/quick-start-guide/codec-settings">
    Pick the right codec for your audience and content.
  </Card>

  <Card title="Session lifecycle" icon="play" href="/resources/concepts/session-lifecycle">
    What happens when a region's worker pool is full.
  </Card>

  <Card title="Quickstart" icon="bolt" href="/resources/get-started/quickstart">
    Create your first project end-to-end.
  </Card>
</CardGroup>