FAQs about Cloud Storage for Firebase changes announced in September 2024
Stay organized with collectionsSave and categorize content based on your preferences.
Firebase is making some changes toCloud Storage for Firebaseand taking
proactive steps to prevent abuse on our platform. This requires us to update our
infrastructure to better align withGoogle Cloud Storagequota and billing.
One result of these infrastructure changes is thatwe'll soon start requiring
projects to be on thepay-as-you-go Blaze pricing planto useCloud Storage for Firebase.
No-cost usage is still available even on the Blaze pricing plan.
Review the following FAQs about the changes we announced in September 2024:
We'll soon start requiring thepay-as-you-go Blaze pricing planif you want to useCloud Storage for Firebase.No-cost usage is still available even on the
Blaze pricing plan.
We understand that these changes will require your time to evaluate and make
changes to your Firebase project and workflows. If you have any questions,
please reach out toFirebase Support.
What are the new pricing plan requirements announced in September 2024?
StartingOctober 30, 2024, the following
changes will happen:
To provision a new default bucket using theFirebaseconsole or REST API,
your project must be on thepay-as-you-go Blaze pricing plan.
Note the following about all default bucketsprovisioned afterOctober 30, 2024:
They will have a name format ofPROJECT_ID.firebasestorage.app(instead of the formerPROJECT_ID.appspot.com).
StartingOctober 1, 2025, the following
changes will happen:
To maintain access to your default bucket and all otherCloud Storageresources, your project must be on thepay-as-you-go Blaze pricing plan. Any*.appspot.comdefault bucket will maintain its
current no-cost level of usage even on the Blaze pricing plan.
Why is Firebase making these pricing plan changes?
Firebase strives to keep our products and our ecosystem safe and secure. As part
of that, we're making some changes toCloud Storage for Firebaseand taking
proactive steps to prevent abuse on our platform. This includes updating our
infrastructure to better align withGoogle Cloud Storagequota and billing.
Can I keep no-cost usage if I upgrade to the Blaze pricing plan?
Yes. If you have aPROJECT_ID.appspot.comdefault bucket and you
upgrade to thepay-as-you-go Blaze pricing plan, then you will maintain your default
bucket's current no-cost level of usage, as described below. Any usage over this
no-cost usage will be charged according toGoogleApp Enginepricing.
5 GB stored
1 GB downloaded / day
20,000 uploads / day
50,000 downloads / day
Note thatstartingOctober 30, 2024, all new
default buckets have the name format ofPROJECT_ID.firebasestorage.appand they followGoogle Cloud Storagepricing and usage,
which provides an"Always Free" tierfor buckets inUS-CENTRAL1,US-EAST1, andUS-WEST1.
When do I need to upgrade to the Blaze pricing plan?
If you want to maintain access to yourPROJECT_ID.appspot.comdefault
bucket, then you need toupgrade to the pay-as-you-go Blaze pricing plan plan
byOctober 1, 2025.
What if I don't upgrade my project to the Blaze pricing plan?
StartingOctober 30, 2024: If you haven't
yet provisioned a defaultCloud Storagebucket in your project, then you won't be
able to provision it unless your project is on the Blaze pricing plan.
StartingOctober 1, 2025: If your
project isn't on the Blaze pricing plan, then you'll lose read/write
access to yourPROJECT_ID.appspot.comdefault bucket. You also won't
be able to view the bucket or access its data in theFirebaseconsole or
theGoogle Cloudconsole.
Note that any data will remain in your bucket, but it will be inaccessible
until you upgrade to the Blaze pricing plan.
What happens if my*.appspot.comdefault bucket's usage is over the no-cost usage level ?
If you have aPROJECT_ID.appspot.comdefault bucket, and you upgrade to
the Blaze pricing plan with a usage that's over the no-cost usage
levels described below, then you will be charged for the overage according toGoogleApp Enginepricingon your next billing cycle.
We understand that these changes will require your time to evaluate and make
changes to your Firebase project and workflows. If you have any questions,
please reach out toFirebase Support.
Will the name of my default bucket change?
No. When you upgrade to the Blaze pricing plan, the name of your
defaultCloud Storagebucket willnotchange.
If you provisioned your default bucketbeforeOctober 30, 2024, then your default bucket
will always have a name format ofPROJECT_ID.appspot.com.
If you provisioned your default bucketon or afterOctober 30, 2024, then your default bucket
will always have a name format ofPROJECT_ID.firebasestorage.app.
What happens if I delete my*.appspot.comdefault bucket?
A deleted bucket is restorable using the Cloud StorageBuckets: restoreAPI until its hard delete time has elapsed.
StartingOctober 30, 2024: If you delete yourPROJECT_ID.appspot.comdefault bucket, then you won't be able to
provision a bucket with that same name format.
Instead, you can create a new defaultCloud Storagebucket (if your project is on
the Blaze pricing plan) that has a name format ofPROJECT_ID.firebasestorage.app. It will followGoogle Cloud Storagepricing and usage,
which provides an"Always Free" tierfor buckets inUS-CENTRAL1,US-EAST1, andUS-WEST1.
Do I need to update my app's codebase?
No. To accommodate these changes, you donotneed to update your app's
codebase.
All existingPROJECT_ID.appspot.comdefault buckets will maintain their
name format.
To avoid any service interruptions, make sure to upgrade your project to thepay-as-you-go Blaze pricing planbyOctober 1, 2025.
After upgrading to the Blaze pricing plan, your codebase will continue
to interact with thePROJECT_ID.appspot.comdefault bucket as it always
has.
Do I need to move my data out of my*.appspot.comdefault bucket?
No. To accommodate these changes, you donotneed to move your data out of
yourPROJECT_ID.appspot.comdefault bucket.
As long as you upgrade your project to thepay-as-you-go Blaze pricing planbyOctober 1, 2025, then you'll see no service
interruptions.
Changes for programmatic interactions (like REST APIs and Terraform)
If you provision or work with defaultCloud Storage for Firebasebuckets
programmatically (for example, using REST APIs or Terraform), review the
following changes to see if you need to change anything in your workflows or
apps.
We understand that these changes will require your time to evaluate and make
changes to your Firebase project and workflows. If you have any questions,
please reach out toFirebase Support.
What are the changes for using REST APIs?
StartingOctober 30, 2024, the following
changes will happen:
The default buckets provisioned by this endpoint will have the name format
ofPROJECT_ID.firebasestorage.app(instead of the formerPROJECT_ID.appspot.com).
These default buckets will followGoogle Cloud Storagepricing and
usage, which provides an"Always Free" tierfor buckets inUS-CENTRAL1,US-EAST1, andUS-WEST1.
StartingOctober 30, 2024, the following
changes will happen that are related to using Terraform withCloud Storage for Firebase.
You can no longer provision the defaultCloud Storage for Firebasebucket using
Terraform. This is because you can no longer provision this bucket viaGoogleApp Engine. Instead, you can do one of the following:
Provision the bucket through theFirebaseconsole. Visit theStoragesectionof the console to get started.
Additionally, note the following about defaultCloud Storagebuckets provisioned
startingOctober 30, 2024:
Your project must be on the pay-as-you-go Blaze pricing plan to provision a
defaultCloud Storagebucket.
You no longer need to provision your defaultCloud Firestoreinstance before
your defaultCloud Storagebucket.
The location you select for your defaultCloud Firestoreinstance is not
applicable to your defaultCloud Storagebucket (this means that your defaultCloud Firestoreinstance and your defaultCloud Storagebucket can be in different
locations).
The name format of the defaultCloud Storagebucket will bePROJECT_ID.firebasestorage.app(instead of the formerPROJECT_ID.appspot.com).
defaultCloud Storage for Firebasebucket (specifically those with the name
format ofPROJECT_ID.appspot.com)
GoogleCloud Scheduler(specifically for 1st gen scheduled
functions)
With many changes over the years to the Firebase ecosystem, the associations of
Firebase-related resources toGoogleApp Enginehave been changing.
We understand that these changes will require your time to evaluate and make
changes to your Firebase project and workflows. If you have any questions,
please reach out toFirebase Support.
What's happening to the "location for defaultGoogle Cloudresources"?
defaultCloud Storage for Firebasebucket (specifically those with the name
format ofPROJECT_ID.appspot.com)
GoogleCloud Scheduler(specifically for 1st gen scheduled
functions)
When you set up any one of these resources in your project, you're transitively
setting the location of theGoogleApp Engineapp in your project.
This, in turn, sets the location for all the resources associated withGoogleApp Engine.
Note the following:
Any defaultCloud Storagebucket provisionedbeforeOctober 30, 2024(with a name format ofPROJECT_ID.appspot.com) is associated withGoogleApp Engine. This means the following:
The bucket's location will set the location of resources associated withGoogleApp Engine(like the location of the defaultCloud Firestoreinstance).
Any defaultCloud Storagebucket provisioned startingOctober 30, 2024(with the name format ofPROJECT_ID.firebasestorage.app) isnotassociated withGoogleApp Engine. This means the following:
Provisioning your defaultCloud Storagebucket will no longer set the location
of resources associated withGoogleApp Engine(like the location
of the defaultCloud Firestoreinstance).
Provisioning your defaultCloud Firestoreinstance will no longer set the
location of your project's defaultCloud Storagebucket.
defaultCloud Storage for Firebasebucket (specifically those with the name
format ofPROJECT_ID.appspot.com)
GoogleCloud Scheduler(specifically for 1st gen scheduled
functions)
StartingOctober 30, 2024, the concept of
"defaultGoogle Cloudresources" doesn't apply tonewly provisioneddefaultCloud Storagebuckets. Default buckets provisionedafterthis date have the name
format ofPROJECT_ID.firebasestorage.app, and they arenotassociated withGoogleApp Engine. To learn more, review the FAQ:What happens to the "location for defaultGoogle Cloudresources"?
If you want to set or get the location for any resource in a project, then you
should interact directly with the resource instead.
DefaultCloud Storage for Firebasebucket
In theFirebaseconsole:
Set and find the location of a defaultCloud Storagebucket in theStoragesectionof theFirebaseconsole.
Note that startingOctober 30, 2024,
calling this endpoint will require thepay-as-you-go Blaze pricing plan. So before
attempting to create a default bucket, make sure that the project is
linked to aCloud Billingaccount (for example, usingprojects.updateBillingInfo).
Note that if you provisioned a defaultCloud Storagebucket beforeOctober 30, 2024, then the location of the
project's defaultCloud Firestoreinstance has already been set (due to
associations withGoogleApp Engine).
In theFirebaseconsole:
Set and find the location of a defaultCloud Firestoreinstance in theFirestoresectionof theFirebaseconsole.
Using REST APIs:
Set the location of a defaultCloud Firestoreinstance during its provisioning
when callingprojects.databases.create.
Note that if you provisioned a defaultCloud Storagebucket beforeOctober 30, 2024, then the project's scheduled
functions (1st gen) has already been set (due to associations withGoogleApp Engine).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-05 UTC."],[],[],null,[]]
