What is an MPO File?
A Multi-Picture Object file stores multiple JPEG images in one container. The images commonly represent separate views of a stereoscopic photograph, though the container can hold other related pictures.
How MPO Files work
An MPO packages a sequence of JPEG-coded images and links them with metadata that describes their order and relationship. The first image is commonly readable as an ordinary JPEG, which explains why unaware viewers can display a plausible picture while ignoring additional views. Stereo captures typically pair left- and right-eye images, but bursts or other associated images can use the same structure. Import workflows must enumerate the embedded images and preserve their pairing metadata before editing or conversion.
Key facts
- 1MPO files are defined by CIPA DC-007, the Multi-Picture Format standard, which uses JPEG application metadata to index the offsets and sizes of the contained images.
- 2A JPEG-only decoder may stop after the first codestream without reporting that more images follow, creating silent data loss during naive conversion.
- 3Extracted views can have distinct metadata or orientation requirements, so treating every embedded JPEG as an interchangeable duplicate is unsafe.
When MPO Files matter
Detect MPO structure when importing photographs from 3D cameras or devices that capture linked views. Generic JPEG software may expose only the first image, so extract each frame when all views are required.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically MPO Files.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just MPO Files.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.