Text of docs.cloud.google.com › shell › docs › quotas-limits as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Cloud Shell Quotas and limits | Google Cloud Documentation

Skip to main content Console English Deutsch Español Español – América Latina Français Indonesia Italiano Português Português – Brasil עברית 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in Cloud Shell Start free Home Documentation Application development Cloud Shell Resources Stay organized with collections Save and categorize content based on your preferences. Cloud Shell Quotas and limits Cloud Shell uses quotas and system limits to maintain fair resource allocation, prevent service overloads, and help you manage resource use.

Quotas and system limits are similar but differ in the following ways: Quotas have default values, but you can typically request adjustments. System limits are fixed values that can't be changed. Google Cloud uses quotas to help maintain fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components.

For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources. The Cloud Quotas system does the following: Monitors your consumption of Google Cloud products and services Restricts your consumption of those resources Provides a way to request changes to the quota value and automate quota adjustments In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.

Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses. For more information, see the Cloud Quotas overview . There are also system limits on Cloud Shell resources. System limits can't be changed. To adjust most quotas, use the Google Cloud console.

For more information, see Request a quota adjustment . Usage quotas The default weekly Cloud Shell quota is 50 hours. This quota resets every 7 days. Viewing your weekly Cloud Shell quota and reset schedule If you reach your quota, you'll need to wait until the date and time specified before you can use Cloud Shell again. To view your weekly quota and reset schedule within Cloud Shell: Click Session information and then click Usage quota .

A dialog appears and displays the hours remaining in your quota, the total number of hours in your quota, and the date and time that the quota resets. If you need more quota, we strongly recommend upgrading to Cloud Workstations , which does not have weekly usage limitations. Cloud Workstations lets you customize, rightsize and secure your development environment. Upgrade to Cloud Workstations for managed secure development environments provisioned in your VPC without usage limits.

If you're using Cloud Shell to work with the Google Cloud CLI, you can install and use the Google Cloud CLI on your local machine to avoid Cloud Shell limits. Cloud Shell inactivity To prevent your $HOME directory from being deleted due to inactivity for 120 days, start a session. For sensitive data you want to store long term, consider a different solution on Cloud Storage . Non-interactive usage Cloud Shell is intended for interactive use only.

Non-interactive sessions are ended automatically after 40 minutes. Cloud Shell sessions are capped at 12 hours, after which sessions automatically terminate. You can start a new session immediately after. Restoring a session after a service limit violation If your session is terminated and can't be re-established because you violated a service limit or the terms of service, Cloud Shell displays an error with additional information about the restriction.

To appeal a restriction, visit Google Cloud console Support to open an appeal ticket with details on your workload. Limitations and restrictions Custom installed software packages and persistence The virtual machine instance that backs your Cloud Shell session isn't permanently allocated to your Cloud Shell session and terminates if your session is inactive for 40 minutes. After the instance is terminated, any modifications that you made outside your $HOME directory are lost.

To have your configurations persist across sessions, consider customizing your environment . Users younger than 18 or whose age is unknown Cloud Shell isn't available to users younger than 18 or whose age is unknown. By default, Google Workspace for Education blocks access to Cloud Shell for all users. If your institution has students older than 18 who you want to have access to age-restricted services including Cloud Shell, see Control access to Google services by age for steps to identify users who are 18 years or older.

Cloud Shell Editor extensions Cloud Shell Editor does not support the installation of custom editor extensions. However, the Cloud Shell Editor comes with a set of essential extensions already installed and kept up-to-date. .bashrc content Cloud Shell can produce errors if the .bashrc file is modified or deleted. The .bashrc file must contain the following lines: if [ -f "/google/devshell/bashrc.google" ]; then source "/google/devshell/bashrc.google" fi gcloud output formatting By default, Cloud Shell enables gcloud accessibility features .

With accessibility features enabled, gcloud table output is rendered as a flattened list of items. To restore the default behavior of boxed tables for many commands, append the following command to the end of your $HOME/.bashrc file: gcloud config set accessibility/screen_reader false Slow connection performance Connecting to a Cloud Shell for the first time involves creating your home disk and can take up to 25 seconds.

Subsequent connections to existing virtual machine instances take about five seconds. However, if you haven't used Cloud Shell for a week, connection performance will be slower since the home directory is restored from an archive. Cloud Shell also offers Ephemeral mode which is the Cloud Shell experience without persistent disk storage. Ephemeral mode offers faster connection performance but all the files you create in your session are lost on session end.

Corporate proxies, firewalls, and SSL inspection If your enterprise network uses forward proxies, firewalls, or security solutions such as Zscaler that perform active SSL inspection and TLS decryption, your Cloud Shell terminal connection might fail with a timeout, or stop responding when it gets to Connecting to your Cloud Shell instance . To ensure uninterrupted connectivity, your network administrator must configure firewalls and forward proxies to permit bidirectional WebSocket traffic to port 443 for the endpoint *.cloudshell.dev and exempt Cloud Shell relay endpoints from SSL inspection.

Browser support Cloud Shell supports the latest versions of Google Chrome, Mozilla Firefox, Microsoft Edge, Microsoft Internet Explorer 11+, and Apple Safari 8+. Safari in private browser mode is not supported. Private browsing and disabled third-party cookies The Cloud Shell Editor can't load in Cloud Shell if third-party cookies are disabled. Some browsers have third-party cookies disabled by default and most browsers' Incognito or Private Browser modes block these cookies as well.

With third-party cookies disabled, you can still use the Cloud Shell Editor in its own window by clicking the Open in New Window button accessible when you open an editor session . Alternatively, you can navigate to port 970 using the Web Preview . Tip: If you're using Google Chrome, you can enable third-party cookies by clicking the Third-party cookie blocking icon in your address

The rest of this page is on the live site.