# Firebase Extensions Shutting Down: Replace Them by 2027 > Firebase Extensions is shutting down on March 31, 2027: installed ones keep running but can't be updated. How to migrate, from docs checked Oct 21, 2026. Canonical: https://app369.com/blog/firebase-extensions-shutting-down-replace-2027/ Last updated: 2026-10-21 [![Simon Dziak](https://app369.com/.netlify/images?w=48&h=48&fm=webp&q=100&url=%2Fimages%2Fszymon.jpg) **Simon Dziak** Founder & developer, App369](https://app369.com/about/szymon-dziak/) [LinkedIn](https://www.linkedin.com/in/szymondziak/) Published October 19, 2026 · Updated October 21, 2026•Facts last verified October 21, 2026•8 min App369https://app369.com/blog/firebase-extensions-shutting-down-replace-2027/ [← Back to Blog](https://app369.com/blog/) ## Key takeaways - →The Firebase Extensions service shuts down on March 31, 2027. Firebase says already-installed extensions keep executing, but after that date you cannot update, reconfigure or uninstall them through the console or CLI, or download their configuration. - →Firebase names two migration paths: an npm-shared function kit, recommended for Stream Firestore to BigQuery and other kits on npm, or forking the extension source and managing it yourself as Cloud Functions v2. - →Run firebase ext:list --project to see every installed extension. Its output includes a Replacement Kit column, and the migration guide needs firebase-tools 15.32.0 or later. - →Most extensions use the legacy Cloud Functions v1 SDK. Firebase warns that functions may stop running or be disabled once Google decommissions the older Node.js runtimes. - →Firebase says to save your configuration while you still can, because after March 31, 2027 you cannot fetch it. Uninstall extensions you no longer use before that date. Pricing an app? Try the free [app cost calculator](https://app369.com/tools/app-cost-calculator/) or get a range for your project in the [instant quote](https://app369.com/instant-quote/). **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 21, 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 | Date | What happens | Source | | --- | --- | --- | | June 18, 2026 | The Stripe-built Firebase extensions repository is archived by its owner and marked not actively maintained | [GitHub](https://github.com/invertase/stripe-firebase-extensions) | | September 2026 | Per the FAQ, additional migration guidance and tools are due this month, and two migration paths are officially supported from it. The page keeps the future tense. The migration guide and the BigQuery kit on npm are live now | [Firebase FAQ](https://firebase.google.com/docs/extensions/faq-and-troubleshooting) | | **March 31, 2027** | The Firebase Extensions service shuts down. Installed extensions keep executing, but key management features are no longer available | [Firebase](https://firebase.google.com/docs/extensions) | For the other Firebase retirements, see my [Firebase deprecations table](https://app369.com/blog/firebase-deprecations-shutdown-dates-2026/). ## 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. To spot extensions in your code too, the free [Firebase shutdown checker](https://app369.com/tools/firebase-shutdown-checker/) looks for an `extensions` key in `firebase.json` in your browser. For instance IDs only, the best-practices page gives `firebase ext:list --json --project | 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. | Path | Firebase recommends it for | What you do | | --- | --- | --- | | NPM-shared function kit | Stream Firestore to BigQuery and other kits published on npm | Install a kit built on the Cloud Functions v2 SDK through the CLI | | Fork and self-manage | Extensions with no npm kit | Fork the source, refactor the triggers into v2 functions, and maintain the code yourself | 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 ``` You can narrow it with `--extension firebase/firestore-bigquery-export` or `--ext-instance `. 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 --project ` and `firebase deploy --only extensions --project `. Then install the kit with `firebase functions:kits:install --template migration --no-configure --package --project `. 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-`. ### 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 --project `. 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. | Extension | Kit package | What its README says | | --- | --- | --- | | Stream Firestore to BigQuery | `@firebase-function-kits/firestore-bigquery-export` | Has a “Migrating from the extension” section. Released on npm (0.1.1 on September 28, 2026) | | Trigger Email from Firestore | `@firebase-function-kits/firestore-send-email` | Has a section on differences from the extension. Carries a pre-release notice | | Resize Images | `@firebase-function-kits/storage-resize-images` | Has a section on differences from the extension. Carries a pre-release notice | The BigQuery kit README gives this migration command, run from your Firebase project directory: ``` firebase ext:migrate --ext-instance ``` 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 --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. If you’d rather move billing into your own code, the [Stripe Billing Fix and Setup](https://app369.com/fixed-price/stripe-billing-setup/) sets up Checkout, the customer portal and a subscription webhook handler, tested in Stripe test mode. If your members were charged one-time payments rather than subscriptions, [this guide covers moving them to auto-renew](https://app369.com/blog/stripe-memberships-not-auto-renewing-fix-2026/), including who has to enter a card again. ## 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](https://app369.com/blog/app-store-google-play-deadlines-2026-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](https://app369.com/fixed-price/flutter-firebase-bug-fix/) 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](https://app369.com/contact/). ## **Want this done at a fixed price?** Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed. - [**App Fix Ticket**from $450One reproducible bug in an existing mobile or web app, diagnosed and fixed.](https://app369.com/fixed-price/flutter-firebase-bug-fix/) ## **Frequently asked questions**
**When does Firebase Extensions shut down?**
On March 31, 2027. The Firebase Extensions page says the service is deprecated and will shut down on that date. The FAQ adds that additional migration guidance and tools were due in September 2026, per the FAQ's own wording.
**Will my installed extensions stop working on March 31, 2027?**
Not on that day. Firebase says already-deployed extensions run on standard Google Cloud infrastructure and continue to execute. What goes away is management: you cannot update, reconfigure or uninstall them through the console or CLI, or download their configuration. Firebase also warns that most extensions use the legacy Cloud Functions v1 SDK, and that they may stop running once older Node.js runtimes are decommissioned.
**What does Firebase recommend instead of extensions?**
Self-managed function kits. Firebase's first path is an npm-shared kit built on the Cloud Functions v2 SDK and installed through the CLI. Its second path, for extensions with no kit, is to fork the extension source, refactor the triggers into v2 functions and maintain the code yourself.
**How do I see which extensions my project has installed?**
Run firebase ext:list --project YOUR_PROJECT_ID. Firebase says the output shows the extension, publisher, instance ID, state, version, your last update and a Replacement Kit column. The console Extensions page also shows whether a replacement is available.
**What about the Stripe payments extension?**
Stripe's Firebase extensions repository says it was archived by its owner on June 18, 2026 and is no longer maintained. It also notes the 2023 transfer of the payments extension to Invertase. That is a repository status, not a Firebase shutdown notice, so check the extension you actually run.
## **Sources** 1. [Firebase, Firebase Extensions overview (deprecation notice)](https://firebase.google.com/docs/extensions) 2. [Firebase, Firebase Extensions deprecation FAQ and troubleshooting](https://firebase.google.com/docs/extensions/faq-and-troubleshooting) 3. [Firebase, migrate an extension to Cloud Functions as a user](https://firebase.google.com/docs/extensions/users/migrate) 4. [Firebase, post-migration best practices](https://firebase.google.com/docs/extensions/migration-best-practices) 5. [GitHub, firebase/extensions repository](https://github.com/firebase/extensions) 6. [GitHub, firestore-bigquery-export function kit README](https://github.com/firebase/extensions/tree/kits/kits/firestore-bigquery-export) 7. [GitHub, firestore-send-email function kit README](https://github.com/firebase/extensions/tree/kits/kits/firestore-send-email) 8. [GitHub, storage-resize-images function kit README](https://github.com/firebase/extensions/tree/kits/kits/storage-resize-images) 9. [GitHub, function kits folder in firebase/extensions](https://github.com/firebase/extensions/tree/kits/kits) 10. [GitHub, Stripe Firebase extensions repository](https://github.com/invertase/stripe-firebase-extensions) Tags #firebase extensions shutting down #firebase extensions deprecated #firebase extensions replacement #firebase extensions march 31 2027 #firebase ext migrate #firebase function kits #firestore bigquery export kit #trigger email firebase replacement #resize images extension replacement #stripe firebase extension archived Generated from app369.com . © 2026 App369. All rights reserved. **Share:** [Share on Twitter](https://twitter.com/intent/tweet?text=Firebase%20Extensions%20Shutting%20Down%3A%20Replace%20Them%20by%202027&url=https%3A%2F%2Fapp369.com%2Fblog%2Ffirebase-extensions-shutting-down-replace-2027%2F) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fapp369.com%2Fblog%2Ffirebase-extensions-shutting-down-replace-2027%2F) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fapp369.com%2Fblog%2Ffirebase-extensions-shutting-down-replace-2027%2F) ## **Related Resources ** [Firebase Studio Shutting Down: How to Migrate by March 2027](https://app369.com/blog/firebase-studio-shutting-down-migrate-project-2027/) [Firebase ML Model Hosting Shutting Down: How to Migrate](https://app369.com/blog/firebase-ml-model-hosting-shutting-down-migrate-2027/) [Firebase Test Lab Shutting Down: Alternatives for 2027](https://app369.com/blog/firebase-test-lab-shutting-down-alternatives-2027/) [Firebase Deprecations: Every Shutdown Date, 2024 to 2027](https://app369.com/blog/firebase-deprecations-shutdown-dates-2026/) [Google Play Games Services v1 Shutdown 2027: Migrate to v2](https://app369.com/blog/play-games-services-v1-shutdown-migrate-to-v2-2027/) [RevenueCat + Stripe + Firebase Stack](https://app369.com/blog/revenuecat-stripe-firebase-monetization-stack-template369/) ## **Related guides ** [

**Firebase Deprecations: Every Shutdown Date, 2024 to 2027**

Firebase deprecations from 2024 to 2027 in one dated table: what stops working, the deadline, and what to move to, from Firebase docs checked Oct 21, 2026.**Read more **](https://app369.com/blog/firebase-deprecations-shutdown-dates-2026/) [

**Firebase Studio Shutting Down: How to Migrate by March 2027**

Firebase Studio is shutting down on March 22, 2027, and remaining data is deleted. The timeline and migration paths, from Firebase pages checked Oct 21, 2026.** Read more **](https://app369.com/blog/firebase-studio-shutting-down-migrate-project-2027/) [

**App Store and Google Play Deadlines for 2026 and 2027**

Dated table of App Store, Google Play, Firebase and Google API deadlines for mobile apps in 2026 and 2027, each linked to its source. Checked Oct 21, 2026.** Read more **](https://app369.com/blog/app-store-google-play-deadlines-2026-2027/)