Available GPUs

GPUs are used to accelerate workloads, and Cloud Workstations supports attachingGPUs to workstations. Cloud Workstations supports many of thevariousGPU models that are available to attach toCompute Engine VMs. The model and quantity of GPUs to attach to each workstationare specified on the workstation configuration. Cloud Workstations handlesattaching the GPUs and installing their device drivers.

Attaching GPUs to workstations will affect costs as described in theCloud Workstations pricing overview.

Limitations

A workstation configuration may specify GPUs, subject to the followinglimitations:

  • Cloud Workstations only supports GPUs for configurations that specify machinetypes in theN1 machine series, theA2 machine series, or theA3 machine series. Refer tosupported GPU models for details.
  • The configuration must specifyreplica zoneswhere the chosenGPU model is available.
  • It is not possible to configure workstations to have more than one model ofGPU attached at a time.
  • Configurations that specify A2 Ultra machine types must not specify persistent storage. Consider using an NFS-based solution such asFilestore orCloud Storage FUSE if persistent file storage is required. Note that A2 Standard machine types do support persistent storage.To create configurations without persistent storage, use the following Google Cloud CLI command:

    gcloudworkstationsconfigscreateCONFIG_NAME\--project=PROJECT_ID\--cluster=CLUSTER_NAME\--region=LOCATION\--machine-type=A2_MACHINE_TYPE\--no-persistent-storage

    Replace the following:

    • PROJECT_ID: the ID of the project that contains the workstation configuration.
    • LOCATION: the region of the workstation cluster.
    • CLUSTER_NAME: the name workstation cluster that contains the workstation configuration.
    • CONFIG_NAME: the name of the workstation configuration.
    • A2_MACHINE_TYPE: the type of the A2 machine.
  • Configurations that specify A3 machine types only support Hyperdisk persistent volumes.

  • Using Google Cloud Hyperdisk disk types is only supported on these following machine series:

    • A3
    • C3
    • C4
    • G4
    • M3
    • N4
    • N4D
    • Z3

Supported GPU models

Cloud Workstations supports many of the GPU models that Compute Engine makesavailable. The models that are supported depend on the machine series chosen forthe workstation configuration, as summarized in the following table.

N1 machine series

TheN1 general-purpose machine series supports several GPU models, and workstation configurations that specify any of the N1 machine types can also specify one of the following GPU models. For the chosen GPU model, the configuration may specify a count of how many GPU cards to attach to each workstation.

GPU modelGPU counts
NVIDIA T4 (nvidia-tesla-t4)1, 2, or 4 GPUs
NVIDIA P4 (nvidia-tesla-p4)1, 2, or 4 GPUs
NVIDIA V100 (nvidia-tesla-v100)1, 2, 4, or 8 GPUs
NVIDIA P100 (nvidia-tesla-p100)1, 2, or 4 GPUs

A2 machine series

TheA2 standard accelerator-optimized machine series has a fixed number of NVIDIA A100 GPUs attached, based solely on the chosen machine type.

The following table shows the mapping from machine type to the number of cards that will be attached.

GPU modelMachine typeGPU count
NVIDIA A100 40GB (nvidia-tesla-a100)a2-highgpu-1g1 GPU
a2-highgpu-2g2 GPUs
a2-highgpu-4g4 GPUs
a2-highgpu-8g8 GPUs
a2-megagpu-16g16 GPUs

Cloud Workstations does not support A2 ultra machine types.

A3 machine series

TheA3 Mega and A3 High accelerator-optimized machine series has a fixed number of NVIDIA H100 GPUs attached, based solely on the chosen machine type.

The following table shows the mapping from machine type to the number of cards that will be attached.

GPU modelMachine typeGPU count
NVIDIA H100 80GB (nvidia-tesla-h100)a3-highgpu-8g8 GPUs
a3-megagpu-8g8 GPUs

Google Cloud Hyperdisk Support

Some GPU workloads require very high disk throughput. To satisfy this use case, Cloud Workstations allows the use ofGoogle Cloud Hyperdisk Balanced High Availability disks as persistent directories for the machine types enumerated earlier.

Hyperdisk storage can be configured through both the Console and with thegcloud CLI.It is not possible to change the disk type after creating a Workstation configuration.

Attaching a Hyperdisk to a Workstation will affect costs as described inGoogle Cloud Hyperdisk pricing.

Add GPUs to an Existing Workstation Configuration

To add GPUs to a workstation configuration, complete the steps in one of the following tabs.

Before you begin

Select the tab for how you plan to use the samples on this page:

Console

When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.

gcloud

Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:

gcloudinit

If you're using an external identity provider (IdP), you must first sign in to thegcloud CLI with your federated identity.

Review theCloud Workstations pricingoverview to understand how your costs will be affected by configuring GPUs. Notethat GPUs are attached to the pre-started virtual machines (VMs) specifiedby a configuration'sQuick start pool size.

Updating your existing configuration

Console

Configure GPUs on an existing workstation configuration from theGoogle Cloud console, by doing the following:

  1. In the Google Cloud console, go to theWorkstation configurations page.

    Go to Workstation configurations

  2. In theWorkstation configurations list, click theName of theconfiguration to add GPUs to.

  3. On theWorkstation configuration details page, clickeditEdit.

  4. On theEdit workstation configuration page, clickMachine settingsin the navigation menu.

  5. Click the toggle to selectGPUs instead of theGeneral purposemachine family.

    In theGPU type field, select the GPU Model that you want to use.

    In theNumber of GPUs field, select the number of GPU cards you wantto attach to each workstation.

    In theMachine type field, select the machine type you want to use.

    Note: the options for each field vary depending on thereplica zones chosen for the configuration and theGPU andmachine type availability inthose zones. If you cannot find suitable GPUs in the replica zones forthis configuration, you may decide tocreate a new configuration with GPUsinstead.
  6. ClickSave to update the configuration.

gcloud

Configure GPUs on an existing workstation configuration by running thegcloud workstations configs update command.

First though, collect some information to see which GPU models areavailable and to choose one for your configuration:

  1. Check which replica zones the configuration specifies by running thefollowinggcloud CLI command:

    gcloudworkstationsconfigsdescribe\--format="table(name.scope(workstationConfigs),replicaZones.list())"\--project=PROJECT_ID\--region=LOCATION\--cluster=CLUSTER_NAME\CONFIG_NAME

    Replace the following:

    • PROJECT_ID: the ID of the project that contains the workstation configuration.
    • LOCATION: the location of the workstation cluster.
    • CLUSTER_NAME: the name workstation cluster that contains the workstation configuration.
    • CONFIG_NAME: the name of the workstation configuration.
  2. Choose a supported GPU model that is available inboth of theconfiguration's replica zones by running thegcloud compute accelerator-types list command:

    gcloudcomputeaccelerator-typeslist\--format="table(name:sort=1,zone,description,maximumCardsPerInstance)"\--filter='zone.basename()=(ZONES) AND name~"nvidia-tesla-(a100|p100|p4|t4|v100)$"'\--project=PROJECT_ID

    ReplaceZONES with a comma-separated list of thereplica zones determined in the previous step(for example,us-central1-a,us-central1-c).

    Choose a GPU model that is listed twice in the table, indicating it isavailable in both replica zones.

    Take note of the maximum cards you can attach for the chosen GPU model.

    Note: If there isn't suitableGPU Availability in thereplica zones for this configuration, you may decide tocreate a new configuration with GPUsinstead.
  3. Determine which of the supported machine types are available inbothof the configuration's replica zones using thegcloud compute machine-types list command.

    1. If you chose the NVIDIA A100 40GB GPU model in the previous step,your configuration must use the A2 machine series:

      gcloudcomputemachine-typeslist\--format="table(name,zone,guestCpus:sort=1)"\--filter="name:a2-highgpu- OR name:a2-megagpu-"\--zones=ZONES\--project=PROJECT_ID
    2. If you chose any other GPU model in the previous step, yourconfiguration must use the N1 machine series:

      gcloudcomputemachine-typeslist\--format="table(name,zone,guestCpus:sort=1)"\--filter="name:n1-standard-"\--zones=ZONES\--project=PROJECT_ID

    Choose a machine type that islisted twice in the table, indicating itis available inboth replica zones.

  4. Now that you have selected a GPU model and compatible machine type,update the configuration:

    1. For NVIDIA A100 40GB GPUs, run this command to update yourconfiguration:

      gcloudbetaworkstationsconfigsupdate\--project=PROJECT_ID\--region=LOCATION\--cluster=CLUSTER_NAME\CONFIG_NAME\--machine-type=A2_MACHINE_TYPE

      ReplaceA2_MACHINE_TYPE with the chosen A2 machinetype determined in the previous step (for example,a2-highgpu-1g).

      Note: for the A2 machine series the model and quantity of GPUs isfixed based on the machine type, so you may omit the--accelerator-type and--accelerator-count flags.
    2. For all other GPU models, run this command:

      gcloudbetaworkstationsconfigsupdate\--project=PROJECT_ID\--region=LOCATION\--cluster=CLUSTER_NAME\CONFIG_NAME\--machine-type=N1_MACHINE_TYPE\--accelerator-type=ACCELERATOR_TYPE\--accelerator-count=ACCELERATOR_COUNT

      Replace the following:

      • N1_MACHINE_TYPE: the chosen machine type from theN1 series (for example,n1-standard-2).
      • ACCELERATOR_TYPE: the chosen GPU model's name(for example,nvidia-tesla-t4).
      • ACCELERATOR_COUNT: the number of GPUs to attachto each workstation (for example,1,2,4). Must be a power of twoless than the maximum for the GPU model.

WARNING: It is not possible to switch to Hyperdisk after the Workstation configuration is created.

Create a new Workstation Configuration with GPUs

To create a new workstation configuration that attaches GPUs to workstationsthat are based on it, complete the steps in one of the following tabs.

Before you begin

Select the tab for how you plan to use the samples on this page:

Console

When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.

gcloud

Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:

gcloudinit

If you're using an external identity provider (IdP), you must first sign in to thegcloud CLI with your federated identity.

REST

To use the REST API samples on this page in a local development environment, you use the credentials you provide to thegcloud CLI.

    Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:

    gcloudinit

    If you're using an external identity provider (IdP), you must first sign in to thegcloud CLI with your federated identity.

For more information, seeAuthenticate for using REST in the Google Cloud authentication documentation.

Choose aGPU model and consult theGPU availability table to select aregion where the chosen GPU model is available in atleast two zones.

If you don't already have a cluster in the chosen region where you can create anew configuration, follow the steps toCreate a workstation cluster in the region.

Review theCloud Workstations pricingoverview to understand how your costs will be affected by configuring GPUs. Notethat GPUs are attached to the pre-started virtual machines (VMs) specifiedby a configuration'sQuick start pool size.

Creating a new configuration

Console

Create a new workstation configuration with GPUs from theGoogle Cloud console, by doing the following:

  1. In the Google Cloud console, go to theWorkstation configurationspage.

    Go to Workstation configurations

  2. On theWorkstation configurations page, clickadd_boxCreate.

  3. On theBasic information step of theCreate workstation configuration page, specify a name for yourconfiguration in theName field.

    In theWorkstation cluster field, select a cluster in the chosenregion.

    Tip: GPUs are also attached toQuick start workstations. You can keepcosts down by selectingDisabled.

    ClickContinue to advance to theMachine settings step.

  4. On theMachine settings step of theCreate workstationconfiguration page, begin by clicking the toggle to selectGPUsinstead of theGeneral purpose machine family.

    1. Then, in theZones field, select the checkboxes next to two zoneswhere the GPU model you chose is available (see theGPU availability table).

    2. In theGPU type field, select the GPU Model that you want to use.

    3. In theNumber of GPUs field, select the number of GPU cards youwant to attach to each workstation.

    4. In theMachine type field, select a compatible machine type.

  5. Optional: This feature is not yet supported in the UI. See thegcloud instructions to use the CLI to configure this feature.

  6. ClickContinue to configure the Environment settings and Identity and Access Management (IAM) policybefore clickingCreate to provision the new workstationconfiguration.

gcloud

Create a new workstation configuration with GPUs using thegcloud CLI, by running thegcloud workstations configs create command.

NVIDIA GPU device drivers

Cloud Workstations installs the NVIDIA device drivers on workstations' host VMsduring VM startup.

To determine which version device driver has been installed on a workstation,run the following command:

nvidia-smi--query-gpu=name,driver_version--format=csv

GPU availability by region and zone

You can search either by location or GPU model, or a combination ofboth.

ZonesLocationGPU platforms
asia-east1-aTaiwanP100, T4
asia-east1-bTaiwan
asia-east1-cTaiwanH100, P100, T4, V100
asia-east2-aHong KongT4
asia-east2-bHong Kong
asia-east2-cHong KongT4
asia-northeast1-aTokyoA100 40GB, T4
asia-northeast1-bTokyoH100
asia-northeast1-cTokyoA100 40GB, T4
asia-northeast3-aSeoulA100 40GB, H100
asia-northeast3-bSeoulA100 40GB, T4
asia-northeast3-cSeoulH100, T4
asia-south1-a
asia-south1-b
MumbaiT4
asia-south1-cMumbaiH100
asia-southeast1-aSingaporeT4
asia-southeast1-b
asia-southeast1-c
SingaporeA100 40GB, H100, P4, T4
australia-southeast1-aSydneyP4, T4
australia-southeast1-bSydneyP100, P4
australia-southeast1-cSydneyH100, T4
australia-southeast2-a
australia-southeast2-b
australia-southeast2-c
Melbourne
europe-central2-aWarsaw
europe-central2-b
europe-central2-c
WarsawT4
europe-north1-a
europe-north1-b
Finland
europe-north1-cFinlandH100
europe-southwest1-a
europe-southwest1-b
europe-southwest1-c
Madrid
europe-west1-bBelgiumH100, P100, T4
europe-west1-cBelgiumH100, T4
europe-west1-dBelgiumP100, T4
europe-west12-a
europe-west12-b
Turin
europe-west2-aLondonT4
europe-west2-bLondonH100, T4
europe-west2-cLondon
europe-west3-aFrankfurtH100
europe-west3-bFrankfurtT4
europe-west3-cFrankfurtH100
europe-west4-aNetherlandsA100 40GB, P100, T4, V100
europe-west4-bNetherlandsA100 40GB, H100, P4, T4, V100
europe-west4-cNetherlandsH100, P4, T4, V100
europe-west6-a
europe-west6-b
europe-west6-c
Zurich
europe-west8-a
europe-west8-b
Milan
europe-west8-cMilanH100
europe-west9-a
europe-west9-b
Paris
europe-west9-cParisH100
me-central2-a
me-central2-b
me-central2-c
Dammam
me-west1-aTel AvivA100 40GB
me-west1-bTel AvivT4
me-west1-cTel AvivA100 40GB, T4
northamerica-northeast1-a
northamerica-northeast1-b
MontréalP4
northamerica-northeast1-cMontréalP4, T4
southamerica-east1-aSão PauloT4
southamerica-east1-bSão Paulo
southamerica-east1-cSão PauloT4
southamerica-west1-a
southamerica-west1-b
southamerica-west1-c
Santiago
us-central1-aIowaA100 40GB, H100, P4, T4, V100
us-central1-bIowaA100 40GB, H100, T4, V100
us-central1-cIowaA100 40GB, H100, P100, P4, T4, V100
us-central1-fIowaA100 40GB, P100, T4, V100
us-east1-bSouth CarolinaA100 40GB, P100
us-east1-cSouth CarolinaP100, T4, V100
us-east1-dSouth CarolinaT4
us-east4-a
us-east4-b
us-east4-c
Northern VirginiaH100, P4, T4
us-east5-aColumbusH100
us-east5-b
us-east5-c
Columbus
us-west1-aOregonH100, P100, T4, V100
us-west1-bOregonA100 40GB, H100, P100, T4, V100
us-west1-cOregon
us-west4-aLas VegasH100, T4
us-west4-bLas VegasA100 40GB, T4
us-west4-cLas Vegas

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.