How should I use the TBZ2 manifest endpoint?

Fetch manifest JSON to pin fixture names, sizes, hashes, and MIME expectations in automated tests.

Why does this format have a category-specific hub?

A category-specific hub keeps assumptions aligned with practical workflows and related format alternatives.

Format reference

TBZ2 Format Hub

TAR.BZ2 (.tbz2) combines TAR with BZip2 compression for alternative archival workflows. Use sample .tbz2 files to validate compression levels, sparse file support, and error resilience.

Open Sample Page Open Manifest JSON

4 Files

202 Downloads (30d)

application/x-tar

Related Formats in Archive

Keep adjacent formats visible.

ZIP (67) ZST (8) 7Z (4) BZ2 (4) GZ (4) RAR (4) TAR (4) TAR.XZ (4)

Format Strategy Links

Keep strategy links secondary but close.

Open TBZ2 FAQ

Implementation Notes

Keep implementation notes explicit.

Use the manifest endpoint for deterministic fixture selection in CI, then validate MIME/type detection against actual parser output.

If this format appears in multiple categories, prefer category-specific hub pages to keep test assumptions aligned with real usage.