The 'Error 404: project not found' in Firebase means the project ID in your configuration does not match any existing Firebase project. This usually happens when the project was deleted, the ID was mistyped, or you are using a different Google account than the one that owns the project. Verify the project ID in Firebase Console and update your configuration.
What does "Error 404: project not found" mean in Firebase?
This error means Firebase cannot find a project matching the ID in your configuration. The project ID is the unique identifier for your Firebase project (like my-app-12345), and it must match exactly. Firebase returns 404 when the ID does not correspond to any existing project your account has access to.
This error appears in multiple contexts: the Firebase CLI during deployment, the Firebase Console when navigating to a project URL, in SDK initialization when the projectId is wrong, and in Cloud Functions when they reference a non-existent project.
The most common cause is a typo in the project ID. Firebase project IDs are case-sensitive and often include random suffixes (like -12345) that are easy to mistype. Other common causes include using a deleted project's ID, deploying from the wrong Google account, or referencing a project that was created in a different Firebase organization.
Common causes
The project ID in the Firebase configuration object or
.firebaserc file has a typo or is incorrect
The Firebase project was deleted
and the ID no longer exists in any Firebase organization
You are authenticated with a
different Google account than the one that owns the Firebase project
The .firebaserc file references a project from
a different environment (development vs production)
The project was created in
a different Google Cloud organization that your current account does not have access to
Environment variables for the project ID are
missing or unprefixed, passing undefined as the project identifier
How to fix "Error 404: project not found" in Firebase
First, verify the correct project ID. Open the Firebase Console (console.firebase.google.com), click on your project, and check the project ID in Project Settings (gear icon) > General tab. The project ID is shown under 'Project ID.'
Compare this ID with what is in your code and configuration files. Check firebase config objects (the projectId field), the .firebaserc file (which maps aliases to project IDs), and any environment variables that hold the project ID.
For CLI errors, ensure you are logged into the correct Google account. Run firebase login:list to see which account is active. Run firebase login to switch accounts if needed. Then run firebase use --add to select the correct project.
For SDK errors, verify the full Firebase config object. All fields must match the project shown in Firebase Console > Project Settings > Your apps. Pay special attention to projectId — it is case-sensitive.
If the project was deleted, it cannot be recovered after 30 days. You will need to create a new project. If the project exists but is in a different organization, you need the organization admin to grant you access.
Prevention tips
- Copy the project ID directly from Firebase Console > Project Settings instead of typing it manually to avoid typos
- Check .firebaserc to ensure the correct project is mapped to your deployment alias (usually 'default')
- Run firebase login:list to verify you are using the correct Google account — deploying from the wrong account returns 404
- Use environment variables for the project ID and validate they are not undefined before initializing Firebase
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
Firebase shows 'Error 404: project not found' when I try to deploy. I can see the project in the Firebase Console. What could cause the CLI to not find a project that exists?
My Firebase deployment fails with 'Error 404: project not found'. Here is my .firebaserc: [paste]. And my firebase config: [paste]. Find the mismatch and fix the configuration.
Frequently asked questions
What causes "Error 404: project not found" in Firebase?
The project ID in your configuration does not match any Firebase project your account has access to. Common causes are typos in the project ID, using a deleted project's ID, being logged into the wrong Google account, or missing/undefined environment variables.
How do I find my Firebase project ID?
Open the Firebase Console, click on your project, go to Project Settings (gear icon) > General tab. The project ID is listed under 'Project ID'. Copy it directly to avoid typos.
Can I recover a deleted Firebase project?
Firebase projects can be recovered within 30 days of deletion through the Google Cloud Console > IAM & Admin > Manage Resources > filter by 'Delete Requested'. After 30 days, the project and all data are permanently deleted.
Why does the Firebase CLI say project not found when I can see it in the Console?
You are likely logged into a different Google account in the CLI than in your browser. Run firebase login:list to check the active CLI account. Run firebase login to switch to the account that owns the project.
Can RapidDev help with Firebase project configuration issues?
Yes. RapidDev can audit your Firebase configuration across all environments (development, staging, production), set up proper .firebaserc mappings, configure environment variables, and ensure consistent project references across your deployment pipeline.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your issue.
Book a free consultation