Get Started on Web

Cloud Storage for Firebase lets you upload and share user generated content, such as images and video, which allows you to build rich media content into your apps. Your data is stored in a Google Cloud Storage bucket, an exabyte scale object storage solution with high availability and global redundancy. Cloud Storage lets you securely upload these files directly from mobile devices and web browsers, handling spotty networks with ease.

Prerequisites

Add and configure the Firebase SDK into your app.

Create a default Storage bucket

From the navigation pane of the Firebase console, select Storage, then click Get started.
Review the messaging about securing your Storage data using security rules. During development, consider setting up your rules for public access.
Select a location for your default Storage bucket.
- This location setting is your project's default Google Cloud Platform (GCP) resource location. Note that this location will be used for GCP services in your project that require a location setting, specifically, your Cloud Firestore database and your App Engine app (which is required if you use Cloud Scheduler).
- If you aren't able to select a location, then your project already has a default GCP resource location. It was set either during project creation or when setting up another service that requires a location setting.
If you're on the Blaze plan, you can create multiple buckets, each with its own location.

Warning: After you set your project's default GCP resource location, you cannot change it.
Click Done.

Set up public access

Cloud Storage for Firebase provides a declarative rules language that allows you to define how your data should be structured, how it should be indexed, and when your data can be read from and written to. By default, read and write access to Storage is restricted so only authenticated users can read or write data. To get started without setting up Authentication, you can configure your rules for public access.

This does make Storage open to anyone, even people not using your app, so be sure to restrict your Storage again when you set up authentication.

Add your bucket URL to your app

If it's not included already, you need to add your Storage bucket URL to your Firebase app's configuration object.

Go to your Storage dashboard in the Firebase console.
Click the Files tab, then look in the header of the file viewer.
Copy the URL to your clipboard. It's usually in the form project-id.appspot.com.

To your firebaseConfig object in your app, add the storageBucket attribute with your bucket URL:

  // Set the configuration for your app
  // TODO: Replace with your app's config object
  var firebaseConfig = {
    apiKey: '<your-api-key>',
    authDomain: '<your-auth-domain>',
    databaseURL: '<your-database-url>',
    storageBucket: '<your-storage-bucket-url>'
  };
  firebase.initializeApp(firebaseConfig);

  // Get a reference to the storage service, which is used to create references in your storage bucket
  var storage = firebase.storage();

You're ready to start using Cloud Storage!

Next step? Learn how to create a Cloud Storage reference.

Advanced setup

There are a few use cases that require additional setup:

Using storage buckets in multiple geographic regions
Using storage buckets in different storage classes
Using storage buckets with multiple authenticated users in the same app

The first use case is perfect if you have users across the world, and want to store their data near them. For instance, you can create buckets in the US, Europe, and Asia to store data for users in those regions to reduce latency.

The second use case is helpful if you have data with different access patterns. For instance: you can set up a multi-regional or regional bucket that stores pictures or other frequently accessed content, and a nearline or coldline bucket that stores user backups or other infrequently accessed content.

In either of these use cases, you'll want to use multiple storage buckets.

The third use case is useful if you're building an app, like Google Drive, which lets users have multiple logged in accounts (for instance, a personal account and a work account). You can use a custom Firebase App instance to authenticate each additional account.

Use multiple storage buckets

If you want to use a storage bucket other than the default provided above, or use multiple storage buckets in a single app, you can create an instance of firebase.storage that references your custom bucket:

// Get a non-default Storage bucket
var storage = firebase.app().storage("gs://my-custom-bucket");

Working with imported buckets

When importing an existing Cloud Storage bucket into Firebase, you'll have to grant Firebase the ability to access these files using the gsutil tool, included in the Google Cloud SDK:

gsutil -m acl ch -r -u firebase-storage@system.gserviceaccount.com:O gs://<your-cloud-storage-bucket>

This does not affect newly created buckets, as those have the default access control set to allow Firebase. This is a temporary measure, and will be performed automatically in the future.

Use a custom Firebase App

If you're building a more complicated app using a custom firebase.app.App, you can create an instance of firebase.storage.Storage initialized with that app:

// Get the default bucket from a custom firebase.app.App
var storage = customApp.storage();

// Get a non-default bucket from a custom firebase.app.App
var storage = customApp.storage("gs://my-custom-bucket");