Skip to main content

Region selection

Cloud Run is in Alpha, which means APIs may change in any version and documentation is not yet finished. See the changelog to stay up to date with breaking changes.

import {GcpRegionList} from '../../components/cloudrun/regions.tsx';

Before going live with Remotion Cloud Run, you need to think about into which GCP region you are deploying your service and bucket (which will hold your sites and renders).

This document explains how to select a region and which considerations you need to make.

Available regions​

The following GCP regions are available:

You can call getRegions() or type npx remotion cloudrun regions to get this list programmatically.

Default region​

The default region is us-east1.

Selecting a region​

There are 3 ways to select a region:

  • When using the Node.JS APIs, you have to pass the region explicitly to each function. Make sure your projects satisfy the Typescript types or follow the documentation.

  • When using the CLI, you can set the region using the REMOTION_GCP_REGION environment variable. It's best to put it in a .env file so you don't forget it sometimes.

  • You can also pass the --region flag to all CLI commands to override the region. The flag takes precedence over the environment variable.

info

The REMOTION_GCP_REGION environment variable and --region flag do not have an effect when using the Node.JS APIs. You need to pass a region explicitly.

If you don't set a region, Remotion will use the default region.

Which region should I choose?​

Note that each region falls into one of two different pricing tiers. Some regions also offer low CO2 intensity electricity usage. The full list of regions per tier is available in the Cloud Run Docs.

Other considerations​

  • The Cloud Run service and Cloud Storage bucket should be in the same region to eliminate latency across datacenters.