MPEG-4: Browser Support, Features, Known Issues

What is MPEG-4?

MPEG-4 is a family of audio, video, and container standards from the ISO/IEC Moving Picture Experts Group, published as ISO/IEC 14496. The standard has more than 30 parts. The most used in web browsers are Part 10 (H.264 video), Part 3 (AAC audio), and Part 14 (the MP4 container).

Which browsers does MPEG-4 support?

Almost every modern browser plays MPEG-4 H.264 video. Chrome, Edge, Safari, Firefox, Opera, Samsung Internet, Android Browser, and Internet Explorer 9 and later all decode it through the HTML5 video element, while Opera Mini never added support.

What are the key features of MPEG-4?

MPEG-4 bundles a video codec, an audio codec, a container, and a streaming model into one standard. The features below decide whether MPEG-4 is the right pick for a web video pipeline.

• ISO/IEC 14496 standard: MPEG-4 is the umbrella standard from ISO/IEC and the Moving Picture Experts Group, with more than 30 parts that cover video, audio, scene description, file format, and content protection.
• Part 10 (H.264 AVC) video: The most widely used MPEG-4 video codec. Every modern browser, smartphone, smart TV, and Blu-ray player can decode it, and most ship a hardware decoder for low-CPU playback.
• Part 2 visual codec: MPEG-4 Visual is the older video codec inside DivX and Xvid files. It plays on most desktop media players but does not play in any browser through the HTML5 video element.
• Part 14 MP4 container: The .mp4 file that packs H.264 video, AAC audio, subtitles, and chapter markers into one file. The same container also holds H.265, AV1, and Opus when the player supports them.
• Part 3 audio codecs: MPEG-4 Audio defines AAC-LC, HE-AAC, AAC-LD, and ALS. AAC-LC at 128 to 192 kbps is the default audio track for MP4 video on the web.
• Hardware decode support: Every Intel, AMD, Qualcomm, Apple, and Samsung GPU ships a fixed-function H.264 decoder. This is why MPEG-4 video runs at low CPU cost on every laptop and phone.
• Adaptive streaming friendly: MPEG-4 fragments fit the MPEG-DASH and HLS streaming protocols, which is why YouTube, Netflix, and Disney+ deliver MPEG-4 fragments to browser clients.
• DRM-ready through CENC: MPEG-4 Common Encryption integrates with the Encrypted Media Extensions API, which Widevine, PlayReady, and FairPlay use to lock paid video to the browser.

What are the use cases of MPEG-4?

MPEG-4 is the default video format on the web, mobile devices, and consumer electronics. The list below covers where it shows up in production.

• HTML5 video on the web: MPEG-4 H.264 + AAC is the lowest-friction way to deliver video that plays in every browser. Sites like YouTube, Vimeo, and Twitter use MPEG-4 fragments as the baseline track.
• Adaptive streaming: MPEG-DASH and HLS slice MPEG-4 video into 2 to 10 second fragments, which the browser pulls based on bandwidth. Netflix, Disney+, and Hulu all rely on MPEG-4 fragments inside DASH.
• WebRTC video calls: WebRTC requires every endpoint to support either VP8 or H.264. Most enterprise video tools, including Zoom and Microsoft Teams, pick H.264 for hardware-accelerated calls.
• Mobile video capture: iPhone, iPad, and most Android phones save camera video as MPEG-4 H.264 inside an .mp4 file by default, so user uploads come through as MPEG-4.
• Broadcast and OTT: Apple TV, Roku, Amazon Fire TV, Chromecast, and Smart TVs all decode MPEG-4 H.264 in hardware. OTT apps target it as the safe-fallback codec.
• Audio-only delivery: Apple Music, podcasts, and audiobooks ship as .m4a or .m4b files, which are MPEG-4 Part 14 containers carrying AAC or ALAC audio without a video track.

A typical MPEG-4 video element looks like the snippet below. The codecs string locks the browser to H.264 baseline plus AAC-LC, so only browsers that can decode both ever request the file:

<!-- Play an MPEG-4 H.264 file in the HTML5 video element.
     The codecs string locks the browser to H.264 baseline plus
     AAC-LC audio, so it can pick the file up only if it can decode
     both. The webm source is the fallback for older Firefox builds. -->
<video controls width="800" height="450" preload="metadata">
  <source src="trailer.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />
  <source src="trailer.webm" type="video/webm" />
  <p>Your browser cannot play MPEG-4 video.
     <a href="trailer.mp4">Download the file</a> instead.</p>
</video>

What are the known issues with MPEG-4?

MPEG-4 plays almost everywhere, but the long tail still trips up real projects. The list below covers the failures that surface in production logs and bug trackers.

• Linux Firefox needs system codecs: Firefox on Linux calls the system FFmpeg or GStreamer libraries to decode H.264. A minimal Debian or Alpine container without those packages cannot play MPEG-4 video, even on the latest Firefox build.
• MPEG-4 Part 2 does not play in browsers: DivX and Xvid files use MPEG-4 Part 2 (Visual), which Chrome, Firefox, Edge, and Safari never added. Files saved from older camcorders or P2P video need a transcode to H.264 before they play in HTML5 video.
• Patent licensing for paid streams: H.264 patents are pooled at Via LA. Free-to-viewer streaming (YouTube, Vimeo) is exempt. Subscription services and hardware sellers pay per-unit royalties, which is one reason AV1 is gaining ground.
• Profile and level mismatches: A baseline-only mobile decoder cannot play a high-profile 4K MPEG-4 file. The browser shows a black frame or throws a MEDIA_ERR_DECODE error if the codecs string in the source tag does not match the device.
• Opera Mini cannot decode video: Opera Mini renders pages on Opera's servers and ships compressed images to the device. There is no video decoder on the phone, so MPEG-4 sources fall through to a download link.
• Older Android partial support: Android 2.1 to 4.3 played MPEG-4 only when the device's chipset shipped a baseline H.264 decoder. Some early budget phones from that era can stream MPEG-4 audio but show a black video frame.
• iOS quirks around inline playback: Safari on iOS 9 and earlier always played MPEG-4 video full-screen. Inline playback needs the playsinline attribute added in iOS 10. Sites that miss the attribute see the player jump to full-screen on tap.
• AAC-HE not supported everywhere: The High-Efficiency AAC profile (HE-AAC v2) is part of MPEG-4 Audio, but Safari does not decode it inside the HTML5 audio element. AAC-LC is the safe pick for cross-browser audio tracks.
• Internet Explorer is retired: IE 9 to 11 played MPEG-4, but Microsoft has retired the browser. Anyone still on IE needs a fallback through a polyfill player or a server-side transcode to a different format.

In my experience, the most painful MPEG-4 bug shows up on Linux CI runners. A test hits a Firefox container, the container ships without ffmpeg, and the playback test fails with a silent MEDIA_ERR_SRC_NOT_SUPPORTED. The fix is small (apt install ffmpeg or libavcodec-extra), but the failure looks like a code regression until someone checks the container packages.

Citations

All MPEG-4 version numbers and platform notes in this guide come from these primary sources:

• MDN Web Docs - Web video codec guide: developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Video_codecs
• MDN Web Docs - Media container formats: developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Containers
• Wikipedia - MPEG-4: en.wikipedia.org/wiki/MPEG-4
• Wikipedia - HTML5 video: en.wikipedia.org/wiki/HTML5_video
• ISO - ISO/IEC 14496-10 (AVC) standard: iso.org/standard/83529.html
• ISO - ISO/IEC 14496-14 (MP4 file format): iso.org/standard/79110.html
• ITU-T - H.264 Recommendation: itu.int/rec/T-REC-H.264
• MPEG.org - MPEG-4 standard overview: mpeg.org/standards/MPEG-4
• WebKit - Video on the web (Safari support): webkit.org/blog/6784/new-video-policies-for-ios
• Mozilla Hacks - H.264 support in Firefox: hacks.mozilla.org/2013/06/firefox-22-is-out-asm-js-webrtc-and-more
• Microsoft Learn - HTML5 video in Internet Explorer 9: learn.microsoft.com/en-us/previous-versions/windows/internet-explorer
• Via LA - H.264/AVC patent pool: via-la.com/licensing/avc-h-264