TB2 to TGZ Converter

How to Convert TB2 to TGZ Online

1. Upload Your TB2 File: Drag and drop your .tb2 (or .tbz, .tbz2, .tar.bz2) archive, or click "+ Add Files" to browse. Batch uploads are supported — queue several archives in one session.
2. Pick Single Archive or Individual Archives: Default is Single Archive (merges all uploads into one .tgz). Switch to Individual Archives to produce a separate .tgz per uploaded file — useful when you want each source archive repackaged independently rather than bundled together.
3. Confirm Output Format (TGZ): TGZ is preselected. The conversion decompresses the bzip2 stream, keeps the underlying tar layout (filenames, permissions, symlinks, ownership), and re-wraps it with gzip — no rebuild of directory structure needed.
4. Convert and Download: Click Convert. The repackaged .tgz file is ready to download — no sign-up, no watermark, no email gate.

Why Convert TB2 to TGZ?

TB2 (also written .tbz, .tbz2, or .tar.bz2) is a tar archive compressed with bzip2, while TGZ (.tar.gz) is the same tar archive compressed with gzip. Bzip2 squeezes files slightly smaller, but gzip decompresses several times faster on the same hardware — and gzip is multi-decade ubiquitous across Linux, macOS, BSD, Docker base images, and CI runners. Switching from .tb2 to .tgz is almost always about extraction speed and tooling compatibility, not storage savings.

• CI/CD pipeline speedups — Build systems (GitHub Actions, GitLab CI, Jenkins) extract dependency archives on every run. Swapping .tb2 artifacts for .tgz typically cuts decompress time on the order of 3-4x on the same CPU, shaving real minutes off pipelines that unpack a few hundred MB.
• Docker layer and base-image friendliness — Most Dockerfile ADD/COPY flows and base images (Alpine, Debian, Ubuntu) ship gzip/gunzip by default; bzip2 is sometimes absent on minimal images, forcing a apt-get install bzip2 layer you can avoid by shipping TGZ.
• npm, Python sdist, Go modules — Package registries publish source tarballs as .tgz (npm) or .tar.gz (PyPI sdist). Converting .tb2 mirrors to .tgz matches the format consumers' tooling already expects.
• Cross-platform recipients — Windows users with 7-Zip or WinRAR can open both, but native macOS Finder and Windows 11's built-in tar handler (added in Build 17063, October 2017) decompress gzip more smoothly than bzip2.
• Web download pages — Content-Encoding: gzip is supported by every browser; serving a .tgz saves a round-trip vs. forcing visitors to install a bzip2 utility.
• Legacy mirror migration — Kernel.org dropped bzip2 tarballs in December 2013 in favor of gzip + xz; many distros followed. Converting older .tb2 mirrors to .tgz keeps them compatible with current package-fetcher defaults.

TB2 vs TGZ — Format Comparison

Gzip Compression Level Quick Guide

Gzip supports compression levels -1 (fastest) through -9 (smallest). Most tar tools use -6 as the default. Numbers below are typical for source-code and text-heavy payloads — your mileage varies for already-compressed binaries.

Frequently Asked Questions

Will my file permissions, symlinks, and ownership survive the conversion?

Yes. Only the outer compression layer changes — bzip2 is swapped for gzip. The inner tar stream (filenames, Unix permission bits, symlink targets, UID/GID, mtime) is preserved byte-for-byte. Extract the resulting .tgz with tar -xzf and you should see the same tree you'd get from tar -xjf on the original .tb2.

Why is the .tgz slightly larger than the original .tb2?

That's expected. Bzip2 typically compresses text and source code about 10-15% tighter than gzip because it uses a Burrows-Wheeler block-sort transform before Huffman coding, while gzip uses LZ77 with a sliding window. The tradeoff: gzip decompresses much faster, which is usually what you want for CI artifacts, Docker layers, and package distribution. If maximum compression matters more than speed, look at TB2 to TAR.XZ — xz typically beats both.

How is .tb2 different from .tbz, .tbz2, and .tar.bz2?

They're the same format with different file-name conventions. .tar.bz2 is the long form. .tbz2 is a common short form. .tbz and .tb2 are older short forms used on filesystems that historically limited extensions to three characters. All four are bzip2-compressed tar archives and our converter accepts every variant.

Can I decompress a .tgz natively on Windows, macOS, and Linux?

Yes on all three. Linux and macOS have shipped tar with built-in gzip support for decades — tar -xzf file.tgz just works. Windows 10 added native tar to the command line in Build 17063 (released October 2017) and the built-in tool handles .tgz without extra software. Older Windows versions need 7-Zip, PeaZip, or WinRAR — all free or freemium.

Should I use TGZ for CI/CD artifacts or stay on TB2?

Use TGZ in nearly every CI scenario. Gzip decompression is roughly 3-4x faster than bzip2 on the same CPU, and Docker base images (Alpine especially) often ship gzip but not bzip2. The few MB of extra archive size is almost always cheaper than the seconds you spend decompressing it on every build. For one-time release downloads where total bytes-on-the-wire dominates, TB2 (or better, TAR.XZ) still has a case.

Do I need to extract and re-archive manually, or can I do it in one step?

Our online converter does it in one step — upload your .tb2, click Convert, download the .tgz. From the command line on Linux/macOS you can pipe: bzcat archive.tb2 | gzip -c > archive.tgz. That avoids creating a temporary directory and is the fastest local approach.

What happens if I upload multiple .tb2 files at once?

You control the merge behavior in step 2. Single Archive mode concatenates the contents of all uploaded archives into one combined .tgz (handy for shipping a release bundle). Individual Archives mode produces one .tgz per input, repackaging each .tb2 independently — pick this when each source archive should stay separate. For the reverse direction see TGZ to TB2.

Is the conversion lossless? Can I round-trip back to TB2 later?

Yes. The conversion is lossless because the inner tar stream is untouched. If you ever need to go back, run TGZ to TB2 and you'll get the same files with the same metadata, just re-wrapped in bzip2. If you also want to look inside the archive without converting, our Extract TB2 tool lists and unpacks contents directly.

Why did kernel.org and other major projects move off bzip2?

Kernel.org formally dropped bzip2 tarballs on December 27, 2013, citing the speed gap and the rise of xz, which compresses tighter than bzip2 while still decompressing quickly. They kept gzip (.tar.gz) alongside xz (.tar.xz) until 2018 before going xz-only for new releases. Most other Linux distributions and open-source projects followed a similar arc — gzip remained the broad-compatibility default, xz became the high-compression default, and bzip2 was retired from the mainstream.