MEDIA_URL and MEDIA_ROOT in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is MEDIA_ROOT in Django?

MEDIA_ROOT is the absolute filesystem path where Django will store user-uploaded files.

Think of it as the folder on your computer where all uploaded pictures or documents are saved.

beginner

What does MEDIA_URL represent in Django?

MEDIA_URL is the URL that handles the media served from MEDIA_ROOT.

It is like the web address prefix you use to access uploaded files in a browser.

intermediate

How do MEDIA_URL and MEDIA_ROOT work together?

MEDIA_ROOT stores the files on the server, and MEDIA_URL is the web path to access those files.

Imagine MEDIA_ROOT as a storage room and MEDIA_URL as the street address to visit that room.

beginner

Where do you set MEDIA_URL and MEDIA_ROOT in a Django project?

You set both in the settings.py file of your Django project.

Example:
MEDIA_URL = '/media/'
MEDIA_ROOT = BASE_DIR / 'media'

intermediate

Why do you need to configure MEDIA_URL and MEDIA_ROOT during development?

Because Django does not serve uploaded files automatically in development.

You must tell Django where to find files (MEDIA_ROOT) and how to serve them via URL (MEDIA_URL).

What type of path is MEDIA_ROOT in Django?

A Relative URL path

B URL path

C Absolute filesystem path

D Database path

MEDIA_ROOT is an absolute path on the server's filesystem where files are stored.

What does MEDIA_URL usually end with?

A A slash '/'

B A file extension like '.jpg'

C A number

D A backslash '\'

MEDIA_URL typically ends with a slash to indicate a directory URL, e.g., '/media/'.

Where do you configure MEDIA_ROOT and MEDIA_URL?

A In <code>urls.py</code>

B In <code>settings.py</code>

C In <code>models.py</code>

D In <code>views.py</code>

Both are set in the settings.py file.

What happens if you don't set MEDIA_URL and MEDIA_ROOT?

A Django will automatically serve files

B No effect on file uploads

C Files will be stored in the database

D Uploaded files won't be served properly

Django needs these settings to know where to store and how to serve uploaded files.

During development, how do you serve media files?

A By adding URL patterns to serve <code>MEDIA_URL</code> from <code>MEDIA_ROOT</code>

B By uploading files to a CDN

C By storing files in the database

D By using Django's admin interface only

In development, you add URL patterns to serve media files from MEDIA_ROOT using MEDIA_URL.

Explain in your own words what MEDIA_ROOT and MEDIA_URL do in a Django project.

Think about where files live and how you reach them on the web.

Describe how you would configure Django to serve uploaded media files during development.

Remember Django does not serve media files automatically in development.

Practice

1. What does MEDIA_URL represent in a Django project?

easy

A. The folder path where Django stores static files

B. The URL prefix used to access media files in the browser

C. The database table for storing media file info

D. The Python module for handling media uploads

Solution

1. Step 1: Understand MEDIA_URL purpose

   MEDIA_URL is used to define the URL prefix that browsers use to access media files uploaded by users.

2. Step 2: Differentiate from MEDIA_ROOT

   MEDIA_ROOT is the folder path on the server, not a URL. Static files and database tables are unrelated here.

3. Final Answer:

   The URL prefix used to access media files in the browser -> Option B

4. Quick Check:

   MEDIA_URL = URL prefix [OK]

Hint: MEDIA_URL is always a URL path, not a folder path [OK]

Common Mistakes:

• Confusing MEDIA_URL with MEDIA_ROOT
• Thinking MEDIA_URL is a folder path
• Mixing MEDIA_URL with static files settings

2. Which of the following is the correct way to set MEDIA_ROOT in Django's settings.py?

easy

A. MEDIA_ROOT = os.path.join(BASE_DIR, 'media')

B. MEDIA_ROOT = 'static/media/'

C. MEDIA_ROOT = 'http://example.com/media/'

D. MEDIA_ROOT = '/media/'

Solution

1. Step 1: Understand MEDIA_ROOT type

   MEDIA_ROOT must be a filesystem path, not a URL or relative URL string.

2. Step 2: Check correct syntax

   Using os.path.join(BASE_DIR, 'media') correctly builds an absolute path inside the project folder.

3. Final Answer:

   MEDIA_ROOT = os.path.join(BASE_DIR, 'media') -> Option A

4. Quick Check:

   MEDIA_ROOT = absolute folder path [OK]

Hint: MEDIA_ROOT is a folder path, use os.path.join for safety [OK]

Common Mistakes:

• Setting MEDIA_ROOT as a URL string
• Using relative paths without BASE_DIR
• Confusing MEDIA_ROOT with MEDIA_URL

3. Given the settings:
MEDIA_URL = '/media/'
MEDIA_ROOT = '/var/www/myproject/media/'
What URL will serve the file stored at /var/www/myproject/media/photos/pic.jpg?

medium

A. http://example.com/media/photos/pic.jpg

B. http://example.com/photos/pic.jpg

C. http://example.com/static/photos/pic.jpg

D. http://example.com/media_root/photos/pic.jpg

Solution

1. Step 1: Match file path to MEDIA_ROOT

   The file is inside /var/www/myproject/media/, which matches MEDIA_ROOT.

2. Step 2: Combine MEDIA_URL with relative file path

   The URL to access the file is MEDIA_URL + 'photos/pic.jpg' = /media/photos/pic.jpg.

3. Final Answer:

   http://example.com/media/photos/pic.jpg -> Option A

4. Quick Check:

   MEDIA_URL + relative path = URL [OK]

Hint: URL = MEDIA_URL + file path relative to MEDIA_ROOT [OK]

Common Mistakes:

• Using MEDIA_ROOT as URL prefix
• Confusing static files URL with media URL
• Omitting MEDIA_URL prefix

4. You set MEDIA_URL = '/media/' and MEDIA_ROOT = 'media/' in settings.py. When you upload files, they are not accessible via browser. What is the likely problem?

medium

A. MEDIA_URL must end with a file extension

B. MEDIA_URL should be a filesystem path

C. MEDIA_ROOT and MEDIA_URL cannot have the same name

D. MEDIA_ROOT should be an absolute path, not relative

Solution

1. Step 1: Check MEDIA_ROOT path type

   MEDIA_ROOT must be an absolute path to the folder on disk, not a relative path.

2. Step 2: Understand impact on file serving

   Using a relative path can cause Django or the web server to fail to find the files, making them inaccessible.

3. Final Answer:

   MEDIA_ROOT should be an absolute path, not relative -> Option D

4. Quick Check:

   MEDIA_ROOT = absolute path [OK]

Hint: Always use absolute path for MEDIA_ROOT [OK]

Common Mistakes:

• Using relative paths for MEDIA_ROOT
• Expecting MEDIA_URL to be a folder path
• Not configuring web server to serve media files

5. You want to serve user-uploaded images stored in /home/user/project/media/ at URL prefix /uploads/. Which settings.py configuration is correct?

hard

A. MEDIA_ROOT = '/home/user/project/media/'
MEDIA_URL = '/media/'

B. MEDIA_ROOT = '/uploads/'
MEDIA_URL = '/home/user/project/media/'

C. MEDIA_ROOT = '/home/user/project/media/'
MEDIA_URL = '/uploads/'

D. MEDIA_ROOT = 'media/'
MEDIA_URL = '/uploads/'

Solution

1. Step 1: Match folder path to MEDIA_ROOT

   The folder /home/user/project/media/ is the physical location of files, so it must be set as MEDIA_ROOT.

2. Step 2: Set URL prefix to /uploads/

   To serve files at /uploads/, set MEDIA_URL = '/uploads/'.

3. Final Answer:

   MEDIA_ROOT = '/home/user/project/media/' and MEDIA_URL = '/uploads/' -> Option C

4. Quick Check:

   MEDIA_ROOT = folder path, MEDIA_URL = URL prefix [OK]

Hint: MEDIA_ROOT = folder, MEDIA_URL = URL prefix you want [OK]

Common Mistakes:

• Swapping MEDIA_ROOT and MEDIA_URL values
• Using relative path for MEDIA_ROOT
• Not matching URL prefix with desired access path