Reference Formats
ZIP
A lossless archive format that bundles multiple files into one, using the DEFLATE algorithm by default, and now the most universally supported archive format across every major operating system.
Extension
.zip
Full name
ZIP Archive
Introduced
1989
Vendor
PKWARE (Phil Katz)
What is inside the container
A ZIP archive stores each file as a separate compressed (or stored, uncompressed) entry with its own local header, followed by a central directory at the end of the file listing every entry, its size, and its offset — a design that lets a reader jump straight to one file without decompressing the whole archive. The default and most common compression method is DEFLATE (LZ77 plus Huffman coding), it is entirely lossless, and the format also supports password protection, though the legacy ZipCrypto scheme is weak and the stronger AES-256 option is not supported by every unzip tool.
How to open it
For archives
ZIP is a safe, low-risk choice for bundling and delivering multiple DAM assets together (a client download package, a batch export) because its specification is public, patent-unencumbered, and supported natively by every current OS without installing extra software. It is not itself a preservation strategy for the files inside it, though: a DAM should still catalog and preview the individual assets before zipping, since content inside an archive is generally invisible to search and thumbnail generation unless the DAM explicitly unpacks it at ingest.
Phil Katz released the ZIP format in February 1989 through his company PKWARE, designing it (with contributions from Gary Conway) partly to move past a legal dispute with System Enhancement Associates over his earlier ARC-compatible tools. Katz put the format’s specification into the public domain while keeping his own PKZIP implementation proprietary — a split that let ZIP spread far beyond PKWARE’s own software. Version 2 of PKZIP introduced the DEFLATE algorithm, combining LZ77-style dictionary compression with Huffman coding, which remains the default method in nearly every ZIP archive created today and was later standardized independently as RFC 1951.
For a DAM, ZIP is less an asset format than a delivery and packaging mechanism: it’s how a batch of approved assets gets handed to a client, how a project folder gets exported for backup, or how a multi-file upload arrives for ingestion. Because every current OS opens ZIP natively — Windows Explorer and macOS Archive Utility both handle it without extra software — it remains the safest default for cross-platform file bundling, but a DAM still needs to unpack and individually catalog the contents at ingest time, since the assets inside a ZIP aren’t searchable or previewable as long as they stay compressed.
Frequently asked
Can a DAM search inside the contents of a ZIP file without extracting it?
Generally no for full content/metadata search — most DAM platforms extract or at least list a ZIP's contents at ingest time and catalog each file individually, since compressed entries aren't searchable in place.
What compression algorithm does ZIP use by default?
DEFLATE, which combines LZ77 dictionary-based compression with Huffman coding; it's lossless and was designed by Phil Katz for PKZIP version 2, later standardized as RFC 1951.
Is ZIP compression lossless?
Yes — every byte of the original files is recoverable exactly on extraction, which is why ZIP is safe for archiving any file type, including formats that are themselves already lossy (like JPEG).
Why is ZIP a common choice for delivering a batch of assets from a DAM to a client?
Because it's natively supported without extra software on Windows, macOS, and Linux, is patent-free and openly specified, and lets a DAM package many files with folder structure into a single downloadable object.
Does password-protecting a ZIP file actually secure its contents?
It depends on the method — the original ZipCrypto encryption is cryptographically weak and crackable, while the newer AES-256 option (added later to the spec) is strong, but not every unzip tool supports AES, so compatibility and security trade off against each other.
Can a ZIP archive contain other ZIP or archive files inside it?
Yes — ZIP has no restriction on the file types it stores, including nested archives, though a DAM ingest pipeline needs to decide explicitly whether to recurse into nested archives or treat them as opaque files.
What is the difference between ZIP and a compressed archive like TAR.GZ?
ZIP compresses each file individually within the archive, so files can be extracted independently; TAR.GZ first bundles files uncompressed with TAR, then compresses the whole bundle with gzip, so extracting one file requires decompressing the full stream up to that point.
Who owns the ZIP file format specification today?
PKWARE still publishes and maintains the official .ZIP File Format Specification (APPNOTE.TXT), but the base format has been public and implemented by countless other vendors — Microsoft, Apple, Info-ZIP — since Phil Katz released it in 1989.
Sources
- The ZIP format was made public by Phil Katz of PKWARE in 1989 (specification published as APPNOTE.TXT with PKZIP 0.9), with the format co-designed with Gary Conway. checked 2026-08-07 — FileFormat.com — ZIP
- DEFLATE, the default ZIP compression method combining LZ77 and Huffman coding, was designed by Phil Katz for PKZIP version 2 and later described in IETF RFC 1951. checked 2026-08-07 — Wikipedia — Deflate