Design a profile picture upload system
FreeBackend systemEasy
- Beginner
- System design
- File storage
Quick answer
This backend system interview question asks you to design a profile picture upload system. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a system for uploading, processing, storing, and serving user profile pictures efficiently and securely.
What must a profile picture upload system do?
- Users can upload a profile picture.
- The system should validate file type, file size, and image format.
- The system should generate multiple image sizes such as thumbnail, medium, and full size.
- The system should optimize or compress uploaded images.
- The system should store original and resized image versions.
- Users can update or delete their profile picture.
- The system should serve profile pictures through stable URLs.
- The system should deliver images quickly through a CDN.
How well must it do it?
- Upload and retrieval should be reliable and low latency.
- Image processing should not block the user for too long.
- The system should handle concurrent uploads.
- Uploaded files should be protected from malicious content.
- Stored images should be durable and highly available.
- CDN caching should reduce storage reads and improve global performance.
- The system should support common formats such as JPEG, PNG, WebP, and AVIF.
What scale should you design for?
Use these numbers in your estimates.
| Assumption | Estimate daily uploads from active users and profile update frequency |
|---|---|
| Assumption | Estimate concurrent uploads during peak traffic |
| Assumption | Peak upload traffic may be 3x to 10x average traffic |
| Assumption | Estimate storage using user count x number of image versions x average image size |
| Assumption | For 1M users with 3 versions at 200KB each, storage is around 600GB |
| Assumption | Estimate bandwidth using image views x average served image size |
| Assumption | Estimate processing capacity using uploads per second x number of resize variants |
Key concepts
- Beginner
- System design
- File storage
- CDN
- Image processing
- Secure upload
How you’ll practise
6 short steps · save and come back any time
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a profile picture upload system and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Easy, so it suits engineers who are new to backend system interviews. It is also a good warm-up before harder questions.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- Yes. It is one of the free questions. Sign up to practise it step by step. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team