Firebase Storage: Firebase Storage: User does not have permission to access 'images/photo.jpg'. (storage/unauthorized)
Firebase Security Rules for Cloud Storage denied the request for this path and user.
Firebase Storage: User does not have permission to access (storage/unauthorized)storage/unauthenticated User is not authenticatedFirebase Storage: User is not authenticatedstorage/object-not-found Firebase Storage Meaning
Rules decide access: check storage.rules for the path and condition (request.auth != null), make sure the user is signed in, the path matches your match block, and rules were deployed. Test in the Rules Playground. Also check that the bucket URL in the SDK matches the project.
Common causes
- Not signed in but rules require auth
- Rules path mismatch
- Rules not deployed
- Wrong bucket in the config
- Size or content-type conditions in rules failing
⚡ Quick fix
- Read and fix
storage.rules; deploy withfirebase deploy --only storage - Sign in before upload/download
- Use the Rules Playground to simulate
Detailed fix by platform
Firebase
firebase deploy --only storage
Code examples
storage.rules
rules_version = '2';
service firebase.storage {
match /b/{bucket}/o {
match /images/{userId}/{file} {
allow read: if true;
allow write: if request.auth != null && request.auth.uid == userId;
}
}
}How to diagnose
- Auth — Signed in?
- Rules — Match the path?
- Deploy — Latest rules?
🔧 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
- 403: does not have storage.objects.get access Cloud Storage: 403 Forbidden — user@example.com does not have storage.objects.get access to the Google Cloud Storage object
- auth/invalid-credential Firebase Auth: auth/invalid-credential (auth/wrong-password, auth/user-not-found, auth/invalid-login-credentials)
- CORS: 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
Most viewed in Google Cloud / Firebase
- 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
- Could not load the default credentials Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
- 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 4 Nov 2026