Why VOB Files Are Inefficient for HTTP Streaming

Streaming video over the internet requires container formats and codecs engineered for low latency, efficient compression, and flexible network delivery. Standalone VOB (Video Object) files, originally created as the core container for DVD-Video discs, are fundamentally unsuited for HTTP networks. Their inefficiency stems from an outdated underlying architecture, poor compression ratios, lack of fast-seeking metadata, and zero native support within modern web environments.

Designed for Physical Media, Not Networks

VOB files are based on the MPEG-2 Program Stream format, which was engineered in the 1990s specifically for local optical storage playback. In a standard DVD, a VOB file does not act alone; it relies on accompanying IFO (information) and BUP (backup) files to provide navigation, chapter points, and timing maps. When isolated as a standalone file, a VOB loses this critical structural map, leaving it as a raw, interleaved stream that network protocols cannot efficiently parse or navigate.

Inefficient Compression and High Bandwidth Usage

VOB files primarily encapsulate MPEG-2 video along with AC-3 or uncompressed PCM audio. Compared to modern web standards like H.264 (AVC), H.265 (HEVC), or AV1, MPEG-2 is highly inefficient:

• Excessive File Sizes: Achieving acceptable standard-definition (480p or 576p) quality requires bitrates between 4 to 8 Mbps. Modern codecs can deliver high-definition (1080p) video at a fraction of that bandwidth.
• High Network Overhead: Delivering large MPEG-2 payloads over HTTP strains network capacity, dramatically increases bandwidth costs, and leads to frequent buffering for end users on slower connections.

Inability to Handle HTTP Byte-Range Requests Efficiently

Modern web streaming relies on HTTP range requests, allowing players to instantly jump to specific timestamps without downloading the entire file. Modern web containers, such as MP4 or WebM, place structural metadata (like the MP4 moov atom) at the beginning of the file to map playback time directly to byte offsets.

Standalone VOB files lack this global indexing structure. Time stamps are embedded locally inside individual packet headers throughout the stream. As a result, an HTTP client cannot perform precise random access or fast-forwarding; it must sequentially download large segments of data just to locate the desired keyframe (I-frame), creating severe latency when seeking.

Lack of Adaptive Bitrate (ABR) Compatibility

Modern video streaming relies heavily on Adaptive Bitrate (ABR) protocols such as HLS (HTTP Live Streaming) and MPEG-DASH. These protocols dynamically adjust stream quality based on the viewer's network conditions by chopping video into short, addressable segments.

VOB files cannot be cleanly integrated into ABR delivery without being demuxed and re-encoded. Their rigid multiplexing structure does not align with modern container standards like fragmented MP4 (fMP4) or elementary stream transport formats.

Complete Lack of Native Browser Support

No modern web browser supports the direct playback of VOB containers or native decoding of MPEG-2 video via HTML5 <video> tags. To deliver a VOB file over HTTP to a user, the host server must perform real-time, on-the-fly transcoding into a supported web format like MP4 with H.264 video. This process introduces substantial processing overhead on the server, increases playback start latency, and severely limits how many concurrent viewers the infrastructure can support.