Extract TB2

How to Extract a TB2 Archive Online

1. Upload Your TB2 File: Click "+ Add Files" or drag a .tb2 archive onto the page. You can also pull files from Google Drive or Dropbox. Multiple archives can be queued at once.
2. Click Extract: XConvert decompresses the bzip2 layer (Burrows-Wheeler transform plus Huffman coding) and unpacks the inner tar archive — the same two-stage operation tar -xjf archive.tb2 performs on Linux, but in your browser session.
3. Browse the File Tree (Optional): Once extraction finishes, the archive's directory structure is listed. POSIX file modes, ownership (UID/GID), modification times, and symbolic links recorded in the tar header are exposed where the browser permits.
4. Download Individually or as ZIP: Pick single files from the tree, or download all extracted contents repackaged as a ZIP — convenient on Windows, which doesn't natively open .tb2 from Explorer.

Why Extract TB2 Files?

The .tb2 extension is a three-letter shorthand for a .tar.bz2 archive — a tar bundle compressed with bzip2. The compact name dates back to DOS and FAT16 filesystems, which couldn't reliably handle two dots in a filename and capped extensions at three characters. The format itself is identical to .tar.bz2, .tbz2, and .tz2: any tool that opens one will open the others if it inspects file magic instead of relying on the extension. bzip2, originally released by Julian Seward in 1996 and frozen at the stable 1.0.8 release on July 13, 2019, typically produces archives 10–15% smaller than gzip on text-heavy payloads.

• Opening legacy mirrors and DOS-era downloads — .tb2 shows up most often on older FreeBSD ports trees, archive databases that predate long filename support, and CD-ROM distributions from the late 1990s. The byte stream is the same as a modern .tar.bz2.
• Working on Windows without 7-Zip or WSL — Windows Explorer doesn't open .tb2 natively. A browser-based extractor avoids installing third-party software on a locked-down work laptop.
• Inspecting a single file from a multi-megabyte archive — pulling one config file out of a source tarball is faster in a tree view than re-running tar tjf | grep followed by tar xjf --strip-components.
• Recovering files on a Chromebook — most managed Chromebook images don't include the Linux container, so command-line tar isn't available. The browser path needs no install.
• Repackaging into a more current container — once extracted, you can repack the contents as .zip for cross-platform sharing or as .tar.xz, which usually beats bzip2's ratio by another 10–20% on the same input. See Convert TB2 to ZIP or use Extract TAR.BZ2 for the longer-form extension.

TB2 vs Related bzip2-Tar Extensions

The same byte format ships under several extensions because early DOS, FAT16, and some legacy Unix filesystems forbade two dots in a filename. They are interchangeable:

Note the auto-detect column: the GNU tar manual lists .bz2, .tz2, .tbz, and .tbz2 as bzip2 triggers for the -a flag — .tb2 is not in that list, even though Wolfram Language, libarchive, 7-Zip, and most cross-platform tools recognize it. On Linux, extracting a .tb2 is most reliable with explicit flags: tar -xjf archive.tb2.

TB2 vs TAR.GZ vs TAR.XZ

Frequently Asked Questions

What does the .tb2 extension mean?

.tb2 is a three-letter shorthand for a .tar.bz2 archive — a tar bundle compressed with bzip2. The byte format is identical to .tar.bz2, .tbz2, and .tz2; only the filename convention differs. The shorter form exists because DOS, FAT16, and some legacy Unix filesystems either forbade two dots in a filename or capped extensions at three characters.

Is .tb2 the same as .tar.bz2 and .tbz2?

Yes — same byte format, different filename conventions. Any tool that reads file magic (the first few bytes) instead of trusting the extension will open all four interchangeably. The GNU tar manual specifically lists .bz2, .tz2, .tbz, and .tbz2 for the auto-compress (-a) flag; .tb2 isn't in that list, but tar will still extract one with explicit flags (tar -xjf) or via --bzip2.

Why do I sometimes see .tb2 instead of .tar.bz2?

The .tb2 form is most common on legacy mirrors, FreeBSD ports trees from the early 2000s, and CD-ROM software from the DOS era. Modern Linux distributions and source projects almost always publish .tar.bz2 (or, more commonly today, .tar.xz and .tar.zst). If you've downloaded a .tb2, the source is usually older or originated on a system with strict filename rules.

Do I need Linux or 7-Zip to extract a .tb2 file?

No. Extraction runs in your browser session — no install, no command line. On Linux or macOS, the equivalent command is tar -xjf archive.tb2 (modern GNU tar can also auto-detect with tar -xf archive.tb2). On Windows, third-party tools like 7-Zip, WinRAR, and PeaZip open .tb2 correctly, but the browser path skips the install entirely.

How is the contents of a .tb2 different from a .zip?

A .tb2 is a streamed two-layer format: tar concatenates files with their POSIX metadata (mode, owner, mtime, symlinks) into one stream, then bzip2 compresses the whole stream as a unit. ZIP, by contrast, compresses each file individually and stores a central directory at the end. Two practical consequences: you can list a ZIP without decompressing, but you cannot list a .tb2 without first decompressing the whole bzip2 stream; and .tb2 preserves Unix file permissions and symlinks that ZIP does not.

Can I extract just one file from inside a large .tb2?

After extraction, the directory tree is shown and you can download individual files without grabbing everything. Note that the bzip2 stream itself isn't seekable — the whole archive must be decompressed once internally before per-file selection becomes possible. This is a limitation of the bzip2 format, not the tool. ZIP and 7z are random-access; .tb2 is not.

Are file permissions and symlinks preserved?

The tar header records POSIX file modes (rwx bits), ownership (UID/GID), modification times, and symbolic links. XConvert reads those fields and exposes timestamps in the file listing. Browsers can't apply Unix permissions or recreate symlinks during a download, so if you need exact permissions and links restored, finish extraction on a Linux or macOS system with tar -xjf so the kernel can apply the metadata.

Why use bzip2 instead of gzip or xz?

bzip2 sits between gzip and xz in compression ratio: typically 10–15% smaller than gzip on source code and text, but 10–20% larger than xz on the same content. It uses the Burrows-Wheeler transform plus Huffman coding rather than gzip's DEFLATE. The Linux kernel switched its tarballs from .tar.bz2 to .tar.xz at the end of 2013 because xz produces smaller archives, and Arch Linux packages migrated from .pkg.tar.xz to .pkg.tar.zst in 2020 for faster decompression. The bzip2 format itself isn't deprecated — it's still maintained at version 1.0.8 — but newer projects pick xz or zstd by default.

Is there a file-size limit?

Decompression runs in the browser, so the practical ceiling is your device's available memory plus a working buffer for the tar stream. A 1 GB .tb2 expanding to 4–5 GB on disk works fine on a desktop with 8+ GB RAM but may stall on a low-end mobile device. For very large archives — kernel sources, full distro snapshots — a desktop browser is a better fit than mobile, and command-line tar is faster still.

What if my file is just .bz2 with no tar layer?

That's a single bzip2-compressed file rather than an archive (e.g. database.sql.bz2, access.log.bz2). The format wraps one file rather than a tar bundle. If your .tb2 is actually a misnamed plain .bz2, the extractor outputs the single decompressed file directly. For a tar archive without compression, see Extract TAR; for the gzip-compressed sibling, Extract TAR.GZ.