What Is a TAR.GZ File and How to Open It
A TAR.GZ file is a compressed archive that stacks two older technologies on top of each other: TAR bundles a pile of files and folders into one continuous file, and GZIP then squeezes that bundle down to a smaller size. If your computer refuses to open one, it is almost certainly because you are on Windows, where support arrived only recently, or because your extraction tool is unpacking just one of the two layers and leaving you with a mysterious .tar file you did not ask for.
You will meet these files, often nicknamed "tarballs," constantly if you download anything from the Linux, macOS, or open-source world: source code, server software, developer tools, dataset releases, and website backups all ship this way. The same archive may appear as .tar.gz or as the shorter .tgz, which means the same thing.
This guide explains what is actually inside a TAR.GZ file, why the format works in two stages, how to open one on every platform, the double-extraction trap that confuses most Windows users, and the no-installation route when you simply want the contents without learning anything new.
Two Formats Doing Two Different Jobs
The double extension is the key to understanding everything about this format, because it is not one thing but two, applied in sequence.
TAR stands for Tape Archive, and the name gives away its age. It dates to the late 1970s, when Unix systems wrote backups onto magnetic tape, and it does exactly one job: it takes many files and folders and concatenates them into a single continuous stream, recording each file's name, size, permissions, ownership, and timestamps along the way. What TAR does not do is compress anything. A plain .tar file is roughly the same size as the sum of everything inside it.
GZIP handles the compression. Created in the early 1990s as a free replacement for an earlier patented tool, gzip takes a single file and shrinks it using the DEFLATE algorithm, the same general technique underpinning ZIP. Gzip compresses one file at a time and has no concept of folders or multiple files.
Put them together, and the logic becomes obvious. TAR turns your hundred files into one file; gzip then compresses that one file. The result is archive.tar.gz, a single compressed container holding everything.
This design reflects the Unix philosophy that each tool should do one job well and combine cleanly with others. It also explains why you occasionally encounter cousins of the format such as .tar.bz2 or .tar.xz: the TAR layer is unchanged, and only the compression tool has been swapped for one that squeezes harder at the cost of speed.
Why This Beats ZIP in Some Ways and Loses in Others
The two-stage approach produces a genuine technical difference from ZIP, and it cuts both ways.
ZIP compresses each file individually and then stores the compressed pieces together in a container. TAR.GZ does the opposite: it joins everything first, then compresses the whole stream as a single unit. This is called solid compression, and it matters because compression works by spotting repetition. When a hundred similar source-code files are compressed as one continuous stream, the algorithm notices patterns repeating across file boundaries and exploits them. When each file is compressed in isolation, as in ZIP, those cross-file patterns are invisible.
The practical upshot is that a TAR.GZ archive of many small, similar files is often noticeably smaller than the equivalent ZIP, which is a real advantage when distributing source code.
The trade-off is random access. Because the archive is one continuous compressed stream, you cannot pull out a single file from the middle without decompressing everything ahead of it. ZIP, with its individually compressed entries and central index, lets you extract one file instantly from a huge archive. This is exactly why ZIP won on desktop operating systems, where people browse into archives casually, while TAR.GZ dominates in software distribution, where you almost always want the entire contents anyway.
There is one more reason the Unix world sticks with TAR: it faithfully preserves file permissions, ownership, and symbolic links. For software that needs particular files to be executable and particular directories to carry specific permissions, that fidelity is not a nicety but a requirement. ZIP handles this inconsistently at best.
Opening a TAR.GZ File on Windows
Windows is where most of the confusion lives, and the situation depends heavily on your version.
Windows 11 can open TAR.GZ archives natively. Microsoft added built-in support for a range of archive formats to File Explorer, so on an updated Windows 11 machine you can double-click a .tar.gz file to browse it or right-click to extract, with nothing installed. If yours does not behave this way, installing pending Windows updates is the first thing to try.
Windows 10 does not handle it in File Explorer, but it does include a hidden capability many people never discover: a built-in tar command. Open Command Prompt or PowerShell, navigate to the folder containing your archive, and run a single command with the archive's name to extract everything into the current directory. It works on a stock Windows 10 installation with nothing added.
If you would rather stay in the graphical interface, 7-Zip is the standard free tool and handles TAR.GZ perfectly well, as do PeaZip and WinRAR.
The Double-Extraction Trap
This is the single most common point of confusion, and it follows directly from the two-layer design. When you extract archive.tar.gz with 7-Zip, it removes only the gzip layer, leaving you with archive.tar. Many people assume something went wrong. Nothing did. You are simply looking at the middle of the process, and you need to extract that .tar file a second time to get the actual contents.
So on Windows with 7-Zip, expect two right-clicks rather than one. Windows 11's native support and the tar command both handle both layers in a single step, which is why they are the smoother options.
Opening a TAR.GZ File on macOS
Macs handle this format natively, which surprises Windows users who have wrestled with it. macOS is built on a Unix foundation, so both TAR and gzip are part of the system.
Double-click a .tar.gz file in Finder and Archive Utility unpacks both layers automatically, leaving a normal folder in the same location. There is nothing to install and no double-extraction step.
If you prefer the Terminal, the standard tar command works exactly as it does on Linux. And if you want a graphical tool with more control, Keka and The Unarchiver are both free and handle TAR.GZ alongside every other archive format you are likely to meet.
Opening a TAR.GZ File on Linux
Linux is the format's native environment, and every distribution includes the necessary tools by default.
From the command line, the conventional approach uses tar with flags telling it to extract, to handle gzip decompression, and to read from a named file. It is worth understanding what those flags mean rather than copying the incantation blindly, because the same command with a different flag creates archives instead of extracting them, and swapping the compression flag handles .tar.bz2 or .tar.xz files instead. Modern versions of tar can also detect the compression type automatically, so you often do not need to specify it at all.
Graphically, the file managers in GNOME, KDE, and other desktop environments open TAR.GZ archives with a double-click, letting you browse the contents and drag files out.
Opening a TAR.GZ File on Android and iPhone
Phones need help, but the apps are free.
On Android, ZArchiver is the reliable choice and handles TAR.GZ along with essentially every other archive format. Some built-in file managers manage it as well, though support varies by manufacturer.
On iPhone and iPad, the Files app unzips ZIP archives natively but does not handle TAR.GZ. iZip or Documents by Readdle will extract them. Because iOS is the most restrictive platform here, the conversion approach described next is often faster than fighting with apps.
The No-Installation Route: Convert TAR.GZ to ZIP
If you cannot install software, or simply do not want to, there is a cleaner path than teaching your device a new format. Change the archive into one your device already understands.
ZIP is the obvious target, because ZIP support is built into Windows, macOS, Android, and iOS with nothing added. To take this route, convert TAR.GZ to ZIP in your browser: upload the archive, convert it, and download a ZIP you can open with a double-click anywhere. This handles both layers at once, which neatly sidesteps the double-extraction problem, and nothing gets installed. It is particularly useful on a locked-down work computer, a borrowed machine, or an iPhone.
The same approach rescues you from the related formats. Plain uncompressed TAR archives turn up frequently in the same contexts, and you can convert TAR to ZIP to open one without any command-line work. Downloads from software and game communities often arrive as 7z archives instead, and you can convert 7Z to ZIP for exactly the same reason; if you would like a fuller walkthrough of that particular conversion and why people make the switch, this guide to converting 7Z files to ZIP online covers the process step by step.
The technique works in reverse too. If you are uploading something to a Linux server, submitting source code, or following documentation that expects a compressed tarball, you can convert ZIP to TAR.GZ rather than installing command-line tools to build one. Because archive formats are just different wrappers around the same contents, converting between them repacks the files without re-encoding anything, so nothing inside is degraded.
Problems You Might Run Into
A handful of situations cause trouble, and each has a specific explanation.
You extracted it and got a .tar file. This is the double-extraction issue described above, not an error. Extract the resulting .tar a second time.
The archive reports an unexpected end of file. This almost always means the download was interrupted rather than that the archive is broken at the source. Download it again on a stable connection.
Extraction seems to take forever. Because the archive is one continuous compressed stream, extracting a large tarball genuinely takes time, and pulling out a single file requires working through everything before it. A multi-gigabyte archive on an older machine needs patience, and extracting to a slow external drive or network share makes it considerably worse.
The archive contains a single folder, or spills files everywhere. Tarballs vary in how they are packaged. Well-made ones contain a single top-level folder; carelessly made ones dump dozens of files directly into whatever directory you extract into. It is worth previewing the contents before extracting into a folder you care about.
Long paths fail on Windows. Archives created on Linux sometimes contain deeply nested paths that exceed traditional Windows path limits. Extracting closer to the drive root, such as into a folder directly on C:, usually resolves it.
A Note on Safety
The usual caution applies. Extract archives only from sources you trust, since compressed files are a routine delivery method for unwanted software. Be wary of executables you were not expecting, and check available disk space before unpacking anything described as very large, because a modest archive can expand into something enormous. When using a browser-based converter, it is also worth knowing that reputable services delete uploaded files automatically after a short window.
Final Thoughts
A TAR.GZ file is simply two formats working together: TAR bundles your files into one, and gzip compresses the result. That layering explains everything about the format, from its excellent compression on collections of similar files, to its inability to pull out one file quickly, to the double-extraction step that trips up Windows users.
Opening one is native on macOS and Linux, native on Windows 11, and a single command or a free tool such as 7-Zip on Windows 10. On phones, ZArchiver or iZip do the job. And when you would rather not install anything at all, converting the tarball to ZIP gives you a file that opens instantly on any device, with both layers already handled. Once you know which route suits your setup, tarballs stop being an obstacle and become what they have always been: an efficient, faithful way to move a lot of files at once.