Can you still use Firebase Studio?
Google stopped new signups and new workspaces on June 22, 2026. Existing users can keep working in their current workspaces until March 22, 2027, when Google says it will shut down Studio and delete the workspace data still there.
Firebase Studio grew out of Project IDX. It gave you a browser workspace to edit and preview app files with AI assistance. If you used it to build an app you still need, save a copy of the project before the shutdown.
What should you take out of your workspace?
Download a local copy of your project files. Google’s migration guide shows how to use Zip and Download. Open the downloaded copy and check that it includes your latest edits, the files that tell the app how to build and start, and assets such as images your app needs.
Write down the names of the settings your app needs and where you manage them. Keep private keys and passwords in your existing secure storage. Keep any downloaded copy that contains private values out of shared repositories. If you need old conversations, Google says chat history requires a separate download.
If someone shared the workspace with you, ask the person who created it to help. Only that person can use Move now. A manual export from a shared workspace can still point to the original owner’s Firebase project.
What happens to an app that already uses Firebase?
Google says Firestore, Firebase Authentication and App Hosting will continue outside Studio. Your project download saves app files. Check separately which account hosts the app, where its records and uploads live, and which service handles sign-in.
If you want to keep your app’s current address, first find the hosting service that serves it and confirm who can manage it. Google documents a way to keep the existing address for apps already published with App Hosting by linking your project to the existing hosting setup. Verify that you have permission to manage that setup before reconnecting it.
- See what Firebase stores and how to export itFind out what needs its own export if you also move the app’s data or sign-in service.
Where can you keep working on the app?
Google describes Google AI Studio for browser-based prototyping and Google Antigravity for people who want to work directly with the code in an editor. The migration guide also covers downloading the source so you can open it in another development environment.
Choose based on how you want to edit the app and which services it needs to connect to. Check whether the new environment can open your project, use the settings it needs and work with your intended host.
How do you check the moved copy?
Before running the copy, check where its database, sign-in and file storage connections actually point. Confirm that they connect only to a separate test project or local emulators, which stand in for those services on your computer. Use invented records and test accounts. Keep live email, payments and other outgoing jobs disconnected in the copy. If you can’t verify those settings, inspect the files without running the app.
Pick one action you know well, such as signing in as a test user and saving a sample record. Check that the record appears in the test project or emulator you intended to use. Keep the original copy so you can compare files if the moved app behaves differently.