Skip to content
Migration Guide

How to Export a Firebase Studio Project to GitHub (Step-by-Step Guide)

Step-by-step guide to push your Firebase Studio (formerly Project IDX) workspace to a GitHub repository.

Export Steps

1
Open your Firebase Studio workspace

Open the workspace you want to export and make sure the app runs. Firebase Studio is a full browser IDE, so everything below happens right inside it.

2
Create a GitHub repository

On GitHub, create a new empty repository (no README, licence, or .gitignore) and copy its URL. Private is a sensible default.

3
Commit in the built-in terminal

Open the terminal in your workspace. If the project is not already a git repository, run git init, then git add . and git commit -m "Export from Firebase Studio".

4
Add the remote and push

Run git remote add origin <repo-url>, then git branch -M main and git push -u origin main. Authenticate with GitHub when prompted — a personal access token works for HTTPS pushes.

5
Verify on GitHub

Open the repository and confirm the files are all there, the default branch is main, and no API keys or .env files were committed.

Alternative Route: Download and Push Locally

  • Firebase Studio workspaces can be downloaded as an archive. If you prefer working on your own machine, download the workspace, unzip it, and run the same git init → commit → push sequence locally.
  • This route also doubles as a backup: you keep a full offline snapshot of the project independent of the browser IDE.

Post-Export Checklist

  • Clone the repo on a local machine and verify the project installs and builds outside Firebase Studio.
  • Review .gitignore so node_modules, build output, and .env* files stay out of the repository.
  • Check the first commit for Firebase service-account keys or other secrets, and rotate anything that slipped through.
  • If your team has multiple contributors, set up branch protection rules on main.

Troubleshooting

  • Authentication fails on push: GitHub no longer accepts account passwords over HTTPS — create a personal access token and use it in place of the password, or set up SSH keys.
  • Push rejected: the GitHub repo was not empty. Recreate it without a README, or run git pull --rebase origin main and push again.
  • Huge first push: build artefacts or node_modules were committed. Add them to .gitignore, run git rm -r --cached on the offending paths, and recommit.

Next Step

Export is done. To move from prototype to production delivery with structured planning and AI implementation: See how Feature1 works.

Verification

Written on August 19, 2026. AI-builder UIs change quickly — if labels differ, follow the tool's current documentation: Firebase Documentation.

More export guides

Ready to ship production features?

Connect your GitHub repository to Feature1 and deliver features with AI-powered planning and implementation.

Join the Waitlist