Firebase Studio Sunset: New Workspace Creation Disabled June 22, 2026; Full Shutdown Set for March 22, 2027

Google has confirmed the sunset of Firebase Studio. New workspace creation is now disabled effective June 22, 2026. Existing workspaces remain accessible for use and migration until the permanent shutdown on March 22, 2027, after which all remaining data will be permanently deleted and unrecoverable.

The official migration guidance page states: “Firebase Studio is sunsetting on March 22, 2027.” Migration tools began rolling out with the announcement on March 19, 2026.

Key Timeline and Facts

• March 19, 2026: Sunset announced; migration tools made available inside Firebase Studio.

• June 22, 2026: New workspace creation disabled. Existing workspaces can still be opened, edited, and migrated.

• March 22, 2027: Full shutdown. Firebase Studio environment, workspaces, and all associated data are permanently deleted with no recovery option.

• Affected components: Firebase Studio development environment, App Prototyping agent, Code View, terminal access, and related agent chat functionality.

• Important limitation: Agent chat history is not included in the automated export zip file and must be handled separately. Only the original workspace creator can use the “Move now” button.

Migration Paths (Official Options)

Google provides three primary migration routes from the official documentation:

1. Google Antigravity (recommended for code-first and agentic development workflows)
   Prerequisites: Google Antigravity IDE installed, Node.js v20+, Firebase CLI v15.10.0+.
   Process includes zipping and downloading the workspace (via “Move now” > “Zip and Download” or CLI command npx firebase-tools@latest studio:export PATH), opening in Antigravity, using the agent prompt @fbs-to-agy-export (Gemini Flash recommended), local preview via Run and Debug, and publishing via agent command or firebase deploy.
2. Google AI Studio (recommended for web-based prototyping)
   Use the “Move now” > “Prepare for AI Studio” flow, followed by “Move to Google AI Studio.” Publishing options include App Hosting (to retain existing URL via GitHub sync and Firebase console connection) or direct publish to Cloud Run (new URL).
3. Manual export to other platforms
   Zip and download the project, then deploy via Firebase CLI (firebase init apphosting linked to existing “studio” backend), external hosting providers, or Firebase Local Emulator Suite for local development.

Troubleshooting notes from the page: If export stalls or times out, delete node_modules, large artifacts, or hidden files. Agent chat history requires manual export as it is not part of the zip.

Implications

This is a forced migration event for any teams or individual developers actively using Firebase Studio for AI-assisted app prototyping and development. The June 22, 2026 cutoff on new workspaces immediately limits expansion or new project starts within the platform. The March 22, 2027 hard deadline creates a hard data-loss risk for any unmigrated workspaces.

The change removes a Google-provided agentic prototyping environment and pushes users toward Antigravity (more code/agent-focused) or Google AI Studio (more web/prototyping-focused), or fully manual/self-managed hosting. Teams relying on the integrated App Prototyping agent and workspace continuity face workflow disruption and must plan data preservation, especially chat history.

Vendor concentration risk increases for projects that have not yet diversified their development and deployment tooling.

Actions to Take

Immediate (this week):

• Log into any active Firebase Studio workspaces and use the “Move now” button to begin export or direct migration while access is guaranteed.

• Manually export and save agent chat history if it contains important prompts, decisions, or code iterations.

• Inventory all workspaces and identify which migration path best fits each project’s needs (Antigravity for agentic/code-heavy work; AI Studio for rapid web prototypes).

Short-term (next 30–60 days):

• Test migration to the chosen target (Antigravity or AI Studio) on non-critical workspaces first to validate the full flow, including preview and deploy steps.

• Update local tooling: Install or update to Firebase CLI v15.10.0+ and Google Antigravity IDE if selecting that route. Ensure Node.js v20+ is in place.

• For teams planning to keep existing URLs, set up GitHub repositories and connect them via Firebase App Hosting in the console as part of the AI Studio or manual path.

• Document current workspace URLs, published app endpoints, and any environment variables or API keys that will need re-securing post-migration.

Before March 22, 2027:

• Complete full migration and verify that all apps run correctly in the new environment (local preview + deployed version).

• Delete or archive any remaining Firebase Studio workspaces once migration is confirmed successful to reduce risk.

• Monitor the official Firebase Studio Community Forum and Firebase Support channels for any updates to migration tools or timelines.

Ongoing monitoring:

• Track Google announcements regarding Antigravity and Google AI Studio feature parity or new capabilities that replace former Firebase Studio agent functionality.

• Review project roadmaps to avoid future dependency on single Google development environments without clear long-term support commitments.