The page is a collection of FAQs and troubleshooting help for Firebase in
general, as well as for specific products.
Do you have other challenges or can't find your issue described on this page?
- [Find more troubleshooting help](https://firebase.google.com/support.md.txt#firebase-troubleshooter)
- [Ask the community (like Stack Overflow, Reddit, and a Google forum)](https://firebase.google.com/support.md.txt#ask-the-firebase-community)
- [Report a bug or request a feature](https://firebase.google.com/support/troubleshooter/report.md.txt)
*** ** * ** ***
## Platforms and frameworks
Visit the platform-specific troubleshooting \& FAQ pages for helpful tips and
answers for more FAQ.
- [iOS+](https://firebase.google.com/docs/ios/troubleshooting-faq.md.txt)
- [Android](https://firebase.google.com/docs/android/troubleshooting-faq.md.txt)
- [Unity](https://firebase.google.com/docs/unity/troubleshooting-faq.md.txt)
*** ** * ** ***
## Firebase projects and Firebase apps
##### 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](https://firebase.google.com/products) 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](https://firebase.google.com/docs/projects/learn-more.md.txt) --- 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](https://firebase.google.com/docs/projects/dev-workflows/general-best-practices) --- 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](https://console.cloud.google.com/iam-admin/labels) for your project in the
Google Cloud console. Learn more about this label in our
[FAQ](https://firebase.google.com/support/faq.md.txt#project-label-firebase-enabled).
##### Is accepting the Firebase Terms of Service required to start using Firebase?
In order to access and use all capabilities of Firebase in a
Google Cloud project, you need to accept the
[Firebase Terms of Service](https://firebase.google.com/terms.md.txt). You also need to accept the Firebase Terms
in order to "add Firebase" to an existing Google Cloud project.
**You only need to accept the Firebase Terms once for your Google Account** no
matter how many projects you have access to. When you accept the terms, you're
accepting them *for your Google Account* ; acceptance is *not* at the
project-level for all project members.
You can accept the Firebase Terms through the [Firebase console](https://console.firebase.google.com/) using any of
the following options. When prompted, accept the Terms. If you're not
prompted to accept the Firebase Terms, then you've already accepted them.
- Accept the Firebase Terms directly using the
[Terms acceptance workflow](https://console.firebase.google.com/?forceCheckTos=true).
- Create a new Firebase project using the Firebase console, and then accept
the Firebase Terms.
- Open an existing Firebase project in the Firebase console, and then
accept the Firebase Terms (for example,
someone has invited you to become a project member (that is, a principal)
on the project).
- Open an existing Google Cloud project in the Firebase console,
["add Firebase"](https://firebase.google.com/docs/projects/use-firebase-with-existing-cloud-project.md.txt#how-to-add-firebase_console)
to it, and then accept the Firebase Terms.
> [!NOTE]
> **Note:** Accepting the Firebase Terms is *not* possible using the Firebase CLI, REST API, or Terraform. It can only be done using the Firebase console using one of the options described above.
> [!IMPORTANT]
> **Important:** If you signed an offline variant of the Google Cloud Master Agreement for use of specified Firebase services under the same Google Cloud Platform Account, the [Firebase Terms](https://firebase.google.com/terms.md.txt) do not apply to your use of such Firebase services, and your offline terms govern your use of such Firebase services.
##### 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](https://docs.cloud.google.com/resource-manager/docs/creating-managing-organization).
##### 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](https://console.firebase.google.com/).
- Using a programmatic option:
- Call the Firebase Management REST API endpoint [`projects.addFirebase`](https://firebase.google.com/docs/reference/firebase-management/rest/v1beta1/projects/addFirebase.md.txt).
- Run the Firebase CLI command [`firebase projects:addfirebase`](https://firebase.google.com/docs/cli.md.txt#management-commands).
- Use [Terraform](https://firebase.google.com/docs/projects/terraform/get-started.md.txt).
Learn more details about
[adding
Firebase to a Google Cloud project](https://firebase.google.com/docs/projects/use-firebase-with-existing-cloud-project).
##### How does Firebase's integration with Google Cloud work?
Firebase is deeply integrated with
[Google Cloud](https://cloud.google.com/).
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](https://cloud.google.com/pricing/).
You can
also export data from Google Cloud directly to
BigQuery for analysis. To learn more, see
[Link BigQuery with Firebase.](https://support.google.com/firebase/answer/6318765)
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](https://cloud.google.com/) for more details.
##### Why does my Google Cloud project have a label of
`firebase:enabled`?
In the
[*Labels* page](https://console.cloud.google.com/iam-admin/labels)
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](https://firebase.google.com/docs/projects/learn-more#firebase-cloud-relationship).
**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](https://firebase.google.com/docs/reference/firebase-management/rest/v1beta1/projects/list)
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](https://console.firebase.google.com/) (or, for advanced use cases, using the
[Firebase Management REST API](https://firebase.google.com/docs/reference/firebase-management/rest/v1beta1/projects/addFirebase.md.txt)
or the
[Firebase CLI](https://firebase.google.com/docs/cli.md.txt#management-commands)).
##### 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](https://firebase.google.com/docs/projects/use-firebase-with-existing-cloud-project#how-to-add-firebase).
Also, you might want to review the FAQ
["Why isn't my Firebase project showing up in my list of Firebase projects?"](https://firebase.google.com/support/faq.md.txt#gcp-projects-not-loading-in-console)
##### 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](https://firebase.google.com/docs/projects/api/reference/rest/v1beta1/projects/list)
- 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](https://console.cloud.google.com/).
- Make sure that your project has the label `firebase:enabled` in the [*Labels* page](https://console.cloud.google.com/iam-admin/labels) 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](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt) (Owner, Editor, Viewer) or a role that has Firebase-related permissions in it, for example a [Firebase predefined
role](https://firebase.google.com/docs/projects/iam/roles-predefined). You can view your role(s) in the [*IAM* page](https://console.cloud.google.com/iam-admin/iam) 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](https://firebase.google.com/support/troubleshooter/access/project/lost.md.txt).
##### 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](https://support.google.com/cloud/answer/6330231).
- 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](https://firebase.google.com/docs/projects/dev-workflows/general-best-practices).
##### 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](https://firebase.google.com/docs/projects/dev-workflows/general-best-practices).
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](https://console.cloud.google.com/iam-admin/quotas)
and have it evaluated. Learn more about
[quota management](https://docs.cloud.google.com/docs/quotas/view-manage#requesting_higher_quota) 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
[**Project settings**](https://console.firebase.google.com/project/_/settings/general/) \> **General**,
then in the *Your project* card under *Environment*, click
to change the environment type.
##### Where can I find the App ID for my Firebase app?
In the Firebase console, go to your
[**Project settings**](https://console.firebase.google.com/project/_/settings/general/). 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**](https://support.google.com/firebase/answer/6392038#permissions-and-roles), 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.
### Permissions and access to Firebase projects
##### 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** \> [**Users and permissions** tab](https://console.firebase.google.com/project/_/settings/iam?useAutoProject=true). You can assign any of the [basic roles](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt) (Owner, Editor, Viewer), the [Firebase Admin/Viewer roles](https://firebase.google.com/docs/projects/iam/roles-predefined-all-products.md.txt), or any of the [Firebase predefined product-category
roles](https://firebase.google.com/docs/projects/iam/roles-predefined-category).
- The Google Cloud console offers an expansive set of tools to assign roles to project members in the **IAM \& Admin** [**IAM** page](https://console.cloud.google.com/iam-admin/iam). You can also create and manage [custom roles](https://firebase.google.com/docs/projects/iam/roles-custom.md.txt), 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](https://firebase.google.com/support/troubleshooter/contact)
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*](https://console.firebase.google.com/project/_/settings/iam?useAutoProject=true) 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](https://console.cloud.google.com/iam-admin/iam) 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](https://firebase.google.com/support/troubleshooter/contact)
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](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt)
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](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt).
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"](https://cloud.google.com/resource-manager/docs/managing-notification-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](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt) 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](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt) to open the
project and perform the required actions. Learn more about
[why and when to assign the
Owner role](https://firebase.google.com/support/faq#why-when-to-assign-project-owner).
### API keys for Firebase
##### Are Firebase API keys secret? Can they be included in my code or
configuration files?
**Here are the most important things to learn about API keys for
Firebase services:**
- **Public by design** : API keys for Firebase services only *identify* your Firebase project and app to those services. *Authorization* is handled through Google Cloud IAM permissions, Firebase Security Rules, and Firebase App Check.
- **Apply restrictions** : All Firebase-provisioned API keys are *automatically* restricted to [Firebase-related APIs](https://firebase.google.com/docs/projects/api-keys.md.txt#faq-required-apis-for-restricted-firebase-api-key). For **all** API keys in your project, it's critical that you [apply appropriate API restrictions](https://firebase.google.com/docs/projects/api-keys.md.txt#apply-restrictions) to prevent unauthorized use of your project's quota for APIs.
- **Use only for Firebase services** : Use your Firebase-provisioned API keys *only* for [Firebase-related APIs](https://firebase.google.com/docs/projects/api-keys.md.txt#faq-required-apis-for-restricted-firebase-api-key). If your app uses any other APIs (for example, the Places API for Maps or the Gemini Developer API), use a [separate API key](https://firebase.google.com/support/faq.md.txt#use-separate-keys-for-specific-apis) and restrict it to the applicable API. *In particular, never include the
Gemini Developer API in the allowlist for a publicly accessible
API key or a key used for other services.*
- **Security Rules and App Check are critical** : Security of your Realtime Database, Cloud Firestore, and Cloud Storage *data* is enforced using Firebase Security Rules, and protection of covered APIs is by Firebase App Check --- not by keeping your Firebase API key secret.
**If your app's setup follows the above guidelines, then
*API keys restricted to Firebase services* do *not* need
to be treated as secrets, and it's safe to include them in your code or
configuration files.**
##### I received an email from Google Cloud about a "publicly accessible
Google API key for your Google Cloud project". What do I need to do?
If you've received an email from Google Cloud about a "publicly accessible
Google API key for your Google Cloud project" *and the API key listed in
the email is your Firebase API key* , then make sure that the API key meets
the following requirements to be safe to include in your code or configuration
files. You can verify the following in the **APIs \& Services** \>
[**Credentials** page](https://console.cloud.google.com/apis/credentials)
of the Google Cloud console.
- It's the API key that you use for your Firebase app and *only* for Firebase services. These keys are usually called `Browser key (auto created by Firebase)` or `Android key (auto created by Firebase)` or `iOS key (auto created by Firebase)`.
- It has all the [required
Firebase-related APIs included in the key's "API restrictions"
allowlist](https://firebase.google.com/docs/projects/api-keys#faq-required-apis-for-restricted-firebase-api-key).
- It does *not* have any other APIs in its "API restrictions" allowlist. In particular, the list should ***not*** have `Generative Language API`.
Also, make sure that you're using Firebase Security Rules and App Check as recommended
for the Firebase products that you use.
You can learn details about API keys for Firebase and find a list of FAQs in
[Learn about using and managing API keys for
Firebase](https://firebase.google.com/docs/projects/api-keys)
**Important** : The API key that you use for calls to the Gemini Developer API in your app should *never* be included in your code or configuration files. It must be protected from public exposure. In the Google Cloud console, it will be called `Gemini API Key` or `Gemini Developer API key (auto created by Firebase)`, and it will be restricted to the `Generative Language API`.
*** ** * ** ***
## Firebase console
##### 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.
> [!NOTE]
> If the Firebase console itself isn't loading for you or displays browser errors, check out the FAQ ["Why is the
> Firebase console not loading for me?"](https://firebase.google.com/support/faq#console-troubleshoot-loading) for applicable troubleshooting steps.
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](https://console.cloud.google.com/apis/library/firebase.googleapis.com) for the project.
- Make sure that you're assigned one of the [basic IAM roles](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt) (Owner, Editor, Viewer) or a role that has Firebase-related permissions in it, for example a [Firebase predefined
role](https://firebase.google.com/docs/projects/iam/roles-predefined). You can view your role(s) in the [*IAM* page](https://console.cloud.google.com/iam-admin/iam) 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](https://firebase.google.com/support/troubleshooter/access/project/lost.md.txt).
##### 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](https://status.firebase.google.com/) for any possible service interruptions.
2. Make sure that you're using a [supported browser](https://firebase.google.com/support/faq.md.txt#console-browser-support).
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](https://developer.chrome.com/docs/devtools/open/#chrome) for any [errors](https://support.google.com/chrome/answer/95669).
If none of the troubleshooting steps above resolve the issue, contact
[Firebase Support](https://firebase.google.com/support/troubleshooter/access/project/loading).
##### 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](https://myaccount.google.com/language).
To change your language preference, see
[Change language](https://support.google.com/accounts/answer/32047).
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](https://firebase.google.com/docs/projects/iam/overview.md.txt).
Firebase supports the
[fundamental (basic) roles](https://firebase.google.com/docs/projects/iam/roles-basic.md.txt)
of Owner, Editor, and Viewer:
- A project **Owner** can add other members to the project, set up [integrations](https://console.firebase.google.com/project/_/settings/integrations?useAutoProject=true) (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**](https://firebase.google.com/docs/projects/iam/roles-predefined.md.txt) --- Curated Firebase-specific roles that enable more granular access control than the basic roles of Owner, Editor, and Viewer.
- [**Custom roles**](https://firebase.google.com/docs/projects/iam/roles-custom.md.txt) --- Fully customized IAM roles that you create to tailor a set of permissions that meet the specific requirements of your organization.
> [!NOTE]
> To manage Firebase integrations with other Google products and services (for example, AdMob, Google Analytics, or Google Play), you may need *additional* permissions, roles, or access levels that are managed within those specific products and services. To learn more, review the documentation for the specific integration.
##### How does the console's "sample app experience" work? What happens and what can I do?
The Firebase console provides a
[sample app experience](https://console.firebase.google.com/?idxSampleProjectTemplateId=gemini&dlAction=IdxSampleProject)
so that you have a real working app to explore and experiment with Firebase and
other Google services (like the Gemini API).
##### Automatic Firebase setup and deployment of the sample app
When you go through the
[sample app experience](https://console.firebase.google.com/?idxSampleProjectTemplateId=gemini&dlAction=IdxSampleProject)
in the Firebase console, we automatically do the following for you:
- Create a new Firebase project for your sample app
- Register a Firebase Web App in the new Firebase project
- Enable services and APIs that are used by the sample app (for example, Firebase Authentication, Cloud Firestore, etc.)
- Provision any required resources (for example, database instances and security rules)
- Set up Firebase AI Logic to use the Gemini Developer API
- Deploy the sample app to a temporary preview URL using Firebase Hosting (by default, this URL [expires in 7 days](https://firebase.google.com/docs/hosting/manage-hosting-resources.md.txt#preview-channel-expiration))
> [!NOTE]
> **Note:** Deploying to a temporary preview URL using Firebase Hosting (called a ["preview channel"](https://firebase.google.com/docs/hosting/test-preview-deploy.md.txt#preview-channels%22)) is an important part of web app development. Preview channels ensure that your app isn't deployed to a live Hosting site before the app is ready for production use. You can view all deploys of your sample app in the [Hosting dashboard](https://console.firebase.google.com/project/_/hosting/main?useAutoProject=true) of the Firebase console.
##### Explore the sample app's codebase
- **Option 1: Open a *personalized* version of the sample app's codebase in
Firebase Studio**
The sample app experience provides a pathway to open a *personalized*
version of the sample app's codebase in
[Firebase Studio](https://studio.firebase.google.com/)
(Google's browser-based workspace for full-stack app development). After
your project and app are set up (see above), you can find links to
Firebase Studio in banners in the Firebase console and at the top of
the deployed app.
When you open your sample app in Firebase Studio, we automatically do
the following for you:
- Use the same Firebase project, Firebase Web App, and resources created in the initial setup (see above)
- Insert your sample app's Firebase configuration into the codebase (usually into `src/bootstrap.js`)
Within Firebase Studio, you can explore the codebase to understand how
you can interact with various Firebase and Google services.
- **Option 2: View the *public, non-personalized* version of the sample app's
codebase in GitHub**
Alternatively, you can view the *public, non-personalized* version of the
sample app's codebase in GitHub.
- "Planning with the Gemini API" - [GitHub repo](https://github.com/FirebaseExtended/make-it-so-angular/tree/trip-plan)
*** ** * ** ***
## Firebase Local Emulator Suite
Visit the
[Local Emulator Suite FAQ and troubleshooting](https://firebase.google.com/docs/emulator-suite/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Pricing
For pricing FAQs specific to a product, see the product's section on this page
or within its dedicated product documentation.
> [!CAUTION]
> When your project is on the Blaze pricing plan, [**set up budget alerts**](https://firebase.google.com/docs/projects/billing/budget-alerts.md.txt). You can use the [Blaze pricing plan calculator](https://firebase.google.com/pricing.md.txt#blaze-calculator) to estimate your monthly costs.
>
> Be aware that **budget alerts do *not* cap your usage or
> charges** --- they are *alerts* about your costs so that you can
> take action, if needed. For example, you might consider
> [using budget notifications to programmatically disable
> Cloud Billing on a project](https://cloud.google.com/billing/docs/how-to/disable-billing-with-notifications).
>
>
> If you use Firebase AI Logic, Firebase App Hosting, Cloud Functions for Firebase, and Firebase Extensions, we strongly recommend that you
> also
> [**set up spend caps**](https://firebase.google.com/docs/projects/billing/spend-caps.md.txt),
> which will pause any new usage of the applicable service if your project
> reaches the budget set for that service.
##### Which products are paid? Which are no-cost?
For detailed information about paid versus no-cost products, see
[Firebase pricing plans](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans.md.txt).
##### Does Firebase offer no-cost trial credits for paid products?
Firebase paid services can be used under the
[Google Cloud Free Trial](https://docs.cloud.google.com/free/docs/free-cloud-features#free-trial).
New Google Cloud and Firebase users can take advantage of a 90-day trial period
that includes $300 in free Cloud Billing credits to explore and evaluate
Google Cloud and Firebase products and services.
During the Google Cloud Free Trial period, you'll be provided a Free Trial
Cloud Billing account. Any Firebase project that's linked to that billing
account will be on the [pay-as-you-go Blaze pricing plan](https://firebase.google.com/pricing.md.txt) during the Free Trial period.
Don't worry, **linking a Firebase project to this
Free Trial Cloud Billing account does not enable us to charge you for usage
beyond these credits** . You are *not* charged for usage beyond these credits
unless you explicitly enable billing by upgrading your
Free Trial Cloud Billing account to a paid account. You can upgrade to a paid
account at any time during the trial. After you've upgraded to a paid account,
you can still use any remaining credits (within the 90-day period).
Once the free trial expires and if you have *not* upgraded the
Free Trial Cloud Billing account to a paid account, then your linked
Firebase project is automatically
[downgraded to the Spark pricing plan](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans.md.txt#downgrade-blaze-to-spark).
Note that you can
[upgrade to the Blaze pricing plan](https://console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered)
again at any time.
Learn more about the
[Google Cloud Free Trial](https://docs.cloud.google.com/free/docs/free-cloud-features#free-trial).
##### How do I know which pricing plan is right for me?
For detailed information about pricing plans, see
[Firebase pricing plans](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans.md.txt).
##### 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,
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 Cloud 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 [pay-as-you-go Blaze pricing plan](https://firebase.google.com/pricing.md.txt) (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 [no-cost Spark pricing plan](https://firebase.google.com/pricing.md.txt).
##### 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](https://console.firebase.google.com/project/_/usage?useAutoProject=true)
- [Authentication *Usage* dashboard](https://console.firebase.google.com/project/_/authentication/usage?useAutoProject=true) (specifically for Phone authentication instances)
- [Cloud Firestore *Usage* dashboard](https://console.firebase.google.com/project/_/firestore/usage?useAutoProject=true)
- [Cloud Functions *Usage* dashboard](https://console.firebase.google.com/project/_/functions/usage?useAutoProject=true)
- [Cloud Storage *Usage* dashboard](https://console.firebase.google.com/project/_/storage/usage?useAutoProject=true)
- [Hosting *Usage* dashboard](https://console.firebase.google.com/project/_/hosting/usage?useAutoProject=true)
- [Realtime Database *Usage* dashboard](https://console.firebase.google.com/project/_/database/usage?useAutoProject=true)
##### Can I cap usage on the Blaze pricing plan?
For several services, you can cap your usage on the
Blaze pricing plan by setting up
[**spend cap budgets**](https://firebase.google.com/docs/projects/billing/spend-caps.md.txt).
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 alerts-only budgets](https://firebase.google.com/docs/projects/billing/budget-alerts.md.txt).
##### What kind of support will I receive?
All Firebase apps, including those using the no-cost Spark pricing plan, 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](https://firebase.google.com/terms/service-level-agreement.md.txt)
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.
Want to learn about the other pricing plans offered by Firebase? Visit our
[Firebase pricing page](https://firebase.google.com/pricing.md.txt).
*** ** * ** ***
## Privacy
##### Where can I find information about privacy and security in Firebase?
Check out the page
[Privacy and Security in Firebase](https://firebase.google.com/support/privacy.md.txt).
##### 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 SDK for Apple platforms 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](https://github.com/firebase/firebase-ios-sdk/tree/master/Firebase/CoreDiagnostics)
*** ** * ** ***
## A/B Testing
Visit the
[A/B Testing FAQ and troubleshooting](https://firebase.google.com/docs/ab-testing/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## AdMob
Visit the
[AdMob FAQ and troubleshooting](https://firebase.google.com/docs/admob/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Analytics
Visit the
[Analytics FAQ and troubleshooting](https://firebase.google.com/docs/analytics/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Authentication
Visit the
[Authentication FAQ and troubleshooting](https://firebase.google.com/docs/auth/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Cloud Functions
Visit the
[Cloud Functions for Firebase FAQ and Troubleshooting](https://firebase.google.com/docs/functions/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Cloud Messaging
Visit the
[FCM FAQ and troubleshooting](https://firebase.google.com/docs/cloud-messaging/troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Cloud Storage for Firebase
Visit the
[Cloud Storage for Firebase troubleshooting \& FAQ page](https://firebase.google.com/docs/storage/faq-and-troubleshooting.md.txt)
for helpful tips and answers to more FAQs.
*** ** * ** ***
## Crashlytics
Visit the
[Crashlytics FAQ and troubleshooting](https://firebase.google.com/docs/crashlytics/troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Dynamic Links
Visit the
[Dynamic Links deprecation FAQ](https://firebase.google.com/support/dynamic-links-faq.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Hosting
Visit the
[Firebase Hosting FAQ and Troubleshooting](https://firebase.google.com/docs/hosting/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Performance Monitoring
Visit the
[Performance Monitoring FAQ and troubleshooting](https://firebase.google.com/docs/perf-mon/troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Realtime Database
Visit the
[Realtime Database FAQ and troubleshooting](https://firebase.google.com/docs/database/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Remote Config
Visit the
[Remote Config FAQ and troubleshooting](https://firebase.google.com/docs/remote-config/faq-and-troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Test Lab
Visit the
[Test Lab troubleshooting](https://firebase.google.com/docs/test-lab/troubleshooting.md.txt)
page for helpful tips and answers to more FAQs.
*** ** * ** ***
## Firebase App Indexing
##### What happened to Firebase App Indexing?
Firebase App Indexing is no longer the recommended way of indexing content
for display as suggested results in Google Search App. This FAQ points to other
useful developer products.
#### Apple platforms
[Universal Links](https://developer.apple.com/documentation/Xcode/allowing-apps-and-websites-to-link-to-your-content)
are the recommended way of linking users directly from search results, websites
and other apps to specific content within your app.
#### Android
> [!CAUTION]
> **Caution:** The Google Search App for Android no longer uses local content indexed via Firebase App Indexing to provide results to users.
[Android App Links](https://developer.android.com/training/app-links)
are the recommended way of linking users directly from search results, websites
and other apps to specific content within your app.
You might also be interested in the following options:
- [**App Search**](https://developer.android.com/guide/topics/search/appsearch):
High-performance on-device search
- [**App Actions**](https://developers.google.com/assistant/app/overview):
Let users launch and control Android apps with their voice, using
Google Assistant.
- [**Android Shortcuts**](https://developers.google.com/assistant/app/dynamic-shortcuts):
Provide users with quick methods to perform an action or access content in
your app.
*** ** * ** ***
## Firebase User Segmentation Storage
##### What is Firebase User Segmentation Storage?
Firebase User Segmentation Storage stores
[Firebase installation IDs](https://firebase.google.com/docs/projects/manage-installations.md.txt)
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.