FAQ & Troubleshooting

This page provides answers to frequently asked questions (FAQs) about Cloud Functions for Firebase.

Cloud Functions runtime support

How do I upgrade to the latest supported version of Node.js?

1. Make sure you're on the pay-as-you-go Blaze pricing plan.

2. Make sure you are using the latest version of the Firebase CLI.

3. Update the engines field in your functions' package.json.

4. Optionally, test your changes using the Firebase Local Emulator Suite.

5. Redeploy all functions.

How can I make sure I deployed my functions to a specific Node.js runtime?

In the Firebase console, go to the functions dashboard, select a function, and check the function's language under Additional details.

I use Firebase Extensions. Will I be affected by Cloud Functions runtime updates?

Yes. Since extensions use Cloud Functions, the runtime of your extensions will need to be updated on the same timeline as Cloud Functions.

We recommend that you periodically update to the latest version of each extension installed in your project. You can upgrade your projects' extensions via the Firebase console or Firebase CLI.

Cloud Functions pricing

When your project is on the Blaze pricing plan, set up budget alerts using the console. You can use the Blaze plan 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.

Why do I need a billing account to use Cloud Functions for Firebase?

Cloud Functions for Firebase relies on some paid Google services. New function deployments with Firebase CLI 11.2.0 and higher rely on Cloud Build and Artifact Registry. Deployments to earlier versions use Cloud Build in the same way, but rely on Container Registry and Cloud Storage for storage instead of Artifact Registry. Usage of these services will be billed in addition to existing pricing.

Storage space for Firebase CLI 11.2.0 and newer versions

Artifact Registry provides the containers in which functions run. Artifact Registry provides the first 500MB at no cost, so your first function deployments may not incur any fees. If you exceed that threshold, each additional GB of storage is billed at $0.10 per month.

Storage space for Firebase CLI 11.1.x and prior versions

For functions deployed to earlier versions, Container Registry, provides the containers in which functions run. You'll be billed for each container required to deploy a function. You may notice small charges for each container stored—for example, 1GB of storage is billed at $0.026 per month.

To understand more about how your bill might change, review the following

• Cloud Functions pricing: existing no-cost tier is unchanged.
• Cloud Build pricing: Cloud Build provides for a no-cost tier.
• Artifact Registry pricing.
• Container Registry pricing.

Does Cloud Functions for Firebase still have no-cost usage?

Yes. Even on the pay-as-you-go Blaze pricing plan, Cloud Functions provides a no-cost tier for invocations, compute time, and internet traffic. The first 2,000,000 invocations, 400,000 GB-sec, 200,000 CPU-sec, and 5 GB of Internet egress traffic is provided at no cost each month. You'll be charged only for usage that exceeds those thresholds.

After the first 500MB of no-cost storage, each deployment operation will incur small-scale charges for the storage space used for the function's container. If your development process depends on deploying functions for testing, you can further minimize costs by using the Firebase Local Emulator Suite during development.

See Firebase Pricing plans and the Cloud Functions Pricing example scenarios.

Is Firebase planning to raise the quotas and limits for Cloud Functions for Firebase?

No. There are no plans to change the quotas except for the removal of a maximum build time limit; instead of receiving errors or warnings when the daily build quota of 120 minutes is reached, you'll be billed under the terms of the pay-as-you-go Blaze pricing plan. See Quotas and limits.

Can I get the Google Cloud $300 credit?

Yes, you can create a Cloud Billing account in the Google Cloud console to get the $300 credit, then link that Cloud Billing account to a Firebase project.

Learn more about the Google Cloud credit.

Note that if you do this, you have to then set up the Blaze pricing plan in the Firebase console in order for your project to continue working after the $300 credit is exhausted.

I want to follow a codelab to learn about Firebase. Can you give me a temporary billing account?

No, sorry. You can use the Firebase Local Emulator Suite for development without having a Cloud Billing account. Alternatively, try applying for a Google Cloud free trial. If you're still having trouble paying your bill because of this change, contact Firebase Support.

I'm worried I'm going to rack up a huge bill.

You can set up budget alerts in the Google Cloud console to help control costs. Also, you can set limits on the number of billed instances created for each of your functions. To get an idea of costing for typical scenarios, see the Cloud Functions Pricing examples.

How can I check my current billing charges?

View the Usage and billing dashboard in the Firebase console.

I use Firebase Extensions. Do I need a billing account?

Yes. Since extensions use Cloud Functions, extensions will be subject to the same charges as other functions.

To use extensions, you will need to upgrade to the pay-as-you-go Blaze pricing plan. You will be charged a small amount (typically around $0.01 per month) for the Firebase resources required by each extension you install (even if they are not used), in addition to any charges associated with your use of Firebase services.