Firebase Extensions help you reduce time spent on development, maintenance,and growth of your app.

When you find aFirebase Extension that solves a need for your appor project, all you do is install and configure the extension. If you needmultiple configurations of the extension, you can install the extension multipletimes, with a different configuration for each instance you install.

With extensions,you don't spend time researching, writing, and debugging the code thatimplements functionality or automates a task for your app or project.

To install or manage extensions, you must be assigned one of these roles:Owner or Editor orFirebase Admin.

To install an extension, your project must be on theBlaze (pay as yougo) plan. Although there is no charge for installing an extension, you might becharged for your use of Firebase services or Cloud services such asCloud Secret Manager, if your usage exceeds the services' freetier.

You can also evaluate extensions before installing them on a project using theExtensions emulator, a component of theFirebase Local Emulator Suite.

Official Firebase extensions

TheofficialFirebase extensions are developed and tested by FirebaseandFirebase Extensions partner services. These extensions are reliable andsecure.

Browse Firebase extensions

Browse Firebase extensions in theExtensions Hub.

View the source code of an extension

To find a link to the source code for an extension,clickLearn more on the extension's card in theExtensions Hub.

Contents of an extension's source code

An extension's source directory includes:

• extension.yaml file — Contains the extension's metadata and definestheresources created, the Google APIs andaccess roles required foroperation, and any user-configured parameters (environment variables) for theextension

• functions directory — Contains the files for the source code for theextension

• README file — Lists the extension's metadata (but in morehuman-readable format) as well as the content from the PREINSTALL file

• PREINSTALL file — Describes how the extension works, any necessarypre-installation tasks, configuration requirements, and details about theextension

• POSTINSTALL file — Describes specific usage instructions and any furtherintegration requirements

Resources for an extension

Every Firebase project contains several types of "resources". Project resourcescan include things like deployed Cloud Functions, database instances,Cloud Storage buckets, Cloud Scheduler jobs, and Cloud Secret Manager data.

When you install an extension, Firebase creates newextension-instance-specificresources in your project. These resources are required by the extension tooperate.

Note that, if youuninstall an instance of anextension, all theresources that Firebase created specifically for that instance of the extensionto operate (like a set of functions) are deleted. However, the following arenot deleted:

• Any artifacts created by the extension (like stored images).

• Any other resources in your project, like a database instance orCloud Storagebucket. Even if the extension interacted with these other resources, theyare notextension-specific, so they aren't deleted if the extension isuninstalled.

Using theFirebase console, theFirebase CLI, or autogenerated SDKs {: #console-vs-cli}

You can install and manage extensions usingeither theFirebase consoleor theFirebase CLI,or in code usingautogenerated SDKs.

Next Steps

• View detailed information about an extension before you install the extension(Extensions Hub orFirebase CLI).

• Install an extension into your Firebase project using either theFirebase console,theFirebase CLI.orautogenerated SDKs.