TAR
TAR archive files for packaging testing
Test TAR uploads, archive entries, long filenames, permissions, and extraction limits for backups, packages, and deployment bundles.
Verified . The local inspector checks the ustar marker at offset 257; entry lists are compared before extraction, and path and size limits are checked against real TAR inputs.
Identify TAR files
- Magic signature
75 73 74 61 72 at offset 257 (ustar)- Registered MIME
application/x-tar
TAR stores fixed 512-byte headers with file metadata followed by file data, ending with zero blocks. Readers must walk the header chain and handle PAX extended headers for long paths, so a valid first header does not prove the whole archive extracts.
Choosing TAR
TAR is an uncompressed archive format supported by operating systems, build tools, and deployment pipelines, often paired with gzip as .tar.gz. The local generator does not produce TAR archives, so validate TAR inputs with the file inspector and the ZIP archive workflows for entry-limit patterns.
Inspect archive entries before extracting anything.
Enforce entry-count, path, and size limits to block traversal and oversized extraction.
Handle long filenames and PAX extensions instead of assuming classic 100-byte names.
Common test cases
- Archive upload validation
- Package and bundle handling
- Extraction limit tests
Invalid and boundary cases
- Entries with absolute or directory-traversal paths
- Long filenames without PAX headers
- Truncated final entry with intact earlier entries
TAR fixture matrix
This format is generated locally in the browser and does not receive a permanent SEO URL.
Open the local generator