File upload handling basics in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the first step to enable file uploads in a Django form?

You must add enctype="multipart/form-data" to the HTML form tag. This tells the browser to send file data along with the form.

beginner

How do you access an uploaded file in a Django view?

Use request.FILES dictionary with the file input's name as the key, for example request.FILES['file_field_name'].

beginner

What Django field type is used to store uploaded files in a model?

Use models.FileField or models.ImageField to store file or image uploads respectively.

intermediate

Why should you validate uploaded files in Django?

To ensure files are safe, the right type, and within size limits. This protects your app from harmful files and errors.

beginner

Where does Django store uploaded files by default?

By default, files are saved to the directory specified by the MEDIA_ROOT setting.

Which attribute must be added to a form tag to upload files in Django?

A method="get"

B enctype="multipart/form-data"

C action="upload/"

D type="file"

The enctype="multipart/form-data" attribute is required to send files through a form.

How do you access an uploaded file in a Django view?

A request.POST['file']

B request.GET['file']

C request.FILES['file']

D request.DATA['file']

Uploaded files are available in request.FILES, not in POST or GET.

Which model field is best for storing uploaded images?

A models.ImageField

B models.FileField

C models.TextField

D models.CharField

models.ImageField is designed for image uploads and validates image files.

Where should you configure the directory to save uploaded files in Django?

A MEDIA_ROOT

B STATIC_ROOT

C TEMPLATES_DIR

D UPLOAD_DIR

MEDIA_ROOT setting defines where uploaded files are stored.

Why is it important to validate uploaded files?

A To improve page load speed

B To prevent uploading large files only

C To reduce server memory usage

D To ensure files are safe and correct type

Validation helps protect your app by checking file type, size, and safety.

Explain the steps to handle a file upload in a Django app from form to saving the file.

Think about form setup, model fields, view handling, and storage.

Describe why and how you validate uploaded files in Django.

Consider security and app stability.

Practice

1. What is the main purpose of request.FILES in Django when handling file uploads?

easy

A. To access the uploaded file data sent by the user

B. To store form validation errors

C. To save files directly to the database

D. To send files from the server to the client

Solution

1. Step 1: Understand the role of request.FILES

   This attribute contains all files uploaded by the user in the current request.

2. Step 2: Differentiate from other request attributes

   request.POST holds form data, but request.FILES specifically holds file data.

3. Final Answer:

   To access the uploaded file data sent by the user -> Option A

4. Quick Check:

   File data = request.FILES [OK]

Hint: Remember: files come in request.FILES, not request.POST [OK]

Common Mistakes:

• Confusing request.FILES with request.POST
• Thinking files are saved automatically
• Assuming request.FILES is a file path

2. Which of the following is the correct way to define a file upload field in a Django form?

easy

A. file = forms.FileField()

B. file = forms.CharField()

C. file = models.FileField()

D. file = forms.ImageField()

Solution

1. Step 1: Identify form field types for file uploads

   forms.FileField() is used in forms to accept any file upload.

2. Step 2: Differentiate from model fields and other form fields

   models.FileField() is for models, not forms. forms.ImageField() is for images only.

3. Final Answer:

   file = forms.FileField() -> Option A

4. Quick Check:

   File upload field in form = FileField() [OK]

Hint: Use FileField() in forms, not CharField() or model fields [OK]

Common Mistakes:

• Using CharField instead of FileField
• Confusing model fields with form fields
• Using ImageField for non-image files

3. Given this Django view snippet handling a file upload:

def upload_file(request):
    if request.method == 'POST':
        uploaded_file = request.FILES['file']
        with open('uploaded.txt', 'wb+') as destination:
            for chunk in uploaded_file.chunks():
                destination.write(chunk)
    return HttpResponse('Upload complete')

What will happen if the uploaded file is large?

medium

A. The file will cause a memory error because it is read all at once

B. The file will be saved in chunks to avoid memory issues

C. The file will be saved as text instead of binary

D. The file upload will fail because chunks() is not a valid method

Solution

1. Step 1: Understand the use of chunks() method

   The chunks() method reads the uploaded file in small parts to avoid loading the entire file into memory.

2. Step 2: Analyze the file saving logic

   The code writes each chunk to the file, so large files are handled safely without memory errors.

3. Final Answer:

   The file will be saved in chunks to avoid memory issues -> Option B

4. Quick Check:

   chunks() saves large files safely [OK]

Hint: chunks() method helps save large files safely [OK]

Common Mistakes:

• Assuming chunks() reads whole file at once
• Thinking chunks() is invalid method
• Ignoring binary write mode 'wb+'

4. Identify the error in this Django view code for file upload:

def upload(request):
    if request.method == 'POST':
        file = request.POST['file']
        with open('file.txt', 'wb') as f:
            f.write(file.read())
    return HttpResponse('Done')

medium

A. Missing form validation before saving the file

B. Opening the file in write mode instead of append mode

C. Using request.POST instead of request.FILES to get the file

D. Not checking if the request method is GET

Solution

1. Step 1: Check how the uploaded file is accessed

   The code uses request.POST['file'], but uploaded files are in request.FILES.

2. Step 2: Understand the impact of this mistake

   Accessing the file from request.POST will cause a KeyError or wrong data type error.

3. Final Answer:

   Using request.POST instead of request.FILES to get the file -> Option C

4. Quick Check:

   Files come from request.FILES, not request.POST [OK]

Hint: Always get files from request.FILES, not request.POST [OK]

Common Mistakes:

• Using request.POST for files
• Not opening file in binary mode
• Ignoring request method check

5. You want to save an uploaded file in Django but only if its size is less than 2MB. Which code snippet correctly checks the file size before saving?

hard

A. if uploaded_file.length < 2 * 1024 * 1024:
with open('file.txt', 'w') as f:
f.write(uploaded_file)

B. if len(uploaded_file) < 2 * 1024 * 1024:
with open('file.txt', 'wb+') as f:
f.write(uploaded_file.read())

C. if uploaded_file.size > 2 * 1024 * 1024:
with open('file.txt', 'wb+') as f:
for chunk in uploaded_file.chunks():
f.write(chunk)

D. if uploaded_file.size < 2 * 1024 * 1024:
with open('file.txt', 'wb+') as f:
for chunk in uploaded_file.chunks():
f.write(chunk)

Solution

1. Step 1: Check the correct attribute for file size

   The size attribute gives the file size in bytes.

2. Step 2: Verify the condition and saving method

   The condition checks if size is less than 2MB (2 * 1024 * 1024 bytes). The file is saved in chunks to handle large files safely.

3. Final Answer:

   if uploaded_file.size < 2 * 1024 * 1024: with open('file.txt', 'wb+') as f: for chunk in uploaded_file.chunks(): f.write(chunk) -> Option D

4. Quick Check:

   Use uploaded_file.size and chunks() to save safely [OK]

Hint: Use uploaded_file.size to check size before saving [OK]

Common Mistakes:

• Using len() or length instead of size
• Opening file in text mode 'w' instead of binary
• Checking size with wrong comparison operator