Open a tar.gz File on Windows 11 (No WSL Needed)

You clicked a download button on a GitHub release page or a Linux vendor site, and what landed in your Downloads folder is grafana-10.2.3.linux-amd64.tar.gz. Double-click it and, depending on your setup, Windows either opens the wrong app, shows a single mystery file inside, or does nothing useful at all. The advice you find online usually starts with "install WSL" — a whole Linux subsystem, several gigabytes, a reboot, all to look inside one archive.

You don't need it. Every Windows 11 machine already has a working tar command sitting in C:\Windows\System32\tar.exe, and File Explorer in recent builds can extract .tar.gz on its own. This guide shows the fastest way to open tar.gz on Windows three different ways — the built-in command line, the GUI, and a browser-based route if you'd rather not touch either — with real commands you can paste.

Why a .tar.gz confuses Windows in the first place

A .zip file is one thing: a container that both compresses and bundles. A .tar.gz is two things stacked.

• .tar — the tape archive. It glues many files and folders into one stream, preserving Unix permissions and symlinks. It compresses nothing.
• .gz — gzip. It compresses exactly one file. Point it at the .tar and you get something.tar.gz (sometimes shortened to .tgz).

That's why old tools show you a single .tar file after "extracting" — they only peeled the gzip layer. You need a second pass to get at the actual files. Tools that understand tar natively, like Windows' own tar.exe, do both layers in one go.

Method 1: the built-in tar command (fastest, zero install)

Windows 10 build 17063 and every Windows 11 release ship bsdtar as tar.exe. It works in Command Prompt, PowerShell and Windows Terminal. Confirm it first:

tar --version
# bsdtar 3.7.x - libarchive 3.7.x

Now extract. Open the folder containing your download in File Explorer, type cmd in the address bar and press Enter — that opens a prompt already in the right directory. Then:

tar -xvzf grafana-10.2.3.linux-amd64.tar.gz

That's the whole job. The flags read as: x extract, v verbose (print each file as it comes out), z gunzip first, f the filename follows. Files land in the current folder, usually inside one top-level directory such as grafana-10.2.3\.

The four tar commands worth memorising

:: 1. Peek inside before extracting 180 MB of files
tar -tvzf node-v20.11.0-linux-x64.tar.gz

:: 2. Extract into a specific folder (create it first)
mkdir node20
tar -xvzf node-v20.11.0-linux-x64.tar.gz -C node20

:: 3. Pull out one file only
tar -xvzf backup.tar.gz etc/nginx/nginx.conf

:: 4. Create a tar.gz from a Windows folder
tar -czvf site-backup.tar.gz .\www

Three practical notes. Quote any path with spaces: tar -xvzf "C:\Users\Sam\My Downloads\app.tar.gz". The -C target folder must already exist — tar won't create it. And you can usually drop the z: bsdtar auto-detects compression, so tar -xvf archive.tar.xz and .tar.bz2 work the same way.

Errors you may hit — and what they mean

• "Cannot open: No such file or directory" — you're in the wrong folder. Run dir *.tar.gz to confirm the file is where you think it is.
• "Can't create ... File name too long" — the archive contains deep Linux paths that bust the 260-character limit. Extract to a short root like C:\t instead of a nested Downloads path.
• Symlink or permission warnings — tar.gz stores Unix permissions and symlinks that NTFS can't always reproduce. These are warnings, not failures; the file contents still extract.
• `Expand-Archive` fails in PowerShell — that cmdlet only handles .zip. Use tar instead; it's on the PATH in PowerShell too.

Method 2: File Explorer, no command line at all

Windows 11 added native read support for tar, tar.gz, 7z, rar and more directly in File Explorer (23H2 and later). Right-click the .tar.gz, choose Extract All…, pick a destination and let it run. It handles both layers in one step, exactly like tar -xvzf.

It's the friendliest option, with two caveats: it's noticeably slower than tar.exe on archives with tens of thousands of small files, and if a third-party archiver has claimed the .gz file association, the right-click menu may show that app's entry instead. On Windows 10, Extract All won't appear for tar.gz at all — use Method 1 or 3.

Method 3: 7-Zip and the double extraction

If 7-Zip is already installed, it works — you just have to do the two-layer dance. Right-click grafana-10.2.3.linux-amd64.tar.gz → 7-Zip → Extract Here. You get grafana-10.2.3.linux-amd64.tar. Right-click that → 7-Zip → Extract Here again, and now you have the real folder tree.

From the command line, 7-Zip can pipe both stages together so no intermediate .tar hits the disk:

:: two explicit steps
7z x grafana-10.2.3.linux-amd64.tar.gz
7z x grafana-10.2.3.linux-amd64.tar -o"C:\apps\grafana"

:: or one pipeline, no temp .tar on disk
7z x -so grafana-10.2.3.linux-amd64.tar.gz | 7z x -si -ttar -o"C:\apps\grafana"

Worth it if you're already a 7-Zip user and want a GUI preview of contents. Otherwise the built-in tar is less typing and nothing to install.

Method 4: turn it into a .zip in the browser

Sometimes you're on a locked-down work laptop where you can't install 7-Zip, the command prompt is blocked by policy, or you simply need to forward the archive to a colleague who will choke on a .tar.gz. In that case the cleanest fix is to change the container: use the tar.gz to ZIP converter on File Convert Online, upload the archive, and download a .zip that every Windows machine, email client and SharePoint library opens by double-click.

This also solves a real-world annoyance: ZIP is readable by Explorer's built-in preview, so you can browse the contents without extracting anything. Expect the .zip to be a little larger than the .tar.gz — gzip over a solid tar stream usually beats ZIP's per-file compression, especially with many small text files. If you need a different target format, the rest of the archive converter hub covers the other common conversions.

Which method should you use?

• You just want the files, now → tar -xvzf file.tar.gz in the folder. Fastest path on any Windows 11 box.
• You avoid the terminal → right-click → Extract All (Windows 11 23H2+).
• Huge archive, 7-Zip already installed → the piped 7z x -so … | 7z x -si -ttar one-liner.
• Can't install anything, or need to share it → convert it to ZIP in the browser.
• You actually need Linux permissions and symlinks preserved → that's the one case where WSL earns its keep.

FAQ

Is tar really built into Windows 11, or do I need to enable something? It's there by default — C:\Windows\System32\tar.exe, a build of bsdtar. No feature to enable, no reboot, no WSL. Run tar --version to confirm.

What's the difference between .tar.gz and .tgz? None. .tgz is just a shorter name for the same gzipped tar, originally for systems that only allowed three-letter extensions. tar -xvzf archive.tgz works identically.

Can tar handle .tar.xz, .tar.bz2 and .tar.zst? The bundled bsdtar handles xz and bzip2 fine — use tar -xvf archive.tar.xz and let it auto-detect. Zstandard support depends on your build; if it errors, 7-Zip or an online converter is the fallback.

Why does my extracted folder look empty in File Explorer? Most Linux tarballs contain dot-directories like .config or .github. Turn on View → Show → Hidden items. Also check whether everything went into a single nested top-level folder.

How do I create a tar.gz on Windows to send to a Linux server? tar -czvf project.tar.gz .\project — c create, z gzip, v verbose, f filename. The result unpacks cleanly on any Linux or macOS box.

Is converting tar.gz to ZIP lossy? The file contents are identical. What you lose is Unix metadata — executable bits, ownership and symlinks — which matters if you're deploying the files to a Linux server, and doesn't matter at all if you just need to read documents, images or source code on Windows.