Firebase Studio sunset and project migration

Firebase Studio is sunsetting on March 22, 2027. We're simplifying our AI developer offerings by transitioning the lessons learned from the Firebase Studio preview into our flagship tools: Google AI Studio and Google Antigravity.

While the interface for building apps is evolving, our commitment to the Firebase ecosystem is stronger than ever. By integrating agentic capabilities directly into our flagship AI platforms, we're ensuring that Firebase continues to provide a seamless, reliable backend for AI-driven development. Core Firebase services, such as Cloud Firestore, Authentication, and App Hosting, will continue to work outside of Firebase Studio.

Why we're making this change

Firebase Studio launched as a preview to explore the future of AI-driven, full-stack development. Based on your feedback, we're streamlining our tools to provide clearer, more powerful paths forward:

• For code-first, agentic development: We're focusing on Antigravity, our next-generation IDE designed for high-velocity, autonomous local workflows.

• For rapid, browser-based prototyping: We've integrated Cloud Firestore and Firebase Authentication directly into Google AI Studio to provide the fastest path from prompt to production.

Your core Firebase services (Cloud Firestore, Authentication, App Hosting, etc.) are not affected. Your databases and user data will continue to function normally. This sunset only applies to the Firebase Studio development environment.

Sunset timeline

We're providing a one-year transition period to ensure you have ample time to migrate your projects:

• March 19, 2026: Sunset announcement, and migration tools start rolling out to Firebase Studio.
• June 22, 2026: New workspace creation is disabled. You can continue to work in and migrate existing workspaces.
• March 22, 2027: Firebase Studio is shut down, and all remaining data is permanently deleted and cannot be recovered.

Choose your migration path

Depending on how you use Firebase Studio, choose the migration path that best fits your workflow.

Migrate to Google Antigravity (available now)

For a code-first, agentic development experience, we recommend migrating to Antigravity. This is our next-generation IDE designed for high-velocity, autonomous local workflows. You should choose Antigravity if you meet any of the following criteria:

• Prefer working in a local, code-first development environment with deeper control over your codebase
• Created your app using a built-in template or imported repository in Firebase Studio
• Primarily use the Code View environment in Firebase Studio
• Want direct access to state-of-the-art agentic AI development capabilities within a powerful IDE, with support for using different models like Claude and GPT-OSS, in addition to Gemini
• Started in Prototyper mode, but added significant features or execution scripts that require a local environment without cloud limitations

Migrate to Google AI Studio (coming soon)

We're still working on the migration pipeline to Google AI Studio to ensure it works reliably. Once it's available, you should choose Google AI Studio if you meet any of the following criteria:

• Prefer a web-based experience, which is ideal for multi-device workflows or environments where you cannot install local software
• Created your app using the the App Prototyping agent in Firebase Studio and value rapid prototyping and prompt-based app generation
• Want the fastest path from prompt to full-stack production app

Check back soon for migration instructions for Google AI Studio!

Migrate apps to Antigravity

Antigravity is a local, agent-first IDE that brings the power of AI into your local development environment.

Prerequisites

Ensure you have the following installed locally and fully up-to-date:

• Google Antigravity IDE
• Node.js (version 20 or higher)
• Firebase CLI (version 15.10.0 or higher)

Step 1: Export and initialize your app

npx firebase-tools@latest studio:export PATH

Step 2: Preview your app

Once you've extracted your project and opened it within Antigravity, you can view your application locally:

1. In Antigravity, navigate to the Run and Debug menu located in the left sidebar.
2. Click the play button to start your local development server.
3. Follow the instructions in the terminal to preview your app.

Step 3: Publish your app

Antigravity uses agent skills to publish your app using Firebase best practices.

1. In the chat panel, enter the following prompt:

   Publish my app
   

2. When prompted to run firebase deploy, choose Yes. The agent will publish to your existing URL if you've previously published to Firebase App Hosting. If this is your first time publishing to App Hosting, the agent will walk you through the process.

3. For future updates, instruct the agent to publish my app in the Antigravity chat panel.

Migrate apps to other platforms

If you prefer to move your project to a different development environment or hosting platform, you can export your source code and manage deployments manually.

Step 1: Export your project source

Before the sunset date, you must download a local copy of your project files:

1. Click the Move now button at the top of your workspace > Zip and Download.
2. Extract the archive to your local machine.

Step 2: Choose your publishing method

Once your code is local, you can continue to serve your app using the following methods:

• Firebase CLI (keeps your existing URL)

  1. Install the Firebase CLI using npm by running the following command:

     npm install -g firebase-tools
     

  2. Navigate to your project directory in your terminal.

  3. Run this command to set up App Hosting deployments for your local project:

     firebase init apphosting
     

  4. When prompted, select Link to an existing backend and choose the backend named studio. This ensures your app's URL remains the same.

  5. Follow the prompts to complete setup. Your App Hosting configuration will be added to firebase.json.

  6. Deploy the application:

     firebase deploy
     

• External hosting: Since your exported code is a standard web application, you can initialize it with any hosting provider. Note that moving to an external provider will result in a new URL.

• Local development only: You can continue to develop and test your app locally using the Firebase Local Emulator Suite for faster, offline testing without deploying to a live environment.

Troubleshooting and FAQ

Review the following common questions and troubleshooting steps for migrating your Firebase Studio projects.

Can I continue using Firebase Studio until the sunset occurs?

Yes, you can access existing workspaces until March 22, 2027. We'll continue to provide critical security patches and Gemini model updates to ensure your current projects remain stable. Note that new workspace creation will be disabled starting June 22, 2026.

Will my agent chat history be migrated?

Your agent chat history isn't part of the current exported zip file. However, you can locate Gemini chat history files for the the App Prototyping agent and Gemini in Firebase agents within your workspace in the /home/user/.idx/ai directory of your Firebase Studio workspace. This contains prompts and responses from all Gemini chat modes.

Here's how to create a zip file that contains your history:

1. Select File > Open Folder.
2. Accept the default /home/user directory.
3. After the files load, right-click on the .idx/ai directory and select Zip and Download.
4. When prompted to rebuild the environment, click Cancel.
5. After your download completes, re-open your working directory from the File menu to move back into your workspace.

For Prototyper sessions, you can also view your prompts as part of the git log. Here's how to locate them:

1. Open Code view ().

2. Perform either of the following:

   • Open a terminal session (Cmd-Shift-C on Mac or Ctrl-Shift-C on ChromeOS, Windows, or Linux) and type git log.
   • Open Source Control (Cmd+Shift+G on Mac or Ctrl-Shift+G on ChromeOS, Windows, or Linux) and view Source history.

I tried to zip and download my files in Firebase Studio, but nothing happened.

This is usually caused by a browser pop-up blocker. Because the migration flow opens a new interface to process your request, some browsers may flag it as an unwanted pop-up.

To fix this, look for a "Pop-up blocked" notification in your browser's address bar (usually on the right side). Click the icon and select the option to allow pop-ups, and then try clicking the button again.

If this doesn't work, use the instructions at How do I download my files from Firebase Studio? to run the Zip and Download command manually.

Can I migrate Firebase Studio workspaces that have been shared with me?

Only the person who created the Firebase Studio workspace can use the Move now button. If you want a copy of the project, you can do either of the following:

• Duplicate the workspace: Create a copy of the project under your own account, allowing you to link it to your own Firebase project and use the migration tools.
• Manually export your code: From Code view, you can open the command palette (Cmd+Shift+P on Mac or Ctrl+Shift+P on ChromeOS, Windows, or Linux) and run the Firebase Studio: Zip & Download command.

What if the export stalls or times out?

If the migration process hangs while preparing your files, it's often due to an oversized project folder.

To clear the path for a successful migration:

• Delete node_modules: As part of the migration process, this folder is generally removed. However, if you renamed or moved it, or plan to manually zip and download your code, delete it before initiating the migration. You don't need to migrate this folder because you can run npm install once you've moved to your new environment.
• Remove large artifacts: Delete any large media files, database exports, or build folders that aren't strictly necessary for the source code.
• Check for "hidden" bloat: Make sure you aren't accidentally zipping a massive .git history or local logs.

Once you've deleted any large files, try again to migrate your project.

Why are my Firebase CLI or npx commands failing in the Antigravity terminal?

If you encounter "command not found" errors or issues running npx commands within Antigravity—even though they work in your standard system terminal—it's likely due to how your shell environment is being initialized.

Antigravity's terminal environment looks for configuration settings in your ~/.bash_profile. Many developers have their npx and path configurations stored in ~/.bashrc instead. If these settings aren't shared, Antigravity won't know where to find your tools.

You can fix this by sourcing your .bashrc file inside your .bash_profile. This ensures that all your existing configurations are loaded whenever Antigravity starts.

1. Open your ~/.bash_profile file in Antigravity.

2. Add the following code block to the file:

   if [ -f ~/.bashrc ]; then
       source ~/.bashrc
   fi
   

3. Save the file.

4. Restart Antigravity.

Need help?

If you have questions, feedback, or encounter any issues migrating your projects, reach out in one of the following places:

• Contact Firebase Support.
• Post in the Firebase Studio Community Forum.