For decades, media workflows have been built around files. But files are the wrong abstraction.
I once worked with a post house where the entire production stopped because one person - I won’t name him - didn’t show up to work. He wasn’t just an employee; he was the catalog. He knew where every file was buried on the SAN, every path, every folder. Without him, nobody could find anything. That’s the absurdity of file-based workflows.
Every editor, engineer, and producer knows the frustration of managing files. A file has a path (where it lives) and a format (how it’s packaged). It sounds simple. But in practice, file-based workflows create limitations, complexity, and waste. They’re brittle, costly to scale, and poorly suited to the collaborative, global, and real-time nature of today’s production demands.
The irony? Other industries including banking, e-commerce and more, solved these same problems years ago by adopting web-based technologies. Why is media production still stuck moving files?
At their core, files are about persistence - bytes stored somewhere so they can be retrieved later. Files solve a basic need: saving and organizing data. But in today’s media workflows, files introduce two fundamental problems:
Files are static. They don’t adapt. And this rigidity creates endless workarounds (downloading, proxy generation, version tracking, archive management) that waste time, resources, and money.
The web doesn’t think in files; it thinks in resources. Every piece of content, a webpage, an image, a video, is addressed by a URL and accessed via HTTP. This model is dynamic, flexible, and scalable.
Consider how we stream video today:
These principles - dynamic access, seamless adaptability, and global scalability - are exactly what the media industry needs.
This approach also aligns closely with the MovieLabs 2030 Vision. MovieLabs envisions a future where media is ingested into the cloud, workflows are software-defined, and content is globally accessible. But achieving that vision requires us to rethink media workflows from the ground up. Files (the digital equivalent of paper) don’t scale. Web-native principles do.
Imagine production workflows working the same way:
This isn’t a hypothetical idea. The tools already exist: HTTP2 and HTTP3 allow for parallel requests and low-latency access. Cloud infrastructure, like AWS, Azure, and Google Cloud, scales infinitely.
The only thing holding media back is the legacy of file-based thinking.
Transitioning from files to web-based workflows requires a shift in thinking. But the benefits are enormous:
The media industry has already made one leap—from analog tape to digital files. But in digitizing workflows, we brought analog constraints with us. Files are the digital equivalent of folders and paper: a useful metaphor for the past, but wholly unnecessary in a cloud-native future.
By rethinking workflows with web-native principles—dynamic access, scalability, adaptability—we can remove decades of complexity and unlock the full potential of cloud-based media production.
The tools exist. The web works. The only question is:
How long will we let files hold us hostage?