What is Fragmented MP4?
Fragmented MP4 divides an ISO base media file into initialization data and separately deliverable media fragments. Fragments commonly contain moof metadata followed by mdat media data.
How Fragmented MP4 works
A fragmented MP4 separates stable track initialization from a sequence of independently appended runs of timed samples. The initialization portion declares tracks and sample formats, while each fragment carries run metadata needed to locate and timestamp its adjacent media payload. This differs from a conventional finalized MP4 whose central sample tables describe the complete presentation. Fragmentation supports incremental generation, segmented distribution, and browser append workflows without waiting for a final global index.
Key facts
- 1The initialization segment normally contains a moov box with track and sample-entry information, while later moof boxes describe samples whose encoded bytes reside in associated mdat boxes.
- 2Decode-time and sample-run fields must form a continuous timeline across fragments. Incorrect base times or data offsets can produce gaps, overlap, stalled appends, or audio-video drift.
- 3For adaptive switching and random segment access, packaging commonly aligns fragment boundaries with suitable random-access video samples; arbitrary cuts may retain undecodable dependencies.
When Fragmented MP4 matters
Developers select fragmented MP4 for segment-based HLS or DASH and for playback before a complete file arrives. Fragment boundaries and timestamps must align with player and packaging requirements.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically Fragmented MP4.
- 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 Fragmented MP4.
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.