Discover
Get started
Create buckets
Access and manage buckets
Upload and download objects
Access and manage objects
Get insights on your stored data
Cache objects
Control data lifecycles
Make requests
Secure data
Monitor data and usage
Protection, backup, and recovery
Mount buckets with Cloud Storage FUSE
Work across products, Clouds, and platforms
Troubleshoot
Stay organized with collections Save and categorize content based on your preferences.
This page describes buckets, a resource in Cloud Storage. For a general overview of how Cloud Storage works, see the Cloud Storage product overview.
BucketsBuckets are the basic containers that hold your data as objects. Everything that you store in Cloud Storage must be contained in a bucket. You can use buckets to organize your data and control access to your data, but unlike directories and folders, you cannot nest buckets.
There is no limit to the number of buckets you can have in a project or location.
When you create a bucket, you give it a globally-unique name and a geographic location where the bucket and its contents are stored.
Your bucket names must meet the following requirements:
-
), underscores (_
), and dots (.
). Spaces are not allowed. Names containing dots require verification.The following are examples of valid bucket names:
my-travel-maps
0f75d593-8e7b-4418-a5ba-cb2970f0b91e
test.example.com
(Requires verification of ownership for example.com
)The following are examples of invalid bucket names:
My-Travel-Maps
(contains uppercase letters)my_google_bucket
(contains "google")test bucket
(contains a space)Bucket names reside in a single namespace that is shared by all Cloud Storage users. This means that:
Every bucket name must be globally unique.
If you try to create a bucket with a name that already belongs to an existing bucket, such as example-bucket
, Cloud Storage responds with an error message.
Bucket names are publicly visible.
Don't use user IDs, email addresses, project names, project numbers, or any personally identifiable information (PII) in bucket names because anyone can probe for the existence of a bucket.
Once you delete a bucket, anyone can reuse its name for a new bucket.
The time it takes a deleted bucket's name to become available again is typically on the order of seconds; however, keep in mind the following:
If you delete the project that contains the bucket, which effectively deletes the bucket as well, the bucket name may not be released for weeks or longer.
If someone reuses your bucket's name, you cannot restore your deleted bucket even if the bucket has soft delete enabled.
If a new bucket with the same name is created in a different location and within 10 minutes of the old bucket's deletion, requests made to the new bucket during this 10 minute timeframe might fail with a 404-Bucket Not Found
error.
If your requests go through the XML API, attempts to create a bucket that reuses a name in a new location might fail with a 404-Bucket Not Found
error for up to 10 minutes after the old bucket's deletion.
If someone reuses your bucket's name, they could inadvertently receive data or requests intended for your original deleted bucket. To mitigate this risk, consider the following best practices:
When creating buckets, use a strong naming convention that's not easy to guess or predict.
When deleting buckets, make sure to remove all references of the deleted bucket's name, such as from external documentation or open source repositories.
If you no longer need a bucket, consider emptying all objects from the bucket and keeping the bucket instead of deleting it.
You can use a bucket name in a DNS record as part of a CNAME
or A
redirect.
In order to do so, your bucket name should conform to standard DNS naming conventions. This means that your bucket name shouldn't use underscores (_
) or have a period next to another period or dash. For example, ..
, -.
, and .-
are invalid character combinations within DNS names.
Although Cloud Storage stores unstructured data in the form of objects, some features let you access and manage your data using folders or directories.
Hierarchical namespaceWhen you create buckets, you can optionally enable hierarchical namespace for the bucket, which lets you use folders to store your objects in a file system manner. Organizing your objects into folders makes it easier to run operations on large scales of data, improving performance, consistency, and ease of management. Using buckets with hierarchical namespace enabled is especially beneficial when working with data-intensive and file-oriented workloads.
To get started using hierarchical namespace, see Create buckets with hierarchical namespace enabled.
Cloud Storage FUSECloud Storage FUSE is a FUSE adapter that lets you mount and access buckets as local file systems, so applications can read and write objects in your bucket using standard file system semantics. Cloud Storage FUSE lets you store your data in Cloud Storage with all the service's benefits, all while retaining the ability to access that data using your application's code without needing changes.
To learn how to use Cloud Storage FUSE, see the Cloud Storage FUSE quickstart.
What's nextExcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-10-02 UTC.
[[["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-10-02 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.5