How to Fix Firebase Hosting Deploy Errors

This error means firebase.json either does not exist or does not contain a hosting section. Run firebase init hosting to create the configuration, or manually add a hosting block to your firebase.json. Make sure the file is in your project root directory where you run the deploy command.

1// If firebase.json is missing, run:
2// firebase init hosting
3
4// Or add the hosting section manually:
5// firebase.json
6{
7  "hosting": {
8    "public": "dist",
9    "ignore": ["firebase.json", "**/.*", "**/node_modules/**"],
10    "rewrites": [
11      {
12        "source": "**",
13        "destination": "/index.html"
14      }
15    ]
16  }
17}

Firebase cannot find the directory specified in the public field of firebase.json. This usually happens when you forget to run your build command before deploying, or when the public field points to the wrong directory name. Check your framework's actual output directory: Vite uses 'dist', Create React App uses 'build', and Next.js static export uses 'out'.

1// 1. Build your app first:
2npm run build
3
4// 2. Verify the output directory exists:
5ls dist   # or build, out, etc.
6
7// 3. Make sure firebase.json matches:
8{
9  "hosting": {
10    "public": "dist"  // Must match your actual build output folder
11  }
12}

A 403 error during deploy means the Firebase CLI does not have permission to deploy to this project. This happens when you are logged into the wrong Google account, your account does not have Editor or Owner role on the Firebase project, or your auth token has expired. Re-authenticate and verify your project selection.

1# Log out and log back in
2firebase logout
3firebase login
4
5# Verify which account is active
6firebase login:list
7
8# Verify which project is selected
9firebase use
10
11# If wrong project, switch:
12firebase use your-correct-project-id

The Spark free plan limits hosting storage to 10 GB and bandwidth to 360 MB per day. If you exceed these limits, deploys fail with a quota error. Either reduce your deployed file size by excluding unnecessary files with the ignore array, or upgrade to the Blaze plan for higher limits. Also check that you are not accidentally deploying large files like node_modules or media assets.

1// firebase.json — exclude large files
2{
3  "hosting": {
4    "public": "dist",
5    "ignore": [
6      "firebase.json",
7      "**/.*",
8      "**/node_modules/**",
9      "**/*.map",
10      "**/test/**",
11      "**/coverage/**"
12    ]
13  }
14}

An outdated Firebase CLI may fail with cryptic errors or incompatibility messages. Firebase regularly updates the CLI and deprecates older versions. If you see errors about unsupported features or unexpected API responses, update the CLI to the latest version. Also verify your Node.js version is 18 or later, as older versions are no longer supported.

1# Check current CLI version
2firebase --version
3
4# Update to latest
5npm install -g firebase-tools@latest
6
7# Check Node.js version (must be 18+)
8node --version
9
10# If Node.js is outdated, update via nvm:
11nvm install 22
12nvm use 22

If your public directory contains too many files or very large files, the CLI may time out during the file listing or upload phase. This is common when accidentally including node_modules, .git, or large media folders in the public directory. Ensure your ignore array excludes non-essential files and that only your built output is in the public directory.

1// Check how many files are in your public directory:
2// find dist -type f | wc -l
3
4// If it's more than a few hundred, check for accidental inclusions.
5// Common culprits: source maps, test files, media assets
6
7// firebase.json — aggressive ignore
8{
9  "hosting": {
10    "public": "dist",
11    "ignore": [
12      "firebase.json",
13      "**/.*",
14      "**/node_modules/**",
15      "**/*.map",
16      "**/*.test.*",
17      "**/*.spec.*"
18    ]
19  }
20}