The tar command appeared in Seventh Edition Unix in January 1979, built by AT&T Bell Laboratories to write files sequentially to magnetic tape drives \u2014 hence Tape ARchive. Its design reflects that origin: a TAR stream is just files concatenated one after another behind small fixed headers, with no index or table of contents the way ZIP has, because a tape drive can only read forward through a reel rather than jump to an arbitrary offset. The format was standardized as “ustar” in the POSIX.1-1988 standard to add longer filenames and better portability, and despite being nominally superseded by the pax utility in 2001, TAR has remained the de facto standard for Unix\/Linux file bundling for over four decades.<\/p>
In a DAM context, TAR is the workhorse of server-side operations rather than a format end users interact with directly: system backups, migrating an asset library between storage backends, or streaming a batch of files to a processing pipeline. Because TAR faithfully preserves Unix file metadata (permissions, ownership, symbolic links) that ZIP handles less consistently across platforms, it’s the safer choice when the receiving system is also Unix-based \u2014 but since TAR itself applies no compression, a DAM backend pipeline almost always pipes the TAR stream through gzip or another compressor before it’s written to disk or sent over the network.<\/p>","protected":false},"excerpt":{"rendered":"
A Unix-originated archive format that concatenates multiple files and their metadata into a single stream without any built-in compression, historically designed for writing sequential data to magnetic tape.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Does a TAR file compress the files inside it?","answer":"No \u2014 TAR only concatenates files and their metadata into one stream; it applies no compression at all, which is why TAR archives are almost always paired with gzip (.tar.gz) or another compressor when smaller file size matters."},{"question":"Why does TAR preserve Unix file permissions better than ZIP?","answer":"TAR's header format was designed natively for Unix filesystems and stores owner, group, and permission bits directly, whereas ZIP's cross-platform design handles Unix-specific metadata less consistently depending on which tool created the archive."},{"question":"Can you extract a single file from a TAR archive without unpacking the whole thing?","answer":"Technically yes with modern tar implementations, but because TAR has no central index like ZIP's, extracting one file still means scanning through the stream from the start rather than jumping directly to it."},{"question":"Does Windows open TAR files without installing anything?","answer":"Windows 10 and 11 include a built-in tar.exe accessible from the command line, but there's no built-in graphical extraction the way File Explorer handles ZIP \u2014 most users still reach for 7-Zip or WinRAR for a GUI."},{"question":"Why would a DAM use TAR instead of ZIP for backend transfers?","answer":"TAR streams sequentially and preserves Unix metadata exactly, making it well-suited to server-to-server transfers, backups, and pipelines between Linux systems, where ZIP's cross-platform compromises aren't needed."},{"question":"What does 'ustar' mean in relation to TAR?","answer":"It's the POSIX.1-1988-standardized version of the TAR format, extending the original design with longer filenames, symbolic link support, and better cross-system portability."},{"question":"Is TAR still relevant given it dates to 1979?","answer":"Yes \u2014 despite its age, TAR remains the default archiving mechanism on virtually every Linux\/Unix system and underlies common formats like .tar.gz and Docker image layers, making it very much a current, active format rather than a legacy one."},{"question":"What's the practical difference between TAR and TAR.GZ for a DAM?","answer":"TAR alone just bundles files with no size reduction; TAR.GZ pipes that same bundle through gzip compression afterward, so TAR.GZ is what a DAM actually wants for space-efficient storage or transfer, while plain TAR suits cases where speed matters more than size."}],"checked_date":"2026-08-07","sources":[{"statement":"The tar command appeared in Seventh Edition Unix, released in January 1979, originally for writing archives to magnetic tape drives.","source_name":"HandWiki \u2014 Tar (computing)","url":"https:\/\/handwiki.org\/wiki\/Software:Tar_(computing)","checked":"2026-08-07"},{"statement":"The tar file structure was standardized as 'ustar' in POSIX.1-1988, extending the format to support longer filenames, symbolic links, and device files.","source_name":"Library of Congress \u2014 Tape Archive (tar) File Format Family","url":"https:\/\/www.loc.gov\/preservation\/digital\/formats\/fdd\/fdd000531.shtml","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"ext":"tar","full_name":"Tape Archive","vendor_name":"AT&T Bell Laboratories (Unix)","introduced":"1979","container_notes":"A TAR archive is simply files laid end to end, each preceded by a 512-byte header recording its name, permissions, owner, and size, with no per-file or whole-archive compression applied \u2014 it's purely a bundling format, which is why it's almost always paired with a separate compressor like gzip (producing .tar.gz) for actual size reduction. Because it was designed for sequential tape access, reading one file out of a TAR archive means scanning through the stream rather than jumping to an index the way ZIP's central directory allows.","open_with":[{"platform":"Linux\/Unix\/macOS","how":"The built-in tar command-line tool (tar -xf, tar -cf) ships by default on virtually every Unix-like system"},{"platform":"Windows","how":"7-Zip or WinRAR can open .tar files, and modern Windows 10\/11 also includes a built-in tar.exe usable from the command line"},{"platform":"GUI archive managers","how":"Archive Manager\/File Roller (Linux), Keka (macOS), or PeaZip (cross-platform) extract TAR through a graphical interface"},{"platform":"DAM\/asset pipeline","how":"Python's built-in tarfile module or Node's tar package let a DAM build and read TAR streams programmatically, common for server-to-server asset transfer or backup pipelines"}],"archive_advice":"TAR is well-suited to a DAM's backend backup and transfer pipelines \u2014 bundling many files while preserving Unix permissions and ownership metadata exactly \u2014 but it should always be paired with a compressor (gzip or better) since raw TAR itself doesn't shrink file size at all. For asset delivery to end users rather than system-to-system transfer, ZIP remains the more broadly recognized choice, since TAR's file-manager support on Windows and macOS is less universal.","related":[],"tool_link":""},"silo":[23],"class_list":["post-3045","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3045","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":0,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3045\/revisions"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=3045"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=3045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}