Why Are VOB Files Split at 1 GB? FAT32 Explained

When examining the structure of a standard DVD-Video disc, video content is consistently broken into sequential VOB (Video Object) files that never exceed 1 gigabyte (GiB) in size. This article explores how the legacy FAT32 file system, historical 32-bit computing limitations, and hardware constraints of the mid-1990s directly influenced the DVD Forum's decision to mandate this strict 1 GB file-splitting rule.

The 1 GB DVD-Video Specification

In the official DVD-Video specification established by the DVD Forum in 1995, video data is stored in the VIDEO_TS directory as .VOB files. Even if a feature-length film is 4 GB to 8 GB in total size, the specification mandates that no individual VOB file may exceed 1,073,741,824 bytes (exactly 1 GiB). Players use navigation files (.IFO) to read these segments sequentially, creating seamless playback without pauses or buffer drops.

The FAT32 and Operating System Landscape of the 1990s

To understand the 1 GB rule, it is necessary to consider the state of computing when the DVD format was finalized between 1995 and 1996:

• The Emergence of FAT32: Microsoft introduced FAT32 with Windows 95 OSR2 in 1996. While FAT32 supported partition sizes up to 2 terabytes, it imposed a hard individual file size limit of 4 GB (specifically 4,294,967,295 bytes).
• The Ubiquity of FAT16: At the time DVDs were designed, millions of consumer personal computers were still running MS-DOS, Windows 3.1, or original Windows 95 using the FAT16 file system. FAT16 had a maximum file size limit of 2 GB.
• The 2 GB Signed Integer Barrier: Most standard C runtime libraries and 32-bit operating systems of that era used signed 32-bit integers to calculate file offsets (the off_t data type). Because the 32nd bit represented the positive/negative sign, any file offset exceeding 2,147,483,647 bytes (2 GB) resulted in integer overflow errors, crashing media players or freezing read operations.

Why 1 GB Instead of 2 GB or 4 GB?

Although FAT32 theoretically allowed up to 4 GB, DVD designers opted for a conservative 1 GB threshold for several critical reasons:

1. Ensuring Universal Cross-Platform Compatibility: DVDs were designed not only for dedicated set-top players but also for DVD-ROM drives on personal computers. To ensure that DVD media could be mounted and read natively on systems formatted with FAT16, early FAT32, Mac OS (HFS), and various UNIX platforms without triggering integer overflows, a 1 GB limit provided a safe buffer well below the 2 GB danger zone.
2. The UDF/ISO 9660 Bridge: DVDs utilize the Universal Disk Format (specifically UDF 1.02) arranged in a "UDF Bridge" format that includes ISO 9660 compatibility. Early implementations of ISO 9660 Level 1 limited file sizes to 2 GB or 4 GB depending on implementation quirks. Setting the operational target to 1 GB prevented read incompatibilities across hybrid disc readers.
3. Hardware Memory and Buffer Management: Dedicated DVD players in the late 1990s relied on inexpensive, embedded 32-bit processors with limited onboard RAM. Working with smaller 1 GB boundaries made it simpler and faster for low-cost firmware to index sector locations, handle error recovery, perform seamless branching for multi-angle scenes, and manage cache buffers during seek operations.

By establishing a hard 1 GB ceiling for VOB files, the architects of the DVD format avoided the architectural boundaries of FAT16 and FAT32, guaranteed stability across 32-bit operating systems, and ensured that standalone hardware could reliably process high-bitrate video streams.