AI & TechnologyFirebase Deprecations: Every Shutdown Date, 2024 to 2027

Firebase isn’t shutting down, but seven of its products and APIs are being retired between 2024 and 2027, and five of the deadlines fall in 2027. If your app uses Extensions, Firebase Studio, Firebase ML model hosting, Test Lab, device groups or the old FCM InstanceId APIs, you have a deadline. The table below lists each one with the date, what stops working and where Firebase says to move.

Every date here comes from Firebase’s own documentation, linked in each row and in the sources. I checked each page again on October 21, 2026. Google can change a deadline, so open the linked page before you plan around one.

Disclosure: App369 is my studio. I build Flutter and Firebase apps, and I run my own product, Workspace369, on Firebase. The last section mentions what I sell. Google doesn’t pay me for anything on this page.

Every Firebase shutdown, in date order

What each 2027 deadline means in practice

Firebase Studio: March 22, 2027

Firebase Studio launched as a preview to explore AI-driven, full-stack app development. Firebase’s migration page points to Google AI Studio, for rapid browser-based prototyping, and Google Antigravity, for code-first agentic work. You can keep working in an existing workspace until March 22, 2027. Any project you want to keep must be migrated before then, and Firebase’s page has steps for both destinations and for exporting the source to anywhere else.

For the step-by-step move, see Firebase Studio is shutting down: how to migrate.

Your Firebase backend isn’t affected. Firebase says Firestore, Authentication, App Hosting and your data keep working outside Firebase Studio. One thing to test after a move: Firebase’s own FAQ has an entry about Google Sign-In not working after migrating to Google AI Studio, so check sign-in first.

Firebase Extensions: March 31, 2027

This one is easy to miss, because nothing breaks on the day. Firebase says installed extensions run on standard Google Cloud services (Cloud Functions, Eventarc, Cloud Run, Cloud Tasks) and keep executing. What you lose after March 31, 2027 is control: you can’t change parameters or environment variables, apply fixes or security patches, uninstall through the console or CLI, or download the configuration to set up a replacement.

For the inventory and function kit steps, see Firebase Extensions are shutting down: how to replace them.

There’s a second risk. Firebase notes that most extensions are built on the legacy Cloud Functions v1 SDK and older Node.js runtimes, and that functions may stop running or be disabled when Google Cloud retires those runtimes. So an extension you can’t update may stop working once those runtimes are retired, and you won’t be able to patch it. Your own functions face the same schedule: Google decommissions the Node.js 20 runtime on October 30, 2026, and the free Cloud Functions Node.js 20 runtime checker shows which runtimes your firebase.json and package.json deploy. If a deploy fails after you change the runtime, why Firebase Functions deploys fail matches the error to its fix.

Before March 31, 2027:

1. List what’s installed. In the Firebase console, open Extensions for each project, including staging and old projects.
2. Uninstall what you no longer use. After the deadline the Uninstall button goes away, and you’d have to delete the underlying resources by hand.
3. Export the configuration of the rest. You need the parameters to set up a replacement.
4. Replace each one. Use the publisher’s function kit on npm if there is one. If not, the extensions are open source, so a developer can rebuild one as Cloud Functions (2nd gen). Firebase’s guide for users covers both.

Firebase ML model hosting: June 15, 2027

This only matters if you host custom TensorFlow Lite models through Firebase ML. On-device ML Kit features are a separate product. Firebase’s suggested route is to download your models and host them in Cloud Storage for Firebase, and its guide covers Android, Apple platforms and Flutter, plus an optional move to the LiteRT CompiledModel API.

For the step-by-step move, see Firebase ML model hosting is shutting down: how to migrate.

FCM InstanceId APIs and device groups: September 29, 2027

If your server checks tokens with iid.googleapis.com, manages topic subscriptions through the old InstanceId endpoints, imports APNs tokens in bulk, or uses device groups, those calls start failing after September 29, 2027. If you manage topics through an older Firebase Admin SDK, you’re affected too. I cover each case and the replacement in the FCM guide.

Test Lab: September 30, 2027

Test Lab runs your Android and iOS tests on devices in Google’s data centers. Firebase says it will be fully shut down on September 30, 2027, and points to the Developer Device Platform on Google Cloud, with a migration guide and FAQ linked from the Test Lab page. If Test Lab runs in your CI pipeline, budget time to move it and to compare device coverage and pricing before the deadline.

For the options and a migration plan, see Firebase Test Lab is shutting down: alternatives for 2027.

Not a shutdown, but dated: CocoaPods and Firebase 13

Firebase Apple SDK 13.0.0, released October 7, 2026, is no longer distributed through CocoaPods. It ships through Swift Package Manager and binary distributions instead. Older CocoaPods releases stay available while the CocoaPods ecosystem lasts, but Firebase says it will not provide official support for installing Firebase from its podspecs now that CocoaPods support has ended. If you build a Flutter app, FlutterFire’s firebase_core 5.0.0 (published October 15, 2026) is a breaking release: it builds on Firebase Apple SDK 13 and the Firebase Android BoM 35, and its Android build requires minSdk 24. Read the changelog before you bump the version, and test an iOS build, because this is a new major version of the whole stack and not a patch.

Add these dates to your calendar

The 2027 Firebase dates above are also in a free calendar you can subscribe to, together with the other dated app platform deadlines from my guides: Google Play, Google Cloud, Google Mobile Ads, Meta, Fitbit and Supabase. Each event is an all-day entry with one line on what changes, a link to my guide and a link to the platform’s own page. When a platform moves a date, I change the calendar too, and a subscribed calendar picks it up on its next refresh. Dates that give only a month aren’t in it, because a calendar entry needs a day.

• Subscribe: add the calendar (webcal link), or download the .ics file.
• Google Calendar: on a computer, open Google Calendar, click Add other calendars next to “Other calendars”, choose From URL, paste https://app369.com/calendars/app-platform-deadlines.ics and click Add calendar. Google says you have to subscribe from a computer, not from its Android or iPhone app.
• Apple Calendar on a Mac: click the webcal link above, or choose File > New Calendar Subscription, paste the same address and click Subscribe. Choose iCloud as the location to see it on your iPhone too, and set Auto-refresh to every day.
• For scripts: the same dates are in a JSON file, with the date, platform, what changes, the source and the guide for each one.

A one-hour check for your project

1. Search your code for iid.googleapis.com, fcm.googleapis.com/fcm/, page.link, firebase-ml-modeldownloader (or firebase_ml_model_downloader in Flutter), and gcloud firebase test. To check your own code against these dates, the free Firebase shutdown checker reads it in your browser.
2. Open the Firebase console for every project you own and look at Extensions, Machine Learning, Test Lab and Studio.
3. Write down each deadline that applies, with the owner of the fix and a target date at least a month early.
4. Start with the earliest deadlines. Of the 2027 ones, Studio and Extensions come first, in March.

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 one of these migrations breaks something, such as pushes that stop arriving, a sign-in flow that fails after a move, or a Cloud Function that won’t deploy, 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. If you want help planning several migrations at once, send me a short description of your project.