Dropbox system design: metadata and immutable file blocks
Dropbox's public engineering posts describe separating file metadata from immutable content blocks, syncing changes with per-namespace cursors, and reclaiming deleted data through garbage collection and compaction.
The idea
Dropbox has published several useful accounts of cloud-file engineering: an older sync protocol that uses a per-namespace journal and content-hashed blocks; a later block-transfer protocol that validates bytes end to end; and more recent work on reclaiming space in an immutable blob store.
Read them as case studies in different layers of the problem, not one timeless architecture diagram. The posts span a decade, focus on specific subsystems, and omit details. The file-sync investigation uses those mechanisms to motivate a generic interview design; its workload, permission contract and architecture are explicit practice assumptions, not a description of Dropbox or Google Drive's private systems.
Read the originals
Written by the engineers who built it.
- Improving storage efficiency in Magic Pocket, our immutable blob store
Facundo Agriel · Post, Apr 2026
A recent operational account explains why immutable blocks make deletes asynchronous, and how reachability-based collection and compaction reclaim unused storage.
- Broccoli: Syncing faster by syncing less
Rishabh Jain and Daniel Reiter Horn · Post, Aug 2020
A published block-transfer protocol shows hash verification, bounded blocks and the cost of compression on real clients; its reported measurements belong to that Dropbox rollout.
- Inside the Magic Pocket
James Cowling · Post, May 2016
Dropbox's overview separates file content from metadata and describes immutable encrypted blocks, durability, replication and access patterns in its own storage system.
- Streaming File Synchronization
Nipunn Koorapati · Post, Jul 2014
A detailed account of namespace-relative paths, content-hashed blocks, the file journal, per-device sync cursors, and why notifications only wake clients to fetch durable changes.
Is this an actual Dropbox interview question?
No. This case study explains published engineering work; it does not claim that Dropbox asks this exact system in interviews. Use the source and linked exercise to practise the design decisions, constraints, and failure cases that transfer to unfamiliar interview prompts.
Practise it
Make the decisions yourself, then compare.