Firebase Studio – existing users and migration
Firebase Studio is closing on 22 March 2027. New sign-ups and workspaces are already disabled. This profile explains the remaining access for existing users and the need to migrate projects before shutdown.
Description
What is Firebase Studio?
Firebase Studio is a legacy Firebase workspace that is being shut down. Google disabled new user sign-up and new workspace creation on 22 June 2026. Existing users can continue working until 22 March 2027, but should plan project migration before then. It should not be promoted as a new app builder that readers can join today.
How it helps
The browser-based development environment combined coding assistance and AI app prototyping. For an existing Studio workspace, Firebase Studio can still be relevant during the transition. Check which projects need keeping, then use the official migration instructions rather than relying on an old tutorial’s sign-up steps.
Check the service status before starting
This entry is useful for people who already have a workspace and need to preserve their work. It should not be treated as a recommendation for a new project: new signups and workspace creation closed on 22 June 2026. Existing users need to prepare for the announced shutdown on 22 March 2027 rather than planning around an indefinite free development environment.
A simple example
For example, an owner with a small app in Firebase Studio should first identify the repository and hosting arrangement, then test the official workspace data export or transfer path. After migration, check the build and an important user flow. A moved code folder alone does not prove that the deployed app still behaves correctly.
Export the project while access remains
Move source code into a repository or another supported export destination, then confirm that the exported copy contains the files you need. Keep a record of setup commands and non-secret configuration. Do not wait until the last day to discover that a project relied on a workspace-only file. Credentials need a separate secure migration process and should not be committed to a public repository.
Setup and limits
The shutdown concerns the Google development workspace, not all Firebase backend services. Google says services such as Firestore, Authentication and App Hosting continue outside Firebase Studio. Check the development environment and the deployed service separately so a migration does not remove a working backend by mistake.
Rebuild the development setup elsewhere
Use the exported source in the chosen replacement environment and install its documented dependencies. Run the app and its checks from that copy. Note any tools, environment variables or preview configuration that existed only in the old workspace. An export is a starting point for migration; a successful clean run in the new environment is stronger evidence that the project can continue.
Firebase Studio pricing
| Plan / route | Monthly or usage price | Annual option | Included use | Extra costs / conditions |
|---|---|---|---|---|
| New user / workspace | Unavailable | Unavailable | Closed since 22 June 2026 | New-user access is closed. |
| Existing Studio workspace | Legacy access | Ends 22 March 2027 | Work and migration in existing workspaces only | Remaining Studio data is deleted at shutdown according to Google. |
| Firestore, Authentication, App Hosting and other Firebase services | Separate service billing | Service-dependent | Continue outside the closing Studio environment | Environment shutdown does not cancel every backend service. |
There is no current new-user Studio subscription to buy. Existing users should migrate before the shutdown date and review their separately billed Firebase resources after moving.
Separate workspace shutdown from backend services
The announced workspace closure does not mean that all Firebase products are ending. Review the project’s actual backend services, hosting and billing separately. Keep the relevant project identifiers and administrator access available during the move. Before deleting or disconnecting anything, verify which service owns the production data and which part was only the development workspace.
Who should use it?
Firebase Studio is relevant mainly to existing users who need a migration route. Google points to AI Studio and Antigravity for different development needs. Save the work you want to keep, follow the official transfer steps and test the result before the deadline. New users should choose a currently available development environment instead.
Common questions
Can a new user create a workspace now?
No. The official migration notice says new signups and workspace creation closed on 22 June 2026. Publish this as a status or migration entry for existing users rather than a normal new-tool spotlight.
Will the shutdown delete every Firebase project?
The notice concerns Studio and its remaining workspace data. Firebase backend products continue separately. Check the official migration guidance and the project’s actual service configuration before making changes.
Check the official pricing and access details before choosing a plan.
For related options on SimplifyAITools, see Google AI Studio and Replit AI.
Key Features
- Legacy browser-based coding and prototyping environment.
- Existing-workspace access during the transition.
- Official migration instructions for AI Studio and Antigravity.
- Code export and transfer paths for existing projects.
- Separate Firebase backend services continue.
- Existing-workspace access: the remaining service period is intended for current users, subject to the closure schedule.
- Source preservation: export or commit the project before the announced end date.
- Migration guidance: official documentation explains the transition away from the workspace.
- Backend separation: Firebase services and their billing need review independently of Studio.
- Replacement verification: run the exported project in its next development environment before relying on the migration.
Strengths & Weaknesses
Strengths
- Official migration paths are documented.
- Existing users have a defined transition period.
- Core Firebase services are distinguished from the closing environment.
- A status page can help readers avoid outdated tutorials.
- A clear status entry can stop readers from following an outdated signup tutorial.
- The published end date gives existing users a concrete migration deadline.
- Separating the workspace from backend products prevents confusion about production services.
- A tested exported copy reduces dependence on the closing development environment.
! Weaknesses
- New user sign-up and workspace creation are disabled.
- The environment shuts down on 22 March 2027.
- Remaining Studio data is deleted at shutdown according to Google.
- New users cannot follow old onboarding instructions to create a fresh workspace.
- Remaining workspace data is scheduled for deletion at shutdown under the official notice.
- A source export may omit setup knowledge or files that were never saved properly.
- Treating the old free workspace as a current long-term plan can mislead readers.
Try Firebase Studio – existing users and migration
Start boosting your productivity today
Official Resources
Helpful guides and demos published by the tool provider.
Work on Firebase Studio – existing users and migration? Add our badge to your website
Let your visitors know your tool is listed here. It's free and you don't have to add it.
Copy the code below and paste it into your website's footer, press page or "As seen on" section. The badge links back to this page. Adding it is up to you. Your listing, rating and review stay the same either way. How badges work
