Bzip2 Compress & Decompress

Compress and decompress Bzip2 (.bz2) files entirely in your browser. Block-sorting compression using the Burrows-Wheeler Transform with instant decompression and no server uploads.

Processed locally

Was this tool helpful?

How to Use

Compress any file into Bzip2 format or decompress existing .bz2 files, entirely within your browser. No uploads, no installations, no file size limits beyond your browser's memory.

Compressing a File

Select Compress mode using the segmented control at the top. This is the default mode when the tool loads.
Drop or select your file. Any file type is accepted — text files, JSON, executables, archives, images, or any other format.
Wait for processing. A progress bar tracks compression progress. Bzip2 uses a multi-stage pipeline (BWT, move-to-front, run-length encoding, Huffman coding), so processing may take a few seconds for larger files.
Review results. The tool displays the original size, compressed size, compression ratio as a percentage, and total processing time.
Download the compressed file. Click the download button to save the .bz2 file. The output filename is your original filename with .bz2 appended.

Decompressing a File

Select Decompress mode using the segmented control — or simply drop a .bz2 file while in Compress mode. The tool auto-detects Bzip2 format by inspecting the "BZh" magic bytes and switches to Decompress automatically.
Drop or select the Bzip2 file. While .bz2 is the standard extension, the tool validates by header structure rather than file extension.
Review results. The tool displays the compressed size, decompressed size, compression ratio, and processing time.
Download the decompressed file. The output filename defaults to the original name with the .bz2 extension stripped. If the input filename does not end in .bz2, a .decompressed suffix is added.

About This Tool

The Bzip2 Algorithm

Bzip2 was created by Julian Seward in 1996 as a high-compression alternative to GZIP. It uses a multi-stage compression pipeline: run-length encoding to collapse repeated bytes, the Burrows-Wheeler Transform (BWT) to reorganize data into compressible clusters, move-to-front encoding to convert symbol frequencies into small integers, and finally Huffman coding for entropy compression. This layered approach consistently produces files 10-20% smaller than GZIP on text-heavy data, though at the cost of higher CPU and memory usage.

The Burrows-Wheeler Transform

The Burrows-Wheeler Transform is the core innovation that makes Bzip2 effective. Invented by Michael Burrows and David Wheeler in 1994, the BWT creates all cyclic rotations of the input block, sorts them lexicographically, and outputs the last column. This rearrangement groups identical characters together — for example, in English text, the letter 't' frequently follows the same context patterns, so many 't' characters end up adjacent in the transformed output. This clustering transforms random-looking input into long runs of repeated characters, which subsequent stages compress efficiently. The transform is fully reversible, requiring only the transformed data and the position of the original string in the sorted rotation list.

Bzip2 vs GZIP (DEFLATE)

GZIP uses the DEFLATE algorithm, which combines LZ77 sliding-window compression with Huffman coding. DEFLATE works on a byte-by-byte basis with a 32 KB window, finding and replacing repeated sequences. Bzip2 takes a fundamentally different approach: it processes data in large blocks (up to 900 KB), applies the BWT to reorganize the entire block, and then compresses the transformed output. The block-level BWT captures long-range patterns that DEFLATE's 32 KB window cannot detect. This is why Bzip2 achieves better compression on text, source code, and structured data. However, GZIP is 2-6x faster for both compression and decompression, and uses less memory. For HTTP content encoding and real-time compression, GZIP remains the practical choice.

Bzip2 File Format

Every Bzip2 file begins with a 4-byte header: the magic bytes BZh (0x42, 0x5A, 0x68) followed by a digit '1' through '9' that indicates the block size in units of 100,000 bytes. For example, BZh9 means a 900 KB block size (the default and maximum). The file then contains one or more compressed blocks, each starting with a 6-byte block magic number (0x31, 0x41, 0x59, 0x26, 0x53, 0x59) and ending with a 32-bit CRC checksum. Unlike GZIP, Bzip2 does not store the original filename or timestamps in the compressed stream — the .tar.bz2 container format provides those features.

Compression Pipeline Stages

Bzip2 applies five stages in sequence for each block: (1) Run-Length Encoding (RLE) collapses sequences of 4-255 identical bytes into a 4-byte sequence plus a repeat count. (2) Burrows-Wheeler Transform reorganizes the RLE output to cluster similar bytes. (3) Move-to-Front (MTF) Transform replaces each byte with its position in a recently-used list, converting clustered data into sequences dominated by small integers (0, 1, 2). (4) Zero-Run-Length Encoding compresses the long runs of zeros produced by MTF using two special symbols (RUNA and RUNB) in a binary representation. (5) Huffman Coding assigns shorter bit sequences to more frequent symbols. This five-stage pipeline is why Bzip2 achieves strong compression on structured data — each stage makes the data more regular for the next stage to exploit.

Why Use This Tool

When to Use Bzip2 Compression

Bzip2 is a strong choice when compression ratio matters more than speed. Here are the most common use cases:

Linux source distribution — The Linux kernel and many open-source projects historically distributed source tarballs as .tar.bz2 files. While .tar.xz has become more common, thousands of packages still use Bzip2.
Bioinformatics and genomics — Genomic sequence data (FASTA, FASTQ) contains highly repetitive patterns that the BWT exploits exceptionally well. Many sequencing pipelines produce and consume Bzip2-compressed data natively.
Log archival — Server logs are text-heavy with repeating patterns (timestamps, IP addresses, status codes). Bzip2 compresses a 1 GB log file to 30-60 MB, compared to 80-120 MB with GZIP.
Database dumps — SQL exports, CSV dumps, and JSON Lines files contain repetitive column names and value patterns that compress 75-90% with Bzip2.
Bandwidth-constrained transfers — When uploading over slow connections, the extra compression time pays for itself in reduced transfer time. A file that takes 5 seconds to compress with Bzip2 but saves 20 seconds of upload time is a net win.

Bzip2 vs Other Compression Formats

vs GZIP — Bzip2 compresses 10-20% smaller but is 2-6x slower. GZIP is the standard for HTTP content encoding and quick compression tasks.
vs LZMA — LZMA typically compresses 10-30% smaller than Bzip2 with faster decompression, but uses much more memory. LZMA is the engine behind 7-Zip and XZ.
vs Zstandard (zstd) — Zstandard matches or exceeds Bzip2 compression ratios at GZIP-like speeds. It is the modern replacement for both GZIP and Bzip2 in most new projects.
vs XZ — XZ uses LZMA2 compression and achieves better ratios than Bzip2. Most Linux distributions now prefer .tar.xz over .tar.bz2 for package distribution.

Privacy

Your files never leave your browser. The Bzip2 algorithm runs entirely in JavaScript within your browser tab — no data is sent to any server, no temporary files are created on remote infrastructure, and no third-party services are contacted. This makes the tool safe for compressing sensitive documents, configuration files with credentials, proprietary source code, or any data that must remain private.

Related Tools

Explore other compression and file tools on DevToolkit: GZIP Compress & Decompress for faster compression with native browser APIs, LZMA Compress & Decompress for maximum compression ratios, TAR Archive & Extract for creating .tar.bz2 archives, Hex Dump Viewer for inspecting binary file contents, and File Checksum for verifying file integrity.

FAQ

How does Bzip2 compare to GZIP compression?

Bzip2 typically achieves 10-20% better compression ratios than GZIP, particularly on text-heavy data. The tradeoff is speed: Bzip2 compression and decompression are both slower than GZIP because the Burrows-Wheeler Transform and move-to-front encoding add computational overhead. Bzip2 also uses more memory — approximately 4-8x the block size during compression.

What is the Burrows-Wheeler Transform used in Bzip2?

The Burrows-Wheeler Transform (BWT) is a reversible text transformation that rearranges characters to group identical bytes together. It sorts all rotations of the input block lexicographically and outputs the last column. This clustering makes subsequent entropy coding (Huffman coding in Bzip2) dramatically more efficient. The BWT itself does not compress data — it reorganizes it to be more compressible.

What block size does Bzip2 use?

Bzip2 processes data in blocks of 100,000 to 900,000 bytes (100KB to 900KB), controlled by the compression level (1-9). This tool uses the default block size. Larger blocks generally produce better compression but require more memory during both compression and decompression.

What file types compress well with Bzip2?

Text files, source code, log files, JSON, XML, CSV, and database dumps compress by 70-90% with Bzip2. Binary executables compress by 30-50%. Already-compressed files like JPEG, PNG, MP4, and ZIP archives see little to no reduction and may grow slightly due to header overhead.

Are my files safe? Does anything get uploaded?

All compression and decompression runs entirely in your browser using JavaScript. No files are uploaded to any server, no network requests are made during processing, and no data leaves your device. The tool is safe for sensitive documents, credentials, and proprietary data.