Google to shut down Firebase Studio on March 22, 2027
Google announced that its cloud full-stack development platform Firebase Studio will shut down on March 22, 2027. Starting June 22, 2026, new workspace creation and user registration have been disabled, and existing workspaces can continue to be used until the shutdown date.
Google said the shutdown applies only to the Firebase Studio development environment. Apps already deployed to Firebase can continue to run, and core Firebase products such as Cloud Firestore, Authentication, and App Hosting will not be affected. The company said it will transfer preview experience into Google AI Studio and Google Antigravity to simplify AI development tools.
Original source:
Title: Firebase Studio sunset and project migration Publisher: Firebase / Google Publication date: 2026-11-05 (page updated) URL: https://firebase.google.com/docs/studio/migrating-project Source type: official documentation Verification status: full text read for this report, verification date 2026-11-08 Supported content: supports the shutdown date, the new-workspace disablement time, continued operation of deployed apps, and the statement about migration to Google AI Studio and Google Antigravity
ABAB AI Insight
Firebase Studio was renamed from Project IDX, with the brand change completed on April 15, 2025, and positioned as a cloud-based agentic development environment combined with Gemini. Google announced its shutdown on March 19, 2026, provided a one-year transition period, and stated in the documentation that migration tools had begun to roll out.
After the shutdown, data will be permanently deleted on March 22, 2027 and cannot be recovered. Google will direct code-first projects to the desktop Antigravity and browser prototype projects to Google AI Studio, and will directly integrate Cloud Firestore and Firebase Authentication in the latter.
ABAB News · Cognitive Law
The preview cloud IDE can be decommissioned and its data deleted within one year as resources concentrate on AI-native tools.
Deployed backend services and the development environment can be shut down separately, and core products are not affected by IDE decommissioning.
Diverting from a unified cloud workspace to browser prototypes and local agent IDEs reflects a shift in the toolchain from a single environment to multiple entry points.