Firebase FAQ

What is a Firebase project?

A Firebase project is the top-level entity for Firebase. In a project, you can register your Apple, Android, or web apps. After you register your apps with Firebase, you can add the product-specific Firebase SDKs to your app, like Analytics, Cloud Firestore, Crashlytics, or Remote Config.

You should register your Apple, Android, and web app variants within a single Firebase project. You can use multiple Firebase projects to support multiple environments, such as development, staging, and production.

Here are some resources for learning more about Firebase projects:

• Understand Firebase projects — provides brief overviews of several important concepts about Firebase projects, including their relationship with Google Cloud and the basic hierarchy of a project and its apps and resources.
• General best practices for setting up Firebase projects — provides general, high-level best practices for setting up Firebase projects and registering your apps with a project so that you have a clear development workflow that uses distinct environments.

Note that for all Firebase projects, Firebase automatically adds a label of firebase:enabled within the Labels page for your project in the Google Cloud console. Learn more about this label in our FAQ.

What is a Google Cloud organization?

A Google Cloud organization is a container for Google Cloud projects (including Firebase projects). This hierarchy enables better organization, access management, and auditing of your Google Cloud and Firebase projects. For more information, refer to Creating and Managing Organizations.

How do I add Firebase to an existing Google Cloud project?

You may have existing Google Cloud projects managed through the Google Cloud console or the Google APIs console.

You can add Firebase to these existing Google Cloud projects using any of the following options:

• Using the Firebase console.
• Using a programmatic option:
  • Call the Firebase Management REST API endpoint projects.addFirebase.
  • Run the Firebase CLI command firebase projects:addfirebase.
  • Use Terraform.

Learn more details about adding Firebase to a Google Cloud project.

How does Firebase's integration with Google Cloud work?

Firebase is deeply integrated with Google Cloud. Projects are shared between Firebase and Google Cloud, so projects can have Firebase services and Google Cloud services enabled. You can access the same project from the Firebase console or the Google Cloud console. Specifically:

• Certain Firebase products are backed directly by Google Cloud, such as Cloud Storage for Firebase. The list of products backed by Google Cloud will continue to grow over time.
• Many of your settings, including collaborators and billing information, are shared by Firebase and Google Cloud. Your usage of both Firebase and Google Cloud appears on the same bill.

In addition, when you upgrade to the pay-as-you-go Blaze pricing plan, you can use any of Google Cloud's world-class Infrastructure-as-a-Service and APIs directly inside your Firebase project, at standard Google Cloud pricing. You can also export data from Google Cloud directly to BigQuery for analysis. To learn more, see Link BigQuery with Firebase.

There are many security-enhancing, latency-improving, and time-saving benefits to using Google Cloud with Firebase (versus other, cloud services that are not co-located). Check out the Google Cloud site for more details.

Why does my Google Cloud project have a label of firebase:enabled?

In the Labels page for your project in the Google Cloud console, you may see a label of firebase:enabled (specifically, a Key of firebase with a Value of enabled).

Firebase automatically added this label because your project is a Firebase project, which means that your project has Firebase-specific configurations and services enabled for it. Learn more about the relationship between Firebase projects and Google Cloud.

We strongly recommend that you don't modify or delete this label. This label is used by Firebase and Google Cloud to list your Firebase projects (for example, using the REST API projects.list endpoint or in menus within the Firebase console).

Be aware that manually adding this label to your list of project labels does NOT enable Firebase-specific configurations and services for your Google Cloud project. To do that, you need to add Firebase using the Firebase console (or, for advanced use cases, using the Firebase Management REST API or the Firebase CLI).

Why is the Firebase console failing to load a list of my existing Google Cloud projects?

This FAQ is most often applicable if you're trying to "add Firebase" to an existing Google Cloud project using the Firebase console and you have access to many thousands of Google Cloud projects.

The Firebase console isn't built to load many thousands of Google Cloud projects. Instead, we recommend using the Firebase CLI, REST API, or Terraform to "add Firebase" to your existing Google Cloud project.

Also, you might want to review the FAQ "Why isn't my Firebase project showing up in my list of Firebase projects?"

Why isn't my Firebase project showing up in my list of Firebase projects?

This FAQ is applicable if you don't see your Firebase project in the following places:

• In a list of projects that you're viewing within the Firebase console
• In the response from calling the REST API projects.list endpoint
• In the response from running the Firebase CLI command firebase projects:list

Try these troubleshooting steps:

1. First, try accessing your project by visiting the project's URL directly. Use the following format:
   https://console.firebase.google.com/project/PROJECT-ID/overview
2. If you can't access the project or receive permissions errors, check the following:
   • Make sure that you're signed into Firebase using the same Google Account that has access to the project. You can sign in and out of the Firebase console via your account avatar in the top-right corner of the console.
   • Check if you can view the project in the Google Cloud console.
   • Make sure that your project has the label firebase:enabled in the Labels page for your project in the Google Cloud console. Firebase and Google Cloud use this label to list your Firebase projects. If you don't see this label but the Firebase Management API is enabled for your project, then manually add the label (specifically, a Key of firebase with a Value of enabled).
   • Make sure that you're assigned one of the basic IAM roles (Owner, Editor, Viewer) or a role that has Firebase-related permissions in it, for example a Firebase predefined role. You can view your role(s) in the IAM page of the Google Cloud console.
   • If your project belongs to a Google Cloud organization, you may require additional permissions to see the project listed in the Firebase console. Contact the person who manages your Google Cloud organization to give you the appropriate role to view the project, for example the Browser role.

If none of the troubleshooting steps above enable you to see your project in a list of Firebase projects, contact Firebase Support.

How many projects can I have per Google Account (email address)?

• Spark pricing plan: Project-creation quota is limited to a small number of projects (usually around 5-10).
• Blaze pricing plan: Project-creation quota is still limited, but it may increase with the linking of a Cloud Billing account in good standing.

Note the following about the limit on project-creation quota:

• This limit is not specific to Firebase. Firebase's limits on project quota are the same as those for Google Cloud.
• In the rare case that's it's needed, you can request an increase in project quota.
• The complete deletion of a project requires 30 days and counts toward project quota until the project is fully deleted.

Learn about Firebase's recommended general best practices for setting up Firebase projects.

How many Firebase Apps can I have in a Firebase project?

A Firebase project is a container for Firebase Apps across Apple, Android, and web. Firebase restricts the total number of Firebase Apps within a Firebase project to 30.

After this number, performance starts to degrade (especially for Google Analytics) and eventually, at a higher number of apps, some product functionality stops working. Additionally, if you use Google sign-in as an authentication provider, an underlying OAuth 2.0 client ID is created for each app in your project. There's a limit of around 30 client IDs that can be created within a single project.

You should ensure that all Firebase Apps within a single Firebase project are platform variants of the same application from an end-user perspective. For example, if you develop a white-label application, each independently labeled app should have its own Firebase project, but the Apple and Android versions of that label can be in the same project. Read more detailed guidance in our general best practices for setting up Firebase projects.

In the rare case your project requires more than 30 apps, you can request an app limit increase. Your project must be on the Blaze pricing plan to make this request. Visit the Google Cloud console to make your request and have it evaluated. Learn more about quota management in the Google Cloud documentation.

What happens if I tag my project as a "production" environment?

In the Firebase console, you can tag your Firebase projects with their environment type, either as Production or Unspecified (non-prod) environments.

Tagging your project as an environment type has no effect on how your Firebase project works or its features. However, the tagging can help you and your team manage your various Firebase projects for the app lifecycle.

If you tag your project as a production environment, we add a brightly colored Prod tag to the project in the Firebase console, reminding you that any changes could affect your associated production apps. In the future, we might add more features and safeguards for Firebase projects tagged as production environments.

To change the environment type of your Firebase project, go to settings Project settings > General, then in the Your project card under Environment, click edit to change the environment type.

Where can I find the App ID for my Firebase app?

In the Firebase console, go to your settings Project settings. Go to the Your apps card, and click the relevant Firebase App to view the app's information, including its App ID.

Here are some example App ID values:

• Firebase iOS Apps: 1:1234567890:ios:321abc456def7890
• Firebase Android Apps: 1:1234567890:android:321abc456def7890
• Firebase Web Apps: 1:1234567890:web:321abc456def7890

What are the prerequisites for linking Google Play / AdMob / Google Ads / BigQuery to my Firebase project or app?

• For linking your Google Play account, you need the following:
  • Either of the following Firebase roles: Owner or Firebase Admin
  • Either of the following Google Play access levels: account Owner or Admin
• For linking your AdMob app, you need to be both a Firebase project owner and an AdMob administrator.
• For linking your AdWords account, you need to be both a Firebase project owner and an AdWords administrator.
• For linking your BigQuery project, you need to be the Firebase project owner.

How do I assign a project member a role, like the Owner role?

To manage the role(s) assigned to each project member, you must be an Owner of the Firebase project (or be assigned a role with the permission resourcemanager.projects.setIamPolicy).

Here are the places where you can assign and manage roles:

• The Firebase console offers a simplified way to assign roles to project members in the settings Settings > Users and permissions tab. You can assign any of the basic roles (Owner, Editor, Viewer), the Firebase Admin/Viewer roles, or any of the Firebase predefined product-category roles.
• The Google Cloud console offers an expansive set of tools to assign roles to project members in the IAM & Admin IAM page. You can also create and manage custom roles, as well as give service accounts access to your project.

  Note that in the Google Cloud console, project members are called principals.

If the Owner of your project can no longer perform the tasks of an Owner (for example, the person left your company) and your project isn't managed via a Google Cloud organization (see next paragraph), you can contact Firebase Support and check with them about how to request access to the Firebase project.

Note that if a Firebase project is part of a Google Cloud organization, it may not have an Owner. If you're unable to find an Owner for your Firebase project, contact the person who manages your Google Cloud organization to assign an Owner for the project.

How do I find the Owner of a Firebase project?

You can view project members and their roles in the following places:

• If you have access to the project in the Firebase console, you can view the list of project members, including Owners, in the Users and permissions page of the Firebase console.
• If you do not have access to the project in the Firebase console, check if you have access to the project in the Google Cloud console. You can view the list of project members, including Owners, in the IAM page of the Google Cloud console.

If the Owner of your project can no longer perform the tasks of an Owner (for example, the person left your company) and your project isn't managed via a Google Cloud organization (see next paragraph), you can contact Firebase Support to have a temporary Owner assigned.

Note that if a Firebase project is part of a Google Cloud organization, it may not have an Owner. Instead, the person who manages your Google Cloud organization can perform many tasks that an Owner can do. However, to perform several Owner-specific tasks (like assigning roles or managing Google Analytics properties), the administrator may need to assign themselves the actual Owner role to perform those tasks. If you're unable to find an Owner for your Firebase project, contact the person who manages your Google Cloud organization to assign an Owner for the project.

Why or when should I assign a project member the Owner role?

To ensure proper management of a Firebase project, it must have an Owner.

Project members with the Owner role are often the only project members who can do administrative tasks or receive important notifications:

• Project members with the Owner role are often the only members who can perform important administrative actions (like assigning roles and managing Google Analytics properties), and Firebase Support can only fulfill administrative requests from demonstrated project Owners.
• Project members with the Owner role are often the only members who (by default) receive notifications about changes to the project or products (like billing and legal changes, deprecations of features, etc.). You can optionally customize your project's "essential contacts" if you want specific or additional project members to receive notifications.

After you set up the Owner(s) for a Firebase project, it's important to keep those assignments up-to-date.

Note that if a Firebase project is part of a Google Cloud organization, the person who manages your Google Cloud organization can perform many tasks that an Owner can do. However, for several Owner-specific tasks (like assigning roles or managing Google Analytics properties), the administrator may need to assign themselves the actual Owner role to perform those tasks.

I don't think that I have a Firebase project, but I got an email about one. How do I access this project?

The email you received should contain a link to open your Firebase project. Clicking the link in the email should open the project in the Firebase console.

If you're not able to open the project in the link, make sure that you're signed into Firebase using the same Google Account that received the email about the project. You can sign in and out of the Firebase console via your account avatar in the top-right corner of the console.

Note that if you're the administrator of a Google Cloud organization, you may be notified about changes to Firebase projects inside your organization. However, you may not have sufficient permissions to open the Firebase project. In these cases, the simplest solution is to assign yourself the actual Owner role to open the project and perform the required actions. Learn more about why and when to assign the Owner role.

What are the supported browsers for accessing the Firebase console?

The Firebase console can be accessed from recent versions of popular desktop browsers such as Chrome, Firefox, Safari and Edge. Mobile browsers are not fully supported.

I can load the Firebase console, but why can't I find or access my Firebase project?

This FAQ is applicable if you're experiencing either of the following issues:

• The Firebase console returns an error page that says your project may not exist or that you don't have access to the project.
• The Firebase console doesn't display your project even when you enter its project ID or project name in the console's search field.

Try these troubleshooting steps:

1. First, try accessing your project by visiting the project's URL directly. Use the following format:
   https://console.firebase.google.com/project/PROJECT-ID/overview
2. If you still can't access the project or receive permissions errors, check the following:
   • Make sure that you're signed into Firebase using the same Google Account that has access to the project. You can sign in and out of the Firebase console via your account avatar in the top-right corner of the console.
   • Make sure that the Firebase Management API is enabled for the project.
   • Make sure that you're assigned one of the basic IAM roles (Owner, Editor, Viewer) or a role that has Firebase-related permissions in it, for example a Firebase predefined role. You can view your role(s) in the IAM page of the Google Cloud console.
   • If your project belongs to a Google Cloud organization, you may require additional permissions to see the project listed in the Firebase console. Contact the person who manages your Google Cloud organization to give you the appropriate role to view the project, for example the Browser role.

If none of the troubleshooting steps above enable you to find or access your project, contact Firebase Support.

Why is the Firebase console not loading for me?

This FAQ is applicable if you're experiencing any of the following issues:

• A page in the Firebase console never finishes loading.
• Data within a page doesn't load as expected.
• You receive browser error messages when loading the Firebase console.

Try these troubleshooting steps:

1. Check the Console row of the Firebase Status Dashboard for any possible service interruptions.
2. Make sure that you're using a supported browser.
3. Try to load the Firebase console in an incognito or private window.
4. Disable all browser extensions.
5. Verify that the network connection is not blocked by ad blocker, antivirus, proxy, firewall, or other software.
6. Try loading the Firebase console using a different network or device.
7. If using Chrome, check the Developer Tools Console for any errors.

If none of the troubleshooting steps above resolve the issue, contact Firebase Support.

How is my Firebase console language determined?

The language setting for the Firebase console is based on the language selected in your Google Account settings.

To change your language preference, see Change language.

The Firebase console supports the following languages:

• English
• Brazilian Portuguese
• French
• German
• Indonesian
• Japanese
• Korean
• Russian
• Simplified Chinese
• Spanish
• Traditional Chinese

What roles and permissions does the Firebase console support?

The Firebase console and Google Cloud console use the same underlying roles and permissions. Learn more about roles and permissions in the Firebase IAM documentation.

Firebase supports the fundamental (basic) roles of Owner, Editor, and Viewer:

• A project Owner can add other members to the project, set up integrations (project linking to services like BigQuery or Slack), and has full edit access for the project.
• A project Editor has full edit access for the project.
• A project Viewer has only read access for the project. Note that the Firebase console does not hide/disable edit UI controls from project Viewers, but these operations will fail for project members assigned the Viewer role.

Firebase also supports:

• Firebase predefined roles — Curated Firebase-specific roles that enable more granular access control than the basic roles of Owner, Editor, and Viewer.
• Custom roles — Fully customized IAM roles that you create to tailor a set of permissions that meet the specific requirements of your organization.

Which products are paid? Which are no-cost?

For detailed information about paid versus no-cost products, see Firebase pricing plans.

How do I know which pricing plan is right for me?

For detailed information about pricing plans, see Firebase pricing plans.

Spark pricing plan

The no-cost Spark pricing plan is a great place to develop your app at no cost. You get all the no-cost Firebase products (like Analytics, Remote Config, Crashlytics, and so on) and generous amounts of our paid infrastructure features. However, if you exceed your Spark pricing plan resources in a calendar month, your app will be shut off for the remainder of that month. In addition, Google Cloud features are not available when using the Spark pricing plan.

Blaze pricing plan

The pay-as-you-go Blaze pricing plan is designed for production apps. The Blaze pricing plan also lets you extend your app with paid Google Cloud features. You pay only for the resources that you consume, allowing you to scale with demand. We strive to make our Blaze pricing plan prices competitive with industry-leading cloud providers.

Can I upgrade, downgrade, or cancel at any time?

Yes, you can upgrade, downgrade, or cancel at any time. Note that we don't provide prorated refunds for downgrades or cancellations. This means that if you downgrade or cancel before the end of your billing period, you still pay for the remainder of the month.

How is the no-cost usage in the Blaze pricing plan different from the no-cost usage in the Spark pricing plan?

No-cost usage on the Blaze pricing plan is calculated daily. Usage limits also differ from the Spark pricing plan for Cloud Functions, phone authentication, and Test Lab.

For Cloud Functions, no-cost usage on the Blaze pricing plan is calculated at the Cloud Billing account level, not the project level and has the following limits:

• 2M invocations/month
• 400K GB-seconds/month
• 200K CPU-seconds/month
• 5 GB of networking egress/month

For phone authentication, no-cost usage on the Blaze pricing plan is calculated monthly.

For Test Lab, no-cost usage on the Blaze pricing plan has the following limits:

• 30 physical device minutes/day
• 60 virtual device minutes/day

Does the no-cost usage quota reset when I change from the Spark pricing plan to the Blaze pricing plan?

No-cost usage from the Spark pricing plan is included in the Blaze pricing plan. No-cost usage does not reset when moving to the Blaze pricing plan.

What happens to my Firebase project if I link a billing account to that project in the Google Cloud console?

If a Cloud Billing account is linked to a project in the Google Cloud console, the same project will automatically be upgraded to the Firebase pay-as-you-go Blaze pricing plan (if that project was on the no-cost Spark pricing plan).

In contrast, if an existing active Cloud Billing account is unlinked from a project in the Google Cloud console, that project will be downgraded to the Firebase no-cost Spark pricing plan.

How can I monitor my usage and billing?

You can track your usage of project resources in the Firebase console on any of the following dashboards:

• Overall project-level Usage and billing dashboard
• Authentication Usage dashboard (specifically for Phone authentication instances)
• Cloud Firestore Usage dashboard
• Cloud Functions Usage dashboard
• Cloud Storage Usage dashboard
• Hosting Usage dashboard
• Realtime Database Usage dashboard

Can I cap usage on the Blaze pricing plan?

For several services, you can cap your usage on the Blaze pricing plan by setting budget spend caps. Currently, the following products support spend caps: Firebase AI Logic, Firebase App Hosting, Cloud Functions for Firebase, and Firebase Extensions.

For the other products that have a paid tier of usage, you cannot cap your usage when on the Blaze pricing plan. However, we are actively evaluating options for these products.

For all products that have a paid tier of usage, you can define a budget for your project or account, and receive alerts as spending approaches those limits. Learn how to set up budget alerts.

What kind of support will I receive?

All Firebase apps, including those using no-cost plans, come with email support from Firebase staff during US Pacific business hours. All accounts have unlimited support for billing-related issues, account-related issues, technical (troubleshooting) questions, and incident reports.

Do you offer open-source, nonprofit, or educational discounts?

The no-cost Spark pricing plan can be used by any type of individual or organization, including nonprofits, schools, and open-source projects. Since these plans already include generous quotas, we don't offer any special discounts or plans for open-source, nonprofit, or educational projects.

Do you offer enterprise contracts, pricing, support, or dedicated infrastructure hosting?

The pay-as-you-go Blaze pricing plan is suitable for enterprises of all sizes, and our SLA meets or exceeds the industry standard for cloud infrastructure. However, we don't offer enterprise contracts, pricing, or support, nor do we offer dedicated infrastructure hosting (that is, on-premises installations) for services like our Realtime Database. However, we're actively investigating options for adding some of these features.

Do you offer ad hoc pricing? I only want pay-as-you-go for one or two features.

We offer ad hoc pricing via the pay-as-you-go Blaze pricing plan, where you pay only for the features that you use.

How do the paid Firebase plans work with Ads? Are there no-cost advertising credits with paid plans?

The Firebase pricing plans are separate from Ads, so there are no advertising credits without cost. As a Firebase developer, you are able to "link" your Ads account to Firebase to support conversion tracking.

All ads campaigns are managed directly in Ads, and Ads billing is managed from the Ads console.

What happened to the Flame pricing plan?

In January 2020, the Flame pricing plan ($25/mo of additional quota) was removed as an option for new sign-ups. Existing plan users were granted a grace period to migrate their projects off the Flame plan. In February 2022, the remaining projects on the Flame pricing plan were downgraded to the no-cost Spark pricing plan.
Accordingly,

• Existing Spark pricing plan and Blaze pricing plan projects and any new projects can no longer switch to or sign up for the Flame plan.
• If you moved an existing Flame plan project to a different pricing plan, the project cannot return to the Flame plan.
• Projects downgraded to the Spark pricing plan can be upgraded to the Blaze pricing plan to resume additional paid services.
• References to the Flame plan have been removed from documentation.

Do you have more questions about the Flame plan retirement? Read some of the additional FAQs below.

Want to learn about the other pricing plans offered by Firebase? Visit our Firebase pricing page. If you'd like to start moving any existing projects to another pricing plan, you can do that in the Firebase console for your project.

Additional FAQs about the Flame plan retirement

Where can I find information about privacy and security in Firebase?

Check out the page Privacy and Security in Firebase.

Do the Firebase SDKs log any usage/diagnostic information outside of Analytics?

Yes. Right now, this is iOS-only, but may change in the future. The Firebase Apple platforms SDK includes the FirebaseCoreDiagnostics framework by default. This framework is used by Firebase to collect SDK usage and diagnostics information to help prioritize future product enhancements. FirebaseCoreDiagnostics is optional, so if you would like to opt out of sending Firebase diagnostic logs, you can do so by unlinking the library from your application. You can browse the full source, including logged values, on GitHub

Dynamic Links: What are Firebase's future plans for Dynamic Links?

See Dynamic Links FAQ.

Dynamic Links: Why does my Android app access each Dynamic Link twice?

The getInvitation API clears the saved Dynamic Link to prevent it from being accessed twice. Be sure to call this API with the autoLaunchDeepLink parameter set to false in each of the deep link activities to clear it for the case when the activity is triggered outside the main activity.

What is Firebase User Segmentation Storage?

Firebase User Segmentation Storage stores Firebase installation IDs and related attributes and segments as well as audience lists you've created to provide targeting information to other Firebase services that use them, such as Crashlytics, FCM, Remote Config personalization, and more.