Can Modern Codecs Like H.264 or AV1 Be Put in a VOB?

Modern video codecs like H.264 and AV1 cannot be placed inside a traditional VOB (Video Object) container while maintaining standard compliance and playability. The VOB format is fundamentally bound to the DVD-Video specifications established in the 1990s, which strictly dictate the types of audio and video streams allowed. This article explores the architecture of the VOB container, the technical constraints preventing modern codecs from functioning within it, and the proper containers to use instead.

Understanding the VOB Container

A VOB file is a container format based on the MPEG-2 Program Stream (MPEG-PS) specification (ISO/IEC 13818-1). It was engineered specifically for DVD-Video media. In a standard DVD-Video structure, a VOB file multiplexes digital video, digital audio, subtitles, DVD menus, and navigation contents into a single stream.

Because VOB is tied directly to the physical DVD-Video format, its specifications are rigidly defined. DVD standards dictate that the primary video stream inside a VOB file must be encoded in either MPEG-2 (Part 2) or, in rare low-resolution cases, MPEG-1 (Part 2).

The Incompatibility with H.264 (AVC)

H.264, also known as AVC (Advanced Video Coding), is far more advanced than MPEG-2. While the MPEG-2 Transport Stream (MPEG-TS) format was updated over time to support H.264 for digital broadcast and Blu-ray discs, the MPEG-2 Program Stream profile used by VOB was never officially updated by the DVD Forum to include H.264.

Some non-standard software multiplexers can technically force an H.264 elementary stream into an MPEG-PS envelope, but this creates a non-compliant file. Even if renamed with a .vob extension:

• Standard DVD players and home theater systems will reject the file because their hardware decoders only look for MPEG-1 and MPEG-2 stream IDs.
• Media software expecting a legitimate VOB will encounter stream parsing errors.
• DVD authoring software will refuse to compile the assets into a playable DVD.

The Incompatibility with AV1

AV1 (AOMedia Video 1) is an open, royalty-free video coding format developed decades after the DVD standard was finalized. There is no official specification, packetization standard, or stream ID mapping for AV1 within MPEG-2 Program Streams or VOB containers.

Standard muxing tools (such as FFmpeg or MP4Box) do not provide a mechanism to pack AV1 into a VOB container. Attempting to force an AV1 stream into a VOB structure is unsupported across all standard media toolchains.

Modern Alternatives to VOB

Containers are responsible for interleaving audio and video, providing timing synchronization, and organizing metadata. Modern codecs rely on container architectures designed to support their specific compression mechanics, such as complex frame references and high-dynamic-range (HDR) metadata.

For H.264 and AV1, the industry standard containers are:

• MP4 (ISO Base Media File Format): The universal standard for web streaming, mobile devices, and consumer playback. It fully supports H.264 and AV1.
• MKV (Matroska): A flexible, open-source container that supports virtually any video and audio codec, including legacy MPEG-2, H.264, and AV1, along with complex subtitle tracks.
• WebM: A subset of Matroska specifically tailored for modern web delivery, commonly used for VP9 and AV1.

A traditional VOB container cannot be used for modern video codecs like H.264 or AV1. VOB remains a legacy format locked to MPEG-2 and DVD-Video constraints.