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).
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 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
- Print the reference
fullPathand compare with the console - Await the upload task before
getDownloadURL - Check the bucket in
storageBucket
Detailed fix by platform
JavaScript
- javascript
await uploadBytes(ref(storage, "avatars/u1.png"), file); const url = await getDownloadURL(ref(storage, "avatars/u1.png"));
How to diagnose
- Path — Exact?
- Upload — Complete?
- 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:
Similar errors
- App Check Firebase App Check: requests rejected (403 / app-check-token-is-invalid / attestation failed)
- auth/account-exists-with-different-credential Firebase Auth: account exists with a different credential (same email, other provider)
- AuthenticationFailed Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed)
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026