Storage bucket structure in Firebase - Step-by-Step Execution

Process Flow - Storage bucket structure

Reference Storage Bucket

↓

Add Folder (Optional)

↓

Upload File

↓

File Stored with Path

↓

Access File via Path

↓

Manage Permissions

This flow shows how a storage bucket is referenced, files are organized in folders, stored with paths, and accessed with permissions.

Execution Sample

Firebase

bucket = admin.storage().bucket('my-app-bucket')
folder = 'images/'
file_path = folder + 'photo1.jpg'
bucket.upload('local/photo1.jpg', {destination: file_path})

This code references a bucket, defines a folder path, and uploads a file to that path inside the bucket.

Process Table

Step	Action	Path/Name	Result
1	Reference bucket	my-app-bucket	Bucket 'my-app-bucket' referenced
2	Define folder path	images/	Folder path 'images/' set (logical, no physical folder)
3	Set file path	images/photo1.jpg	File path set combining folder and file name
4	Upload file	images/photo1.jpg	File uploaded to bucket at 'images/photo1.jpg'
5	Access file	images/photo1.jpg	File can be accessed via this path
6	Set permissions	images/photo1.jpg	Permissions set for file access

💡 File uploaded and accessible at 'images/photo1.jpg' in the bucket

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
bucket	undefined	my-app-bucket	my-app-bucket	my-app-bucket	my-app-bucket
folder	undefined	images/	images/	images/	images/
file_path	undefined	undefined	images/photo1.jpg	images/photo1.jpg	images/photo1.jpg

Key Moments - 3 Insights

Why is the folder 'images/' not a real folder in the bucket?

Because storage buckets use paths as part of file names, folders are logical prefixes, not physical directories. See execution_table step 2 and 4.

How does the file path 'images/photo1.jpg' help organize files?

It creates a clear structure by prefixing the file name with a folder path, making it easier to find and manage files. See execution_table step 3.

What happens if you try to access a file path that does not exist?

Access will fail because the file is not stored there. Files must be uploaded first as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the file path after step 3?

A my-app-bucket/photo1.jpg

B photo1.jpg

C images/photo1.jpg

D images/

💡 Hint

Check the 'Path/Name' column at step 3 in the execution_table

At which step is the file actually uploaded to the bucket?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look for the action 'Upload file' in the execution_table

If the folder variable was empty, what would be the file path after step 3?

A images/photo1.jpg

B photo1.jpg

C /photo1.jpg

D my-app-bucket/photo1.jpg

💡 Hint

See how file_path is set by combining folder and file name in execution_sample

Concept Snapshot

Storage buckets hold files using paths as names.
Folders are logical prefixes, not real directories.
Files are uploaded with full paths.
Access files by their path.
Permissions control who can read/write files.

Full Transcript

This lesson shows how storage buckets organize files using paths that look like folders but are actually part of the file name. We reference a bucket, define a folder path, combine it with a file name to form a file path, and upload the file to that path. The folder is not a real directory but a prefix in the file path. Files can be accessed and managed by their full path inside the bucket. Permissions control access to these files.