This page provides answers to frequently asked questions (FAQs) about the
upcoming deprecation of Firebase Extensions.
Why are we deprecating Firebase Extensions?
Due to upcoming changes and deprecations within our underlying Google Cloud
infrastructure, we will be sunsetting the managed Firebase Extensions
service.
Will existing deployed extensions stop working after March 31, 2027?
No. Already deployed extensions run directly on standard Google Cloud
infrastructure (such as Cloud Functions, Eventarc,
Cloud Run, and Cloud Tasks) and will continue to execute
indefinitely. However, after March 31, 2027, users will lose all ability to
update, reconfigure, or uninstall these extensions through the
Firebase console or CLI.
What happens if a user does nothing?
If a user takes no action, their existing deployed functions will continue to
run as standard assets. However:
- They cannot change configuration parameters or update environment variables.
- They cannot apply bug fixes, security patches, or dependency upgrades.
- Most extensions are currently built on the legacy Cloud Functions v1
SDK, which is tied to older Node.js runtimes. Once these legacy runtimes
are fully decommissioned by Google Cloud, the functions may stop running or
be disabled. See
Runtime support.
What should I do as an extension user?
If you are an extension user and you no longer use your installed extensions,
uninstall them before
March 31, 2027.
Post-decommissioning, the standard "Uninstall" button in the Firebase console
and corresponding CLI commands will be removed. Users must manually delete
all associated Google Cloud resources—including the individual
Cloud Functions, Secret Manager secrets, Cloud Tasks queues,
and custom IAM service accounts—via the Google Cloud console.
However, if you actively use your installed extensions,
update them to
their latest versions now and keep them updated. In September 2026, the
Firebase team will reach out with comprehensive migration
documentation, tools, and detailed transition options.
Is anything replacing Firebase Extensions?
In September 2026, the Firebase team will reach back out to users
with more information on how to migrate installed extensions to self-managed
functions with similar behavior. These self-managed functions can continue to
be updated and reconfigured after the Extensions decommissioning. We'll
provide detailed transition options, migration tools, and documentation to
transition your workloads.
What should I do as an extension publisher?
Your actions go into two distinct phases: in the current phase from
June 20, 2026 forward, you can take steps to prepare your extensions for
migration; in the second phase beginning in September 2026, you will be able
to finalize your migration with a shareable function kit.
For now, we encourage you to start by migrating your published extensions to
2nd gen functions, which is a prerequisite for creating a function kit. This
involves packaging your extension logic using the Cloud Functions v2 SDK.
To simplify your transition, we've updated the Cloud Functions v2 SDK with
support for features like declarative security and lifecycle events. You can
now migrate your existing extension code to a 2nd gen function with minimal
changes to your core business logic. For details, see our
migration guide for publishers.
What if I have other questions?
In September 2026, the Firebase team will reach out to both users and
publishers with comprehensive migration documentation, tools, and detailed
transition options.
Meanwhile, publishers who have questions on how to migrate
Firebase Extensions should start by going through our
migration guide for publishers. This
guide includes instructions on how you can stay informed on updates and get
help with providing an alternative to your published extensions.
