Firebase will retire Extensions by March 2027, the third major product wind-down in about a year, after Studio and ML.
Firebase Extensions, the packaged-integration marketplace for wiring up services like resized image uploads or Stripe billing without writing the glue code, is going away. Firebase’s extensions FAQ confirms the service is deprecated and will shut down March 31, 2027, with console and CLI support for installing, updating, reconfiguring or uninstalling an extension removed on that date (Firebase Extensions Deprecation FAQ).
What actually stops working #
Already-installed extensions keep running past the deadline. Under the hood, an extension is just Cloud Functions, Eventarc, Cloud Run and Cloud Tasks resources in a developer’s own Google Cloud project, and Firebase says that infrastructure “will continue to execute indefinitely” (Firebase Extensions Deprecation FAQ). What disappears is the management layer: no new installs, no config changes, and no Uninstall button. Removing an extension after March 2027 means going into the Google Cloud console and manually deleting each underlying resource yourself, one by one, instead of clicking a button Firebase used to provide.
That makes the next eight months a decision point rather than a grace period. Firebase’s own guidance is blunt: if an installed extension is still in use, update it to its latest version now and keep it current, because the tooling to do that later won’t exist. If it isn’t in use, uninstall it before the deadline while the button still works. Migration documentation and tools are due in September 2026, with the recommended long-term path being to repackage an extension’s logic as an ordinary 2nd-gen Cloud Function a team owns and deploys itself, rather than an installable package Firebase manages (Firebase Extensions Deprecation FAQ).
The third wind-down in a year #
Extensions joins a pattern. Firebase Studio, the AI-assisted IDE, is sunsetting with new workspace creation already disabled and full shutdown set for March 2027 (Firebase Studio migration guide). Firebase ML, the on-device model hosting layer, is deprecated with a shutdown date of June 15, 2027 (Firebase ML docs). Extensions now lands on the same 2027 horizon as both. Three product lines wound down within roughly a year reads less like routine housekeeping and more like Firebase clearing lower-usage surfaces ahead of its Gemini-centric roadmap.
It isn’t the first time an extension deprecation has rattled developers. In 2023, Google pulled the Firebase Stripe extension with what one widely shared Hacker News thread called zero warning, breaking production billing flows without notice (Hacker News, August 2023). This time reads differently: eight months of published notice, a stated migration window, and installed extensions that keep running rather than vanishing outright.
Key Takeaways #
- Firebase Extensions is deprecated; installing, updating, reconfiguring and uninstalling through the console or CLI stop working March 31, 2027.
- Already-installed extensions keep running indefinitely, since they’re built on ordinary Cloud Functions, Eventarc, Cloud Run and Cloud Tasks resources in a developer’s own project.
- Uninstalling after the deadline requires manually deleting those Google Cloud resources yourself, with no Firebase-provided button.
- Migration docs and tools arrive in September 2026; the recommended path is repackaging extension logic as a self-managed 2nd-gen Cloud Function.
- This is the third Firebase product wind-down on the same 2027 timeline, alongside Firebase Studio and Firebase ML.
What to do #
Audit which extensions are actually installed and in production use. Update the ones still earning their keep now, before the tooling to do so goes away, and uninstall the rest while the Uninstall button still works, rather than leaving stale resources for a manual cleanup after March 2027. For anything worth keeping long-term, start planning the move to a self-owned Cloud Function ahead of the September migration guidance, not after it.