Cloud Parts

Google Cloud Storage

Google Cloud’s object storage, where even the archive class answers in milliseconds.

What it is
Object storage
Type
Managed service on Google Cloud
Made by
Google Cloud
License
Proprietary
Facts checked
5 October 2026
Website

What it is

Cloud Storage keeps objects in buckets, and each bucket lives in a location you pick: one region (copies across zones), a dual-region pair, or a multi-region such as US or EU. Writes, reads after writes and listings are strongly consistent everywhere, so a successful upload is visible to the next request. Objects can be up to 5 TiB.

Each object has a storage class: Standard, Nearline, Coldline or Archive. The colder classes cost less to store but add retrieval fees and minimum storage periods of 30, 90 and 365 days. Unlike S3 Glacier or Azure’s archive tier, every class serves data in milliseconds, with no restore step. Autoclass can move objects for you: an object unread for 30 days drops to Nearline, and reading it moves it back to Standard.

Why teams pick it

  • Archive data is readable immediately, with no hours-long rehydration
  • Strong global consistency for writes, overwrites and listings
  • Dual-region and multi-region buckets, with optional turbo replication that copies new data to the second region within 15 minutes
  • Autoclass handles tiering by access pattern, so you don’t write lifecycle rules

Watch out for

  • Each object name can be written about once per second; faster updates to the same object get throttled
  • Nearline, Coldline and Archive charge retrieval fees and bill for 30, 90 or 365 days even if you delete earlier
  • Its native JSON API is its own; S3 tools work only through the XML API with HMAC keys, and not every feature maps

Alternatives

What all object storage have in common →
Amazon S3AWSAWS’s object storage, and the de facto API most object stores copy.Apache OpenDALOpen sourceA Rust library, with bindings for Python, Java, Node.js, Go and more, that gives one API (read, write, stat, list, delete) over 50-plus storage backends: S3 and other object stores, local and HDFS file systems, Google Drive and Dropbox, and key-value stores.Apache OzoneOpen sourceA Hadoop-born object store that serves the same buckets over S3 and as a Hadoop file system.Azure Blob StorageAzureAzure’s object storage, with three blob types and an optional real directory tree for analytics.Backblaze B2 Cloud StorageCommercialLow-cost object storage on Backblaze’s own hardware, with its own API and an S3-compatible one.CephOpen sourceA distributed storage cluster that serves S3 buckets, block devices and a file system from the same pool of disks.Cloudflare R2CommercialS3-compatible object storage from Cloudflare that charges nothing for data going out.GarageOpen sourceA lightweight S3 object store that keeps copies of your data in several sites linked by ordinary Internet connections.MinIOArchivedOpen sourceA self-hosted object store that speaks the S3 API. The open-source edition is archived and its images are gone from Docker Hub; MinIO now sells AIStor.PGSTY SiloOpen sourceA community-maintained fork of the open-source MinIO server, with builds, images, security fixes and the full web console.RustFSOpen sourceA young Rust reimplementation of MinIO’s design: S3-compatible, erasure-coded, Apache 2.0, and generally available since September 2026.SeaweedFSOpen sourceA distributed blob store with an S3 gateway and a file system layer, built to store and serve billions of small files.TigrisCommercialGlobally distributed S3-compatible object storage that moves data to where it’s read, with no egress fees.Versity S3 GatewayOpen sourceA stateless S3 server that exposes an existing file system, or another object store, through the S3 API.Wasabi Hot Cloud StorageCommercialS3-compatible object storage sold at one flat price per TB, with no egress or request fees.Zenko CloudServerOpen sourceScality’s open-source Node.js S3 server: a light S3 endpoint for development and tests, and a front end that can store objects in other clouds.

How it fits with other technologies

What uses Google Cloud Storage

Create an Autoclass bucket, upload, and notify Pub/Sub on new objects · bash

gcloud storage buckets create gs://acme-media \
  --location=europe-west1 --enable-autoclass

gcloud storage cp ./photos/*.jpg gs://acme-media/photos/2026/10/
gcloud storage ls --long gs://acme-media/photos/2026/10/

# publish a Pub/Sub message every time an object is written
gcloud storage buckets notifications create gs://acme-media \
  --topic=media-uploads --event-types=OBJECT_FINALIZE

See it in a real stack

No architecture uses Google Cloud Storage yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2010–2026

Four years after Amazon launched S3, Google opened a storage service of its own to outside developers. Announced on 19 May 2010, at Google I/O, as Google Storage for Developers, it was a RESTful service replicated across several US data centres, with gsutil, an open-source command-line tool, for managing it. The preview was open to a limited number of developers from a waiting list, each with up to 100 GB of storage and 300 GB of monthly bandwidth free. It opened to all developers, with no invitation needed, in May 2011, and was later renamed Google Cloud Storage. Today it runs on Colossus, Google’s cluster file system and the successor to the Google File System (GFS).

Its distinctive bet was that cold data shouldn’t mean slow data. Nearline launched in 2015 with retrieval in about three seconds; today it, Coldline (2016) and Archive (2020) all use the same API as Standard and answer in milliseconds. Instead of waiting hours for a restore, as with S3 Glacier or Azure’s archive tier, you pay a retrieval fee and a minimum storage period. Archive launched in January 2020 at $0.0012 per GB-month, with tape replacement as a headline use.

Location became the other lever: Regional and Multi-Regional classes in 2016, and in 2026 Rapid buckets that place objects in a single zone next to the compute that reads them.

Why it’s built this way

Every storage class answers in milliseconds
Google wanted archived data usable without changing applications. As it put it when Coldline launched, existing systems could store and access cold data “without any updates to the application”.
Built on Google’s internal file system
Rather than a separate stack, Cloud Storage sits on Colossus, the same storage layer that backs Firestore and other Google services.
Location chosen per bucket
Multi-region buckets keep serving through a regional outage, regional ones sit next to compute, and zonal Rapid buckets trade redundancy for speed. You pick per bucket, not per account.
An S3-style XML API beside its own JSON API
Supporting HMAC keys and an XML API close to S3’s lets many tools written for S3 work against Cloud Storage by changing the endpoint.

Timeline

  1. 2010

    Announced as Google Storage for Developers at Google I/O; limited preview (May)

  2. 2011

    Opens to all developers, with objects up to 5 TB (May)

  3. 2015

    Nearline class for rarely read data, still online (March)

  4. 2016

    Coldline, plus Multi-Regional and Regional classes (October)

  5. 2020

    Archive class at $0.0012 per GB-month, readable in milliseconds (January)

  6. 2026

    Rapid buckets store objects in one zone beside compute (March)

Sources9 · facts checked 5 October 2026

Improve this page on GitHub