File validation (size, type) in FastAPI - Performance & Optimization

Performance: File validation (size, type)

MEDIUM IMPACT

This affects page load speed and interaction responsiveness by preventing large or invalid files from being processed or uploaded.

Validating uploaded files for size and type in a FastAPI endpoint

FastAPI

from fastapi import FastAPI, File, UploadFile, HTTPException

app = FastAPI()

MAX_SIZE = 5_000_000

@app.post('/upload')
async def upload_file(file: UploadFile = File(...)):
    if not file.content_type.startswith('image/'):
        raise HTTPException(status_code=400, detail='Invalid file type')
    size = 0
    async for chunk in file.file:
        size += len(chunk)
        if size > MAX_SIZE:
            raise HTTPException(status_code=400, detail='File too large')
    # reset file pointer if needed
    file.file.seek(0)
    # process file
    return {'message': 'File accepted'}

Validates file type immediately and checks size incrementally while streaming, avoiding loading entire file into memory.

📈 Performance GainReduces memory usage and prevents blocking, improving INP and server responsiveness.

Validating uploaded files for size and type in a FastAPI endpoint

FastAPI

from fastapi import FastAPI, File, UploadFile

app = FastAPI()

@app.post('/upload')
async def upload_file(file: UploadFile = File(...)):
    contents = await file.read()
    if len(contents) > 5_000_000:
        return {'error': 'File too large'}
    if not file.content_type.startswith('image/'):
        return {'error': 'Invalid file type'}
    # process file
    return {'message': 'File accepted'}

Reads the entire file into memory before validating size and type, causing high memory use and blocking responsiveness for large files.

📉 Performance CostBlocks event loop during file read, increasing INP and memory usage for large files.

Performance Comparison

Pattern	Memory Usage	Blocking Time	Responsiveness	Verdict
Read full file before validation	High (loads entire file)	Blocks event loop during read	Low (slow response for large files)	[X] Bad
Stream file and validate incrementally	Low (only chunks in memory)	Non-blocking with async iteration	High (fast rejection of invalid files)	[OK] Good

Rendering Pipeline

File validation in FastAPI happens server-side before processing or storing the file, preventing heavy operations on invalid files.

→Network Transfer

→Server Processing

→Response Time

⚠️ BottleneckServer Processing when reading large files fully before validation

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by preventing large or invalid files from being processed or uploaded.

Optimization Tips

1Validate file type immediately before reading file content.

2Stream file data and check size incrementally to avoid high memory use.

3Reject invalid or too large files early to improve server responsiveness.

Performance Quiz - 3 Questions

Why is reading the entire uploaded file into memory before validation a bad practice?

A It reduces network transfer time

B It speeds up validation by having all data at once

C It increases memory usage and blocks server responsiveness for large files

D It improves user experience by showing progress

DevTools: Network and Performance panels

How to check: Use Network panel to monitor upload size and time; use Performance panel to check server response time and event loop blocking

What to look for: Look for long blocking times or large memory spikes during file upload and validation phases