The Firebase Studio alternatives that fit depend on which half of the product you were using.
If you built with the App Prototyping agent, move to Google AI Studio. If you lived in Code view, export the repo and open it in Google Antigravity. Those are the two Firebase Studio alternatives Google names in its own sunset notice, and for most projects the decision stops there. The rest of this page is for people who are not satisfied with that answer. One correction before you go shopping: the App Prototyping agent generated Next.js web apps. You are not losing a mobile build pipeline, because there never was one.
The dates are short and they are real. Google disabled new workspace creation and new user signup on 22 June 2026, and it shuts Firebase Studio down on 22 March 2027, when remaining data is permanently deleted. We opened Google's own notice on 1 October 2026 and both dates are on it. So nobody can start a new Firebase Studio project today, and existing workspaces have under six months left. Export first, choose second. If the plan is to turn that project into a phone app, moving a Firebase Studio project is a separate job with its own steps.
See which exit fits youThe short version
Google picked a replacement for you, and which one depends on how you worked.
The migration guide splits users in two. If you prototyped in the browser with the App Prototyping agent and liked that, Google points you at Google AI Studio, and there is a Move now button in the workspace that prepares the transfer. If you worked in Code view, started from a template, or imported a repository, Google points you at Antigravity, its agent-first IDE that you download and run on your own machine. Those are Google's criteria, lifted from the notice, not our ranking.
That is a migration path rather than a verdict on quality. If Firebase Studio was never quite right, this is the cheapest week you will get to leave, because you have to export the code anyway. The shortlist then turns on one question. If the output has to stay a web app, Lovable sits closest to what you had. If it does not, you are not replacing Firebase Studio at all, you are starting a different kind of project, and the tools are different too.
What Google announced, and the three dates in the notice
Google's page is called Firebase Studio sunset and project migration. We opened it with a plain GET on 1 October 2026 and it returned 200. It carries three dates. On 19 March 2026 Google announced the sunset and began rolling migration tools into the product. On 22 June 2026 new workspace creation and new user signup were disabled. On 22 March 2027 Firebase Studio is shut down, and the page says all remaining data is permanently deleted and cannot be recovered.
Between those last two dates the product still works. Google says you can keep working in existing workspaces until the sunset, and that it will keep shipping critical security patches and Gemini model updates in the meantime. So this is a deadline, not an outage. The practical reading is simpler than the announcement. Nobody new can join, and anyone already inside has until 22 March 2027 to get their source code out of the browser.
It is worth saying what is not ending, because headlines blur it. Core Firebase products are untouched. The notice names Cloud Firestore, Authentication and App Hosting, and says they continue to work outside Firebase Studio. Apps you already deployed keep running after the sunset date. The thing being switched off is the browser development environment, not your database, not your sign-in and not your hosting. That matters, because it means many projects need a new editor rather than a new stack.
Google, Firebase Studio sunset and project migration, read 1 October 2026
Export the workspace before you pick anything
Google documents three ways out. The first is the Move now button at the top of the workspace, followed by Zip and Download; if that button is missing, the command palette has a Firebase Studio: Zip and Download command. The second is the CLI, npx firebase-tools@latest studio:export, pointed at your extracted folder or at the zip. Google notes that this command is optimized for Next.js, Flutter and Angular workspaces, and that other workspace types may not have every code artifact updated. The third is pushing the workspace to GitHub.
One thing does not come out in the zip, and it catches people. Google says agent chat history is not part of the exported zip file. It sits in the .idx/ai directory inside the workspace, and the way to keep it is to open the home folder, then zip and download that directory on its own. Prompts from Prototyper sessions also show up in the git log. If the prompts are how you remember what the app was supposed to do, grab them before the tab closes for the last time.
Once the code is on your machine, every tool choice gets cheap, and that is the right order to work in. A migration you can redo is a decision you can change later. If you are reopening the wider question of which builder to use, rather than just where this one project lands, the field is laid out in best ai tools idea to app.
The alternatives, grouped by how you actually used it
Start with Google's two, because they cost the least effort. Google AI Studio is the browser path, and the notice recommends it if you built with the App Prototyping agent and want prompt-based generation to carry on. After the transfer you publish either to Cloud Run on a new run.app URL, or back to Firebase App Hosting through GitHub sync, which keeps your existing hosted.app address if you already published one. We could not open Google AI Studio's own documentation without signing in, so everything here about it comes from Google's Firebase migration guide rather than from AI Studio's pages.
Antigravity is the local path. Google recommends it if you prefer an agent-first desktop environment, used Code view, began from a template or an imported repository, or outgrew the cloud limits in Prototyper. It is a download rather than a website, and Google's Antigravity site offers builds for Apple Silicon and Intel at no charge for developers. The migration flow includes an agent prompt that converts an exported Firebase Studio project for you. Publishing stays on Firebase, and Google says the agent publishes to your existing URL if you had already published to App Hosting.
If you want out of Google's stack entirely, the nearest like-for-like is Lovable, which also turns prompts into a full-stack web app in the browser. Read its own FAQ first if anything about your plan is mobile shaped. Lovable's FAQ says it builds web applications and does not generate React Native projects, and that the two routes onto a phone are a Progressive Web App or a Capacitor wrapper. That is the same shape of limit Firebase Studio had. We ran this exercise for another prompt-to-app tool in base44 alternatives.
Two questions
Which exit is yours
What did you use Firebase Studio for?
What do you want to ship next?
Google AI Studio
Google's migration guide points App Prototyping agent users here, and the Move now button prepares the transfer. GitHub sync can keep your existing App Hosting address if you already published from Firebase Studio.
If you wanted an installable app, this is a different project
Firebase Studio's own documentation is clear about what the App Prototyping agent produced. The agent supports Next.js apps, with other platforms and frameworks planned for the future, and the page repeats that it helps you build web apps with Next.js. The preview documentation matches that: web previews in Chrome, and Android emulators only inside Flutter workspaces, which you configured yourself rather than generated from a prompt. There was no iOS preview, no signed build and no store submission. No alternative can hand back a mobile pipeline you never had.
If a phone app is the real goal, the shortlist changes shape. Replit's own mobile documentation says Agent scaffolds React Native with Expo, streams an iOS Simulator or an Android Emulator into the project editor, and walks you through TestFlight and App Store submission. The same page says publishing to Google Play is not yet supported by Replit. Newly also writes React Native and TypeScript, previews on cloud iOS and Android simulators, and ships to TestFlight and to Google Play internal testing, and it uploads rather than submitting for review. Choose on the store you actually need.
Either way the next question is data, and it arrives sooner on a phone than it did on the web. A Firebase Studio project usually leaned on Firestore and Firebase Authentication, and both keep working, so one honest option is to keep them and change only the editor. If you are rebuilding rather than porting, the trade-offs are set out in picking the backend.
Google, Firebase Studio documentation, Get started with the App Prototyping agent
What each option builds, checked against its own pages on 1 October 2026
| Option | What it generates | Preview while you build | How it reaches people | Where that is stated |
|---|---|---|---|---|
| Google AI Studio | Google's migration guide does not say which framework | In the browser | Firebase App Hosting through GitHub sync, or Cloud Run on a new URL | Google's migration guide |
| Google Antigravity | Whatever your exported project already was | A local dev server you start in the IDE | A Firebase deploy, to your existing App Hosting URL if you had one | Google's migration guide |
| Lovable | Web applications; its FAQ says it does not generate React Native projects | In the browser | Published on the web, or a PWA or Capacitor wrapper for the stores | Lovable FAQ |
| Replit | React Native with Expo | Cloud iOS Simulator and Android Emulator, or Expo Go on a phone | TestFlight and the App Store; Google Play not yet supported | Replit mobile app docs |
| Newly | A React Native and TypeScript project you own | Cloud iOS and Android simulators | TestFlight and Google Play internal testing, plus a standalone APK; you submit | docs.newly.app |
What a clean restart looks like
If you decide the project is worth rebuilding rather than porting, write the brief you have now instead of reusing the one from a year ago. You know which screens people used, which features nobody touched, and whether anyone ever asked for it on a phone. That brief is worth more than the tool argument, and it is the part no migration guide can do for you.
Newly is an AI app builder. You describe the app in plain English and it writes a real React Native and TypeScript project you own, runs it on cloud iOS and Android simulators while it builds, then ships it to TestFlight and to Google Play internal testing. It is $25 a month and there is no free plan. New apps start local-first, keeping their data on the phone with no accounts and no server. The agent adds a hosted backend, with sign-in, an API service, a Postgres database per environment and file storage, only when the app needs accounts, shared data, syncing or payments. Code comes out as a ZIP from project Settings, through the two-way GitHub sync under Deploy, or with the CLI.
The reasons to pick something else are easy to name. If the thing you are migrating is a web app and should stay one, a React Native builder is the wrong shape, and Google's two destinations are far less work. If you need Google Play on day one, check each tool's current support on its own page rather than trusting any comparison table, this one included. And if your app is mostly a Firestore front end that already works, the cheapest move is to change editors and leave the app alone.
Questions people ask about leaving Firebase Studio
Yes. Google's sunset and migration page says Firebase Studio shuts down on 22 March 2027, and that all remaining data is permanently deleted on that date and cannot be recovered. New workspace creation and new user signup were disabled on 22 June 2026. We checked both dates on Google's own page on 1 October 2026. Existing workspaces keep working until the shutdown.
Export the workspace, then decide what it should have been
You have until 22 March 2027, but the export takes a few minutes and every decision gets easier once the code is on your machine. Pull the zip, reread the brief, and if the honest answer turns out to be a phone app, describe it in a sentence and see what comes back.
Start building