DPX uncompressed 10-bit format—industry standard exchange between VFX houses, rendering farms, color suites. Platform-agnostic, high color depth.
In the compositing workflow, Digital Picture Exchange (DPX) serves as the backbone between VFX departments, post-production studios, and external services. Anyone working with effect pipelines cannot avoid this format—and for good reason: DPX transports 10-bit color information uncompressed, meaning without loss of quality across multiple generations of outputs. A compositor receives uncompressed plates from the rotoscope team, works on them, and passes the results to the finishing technician—nobody loses color depth or dynamic range in the process.
The practical relevance lies in its platform independence. A DPX sequence from Maya loads into Nuke just as easily as it does onto a Linux server in After Effects—the byte structure has been standardized since the format was established by Kodak in the 1990s. Every studio uses DPX as an exchange standard because it works, not because it's elegant. The file sizes are considerable—a 2K sequence in 10-bit can easily become several terabytes—but the investment in storage pays off when you work with it.
On set or during dailies, the camera records in DNxHD or ProRes; in the edit, the editor works with proxy material. However, as soon as VFX comes into play, it's converted to DPX. The colorist receives DPX sequences for grading work, the VFX supervisor sends plates as DPX for rendering. Sequencing is standard in this process: multiple individual frames instead of one large file, numbered sequentially (001, 002, 003...). This enables server rendering without file corruption in case of a crash—you simply restart at frame 47.
Specific pitfalls: DPX stores metadata-free, meaning timecode and other information must be managed externally. The conversion itself is computationally intensive—a good transcode server should be available. Furthermore, many software houses differentiate between DPX 1.0 and 2.0 (with additional channels for alpha or depth), which can lead to incompatibility if the sender and receiver read different versions. That's why all studios still talk about DPX—it's the safe choice.