Stay organized with collections
Save and categorize content based on your preferences.
This page describes the quotas and limits of Filestore.
Number of instances
The number of instances you can create is limited only by the amount of
Filestore quota for a given project and region as well as the minimum
file share capacity. For example, if you have 32 TiB of quota in a given
region, you can create 32 instances each with 1 TiB of capacity. To see
your available per project, per region quota, go to
the Quotas page.
Number of snapshots
Service tier
Maximum recommended number of snapshots per instance
Basic HDD
Not supported
Basic SSD
Not supported
Zonal
240
Regional
240
Enterprise
240
Number of clients
Maximum number of client connections for instances
2,000 connections per 1 TiB Scales in increments of 500 for up to 19,500 connections per instance
100 connections per 1,000 purchased IOPS
Zonal (10 TiB to 100 TiB) (previously high scale SSD)
8,000 connections per 10 TiB Scales in increments of 2,000 for up to 80,000 connections per instance
100 connections per 1,000 purchased IOPS
Regional (1 TiB to 9.75 TiB)
2,000 connections per 1 TiB Scales in increments of 500 for up to 19,500 connections per instance
100 connections per 1,000 purchased IOPS
Regional (10 TiB to 100 TiB)
8,000 connections per 10 TiB Scales in increments of 2,000 for up to 80,000 connections per instance
100 connections per 1,000 purchased IOPS
Enterprise
2,000 connections per 1 TiB Scales in increments of 500 for up to 20,000 connections per instance
Custom performance not supported
Number of VPC networks used with Filestore
You can create Filestore instances on no more than 49 unique VPC
networks, even if previously used networks are deleted. If you think that you've
reached this limit, see the troubleshooting guide topic on
error code 13
for possible solutions.
File share capacity
Service tier
Capacity
Basic HDD
1 TiB to 63.9 TiB
Basic SSD
2.5 TiB to 63.9 TiB
Zonal with a lower capacity range
1 TiB to 9.75 TiB
Zonal with a higher capacity range
10 TiB to 100 TiB
Regional with a lower capacity range
1 TiB to 9.75 TiB
Regional with a higher capacity range
10 TiB to 100 TiB
Enterprise
1 TiB to 10 TiB
Enterprise instances combined with the Filestore
multishares feature can support a minimum share capacity of 10 GiB.
Approximately 89,000,000 files per 1 TiB of capacity
Regional
Approximately 89,000,000 files per 1 TiB of capacity
Enterprise
Approximately 89,000,000 files per 1 TiB of capacity
The number of files listed is an indication of the maximum number of supported
connections to small or empty files. The number of supported file connections
decreases as file size increases.
While no practical limit exists across service tiers, instance performance
may be delayed when supporting a large number of files.
To check your usage, run the following command:
df -i
IUsed reflects the current number of files you have and IFree reflects the
number of additional files that you can store.
File locks
A file-locking
client is a client with at least one acquired or requested file lock. Anything
greater than the maximum recommended limit listed introduces inconsistent
locking behaviors that may result in production outages when the instance
undergoes maintenance:
Service tier
Maximum recommended number of file-locking clients per instance
Basic HDD
128
Basic SSD
128
Zonal
250
Regional
250
Enterprise
250
Rate limits for backups
The following backups operations have a rate limit of
once per 10 minutes in the steady state:
Creating a backup of Filestore instance
Restoring a Filestore instance from a backup (in-place
restore)
Creating a new Filestore instance from a backup
If you want to issue a burst of requests to back up your file shares, you can
issue at most 6 requests in 60 minutes.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eFilestore instance creation is limited by the project and region's Filestore quota and the minimum file share capacity.\u003c/p\u003e\n"],["\u003cp\u003eThe maximum recommended number of snapshots per instance is 240 for Zonal, Regional, and Enterprise service tiers, while Basic HDD and Basic SSD do not support snapshots.\u003c/p\u003e\n"],["\u003cp\u003eThe number of client connections supported varies by service tier and capacity, scaling up to 80,000 for Zonal and Regional (10 TiB to 100 TiB).\u003c/p\u003e\n"],["\u003cp\u003eFilestore instances can only be created across a maximum of 49 unique VPC networks.\u003c/p\u003e\n"],["\u003cp\u003eThe maximum file size supported is up to 16 TiB for Basic HDD and Basic SSD, and up to the size of instance capacity for other service tiers, with the file limit ranging from approximately 67 million to 89 million per TiB of capacity.\u003c/p\u003e\n"]]],[],null,["# Quotas and Limits\n\nThis page describes the quotas and limits of Filestore.\n\nNumber of instances\n-------------------\n\nThe number of instances you can create is limited only by the amount of\nFilestore quota for a given project and region as well as the minimum\nfile share capacity. For example, if you have 32 TiB of quota in a given\nregion, you can create 32 instances each with 1 TiB of capacity. To see\nyour available per project, per region quota, go to\n[the Quotas page](https://console.cloud.google.com/iam-admin/quotas).\n\nNumber of snapshots\n-------------------\n\nNumber of clients\n-----------------\n\nNumber of VPC networks used with Filestore\n------------------------------------------\n\nYou can create Filestore instances on no more than 49 unique VPC\nnetworks, even if previously used networks are deleted. If you think that you've\nreached this limit, see the troubleshooting guide topic on\n[`error code 13`](/filestore/docs/create-instance-issues)\nfor possible solutions.\n\nFile share capacity\n-------------------\n\nEnterprise instances combined with the Filestore\nmultishares feature can support a minimum share capacity of 10 GiB.\n\nFor more information, see [Filestore multishares](/filestore/docs/multishares#storageclasses_and_dynamic_volume_provisioning).\n\nFile size\n---------\n\nNumber of files\n---------------\n\n- The number of files listed is an indication of the maximum number of supported\n connections to small or empty files. The number of supported file connections\n decreases as file size increases.\n\n- While no practical limit exists across service tiers, instance performance\n may be delayed when supporting a large number of files.\n\nTo check your usage, run the following command: \n\n df -i\n\n`IUsed` reflects the current number of files you have and `IFree` reflects the\nnumber of additional files that you can store.\n\nFile locks\n----------\n\nA [file-locking](https://en.wikipedia.org/wiki/File_locking)\nclient is a client with at least one acquired or requested file lock. Anything\ngreater than the maximum recommended limit listed introduces inconsistent\nlocking behaviors that may result in production outages when the instance\nundergoes maintenance:\n\nRate limits for backups\n-----------------------\n\nThe following [backups](/filestore/docs/backups) operations have a rate limit of\nonce per 10 minutes in the steady state:\n\n- Creating a backup of Filestore instance\n- Restoring a Filestore instance from a backup (in-place restore)\n- Creating a new Filestore instance from a backup\n\nIf you want to issue a burst of requests to back up your file shares, you can\nissue at most 6 requests in 60 minutes.\n\nFor more information, see [Backups feature limitations](/filestore/docs/backups#feature_limitations).\n\nWhat's next\n-----------\n\n- [Service tiers](/filestore/docs/service-tiers)\n- [Known issues](/filestore/docs/known-issues)\n- [Troubleshoot performance-related issues](/filestore/docs/troubleshooting)\n- [Scale capacity](/filestore/docs/scale)"]]
