Question 1

Why does this tar builder exist when I can just google 'tar czvf'?

Accepted Answer

Because the #1 tar footgun is flag-order confusion: people forget that f must precede the filename, mix up c (create) / x (extract) / t (list), and pair the wrong compression flag with the wrong extension (z = gzip .gz, j = bzip2 .bz2, J = xz .xz, --zstd = zstd .zst). This builder picks the right mode letter, the right compression flag, the matching extension, and the right ordering for c/x/t, then explains each flag in plain English so you actually learn the syntax instead of cargo-culting it.

Question 2

How do I extract a tar.gz into a specific directory?

Accepted Answer

Use -C <dir> AFTER the archive name: 'tar -xzf archive.tar.gz -C /target/dir'. The order matters — f must come before the filename, and -C must come after the archive name so tar knows which archive's contents go into that directory. With strip-components=N you can also strip N leading path elements, e.g. 'tar -xzf archive.tar.gz --strip-components=1 -C /target/dir' to drop the top-level folder.

Question 3

What is a tar bomb and how do I avoid it?

Accepted Answer

A 'tar bomb' is an archive that doesn't have a single top-level directory — extracting it dumps all files into the current working directory, polluting it. The builder warns whenever you're extracting without -C (extract-to-directory) and recommends the safe pattern: first list contents ('tar -tzf archive.tar.gz'), then extract into a fresh directory ('mkdir out && tar -xzf archive.tar.gz -C out'). The tool also flags absolute paths and ../ in entries which would escape the target dir.

Question 4

What's the difference between GNU tar and BSD tar (macOS)?

Accepted Answer

GNU tar (Linux default) supports --zstd, --xattrs, --acls, --format=gnu|posix|ustar|pax, -J for xz, and --strip-components natively. BSD tar (macOS / FreeBSD, the 'bsdtar' binary) uses different default formats, auto-detects compression from the file extension (so you can often write 'tar xf archive.tar.gz' without the z), and supports libarchive formats (zip, iso, etc). The builder generates GNU-tar-valid commands by default and adds a BSD note when the syntax differs (e.g. --zstd needs GNU tar ≥ 1.31).

Question 5

What extra features does this tool have?

Accepted Answer

(1) 4 modes — create / extract / list / append-update. (2) 5 compression choices with auto-matching flag and extension. (3) Verbose, preserve-permissions, preserve-xattrs, numeric-owner toggles. (4) Exclude patterns (--exclude / -X exclude-file). (5) --strip-components for extract. (6) Target dir -C with correct ordering. (7) Format selector (gnu/posix/ustar/pax). (8) Tar-bomb + absolute-path + ../ guards with warnings. (9) Per-flag plain-English explanation. (10) Verify mode (-W) toggle. (11) Recipe library (10 common one-liners). (12) GNU/BSD notes. (13) Shell-quoting of archive name and paths. (14) Copy command + download. (15) localStorage history (max 20). (16) Shareable URL with embedded config. 100% client-side — commands are generated, never executed.

tar Archive Command Builder

Generated command

How to use

Generated command