Extract TAR

How to Extract a TAR Archive Online

1. Upload Your TAR File: Drag and drop a .tar archive onto the upload area or click "+ Add Files" to pick from your computer, Google Drive, or Dropbox. Multiple tarballs can be queued in one batch.
2. Confirm the Extension: The page is fixed to the .tar (uncompressed) container. If your file ends in .tar.gz, .tar.bz2, or .tar.xz, switch to the matching extractor — uncompressed .tar has no gzip/bzip2/xz layer, so feeding a compressed tarball here will fail header validation.
3. Extract: Click "Extract". The job parses the archive's 512-byte header blocks, walks every file entry, and rebuilds the directory tree. There is no "Advanced Options" panel for plain TAR — extraction is deterministic; either the archive is well-formed or it is not.
4. Download Your Files: Browse the listing and download files individually, or grab everything as a single bundle. Output preserves the original folder hierarchy and filenames recorded in the tarball.

Why Extract TAR Files Online?

TAR (Tape Archive) was introduced in Seventh Edition Unix in January 1979, originally as a tape-streaming tool — files were written sequentially to magnetic tape with no central index. Forty-six years later that same on-disk layout is still how Linux distros, scientific datasets, and source releases ship. Plain .tar is an archive, not a compressor: it bundles files but does not shrink them. Compression is layered on top by gzip, bzip2, or xz — which is why you so often see .tar.gz and friends.

Why open one in a browser instead of tar -xvf?

• No Linux/macOS shell handy — Windows 10+ ships a tar.exe, but ChromeOS, locked-down corporate desktops, and most mobile browsers have nothing that opens .tar natively. A browser tool fills that gap.
• Pulling a single file out of a giant archive — kernel sources, dataset dumps, and Docker image layers are routinely hundreds of MB. If you only need one config file, listing the contents and grabbing one entry beats a full-disk extract.
• Verifying what's inside before trusting it — .tar archives downloaded from random sources can carry path-traversal entries (../etc/passwd) or symlink tricks. Listing and selectively extracting in a browser sandbox is safer than feeding it to tar with elevated privileges.
• Recovering files from Linux backups on a non-Linux machine — rsnapshot, duplicity, and many homegrown backup scripts produce .tar files; you may need them years later from a Mac or Windows box.
• Inspecting source releases and academic datasets — projects on GNU Savannah, kernel.org, and CRAN distribute .tar (or .tar.gz) tarballs because of TAR's faithful preservation of POSIX permissions, ownership, and timestamps.

TAR Archive Family — When to Use Which

If your file is .tar.gz use the tar.gz extractor. For .tar.bz2 see extract tar.bz2. For .tar.xz see extract tar.xz.

TAR vs ZIP — Two Different Philosophies

If you need to convert between them, see TAR to ZIP or ZIP to TAR.

Frequently Asked Questions

What is a .tar file and how is it different from .tar.gz?

A .tar is a plain bundle — multiple files concatenated with 512-byte header blocks recording each entry's name, mode, owner, group, size, and modification time. It does not shrink the data at all. A .tar.gz is the same .tar stream piped through gzip; the .tar.bz2 and .tar.xz variants apply bzip2 and xz instead. The two-stage design (archive then compress) is why Unix splits the work between tar and a separate compressor.

Do I need Linux or the command line to open a TAR archive?

No. Modern Windows 10/11 ships a built-in tar.exe (PowerShell) and macOS has tar in Terminal, but ChromeOS, iOS, Android, and many locked-down corporate machines do not. This extractor runs entirely in the browser, so it works on any device with no install — useful for opening a Linux backup or source tarball on a Chromebook or work laptop where you can't install 7-Zip.

Will my Unix file permissions, owner, and timestamps survive a browser extraction?

The TAR header itself preserves mode bits, numeric uid/gid, and modification time exactly. However, the browser download API on Windows and macOS strips POSIX mode bits — files come out with whatever permissions the OS assigns to a normal download. Original timestamps and folder structure are kept; if you need exact ownership and chmod bits, extract on Linux/macOS via the shell.

Can I list the contents without extracting everything?

Yes — after upload, the tool reads the header chain and shows every file in the archive. You can download individual files instead of the whole tarball. This is roughly equivalent to tar -tvf archive.tar on the command line.

What's the maximum filename length and file size for .tar?

It depends on the variant. The original (pre-POSIX) TAR header limited paths to 100 characters and per-file size to 8 GB. The USTAR format (POSIX.1-1988) extended that to 255 characters using a separate prefix field. The PAX format (POSIX.1-2001) lifts both limits — unlimited path length, unlimited file size, and full UTF-8 support via extended header records. Most modern .tar archives produced by GNU tar or bsdtar use ustar with PAX extensions when needed.

Why is my .tar archive the same size as the files inside it?

Because TAR doesn't compress — it concatenates. Each file is rounded up to a 512-byte boundary, plus one 512-byte header block per entry, plus two zero-filled blocks at the end of the archive. A .tar is roughly the same size as the originals plus a small per-file header overhead. To shrink it, run gzip/bzip2/xz on top, which is exactly what .tar.gz does.

Can a .tar file be password-protected or encrypted?

Plain TAR has no built-in encryption — the format predates the concept of archive passwords. Tarballs are usually encrypted by piping through GPG (tar cf - dir | gpg -c > dir.tar.gpg) or by using age, openssl enc, or a filesystem-level tool. If your file is .tar.gpg or .tar.enc, decrypt it first; this extractor handles only standard TAR (and via sibling pages, gzip/bzip2/xz compressed TAR).

Is it safe to extract a TAR archive from an untrusted source?

The TAR format itself is benign data, but archives can include path-traversal entries (../../etc/passwd) or absolute-path entries that could overwrite system files when extracted with a naive tool running as root. A browser extractor is sandboxed and writes only to your Downloads folder, which is one reason to inspect unknown tarballs here before unpacking them on a server. GNU tar 1.32+ and bsdtar reject path-traversal by default; older tools may not.

How does TAR compare to 7z, RAR, or modern archive formats?

TAR's job is faithful Unix-metadata preservation; it leaves compression to a separate stage. 7z and RAR bundle archiving and compression together, store an index for random access, and support per-file encryption — features TAR lacks. The trade-off: TAR streams perfectly (you can append to it or pipe it over a network without seeking), and it's the only format with five decades of Unix-tool support. For Linux distribution and source code, TAR (usually .tar.xz) remains the default. For Windows-centric workflows, see extract ZIP, extract 7z, or extract RAR.