Google CloudGoogle Cloud FilestoreStorage

`google_filestore_instance` cost estimation

Managed NFS file storage. Basic HDD at $0.16/GB-month (1 TB min). Basic SSD at $0.30/GB-month. Enterprise tier at $0.45/GB-month with regional replication. High Scale at $0.10/GB-month for parallel workloads.

Cloud Filestore provides managed NFSv3 file storage for GCE and GKE workloads. The google_filestore_instance resource creates the file server. Pricing is purely capacity-based — no IO charges, no per-mount fees.

Service tiers: - Basic HDD: $0.16/GB-month. 1 TB minimum, scales to 64 TB. Right for development, file shares, modest performance needs. - Basic SSD: $0.30/GB-month. 2.5 TB minimum, scales to 64 TB. Better latency than HDD. - Zonal SSD: $0.35/GB-month. 1 TB-9.75 TB, then 10 TB+ tier. High performance, zonal redundancy. - Enterprise: $0.45/GB-month. 1 TB minimum, scales to 10 TB. Regional replication for HA. - High Scale (PD): $0.10/GB-month. 10 TB minimum, scales to 100+ TB. Parallel access for HPC.

Minimum capacity drives a lot of the cost. Basic HDD's 1 TB minimum = $160/month even if you use 100 GB. Right-sizing is about matching tier to actual capacity needed.

Compared to alternatives: - GCS at $0.020/GB-month is 8x cheaper but object storage, not POSIX - Persistent Disk with NFS-server VM is cheaper but operational overhead - AWS EFS Standard at $0.30/GB-month is comparable to Basic SSD

Common use cases: GKE persistent volumes needing ReadWriteMany, legacy applications expecting POSIX file semantics, ML training data shared across nodes.

c3x estimates Filestore based on tier and capacity_gb. Backups and replication are tracked separately when configured.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "google_filestore_instance" "shared" {
  name     = "production-fs"
  location = "us-central1-b"
  tier     = "BASIC_SSD"

  file_shares {
    capacity_gb = 2560  # 2.5 TB minimum for SSD
    name        = "share1"
  }

  networks {
    network = "default"
    modes   = ["MODE_IPV4"]
  }
}

Pricing dimensions

What you actually pay for when you provision google_filestore_instance.

Dimension	Unit	What's being charged
Basic HDD capacity	per GB-month	HDD-backed file storage. 1 TB minimum. $0.16/GB-month ($160/month minimum)
Basic SSD capacity	per GB-month	SSD-backed file storage. 2.5 TB minimum. $0.30/GB-month ($750/month minimum)
Enterprise capacity	per GB-month	Enterprise tier with regional replication for HA. $0.45/GB-month ($450/month minimum)
High Scale capacity	per GB-month	HPC-oriented tier for parallel workloads. 10 TB minimum. $0.10/GB-month ($1,000/month minimum)
Backups	per GB-month	Filestore backups stored separately. Incremental but billed by retained size. $0.10/GB-month

Optimization tips

Common ways to reduce google_filestore_instance cost without changing the workload.

Match tier to actual needs

47% HDD vs SSD

Most teams default to Basic SSD without checking if HDD would suffice. For dev/test or low-IOPS workloads, Basic HDD at $0.16/GB-month is half the price. Audit IOPS usage before choosing tier.

Avoid Filestore for object workloads

85% vs Filestore

If the workload could use object storage (read-mostly, no POSIX semantics needed), GCS is 8x cheaper than Basic HDD. For ML datasets, GCS + GCS Fuse mount often works as well as Filestore at much lower cost.

Right-size capacity at provision time

Variable

Filestore minimum capacities are large (1-10 TB depending on tier). Once provisioned, capacity is billed even if unused. Provision close to actual need; expand later if needed.

Use Enterprise only for HA workloads

33% on non-HA workloads

Enterprise tier is regional (replicated across zones). For workloads that don't need cross-zone HA, Basic SSD at $0.30/GB-month is cheaper than Enterprise at $0.45.

Skip Filestore backups for ephemeral data

Filestore backups are full incremental snapshots. For ephemeral data (cache, scratch), disable backups. For source-of-truth data, keep them.

FAQ

Why is the minimum capacity so large?

Filestore's architecture provisions hardware sized for the minimum. Even if you only use 100 GB on Basic HDD, you're paying for a 1 TB allocation. For smaller workloads, consider GCS, Cloud Storage FUSE, or a self-managed NFS server on a smaller persistent disk.

Can I shrink Filestore capacity?

No. Capacity can be expanded but not reduced. Plan capacity carefully at provision time. If you over-provisioned, the only path is to migrate data to a new smaller instance and delete the old one.

How does Filestore compare to AWS EFS?

Pricing is similar: EFS Standard at $0.30/GB-month matches Filestore Basic SSD. EFS has more tiers (IA, One Zone-IA) for cheaper cold storage. Filestore tiers are simpler. Both are managed NFS. For multi-cloud teams, capabilities are roughly equivalent.

Does Filestore charge for IO?

No. Unlike AWS EFS provisioned throughput mode, Filestore has no per-operation or throughput charges. The tier determines IOPS available, but the price is purely based on capacity. This makes Filestore predictable but potentially more expensive than EFS for low-utilization workloads.