- Not to be confused with Zip disk, an unrelated disk cartridge unit.
ZIP is one of the most popular file compression formats. It was created in 1989 as the native format of the PKZIP program, which was introduced by Phil Katz in the wake of a lawsuit (which he lost) against him by the makers of the then-popular ARC program (and file format) for copyright and trademark infringement in an earlier program PKARC which had been file-compatible with ARC. This resulted in Katz creating a new file format, which rapidly overtook ARC in popularity (to a large extent because of BBS sysops, then the primary users of such compression, resenting the lawsuit). Many programs have been released for a variety of operating systems to compress and decompress ZIP files, and native support for the format is built into several popular operating systems.
ZIP implementations vary in their support for features in the specification from PKWARE, particularly features added since version 2 (1993), some of which are protected by patents and require licensing. Many implementations limit the use of compression to the DEFLATE algorithm, introduced with version 2. Extensions incorporated into the specification that have been widely adopted are: long filenames; large files (using a technique known as ZIP64); and filenames in UTF-8. In 2011 work began on an interoperable subset of the latest APPNOTE.TXT with the intention of publication as ISO/IEC 21320-1, Document Container File -- Part 1: Core. As of November 2012, a discussion draft is available. Designed to promote interoperable implementations, the draft ISO/IEC 21320-1 prohibits compression other than using DEFLATE, segmentation or multiple volumes, and features that are subject to patents.
While .zip is the usual file extension, ZIP-formatted files can be found with many other extensions since a number of other file formats use ZIP compression but store their files in application-specific extensions. See Category:ZIP based file formats for a list of such formats.
The byte sequence
'P' 'K' 0x05 0x06 (the "end of central directory signature") appears somewhere in the file, usually beginning exactly 22 bytes from the end of the file. However, it will appear earlier if the file contains a "ZIP file comment" (common in the BBS era, but rare today), or for various other reasons. There seems to be no theoretical limit to how far back you may have to search for the signature, but some software limits it to around 64KB, which is the maximum length of a comment.
Most ZIP files (but not self-extracting ZIP files) happen to begin with
'P' 'K' 0x03 0x04. This is not a global file signature, but is the signature that appears once for every compressed file inside the ZIP file. Some ZIP-based formats are designed such that they necessarily begin in this way. But in general, it is even legal for a ZIP file to contain zero files, and such a ZIP file would not contain this signature at all.
Each file in a ZIP file is compressed using one of a number of compression algorithms. Only compression types 0 (uncompressed) and 8 (DEFLATE) are likely to be seen in modern portable ZIP files. In old ZIP files, types 1 (Shrink) and 6 (Implode) are common.
|Code||Compression scheme||Notes and references|
|1||Shrink (LZW)||Used by PKZIP prior to v2.0.|
|2–5||Reduce||Used by PKZIP v0.x.|
|6||Implode (Shannon–Fano coding)||Used by PKZIP v1.x. See also TTComp archive.|
|8||DEFLATE||Used by PKZIP v2.0+.|
|9||Deflate64, a.k.a. Enhanced Deflate||Defined in ZIP specification v2.1+.|
|10||PKWARE Data Compression Library Imploding (old IBM TERSE)|
|12||Bzip2||Defined in ZIP specification v4.6+.|
|14||LZMA (EFS)||Defined in ZIP specification v6.3+.|
|18||IBM TERSE (new)|
|19||IBM LZ77 z Architecture (PFS)|
|96||(JPEG, according to WinZip)|
|97||WavPack||Defined in ZIP specification v6.3.2+.|
|98||PPMd version I, Rev 1||Defined in ZIP specification v6.3+.|
|99||(AES encryption, according to WinZip)|
Extensible data fields
Each member file of a ZIP file may have one or more extensible data fields (or extra fields), containing arbitrary data. Each field is tagged with a 16-bit identifier. Extra fields are normally used for platform-specific or filesystem-specific metadata, or to work around limitations of the original ZIP format. They are not normally used for application-specific data.
Most of the extra fields in use are documented in the ZIP "APPNOTE" specification, or by the Info-ZIP software (e.g. the proginfo/extrafld.txt file in the Zip program's source distribution).
Known extensible data fields
|ID||Owner||Description||Reference (identification)||Reference (details)|
|0x0001||PKWARE||Zip64 extended information||APPNOTE||APPNOTE, Info-ZIP|
|0x0008||PKWARE||Reserved for extended language encoding data (PFS)||APPNOTE|
|0x000e||PKWARE||Reserved for file stream and fork descriptors||APPNOTE|
|0x000f||PKWARE||Patch Descriptor||APPNOTE||APPNOTE, Info-ZIP|
|0x0014||PKWARE||PKCS#7 Store for X.509 Certificates||APPNOTE||APPNOTE, Info-ZIP|
|0x0015||PKWARE||X.509 Certificate ID and Signature for individual file||APPNOTE||APPNOTE, Info-ZIP|
|0x0016||PKWARE||X.509 Certificate ID for Central Directory||APPNOTE||APPNOTE, Info-ZIP|
|0x0017||PKWARE||Strong Encryption Header||APPNOTE||APPNOTE|
|0x0018||PKWARE||Record Management Controls||APPNOTE||APPNOTE|
|0x0019||PKWARE||PKCS#7 Encryption Recipient Certificate List||APPNOTE||APPNOTE|
|0x0065||PKWARE||MVS / IBM S/390 (Z390) attributes - uncompressed||APPNOTE||APPNOTE|
|PKWARE||OS/400 / AS/400 (I400) attributes - uncompressed||APPNOTE||APPNOTE|
|0x0066||PKWARE||Reserved for IBM S/390 (Z390), AS/400 (I400) attributes - compressed||APPNOTE|
|0x07c8||Macintosh (Info-ZIP Macintosh, old)||APPNOTE||Info-ZIP|
|0x2605||ZipIt Macintosh||APPNOTE||APPNOTE, Info-ZIP|
|0x2705||ZipIt Macintosh 1.3.5+ (w/o full filename)||APPNOTE||APPNOTE, Info-ZIP|
|0x2805||ZipIt Macintosh 1.3.5+||APPNOTE||APPNOTE|
||Windows NT security descriptor (binary ACL)||APPNOTE||Info-ZIP|
|0x4690||PKWARE||POSZIP 4690 (reserved)||APPNOTE|
||FWKCS MD5||APPNOTE||APPNOTE, Info-ZIP|
||OS/2 access control list (text ACL)||APPNOTE||Info-ZIP|
||Xceed original location||APPNOTE|
||(Observed in some Psion files.)|
||AOS/VS (binary ACL)||APPNOTE||Info-ZIP|
||Info-ZIP UNIX (original, also OS/2, NT, etc.)||APPNOTE||Info-ZIP|
||Info-ZIP Unicode Comment||APPNOTE||APPNOTE, Info-ZIP|
||BeOS (BeBox, PowerMac, etc.)||APPNOTE||Info-ZIP|
||Info-ZIP Unicode Path||APPNOTE||APPNOTE, Info-ZIP|
||Info-ZIP Unix (previous new)||APPNOTE||Info-ZIP|
||Info-ZIP Unix (new)||Info-ZIP||Info-ZIP|
|0xa220||Microsoft Open Packaging Growth Hint||APPNOTE||APPNOTE|
- APPNOTE from PKWARE (latest version of formal spec)
- APPNOTE Archives from PKWARE (selected versions all the way back to 1.0)
- An early version of APPNOTE (not numbered or dated); perhaps the very first
- IANA registration for application/zip in July 1993 (corresponds to version 2 of APPNOTE.TXT)
- Documentation from Info-ZIP (Includes Info-ZIP variants on APPNOTE.TXT dated from 1996 to 2004, specifications used as the basis for various open-source tools)
- November 2012 working draft of ISO/IEC WD 21320-1, Document Container File -- Part 1: Core Intended as restricted subset of APPNOTE 6.3.3 designed to promote interoperability.
- February 2013 committee draft of ISO/IEC CD 21320-1, Document Container File -- Part 1: Core Essentially the same as November 2012 working draft except that it mandates use of the UTF-8 indicator.
- Archive format info, including ZIP (from 1989, when ZIP was newly released)
- ZIP file header format (among other archive types)
- Note that in general there is no official file name encoding for ZIP files, and non ASCII filenames are not generally well supported. The original implementation specified IBM Code Page 437 for filenames, but as many characters cannot be expressed in that encoding, the filename bytes have often been interpreted using the current system codepage (implementation dependent behaviour). There is a flag to specify UTF-8 as the encoding, but it is not supported in all major clients (e.g. Windows Explorer).
- Info-ZIP's "extra fields" documentation
- Info-ZIP: Zip, UnZip
- zlib - The zlib library does not support ZIP format, but it is distributed with "minizip" code that supports most ZIP files.
- libzip - Uses zlib.
- libarchive - Uses zlib.
- Archive::ZZip: Perl bindings for zziplib
- 1608A.ZIP → D1-MAC.ZIP: Example of a file that uses the uncommon "Reduce" compression scheme
- ↑ http://www.pkware.com/documents/casestudies/APPNOTE.TXT
- ↑ http://kikaku.itscj.ipsj.or.jp/sc34/open/1855.pdf
- Wikipedia: Zip (file format)
- Wikipedia: PKZIP
- Zip files all the way down (creating an infinitely-regressed ZIP file)
- ZIP101 an archive walkthrough
- Serve deepzoom images from a zip archive with openseadragon
- How are zlib, gzip and Zip related? What do they have in common and how are they different? - Response to StackOverflow question by zlib/gzip co-creator Mark Adler