> [!WARNING] > **As of June 22, 2026, new workspace creation and new user signup for > Firebase Studio are disabled.** > > > Until the sunset date (March 22, 2027 ), you can continue > working on projects in *existing* Firebase Studio workspaces. > However, for any projects that you want to maintain beyond that sunset date, > you must migrate them *before March 22, 2027* using > the instructions on this page. **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 platform designed for high-velocity, autonomous multi-agent 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 and user signup are 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 For a code-first, agentic development experience, we recommend [migrating to Antigravity](https://firebase.google.com/docs/studio/migrating-project.md.txt#migrate-antigravity). This is our next-generation, agent-first platform designed for high-velocity, autonomous workflows and multi-agent orchestration. You should choose Antigravity if you meet any of the following criteria: - Prefer working in an agent-first desktop environment with deeper control over your codebase using the **Antigravity IDE** or terminal - 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 agent hub, 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 For a web-based prototyping environment that brings the power of AI into your browser, we recommend [migrating to Google AI Studio](https://firebase.google.com/docs/studio/migrating-project.md.txt#migrate-ai-studio). It offers the fastest path from prompt to full-stack production app. 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 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 > [!NOTE] > **Note:** If you initially choose to start with Google AI Studio, you can migrate to Google Antigravity at a later stage by switching to the **Code** tab in Google AI Studio \> **Export** \> **Export to Antigravity**. ## Migrate apps to Google AI Studio Google AI Studio offers the fastest path from prompt to full-stack production app. ### Step 1: Transfer your workspace 1. Click the **Move now** button at the top of your workspace, then select **Prepare for AI Studio**. 2. After the preparation step is complete, click **Move to Google AI Studio**. 3. If requested, review and accept the Terms of Service. Your code will automatically open in a new Google AI Studio workspace. It may take several minutes for Google AI Studio to convert and load your app. It will notify you when it's complete. When finished, you can continue iterating on your app with help from the Google AI Studio agent. Learn more about building apps in [Google AI Studio](https://ai.google.dev/gemini-api/docs/aistudio-build-mode). ### Step 2: Choose your publishing method Depending on your deployment needs and whether you want to preserve your existing application URL, select one of the following publishing methods. #### Option A: Publish to App Hosting and keep your existing URL If you previously published your app through Firebase Studio and want to keep your `*.hosted.app` URL or custom domain, secure your Gemini API key and use GitHub Sync: > [!NOTE] > **Note:** When you used Firebase Studio to publish your app to App Hosting, Firebase Studio automatically extracted your Gemini API key from your workspace `.env` file and configured it as an App Hosting environment variable, accessible by your app but not your users. When you migrate to Google AI Studio, you must manually set the environment variable in the Firebase console to continue publishing to App Hosting through GitHub sync (as the `.env` file shouldn't be stored in GitHub to avoid API key exposure). While this method stores the key securely, it remains accessible to anyone with access to your Firebase project. If you require more granular access controls, consider storing your key in [Secret Manager](https://firebase.google.com/docs/app-hosting/configure.md.txt#secret-parameters) instead. 1. Secure your Gemini API key: 1. In the Firebase console, go to the [App Hosting page](https://console.firebase.google.com/project/_/apphosting?useAutoProject=true). 2. Find your existing backend (usually named `studio`) and click **View**. 3. In the **Settings** tab, navigate to **Environment**. 4. Click **Add new** and paste the contents of your `.env` file into the **Key** field to securely store your Gemini API key as an environment variable. > [!TIP] > **Tip:** You can find your `.env` file by switching to **Code mode** in Firebase Studio. 2. Sync to GitHub from Google AI Studio: 1. In Google AI Studio, click the **Settings** icon and navigate to the **GitHub** panel. 2. Click **Sign in to GitHub** and install the Google AI Studio GitHub App. 3. Click **Create GitHub repository**. > [!IMPORTANT] > **Important:** Review the file list and confirm `.env` is not included. 4. Select **Stage and commit all changes**. 3. Connect the repository to App Hosting: 1. In the Firebase console, go to the [App Hosting page](https://console.firebase.google.com/project/_/apphosting?useAutoProject=true). 2. Find your existing backend (usually named `studio`) and click **View**. 3. In the **Settings** tab, select **Deployment** \> **Connect to GitHub**. 4. Sign in to GitHub and install the Firebase App Hosting GitHub App. 5. Select your repository, set the branch to `main`, and the root directory to `/`. 6. Click **Save and deploy**. 4. Sync your changes to GitHub and deploy: 1. In Google AI Studio, navigate to the **GitHub panel**. 2. Review the changes to be published. 3. Click **Stage and commit all changes**. 4. Navigate to the [Firebase console](https://console.firebase.google.com/project/_/apphosting?useAutoProject=true) to monitor the progress of the App Hosting deployment. #### Option B: Move to Cloud Run and publish your app to a new URL If you prefer a one-click experience and either haven't previously published your app, or don't mind a new URL (`*.run.app`), use the *Publish* button in Google AI Studio: 1. Open your app in Google AI Studio, and click **Publish**. 2. In the project selector, click **Import project**. 3. Search for and select the project name used by Firebase Studio (found in the top navigation bar of your Firebase Studio workspace). 4. Click **Import** , and then click **Publish**. > [!NOTE] > **Note:** If you have a custom domain, you must map it to your new Cloud Run service. Domain mapping can take up to 24 hours and may result in downtime for your app. Alternatively, you can continue publishing to Firebase App Hosting using [GitHub sync in AI Studio](https://firebase.google.com/docs/studio/migrating-project.md.txt#ais-publish-app-hosting) to avoid migrating domains. ## Migrate apps to Antigravity [Video](https://www.youtube.com/watch?v=7K_8bD7YkH8) Antigravity is a local, agent-first platform and agent hub that brings the power of autonomous multi-agent workflows into your local development environment. ### Prerequisites Ensure you have the following installed locally and fully up-to-date: - [Google Antigravity IDE](https://antigravity.google/download): From the download options, choose the **Antigravity IDE** (the editor environment). This is the code-first workspace where you will open and run your migrated app. - [Node.js](https://nodejs.org/en) (version 20 or higher) - [Firebase CLI](https://firebase.google.com/docs/cli.md.txt) (version 15.10.0 or higher) ### Step 1: Export and initialize your app ### Automated migration This workflow uses the Antigravity agent to autonomously handle project transformation. 1. In Firebase Studio, click the **Move now** button at the top of your workspace. 2. Follow the export method based on the window that appears: - If you see a **Zip and Download** button, click it. - Otherwise, 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. > [!TIP] > **Tip:** If the download window doesn't appear, check your browser's address bar for a pop-up blocker icon and ensure pop-ups are allowed. 3. Extract the folder locally and open it in the **Antigravity IDE**. 4. In the **Agent** pane within the **Antigravity IDE** interface, enter the following prompt. To optimize your workflow and conserve tokens, we recommend selecting the **Gemini Flash** model. It's designed for speed and efficiency in high-volume transformation tasks like file conversion. @fbs-to-agy-export 5. The Antigravity agent will begin project migration, requesting your assistance along the way. Follow the agent's guidance to complete the migration process. If you encounter any errors, prompt the agent to try again. ### Manual export If you prefer to manage the migration yourself without using AI tokens, you can use the Firebase CLI to manually export your project. This method is direct and does not require agent interaction. Open your terminal and run the following command, replacing PATH with the path to your extracted project folder or the original zip file (use `.` if you're already in the target directory): npx firebase-tools@latest studio:export PATH > [!NOTE] > **Note:** The `studio:export` command is optimized for Next.js, Flutter, and Angular workspaces. While you can use this command for other workspace types, the migration may not update all code artifacts for use in Antigravity. We're actively working to improve the migration flow. ### Step 2: Preview your app Once you've extracted your project and opened it within the Antigravity IDE, you can view your application locally: 1. In the **Antigravity IDE** , 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. > [!TIP] > **Tip:** To refine your app or troubleshoot issues, chat with the agent using natural language in the agent pane. If the agent pane is hidden, click the **Toggle Agent** icon at the top of the window to reopen it. ### Step 3: Publish your app Antigravity uses agent skills to publish your app using Firebase best practices. 1. In the agent 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 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. > [!TIP] > **Tip:** You can also export your workspace to GitHub. Learn more at [Upload your app to GitHub](https://firebase.google.com/docs/studio/github.md.txt). ### 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](https://firebase.google.com/docs/cli.md.txt#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: ```bash 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](https://firebase.google.com/docs/emulator-suite.md.txt) for faster, offline testing without deploying to a live environment. > [!NOTE] > **Note:** Core Firebase services like Cloud Firestore and Authentication will continue to function normally regardless of which platform you choose for hosting. ## 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. > [!IMPORTANT] > **Important:** **You must migrate your projects before > March 22, 2027** . On that date, Firebase Studio will be shut down, and all remaining data will be permanently deleted and cannot be recovered. ### Will my agent chat history be migrated? Your agent chat history isn't part of the current exported zip file. However, you can locate chat history files for the App Prototyping agent and Gemini agents within your workspace in the `/home/user/.idx/ai` directory of your Firebase Studio workspace. This contains prompts and responses from all 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 (![Code switch icon](https://firebase.google.com/static/docs/studio/images/icons/codicon-code.svg)). 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?](https://firebase.google.com/docs/studio/troubleshooting#download-files) 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**](https://firebase.google.com/docs/studio/get-started-workspace.md.txt#duplicate-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. > [!IMPORTANT] > **Important:** If you choose to manually export code from a shared workspace, remember that the backend configuration (like the Firebase project and API keys) will still point to the original owner's resources. You'll need to create a new Firebase project and update your environment variables to ensure the app functions under your own account. ### Where can I find the apps I've migrated to Google AI Studio? The [**Your apps** page](https://aistudio.google.com/apps?source=user) provides a unified list of all your projects, including those created from scratch in Google AI Studio and any you've migrated. ### Firebase Authentication with Google Sign-In doesn't work after migrating to Google AI Studio. If your app uses Google Sign-In, you must authorize your new project domain. 1. In the Firebase console, go to the [Authentication settings page](https://console.firebase.google.com/project/_/authentication/settings?useAutoProject=true). 2. Click **Authorized domains**. 3. Click **Add domain** and add the domain of your Google AI Studio app. ### What should I do if the Google AI Studio agent stops working or I see errors in Google AI Studio after the migration? Because the Google AI Studio agent manages complex background tasks while migrating your app, the agent can occasionally encounter issues like "task canceled," repeating messages, or unresponsive threads. - If the agent stops mid-task without a clear error, giving it a prompt like "Continue where you left off" or "Try that last step again" often jump-starts the process. - If you see a message that there were errors running the code, click the **Fix** button to prompt the agent to resolve them automatically. ### 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. ## Other resources - [Try the Firebase Studio to Antigravity migration codelab](https://codelabs.developers.google.com/antigravity/how-to-migrate-from-firebase-studio-to-antigravity). - [Explore the Antigravity documentation](https://antigravity.google/docs/firebase-studio-migration). - [Explore the Google AI Studio documentation](https://ai.google.dev/gemini-api/docs/aistudio-build-mode). ## 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](https://firebase.google.com/support/troubleshooter/studio/help). - Post in the [Firebase Studio Community Forum](https://community.firebasestudio.dev/).