Firebase Storage: storage/object-not-found — No object exists at the desired reference

The path you requested doesn't exist in the bucket (or isn't visible to the user).

Exact message you may see Firebase Storage: Object 'path' does not exist. (storage/object-not-found)No object exists at the desired referenceStorageException: Object does not exist at location404 Not Found Firebase Storage object
Seen on: Firebase JavaScript

Meaning

Check the exact path and case, wait for uploads to finish before reading, confirm the right bucket, and note that rules can make missing/forbidden objects look the same. getDownloadURL fails if the upload didn't complete.

Common causes

  • Typo or wrong case in the path
  • Upload not finished
  • Wrong bucket
  • Object deleted
  • Reading before write completes

⚡ Quick fix

  1. Print the reference fullPath and compare with the console
  2. Await the upload task before getDownloadURL
  3. Check the bucket in storageBucket

Detailed fix by platform

JavaScript

  1. javascript
    await uploadBytes(ref(storage, "avatars/u1.png"), file);
    const url = await getDownloadURL(ref(storage, "avatars/u1.png"));

How to diagnose

  1. Path — Exact?
  2. Upload — Complete?
  3. Bucket — Right?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

App Check — Firebase App Check: requests rejected (403 / app-check-token-is-invalid / attestation failed) (Google Cloud / Firebase)App Checkauth/account-exists-with-different-credential — Firebase Auth: account exists with a different credential (same email, other provider) (Google Cloud / Firebase)auth/account-exists-w…AuthenticationFailed — Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed) (Azure)AuthenticationFailedAuthorizationPermissionMismatch — Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission (Azure)AuthorizationPermissi…command not found — bash: command not found (Linux)command not foundContainerNotFound — Azure Storage: ContainerNotFound / BlobNotFound — The specified container (or blob) does not exist (Azure)ContainerNotFoundCORS: No Access-Control-Allow-Origin (Cloud Storage) — Browser: Access to fetch at 'https://storage.googleapis.com/bucket/file' from origin 'https://app.example.com' has been blocked by CORS policy (Google Cloud / Firebase)CORS: No Access-Contr…FailedMount — Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition (Kubernetes)FailedMountobject-no…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.