Firebase Studio shuts on 22 March 2027 as Google points to AI Studio

Firebase Studio shuts on 22 March 2027 as Google points to AI Studio

6 November 2026: Google's Firebase Studio, its browser-based development environment, is closing on 22 March 2027, and teams still working in it have to move their workspaces to Google AI Studio or Google Antigravity. New workspaces and sign-ups were already switched off on 22 June 2026, so anyone with a workspace today is on a closing product with about four and a half months left.

Not yet independently verified. Google's documentation page carries the dates but no publication date, so we cannot say when the sunset was first announced, and we found no blog post on it. We dated this item to the day we read the page. We will update this when it can be confirmed, and remove this note.

What stops and what does not

The notice separates the tool from the platform, and the distinction is useful:

• Stopping: Firebase Studio workspaces, on 22 March 2027. They can be used and migrated until then.
• Already stopped: creating new workspaces and signing up, since 22 June 2026.
• Continuing: apps already deployed to Firebase, which keep running after the sunset date.
• Not affected: core Firebase products, including Firestore, Authentication and App Hosting.

So a production app built in Firebase Studio is not at risk on that date. What goes is the environment where its code was being written and changed, along with whatever customisation a team has built up there.

A workspace holds more than code

The page does not say why Google is closing the product, though the two destinations it names show where it wants this work to go.

Moving a workspace is not just moving code. Development environment configuration, previews, environment variables, secrets and any prompts or agent settings a team relies on should be listed before the move, and the documentation should be checked for which of those the migration carries across. Teams that picked Firebase Studio for its tie to their Firebase project should also test that deployment works from the new tool, well ahead of March.

Choosing where to go

Google gives two options and no recommendation between them on this page. Nothing obliges a team to take either: the code belongs to the team, and core Firebase services work with other editors and hosting tools. A move like this is a sensible moment to check whether the choice still fits, especially for a team that has bought other tools since it started.

We list 11 low-code development platforms for teams that used Firebase Studio mainly to get a first version of an internal app built quickly, and Google has its own profile in our catalogue.

Sources

• Firebase documentation: Firebase Studio (no date on page, read 6 November 2026), 6 November 2026