Saving uploaded files in Flask - Performance & Optimization

Performance: Saving uploaded files

MEDIUM IMPACT

This affects page load speed and server response time during file uploads and saves.

Saving uploaded files in a Flask web app

Flask

file = request.files['file']
filename = secure_filename(file.filename)
filepath = os.path.join(app.config['UPLOAD_FOLDER'], filename)
with open(filepath, 'wb') as f:
    while chunk := file.stream.read(4096):
        if not chunk:
            break
        f.write(chunk)

Streams file in chunks and uses secure filename to avoid blocking and security risks.

📈 Performance Gainreduces blocking time, improves server responsiveness, safer file handling

Saving uploaded files in a Flask web app

Flask

file = request.files['file']
file.save('/uploads/' + file.filename)

Saving files directly without validation or streaming can block the server and delay response.

📉 Performance Costblocks server response during save, increasing LCP by 200-500ms for large files

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct file.save()	N/A	N/A	Blocks response, delays paint	[X] Bad
Streaming file save in chunks	N/A	N/A	Non-blocking, faster response	[OK] Good

Rendering Pipeline

When a file is uploaded, the server must process and save it before responding. Blocking file saves delay the server response, which delays the browser's rendering of the page.

→Server Processing

→Network Response

→Browser Rendering

⚠️ BottleneckServer Processing during file save

Core Web Vital Affected

LCP

This affects page load speed and server response time during file uploads and saves.

Optimization Tips

1Avoid blocking the server thread by streaming file saves in chunks.

2Use secure filenames to prevent security risks during file saving.

3Monitor server response time to keep LCP low during uploads.

Performance Quiz - 3 Questions

What is a main performance issue when saving uploaded files directly with file.save() in Flask?

A It increases CSS selector complexity

B It causes excessive DOM reflows in the browser

C It blocks the server response until the file is fully saved

D It reduces network bandwidth

DevTools: Network

How to check: Upload a file and watch the POST request timing in the Network tab. Check the 'Waiting (TTFB)' time to see server processing delay.

What to look for: Long 'Waiting' time indicates blocking server processing during file save.

Practice

1. In Flask, which object do you use to access files uploaded by a user in a form?

easy

A. request.args

B. request.files

C. request.data

D. request.form

Solution

1. Step 1: Understand Flask request objects

   Flask provides different objects to access data sent by the client. request.files holds uploaded files.

2. Step 2: Identify correct object for files

   request.form is for form fields, request.data is raw data, and request.args is for URL query parameters.

3. Final Answer:

   request.files -> Option B

4. Quick Check:

   Uploaded files = request.files [OK]

Hint: Uploaded files are always in request.files [OK]

Common Mistakes:

• Using request.form to get files
• Trying to access files from request.args
• Confusing request.data with files

2. Which of the following is the correct way to save an uploaded file named file to a folder called uploads in Flask?

easy

A. file.save('uploads/' + file.filename)

B. file.save(file.filename)

C. save(file, 'uploads/')

D. request.save(file, 'uploads/')

Solution

1. Step 1: Use the file object's save method

   The uploaded file object has a save() method that takes the full path to save the file.

2. Step 2: Provide correct path including folder and filename

   Concatenate the folder path and the file's filename to save it in the right place.

3. Final Answer:

   file.save('uploads/' + file.filename) -> Option A

4. Quick Check:

   Use file.save(path) with full path [OK]

Hint: Use file.save('folder/' + file.filename) to save files [OK]

Common Mistakes:

• Calling save() without a path
• Using save() as a standalone function
• Not including folder path in save()

3. What will happen when this Flask code runs after a file upload?

file = request.files['photo']
file.save('/tmp/' + file.filename)
return 'Saved!'

medium

A. Nothing is saved because request.files['photo'] is empty by default

B. The file is saved but the filename is lost, causing an error

C. The code raises an error because save() needs a full absolute path

D. The uploaded file is saved in /tmp/ with its original filename and 'Saved!' is returned

Solution

1. Step 1: Access the uploaded file from request.files

   The code gets the file named 'photo' from the uploaded files correctly.

2. Step 2: Save the file to /tmp/ folder with original filename

   Calling save() with '/tmp/' + filename saves the file in that folder.

3. Final Answer:

   The uploaded file is saved in /tmp/ with its original filename and 'Saved!' is returned -> Option D

4. Quick Check:

   save() stores file at given path, returns confirmation [OK]

Hint: save() stores file at given path, returns confirmation [OK]

Common Mistakes:

• Assuming save() needs absolute path always
• Thinking request.files['photo'] is empty without upload
• Confusing save() behavior with form data saving

4. Identify the error in this Flask code snippet for saving an uploaded file:

file = request.files['file']
file.save(file.filename)

medium

A. Missing folder path in save() can cause files to save in wrong location

B. Using request.files instead of request.form causes error

C. file.save() requires a file object, not a filename string

D. file.filename is not a valid attribute of the file object

Solution

1. Step 1: Check the save() method argument

   The code saves the file using only the filename, without specifying a folder path.

2. Step 2: Understand file saving location

   Without a folder path, the file saves in the current working directory, which may be unintended or insecure.

3. Final Answer:

   Missing folder path in save() can cause files to save in wrong location -> Option A

4. Quick Check:

   Always include folder path in save() [OK]

Hint: Always include folder path in save() to control file location [OK]

Common Mistakes:

• Not specifying folder path in save()
• Confusing request.files with request.form
• Assuming file.filename is invalid

5. You want to securely save an uploaded file in Flask to the uploads folder, avoiding unsafe filenames. Which code snippet correctly achieves this?

from werkzeug.utils import secure_filename
file = request.files['file']
filename = secure_filename(file.filename)
file.save(f'uploads/{filename}')

hard

A. The code will fail because secure_filename() returns a file object, not a string

B. secure_filename() is unnecessary; file.save() cleans filenames automatically

C. This code safely saves the file with a cleaned filename in uploads folder

D. You must manually create the uploads folder before saving, or it errors

Solution

1. Step 1: Use secure_filename to clean the filename

   The function secure_filename() removes unsafe characters to prevent security issues.

2. Step 2: Save the file with the cleaned filename in the uploads folder

   Using file.save() with the cleaned filename inside the uploads folder saves the file securely.

3. Final Answer:

   This code safely saves the file with a cleaned filename in uploads folder -> Option C

4. Quick Check:

   Use secure_filename() before saving uploaded files [OK]

Hint: Use secure_filename() to avoid unsafe file names [OK]

Common Mistakes:

• Skipping secure_filename and risking unsafe filenames
• Assuming save() cleans filenames automatically
• Not creating uploads folder before saving