Firebase Studio is closing: where do I put the demo I built?

Firebase Studio shuts on 22 March 2027 and deletes what is left in it. How to export your project, where Google suggests moving it, and how to keep showing it to clients.

On this page

By Kaz Kato · Published 20 October 2026 · Updated 20 October 2026

Export the workspace before 22 March 2027, when Firebase Studio shuts and deletes everything left in it. Google points code-first work to Antigravity and prototyping to AI Studio. If you only need to keep showing the app to clients, deploy the exported code to a room on mock data, with a link for each person.

This guide says exactly what closes and what does not, how to get your code out, where it can go next, and how to keep a client demo running. It helps whether or not you use Roomi. If you do, container demos covers apps with a server, and mock data in an AI-built demo covers replacing a live database.

What exactly happens, and when?

Two dates. On 22 June 2026, Firebase Studio stopped taking new sign-ups and new workspaces. On 22 March 2027 it shuts, and everything still in it is deleted for good, with no way to recover it. So the months between now and then are the time to move what you have.

Firebase Studio stopped new sign-ups and new workspaces on 22 June 2026, and shuts on 22 March 2027, when everything left in it is permanently deleted.

Does my deployed app stop working too?

Google says its core services are not affected. Cloud Firestore, Authentication and App Hosting keep working outside Firebase Studio, and only the development environment closes. So what goes on 22 March 2027 is the place you built in, and whatever is left there. Check your own app’s setup before you rely on that.

Google says Cloud Firestore, Authentication and App Hosting are not affected by Firebase Studio’s closure and keep working outside it; only the development environment closes.

Google’s migration page also covers how an app that moves to AI Studio can keep its address. A Firebase Studio app moved to Google AI Studio can keep its hosted.app address by publishing to App Hosting through GitHub sync. Publishing to Cloud Run instead gives it a new run.app address. Read that section before you publish it anywhere new.

How do I get my code out?

Three ways, all from Google’s migration page. Download the workspace as a zip, from Move now at the top of the workspace. Export it to GitHub. Or convert it with the Firebase command line. Whichever you choose, open the result somewhere else and build it before the deadline, while the original still exists.

A Firebase Studio workspace can be downloaded as a zip (Move now, then Zip and Download), exported to GitHub, or converted with the Firebase CLI’s studio:export command.

  1. As a zip. In the workspace, choose Move now, then Zip and Download, if it is offered.
  2. To GitHub. Export the workspace to a repository, so the code lives somewhere you control.
  3. With the command line. Run the Firebase CLI’s studio:export command. Google’s migration page gives the full line.

Then unpack or clone the result on your own machine, and build it there. A project that builds outside Studio is one you can move anywhere.

Where should the project go next?

Google recommends Antigravity for code-first work, and Google AI Studio for prototyping in the browser. Your own host suits an app that already has real users. If the app’s job now is to win work, showing it to clients rather than serving customers, a room on mock data may be all it needs.

Google recommends moving Firebase Studio projects to Antigravity for code-first work, and to Google AI Studio for prototyping in the browser.

Where it goes What it suits
Antigravity Code-first work, by Google’s recommendation
Google AI Studio Prototyping in the browser, by Google’s recommendation
Your own host A finished app, with real users and real data
A Roomi room (ours) Showing it to clients on mock data, with a link for each person

How do I keep showing it to a client?

Deploy the export as a demo, on mock data. An app with a server, such as a Next.js one, runs as a container demo on Pro and above. A front end that builds to static files runs as a static demo, on every plan. Its database and sign-in become sample data, and its AI features canned answers.

  • Firestore and Authentication become sample data. A demo’s container has no internet, so it could not reach them anyway. Mock data in an AI-built demo has four ways to do it, and the words to ask your AI agent for each.
  • Gemini calls become canned answers. Demoing an AI app without a live API key shows how.
  • A static front end needs nothing more. Static demos says what roomi init reads.
  • One link per person. On Pro, make each client their own link. Anyone who has an address can open the room, so send each one only to the person it is for.

Rehearse before anything goes live. On its own, roomi deploy scans the project and the build for secrets, builds it and shows what would go live. Nothing is published until you add --commit.

Before 22 March 2027: a checklist

  1. Export the workspace, by one of the three ways above.
  2. Build the export somewhere else, while the original still exists to compare it with.
  3. Take any keys out of the code, and rotate them. They have sat in the workspace’s files. Is it safe to send a client an AI-built app? has the rest of the checks.
  4. Decide where the project lives next: Antigravity, AI Studio, your own host, or a room.
  5. Send each client their new link, so nobody is left with an address that stops working.
  6. List the addresses you have sent clients, and check which of them depend on Firebase Studio itself.

Export it this week, put the client version in a room, and send each client their own link before the deadline does it for you.

Questions people ask

Can I still create a Firebase Studio workspace?

No. Firebase Studio stopped new sign-ups and new workspaces on 22 June 2026, and shuts on 22 March 2027, when everything left in it is permanently deleted. So the only work left in it is moving what you already have.

Will my Firestore data be deleted?

Google says Cloud Firestore, Authentication and App Hosting are not affected by Firebase Studio’s closure and keep working outside it; only the development environment closes. What is deleted on 22 March 2027 is what is still in Firebase Studio itself.

Does a client need a Google account to see the room?

No. Each client opens their own link, with nothing to sign up for. A link carries the name you gave it, so their visits are filed under that name.

Sources

About the author

Kaz Kato, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit. More at katosan.co.uk.

Keep showing the app after the tool it was built in has gone.

Deploy the export; a server and private links start on Pro.