AI & TechnologyFirebase Extensions Shutting Down: Replace Them by 2027

The Firebase Extensions service shuts down on March 31, 2027, and Firebase says extensions you already installed keep running but can no longer be updated, reconfigured or uninstalled through the console or CLI. Firebase's recommended replacement is a self-managed function kit, which is regular Cloud Functions code that lives in your own repository.

The facts below come from Firebase's documentation and a few GitHub repositories, as shown in the sources. I checked each one on October 18, 2026. Google can change a date, so open the linked page before you plan around it.

Disclosure: App369 is my studio. I build and fix Flutter and Firebase apps, and the last section mentions what I sell. Google doesn't pay me for anything on this page.

The dated timeline

For the other Firebase retirements, see my Firebase deprecations table.

What Firebase says happens to installed extensions

The notice on the Extensions page reads: "The Firebase Extensions service is deprecated and will shut down on March 31, 2027." It says already installed extensions will execute indefinitely, and recommends moving to self-managed function kits.

The FAQ spells out the loss. Deployed extensions run on standard Google Cloud infrastructure. After March 31, 2027, you cannot update, reconfigure or uninstall them through the console or CLI, and you cannot download their existing configuration. In practice, Firebase says that means you cannot:

• change parameters or environment variables
• apply bug fixes, security patches or dependency upgrades
• download the configuration to recreate the setup elsewhere

There is a second risk. Firebase says most extensions use the legacy Cloud Functions v1 SDK. Once Google decommissions the older Node.js runtimes, those functions may stop running or be disabled. After that, the console's Uninstall button and the related CLI commands are removed, and you would have to delete the resources by hand in the Google Cloud console.

My advice: treat March 31, 2027 as the last day you can still change anything, not as the day things break. Plan the move for the winter, while the tools still work.

What an extension leaves in your project

Firebase's FAQ says that after the shutdown you would delete these by hand in the Google Cloud console: the individual Cloud Functions, Secret Manager secrets, Cloud Tasks queues and custom IAM service accounts.

The FAQ also says extensions run on Cloud Functions, Eventarc, Cloud Run and Cloud Tasks, and that the Stream Firestore to BigQuery extension creates BigQuery datasets, tables and views during setup.

Those four kinds of resource matter because they are what you would delete manually once the uninstall button is gone. The best-practices page also describes what installing and deploying a kit creates: functions, Eventarc triggers, Cloud Tasks queues and a service account with IAM roles. It does not say what remains after an uninstall, so check your project's resources after you remove one.

Step 1: list what you have installed

Firebase's user migration guide gives this command:

firebase ext:list --project my-project

Firebase says the output shows Extension, Publisher, Instance ID, State, Version, Your last update and Replacement Kit. The console Extensions page also shows replacement availability. The CLI output carries a notice that Firebase Extensions will shut down on March 31, 2027.

Run it for every project you own, including staging and old ones. For instance IDs only, the best-practices page gives firebase ext:list --json --project <project-id> | jq -r '.result[].instanceId'.

The guide needs firebase-tools 15.32.0 or later. Firebase also lists the IAM roles you need, including roles/firebaseextensions.editor, roles/cloudbuild.builds.editor, roles/artifactregistry.writer, roles/run.developer and the two service account roles. If a role is missing, the migration fails, so check before you start.

Step 2: uninstall what you don't use

Firebase says users who no longer need an extension should uninstall it before March 31, 2027. This is the cheapest fix. Every extension you remove is one less thing to migrate.

Step 3: pick one of Firebase's two paths

Firebase says it officially supports two primary pathways.

Firebase also says upgrading to v2 is strongly recommended, and required for function kits.

The kit path, in Firebase's words

The user guide calls ext:migrate the recommended option:

firebase ext:migrate --project <project-id>

You can narrow it with --extension firebase/firestore-bigquery-export or --ext-instance <instance-id>. Firebase describes the command as one that selects the extension and instance, updates it, installs and configures the kit, deploys it, verifies it and uninstalls the extension. It warns that --force deletes the extension right after deploying the kit, with no verification. I would not use --force on a production project.

The manual option is two steps. First update the extension with firebase ext:update <extension-instance-id> --project <project-id> and firebase deploy --only extensions --project <project-id>. Then install the kit with firebase functions:kits:install --template migration --no-configure --package <npm-package-name> --project <project-id>. That creates a directory under function-kits/.

Firebase says kits are standard 2nd gen Cloud Functions managed with the Firebase CLI. Event-triggered kits use Eventarc, which can take a few minutes to provision. To check a kit after deploy, the guide lists firebase functions:logs and firebase functions:list | grep kit-<kit instance id>.

Save your configuration first

Firebase says that if you cannot migrate in time, save the configuration now, because after March 31, 2027 you cannot fetch it. The best-practices page uses firebase ext:export --mode functions. Open the page's "Saving configuration for future migration" section for the exact syntax and output files.

Undoing a migration

Firebase's warning here is specific. To undo, reinstall the extension first, then run firebase functions:kits:uninstall --instance <kit-instance-id> --project <project-id>. The page says not to uninstall the kit before reinstalling the extension, or the CLI will delete the .env file.

Which popular extensions have a documented kit

The firebase/extensions repository has a kits branch with 13 kit folders, including firestore-bigquery-export, firestore-send-email, storage-resize-images, firestore-counter, firestore-translate-text and delete-user-data. The main repository page itself carries no shutdown notice and says nothing about replacements, so the facts below come from each kit's README.

The BigQuery kit README gives this migration command, run from your Firebase project directory:

firebase ext:migrate --ext-instance <instance-id>

It says the command exports the instance's configuration, deploys the kit, then offers to uninstall the extension. It also warns that writes made while the new trigger warms up can reach neither exporter. To avoid that gap, the README says to answer no to the uninstall prompt, confirm the kit logs every write, then run firebase ext:uninstall <instance-id> --immediate. It says running both at once is safe, because BigQuery deduplicates on the shared event ID on a best-effort basis.

For the email and image kits, the READMEs I read say the kit "has not been released yet," that the npm latest tag is a placeholder, and that pre-release builds are published under the next tag. Both mention firebase ext:migrate, which prompts for a region and writes FUNCTION_DEFAULT_REGION to your .env. Check the README and the npm page for release status before you plan a production move to either one.

The Stripe payments extension

This one has a different history. Stripe's repository, described as "Repository of Firebase Extensions built by Stripe," was archived by its owner on June 18, 2026. Its notice says the repository is not actively maintained and that no further updates, bug fixes or support will be provided. It also records a 2023 notice that the payments extension was transferred to Invertase, with a recommendation to uninstall stripe/firestore-stripe-payments and install invertase/firestore-stripe-payments. The page says nothing about the Firebase Extensions shutdown. So if you run a Stripe extension, check which publisher your instance comes from in the ext:list output.

A short checklist

1. Run firebase ext:list in every project and write down each instance.
2. Save the configuration of every extension, because you can't fetch it after March 31, 2027.
3. Uninstall every extension you no longer use, once its config is saved.
4. For each one, check the Replacement Kit column and the kit's README.
5. If there is no kit, plan a fork or a rewrite as Cloud Functions v2.
6. Run the replacement before you uninstall the old one. Only the BigQuery kit README says both can run at once. For email or image extensions, test in a staging project or pause writers so you don't send or process twice.
7. Finish well before March 31, 2027.

My advice: migrate the extension that touches money or user data first, and keep the old one installed until the replacement has logged real traffic. For email or image extensions, do that check in a staging project first, so nothing is sent or processed twice.

For every other dated Apple, Google Play and Firebase requirement in 2026 and 2027, see App Store and Google Play deadlines for 2026 and 2027.

Need a hand?

If your app depends on Firebase Extensions and you want them replaced with code you control before the shutdown, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. Or send me a short description.