bagit · shipping · also BagIt 1.0, BagIt package

BagIt

BagIt is a directory-based packaging format that combines payload files, checksum manifests and metadata tags for storing and transferring digital content.

BagIt 1.0 requires bagit.txt, a data directory and at least one payload manifest; each payload manifest must list every payload file exactly once. [1]

A complete bag has all required elements and referenced files, with its elements conforming to the format. Validity additionally requires every checksum in every payload and tag manifest to verify. Payload-Oxum counts bytes and files, not content identity. [1]

Optional fetch.txt describes remote payload to retrieve before checking completeness, not remote tag files. Optional tag manifests must cover all payload manifests and should cover other tags, but cannot list tag manifests. [1]

Relations

related
Backup manifest, Checksum, Restore test, Oxford Common File Layout

Advantages

  • Payload files remain directly accessible through ordinary filesystem tools. [1]

Limitations

  • An attacker able to replace both files and manifests can create a different valid bag; authentication needs additional protection. [1]

Citations

  1. RFC 8493: BagIt 1.0, structure, complete/valid bags and security (accessed 2026-11-21)
  2. Hesela: BagIt per-manifest coverage and controlled validation outcomes (accessed 2026-11-21)
Sources & caveats
  • Format summary of RFC 8493 sections 1-3 and 5.4; this informational RFC is not an Internet Standards Track specification. [1]
  • Existing software observations are version-specific and separate from the format rules; no new validator experiment was performed for this entry. [2]

JSON: /data/terms/bagit.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. BagIt. Hesela. 2026-11-21. https://hesela.dev/terms/bagit/