A 20GB archive doesn't fit in a Gmail attachment (25MB limit), on a FAT32 USB drive (4GB file limit), or in many cloud storage upload forms. Multi-volume archives split one logical archive into multiple files of a specified size that can be transferred or stored individually, then reassembled for extraction.

The concept is simple: instead of one 20GB file, you get 800 parts of 25MB each. The implementation varies significantly between formats — some handle it natively, others need external tools, and cross-platform compatibility ranges from seamless to painful.

Why Split Archives?

  • Email attachment limits: Gmail caps at 25MB. Outlook at 20MB. Corporate email often caps at 10MB. A single large archive can't be emailed, but 25MB chunks can (though multiple emails are tedious).
  • FAT32 file size limit: FAT32 file systems (still common on USB drives and SD cards) cap individual files at 4GB (4,294,967,295 bytes). A 10GB archive must be split to fit on FAT32. The alternative: format the drive as exFAT (no file size limit, compatible with Windows/macOS/Linux).
  • Upload size limits: Many file-sharing services, LMS platforms, and web forms limit upload size per file. 100MB, 500MB, 1GB, or 2GB caps are common.
  • Network resilience: Transferring one 20GB file over an unreliable connection risks a single interruption ruining the entire transfer. Transferring 100 parts of 200MB means a failure only requires re-transferring one part, not the whole archive.
  • Historical: floppy disks and CDs. Multi-volume archives originated when storage media was small — distributing software across multiple 1.44MB floppies or 650MB CDs required splitting. The use case persists even though the media has changed.

7z Multi-Volume Archives

7-Zip has clean, well-tested multi-volume support:

# Create 100MB volumes
7z a -v100m archive.7z files/
# Creates: archive.7z.001, archive.7z.002, archive.7z.003, ...

# Create 4GB volumes (FAT32 compatible)
7z a -v4g archive.7z files/

# Create 25MB volumes (email-sized)
7z a -v25m archive.7z files/

# Extract (point to the first volume)
7z x archive.7z.001
# 7-Zip finds and uses all subsequent volumes automatically

Volume sizes: b (bytes), k (kilobytes), m (megabytes), g (gigabytes). The last volume is smaller than the specified size (it contains whatever data remains).

All volumes must be present in the same directory to extract. Missing or corrupted volumes make the entire archive unextractable (there's no redundancy — every byte in every volume is required). Rename or renumber the volumes at your own risk; 7-Zip expects the sequential naming convention.

RAR Multi-Volume Archives: The Scene Standard

RAR has the most mature multi-volume support, having been the standard for split archives in file-sharing communities for decades:

# Create 50MB volumes (WinRAR GUI or rar CLI)
rar a -v50m archive.rar files/
# Creates: archive.part1.rar, archive.part2.rar, ...

# Old-style naming (RAR4)
# Creates: archive.rar, archive.r00, archive.r01, ...

# Extract (open first part)
unrar x archive.part1.rar

RAR multi-volume archives have two advantages over 7z:

  • Recovery volumes: RAR can create additional recovery volumes (rar a -v50m -rr3% -rv5 archive.rar files/). If a volume is lost or corrupted, the recovery volumes can reconstruct it — similar to RAID parity or PAR2 files. This is unique to RAR and genuinely useful for transfer over unreliable channels.
  • Lock option: RAR can "lock" multi-volume archives, preventing accidental modification of individual volumes.

The naming convention changed between RAR4 (.rar, .r00, .r01) and RAR5 (.part1.rar, .part2.rar). Both work; RAR5 naming is clearer. If you encounter .r00/.r01 files, they're RAR4 multi-volume archives from the WinRAR/scene era.

ZIP Multi-Volume Support: Limited and Fragile

ZIP technically supports split archives (APPNOTE specification calls them "split archives" and "spanned archives"), but support is inconsistent:

# Create split ZIP (zip command, macOS/Linux)
zip -r -s 100m archive.zip files/
# Creates: archive.z01, archive.z02, ..., archive.zip

# Merge into single ZIP before extracting
zip -s 0 archive.zip --out merged.zip
unzip merged.zip

Problems with split ZIP:

  • Windows' built-in handler can't open them. You need WinRAR, WinZip, or 7-Zip on Windows.
  • macOS Archive Utility can't open them. You need Keka or the command line.
  • Inconsistent naming: Some tools create .zip.001, .zip.002; others create .z01, .z02. The format is the same, but the naming confusion causes problems.
  • No recovery mechanism: Unlike RAR, ZIP has no recovery volumes. A corrupted part means an unextractable archive.

For multi-volume archives, 7z and RAR are significantly better choices than ZIP. If the recipient needs ZIP format, create a single ZIP and split it with the split command (see below).

The Unix split Command: Format-Agnostic Splitting

The split command works with any file — it doesn't know or care about archive formats. It simply cuts a file into fixed-size chunks:

# Split any file into 100MB chunks
split -b 100M large-archive.tar.gz parts-
# Creates: parts-aa, parts-ab, parts-ac, ...

# Split with numeric suffixes
split -b 100M -d large-archive.tar.gz parts-
# Creates: parts-00, parts-01, parts-02, ...

# Reassemble
cat parts-* > large-archive.tar.gz

# Or pipe directly during creation
tar czf - /data | split -b 4G - backup-part-

# Reassemble and extract in one step
cat backup-part-* | tar xzf -

Advantages: Works with any format (TAR.GZ, TAR.XZ, ZIP, 7Z, or any arbitrary file). No special archive support needed. The cat command for reassembly is available on every Unix system.

Disadvantages: No integrity checking (if a part is corrupted, cat doesn't notice). No recovery mechanism. The recipient needs to know to use cat to reassemble. On Windows, reassembly requires copy /b part1+part2+part3 archive.ext or a third-party tool.

Reassembly: Putting the Pieces Back Together

Every splitting method requires reassembly before extraction (or handles it transparently):

FormatReassembly MethodAutomatic?
7zOpen .001 file in 7-ZipYes (finds all parts)
RAROpen .part1.rar in WinRAR/7-Zip/unrarYes (finds all parts)
ZIP (split)zip -s 0 archive.zip --out merged.zipNo (manual merge step)
split commandcat parts-* > original.extNo (manual cat step)

Critical: all parts must be present. Multi-volume archives don't have redundancy (unless RAR recovery volumes are used). A missing or corrupted part makes the entire archive unextractable. Before deleting the original unsplit file, verify that all parts are intact and that you can reassemble/extract successfully.

Cross-Platform Compatibility Issues

Multi-volume archives are less portable than single-file archives:

  • Windows: 7-Zip handles multi-volume 7z and RAR seamlessly. Split ZIP files need WinRAR or 7-Zip (not Windows' built-in handler). split command output requires copy /b or PowerShell to reassemble.
  • macOS: Keka handles multi-volume 7z and RAR. Archive Utility doesn't. For split output, cat works natively in Terminal.
  • Linux: 7z, unrar, and cat all work natively. Multi-volume archives are most natural here.

If the recipient is on Windows and not technically sophisticated, the safest approach is: create a single archive, compress well (7z LZMA2 to minimize size), and use a file-sharing service (Dropbox, Google Drive, WeTransfer) instead of splitting. Multi-volume archives add complexity that non-technical users often can't navigate.

Multi-volume archives solve a real problem — large files that don't fit constraints — but add complexity that trips up non-technical recipients. Use 7z multi-volume when you control both ends. Use RAR with recovery volumes for transfer over unreliable channels. Avoid split ZIP due to poor tool support.

If the underlying issue is file size, consider better compression first: convert ZIP to 7Z for 30-70% smaller files that might not need splitting at all. Or use a file transfer service — in 2026, sending someone a link is usually better than sending multi-volume archives.