How should I use the BZ2 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

BZ2 Format Hub

BZip2 (.bz2) applies Burrows–Wheeler and Huffman compression to single files, offering high compression ratios. Use sample .bz2 files to test block-based decompression performance and integrity checks.

Open Sample Page Open Manifest JSON

4 Files

263 Downloads (30d)

application/octet-stream

Related Formats in Archive

Keep adjacent formats visible.

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

Format Strategy Links

Keep strategy links secondary but close.

Open BZ2 FAQ

Conversion Guides

How to Convert BZ2 to ZIP How to Convert ZIP to BZ2 How to Convert BZ2 to ZST How to Convert ZST to BZ2 How to Convert 7Z to BZ2 How to Convert BZ2 to 7Z

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.