Generated by GPT-5-mini| ISO base media file format | |
|---|---|
| Name | ISO base media file format |
| Extension | .mp4, .m4a, .3gp (derivative) |
| Owner | ISO, MPEG, IEC |
| Released | 2001 |
| Latest | (base standard maintained by ISO/IEC) |
| Genre | Container format |
ISO base media file format is a digital multimedia container standard developed to store timed media, enabling multiplexing of audio, video, and metadata within a single file. It was specified by ISO/IEC JTC 1/SC 29/WG 11 and published as an ISO/IEC standard, forming the foundation for formats adopted by organizations such as Moving Picture Experts Group, MPEG-4 Part 12, and later profiles used by 3GPP, Apple Inc., and Microsoft. The format underpins widely used containers and influenced media delivery in platforms like YouTube, iTunes, QuickTime, and Netflix.
The format originated from collaborative work between Moving Picture Experts Group and International Organization for Standardization committees to modernize and generalize the QuickTime File Format created by Apple Inc. in the early 1990s. Formalization within ISO/IEC JTC 1/SC 29 resulted in publication as MPEG-4 Part 12 in 2001, later integrated into broader suites including MPEG-4 Part 14 and referenced by 3GPP for mobile multimedia. Subsequent updates and registrations with IANA and industry groups supported adoption by vendors such as Microsoft Corporation, Nokia, Sony, and content distributors like Hulu and Amazon Prime Video.
The format defines a hierarchical, extensible box-based layout evolved from QuickTime File Format concepts used by Apple Inc. and adopted by Moving Picture Experts Group. It separates timed media tracks, metadata, and indexing into named containers enabling interoperability across ecosystems including Blu-ray Disc Association, Digital Cinema Initiatives, and Society of Motion Picture and Television Engineers. Design principles emphasize extensibility, random access through indexing, and support for streaming technologies used by DVB, ATSC, and HLS deployments. Governance and registrations have been coordinated with bodies like IETF for streaming integration and W3C when used in web media contexts.
Files are composed of nested 'boxes' (also called atoms), each identified by a type and length, a concept inherited from QuickTime File Format. Core boxes include the file type box (ftyp), movie box (moov), and media data box (mdat), which organize file-level compatibility, track-level timing, and payloads respectively. Extension and metadata boxes allow inclusion of schemas from ID3, Dublin Core, and container-specific features used by Adobe Systems, Microsoft Corporation, and Apple Inc.. The box model supports registration of new box types via registries maintained by ISO and industry groups, enabling adoption by projects such as MPEG-DASH, 3GPP, and CMAF.
The container is codec-agnostic and commonly carries codecs standardized by bodies like MPEG, ITU-T, and Joint Video Experts Team. Typical video codecs include MPEG-4 Part 10 (AVC/H.264), HEVC (H.265), and AV1 where profiles map into the container. Audio codecs frequently used include MPEG-4 Part 3 (AAC), MPEG-1 Audio Layer III (MP3) when wrapped, and Dolby Laboratories formats such as Dolby Digital Plus. Profiles and brands declared in the file type box are used by vendors including Apple Inc., Google, Microsoft Corporation, and Samsung to signal supported feature sets.
Multiple industry formats derive from the base format, including MP4, 3GP, MPEG-4 Part 14, HEIF, and CMAF, each tailored by organizations such as 3GPP, MPEG, JPEG Committee, and DASH Industry Forum. Implementations in operating systems and media frameworks—QuickTime Player, Windows Media Foundation, GStreamer, FFmpeg, and AVFoundation—ensure interoperability across devices from Apple Inc., Microsoft Corporation, Google's Android (operating system), and consumer electronics vendors like Sony and LG Electronics. Registries and compatibility statements published by ISO and MPEG guide profile conformance for broadcast standards like DVB and streaming standards such as HLS and MPEG-DASH.
The format is used across production, distribution, and consumption workflows: digital cinema workflows standardized by Digital Cinema Initiatives, streaming platforms like Netflix and YouTube, mobile telephony services standardized by 3GPP, and creative tools including Final Cut Pro and Adobe Premiere Pro. It supports packaging of subtitles and captions compatible with standards from SMPTE and metadata schemes used by broadcasters like BBC and NHK. Use cases extend to still-image containers via HEIF for Apple devices, adaptive bitrate streaming for services from Spotify (audio) and Vimeo (video), and archival applications referenced by cultural institutions such as the Library of Congress.
As a parsing-heavy, extensible format, security concerns focus on robust handling of box lengths, nested structures, and codec payloads to prevent vulnerabilities exploited in players like QuickTime Player, Windows Media Player, and third-party libraries. Vulnerabilities historically affected software from vendors including Apple Inc., Microsoft Corporation, and open-source projects like FFmpeg when malformed boxes triggered buffer overflows, integer overflows, or denial-of-service conditions. Mitigation relies on secure parsers, fuzz testing practices promoted by organizations such as CERT and OWASP, and patching by vendors including Red Hat and Canonical.
Category:Digital container formats