What is a TAR file?
A Unix archive format that concatenates files and their permissions into a single stream, usually paired with gzip or zstd.
Technical characteristics
- Representation
- binary
- Compression
- None
- Lossy
- No
- Open specification
- Yes
History and origin
- Introduced
- 1979
- Organisation
- Unix / POSIX
Compatibility
- Windowspartial
- macOSfull
- Linuxfull
Advantages of TAR
- Preserves Unix permissions, symlinks and ownership
- Streams well through pipes
Limitations to know about
- No compression on its own
- No random access — extraction reads sequentially
When to use TAR
- Linux packaging
- Backups
- Container images
Convert TAR files
TAR scores
Deterministic scores calculated from the structured facts above. Identical facts always produce identical scores.
Overall score
60/100
Openness score
100- the specification is published openly
- an openly specified format can be implemented without a licence negotiation
Confidence 49% · evidence coverage 100%
Archiving score
97- the specification is public, so a decoder can always be rebuilt
- the specification is published openly
- it is actively maintained and current
- an openly specified format can be implemented without a licence negotiation
Confidence 62% · evidence coverage 89%
Longevity score
88- it is actively maintained and current
- the specification is published openly
- the specification is public, so a decoder can always be rebuilt
- it does not satisfy: mainstream applications ship support for it
Confidence 61% · evidence coverage 100%
AI score
67- open specifications are implemented by the open-source decoders that ML stacks rely on
- the specification is published openly
- only a narrow set of applications handles it
- large lossless payloads cost bandwidth and memory
Confidence 47% · evidence coverage 100%
Printing score
53- lossless data means no compression artefacts appear at print resolution
- only a narrow set of applications handles it
Confidence 50% · evidence coverage 50%
Photography score
44- lossless data survives repeated open-edit-save cycles without degrading
- it stores data losslessly, so files stay large
- some devices ask the person to install something first
Confidence 51% · evidence coverage 44%
Web score
41- the specification is published openly
- it stores data losslessly, so files stay large
- large lossless payloads cost bandwidth and memory
Confidence 50% · evidence coverage 67%
Editing score
38- lossless data survives repeated open-edit-save cycles without degrading
- only a narrow set of applications handles it
Confidence 46% · evidence coverage 63%
Performance score
35- it stores data losslessly, so files stay large
- large lossless payloads cost bandwidth and memory
Confidence 57% · evidence coverage 100%
Streaming score
33- it stores data losslessly, so files stay large
- large lossless payloads cost bandwidth and memory
Confidence 59% · evidence coverage 50%
Compatibility score
32- an open specification means cloud SDKs can implement it without licensing friction
- only a narrow set of applications handles it
- some devices ask the person to install something first
Confidence 63% · evidence coverage 75%
What TAR is recommended for
Every conclusion below is derived from the structured facts on this page — nothing is written by hand.
Cloud compatibility100/100
- Because an open specification means cloud SDKs can implement it without licensing friction.
- Because it converts into many other formats, which suits automated pipelines.
Long-term archiving100/100
- Because the specification is public, so a decoder can always be rebuilt.
- Because lossless storage preserves the original data for future migrations.
- Because it is a current, actively maintained format.
Open standards100/100
- Because the specification is published openly.
Licensing100/100
- Because an openly specified format can be implemented without a licence negotiation.
- Because the core patents are old enough to have expired.
Future-proofing88/100
- Because it is actively maintained and current.
- Because open specifications outlive the companies that create them.
- Because nothing in the graph supersedes it yet.
AI compatibility75/100
- Because open specifications are implemented by the open-source decoders that ML stacks rely on.
- Because lossless pixels avoid compression artefacts leaking into training data.
Printing suitability71/100
- Because lossless data means no compression artefacts appear at print resolution.
What TAR is not recommended for
Software compatibility0/100
- Because only a narrow set of applications handles it.
- Because documented application support is minimal.
Compression efficiency23/100
- Because it stores data losslessly, so files stay large.
- Because its codec generation predates modern entropy coding and block partitioning.
Everyday consumer usage25/100
- Because some devices ask the person to install something first.
- Because it does not satisfy: small files are easy to email, message and upload.
Operating system compatibility33/100
- Because at least one mainstream platform needs extra software.
Web suitability33/100
- Because lossless payloads cost more bandwidth than the web usually justifies.
Related to TAR
Data quality
Every claim on this page is classified as a verified fact, a derived fact or an assumption.
- Overall confidence
- 83%
- Verification status
- verified
- Last reviewed
- 2026-08-03
- Verified facts
- 2
2 classified claims backed by 1 source.
- Convert Always editorial review — Convert Always
Sources and review status
Review status: verified · confidence 80%
Last reviewed 2026-08-03 (revision 1).
- Convert Always editorial review — Convert Always