ZIP (file format)

From Wikipedia, the free encyclopedia

**ZIP** <tr><td colspan="2" style="text-align: center; border: 0px solid #aaaaaa">
A zip archive in WinZip<tr><th style="white-space: nowrap;">File extension:</th><td>`.zip`</td></tr><tr><th style="white-space: nowrap;">MIME type:</th><td>`<code>application/zip`</code></td></tr><tr><th style="white-space: wrap;">Uniform Type Identifier:</th><td>com.pkware.zip-archive</td></tr><tr><th style="white-space: wrap;">Magic:</th><td>`PK\003\004`</td></tr><tr><th style="white-space: nowrap;">Developed by:</th><td>Phil Katz</td></tr><tr><th style="white-space: nowrap;">Type of format:</th><td>Data compression</td></tr>

The ZIP file format is a popular data compression and archival format. A ZIP file contains one or more files that have been compressed, to reduce their file size, or stored as-is.

The format was originally designed by Phil Katz for PKZIP. However, many software utilities other than PKZIP itself are now available to create, modify, or open (unzip, decompress) ZIP files, notably WinZip, BOMArchiveHelper, KGB Archiver, PicoZip, Info-ZIP, WinRAR, IZArc, 7-Zip and ALZip. Microsoft has also included minimal built-in ZIP support (under the name "compressed folders") in later versions of its Windows operating system. Apple has included built-in ZIP support in Mac OS X v10.3 and later.

ZIP files generally use the file extensions ".zip" or ".ZIP" and the MIME media type application/zip. Some software uses the ZIP file format as a wrapper for a large number of small items in a specific structure. Generally when this is done a different file extension is used. Examples of this usage are Java JAR files, id Software .pk3/.pk4 files, package files for StepMania and Winamp/Windows Media Player skins, XPInstall, and some OpenOffice.org document formats. The OpenDocument format usually uses the JAR file format internally, so it can be easily uncompressed and compressed using tools for ZIP files.

1 History
- 1.1 Early history
- 1.2 Moving beyond the command line
2 Technical information
- 2.1 Compression methods
3 References
4 See also
5 External links

[edit] History

[edit] Early history

The ZIP file format was originally created by Phil Katz, founder of PKWARE, after a prolonged legal dispute between PKWare and System Enhancement Associates (SEA) over the trademark name "ARC" (short for "Archive") and the file name extension .arc

PKWare's first archive product, PKARC, borrowed heavily from SEA's published code, and improved on it by converting SEA's ARC C code into hand optimised assembler, which was much faster. PKARC also used the ".ARC" file name extension. SEA contended that Katz had based his product on their code and trademark name, and thus ought to license the code from them and pay royalties. PKWare refused. SEA brought a successful copyright infringement lawsuit against Phil Katz and PKWare. After suit was brought, Katz briefly released a relabeled version of PKARC named PKPAK in a futile effort to invalidate the suit.

During settlement, Katz still refused to pay license fees to SEA, instead agreeing to pay SEA's legal fees and stop selling PKARC. He then went on to create his own file format, which is known worldwide now as the ZIP format (commonly called a ZIP File). The ZIP format he designed was more resistant to data loss than the ARC format because of redundant catalog storage; it also was more flexible than ARC, providing room for additional optional compression algorithms and room for future expansion. Along with the new format, PKZIP included at least one more efficient compression algorithm than any supported by ARC. Once the PKZIP software was released, many users abandoned ARC because of its slower speed and less effective compression performance, and because Katz had successfully put forth the idea that he was the "good guy" who was being unfairly treated by an "evil corporation."

Katz publicly released technical documentation on the ZIP file format, along with the first version of his PKZIP archiver, in January 1989.

The name zip (meaning speed) was suggested by Katz's friend Robert Mahoney. They wanted to imply that their product would be faster than ARC and other compression formats of the time.

[edit] Moving beyond the command line

In the mid 1990s, as more new computers included graphical user interfaces, there were more users who were not comfortable with the command-line operation of PKZIP. Seeing an opportunity, shareware authors began pitching compression and archival programs with graphical user interfaces. Many of these used the ZIP format. WinZip was among the most popular. PKWare (Katz's company) also offered a graphical version of PKZip. These graphical compression programs were easier to learn to use than the older command-line equivalents, but they still required learning an additional program and an additional interface just for compression.

In the late 1990s, various file manager software products started integrating support for the ZIP format into the file manager user interface. Even before that, Norton Commander and clones like Volkov Commander in DOS started that trend, and that remains the norm for the "Commander-like" or Orthodox file managers like Midnight Commander (Linux and UNIX like systems) and Total Commander, previously Windows Commander (Windows). The KDE file manager (kfm) supported this very early, and support was also added to Windows Explorer first with Plus! for Windows 98 and later included with Windows Me and Windows XP, the Mac OS Finder (as of Mac OS X, via the BOMArchiveHelper utility), the Nautilus file manager used with GNOME, the Konqueror file manager used with newer versions of KDE, and others. By 2002, all major desktop environments included ZIP file support in their file managers. Typically, in any modern file manager, a ZIP file may be treated as a directory or folder, so that files are copied into and out of it in the same manner as any other folder; the compression is handled in a way that is largely transparent to the end user. This eliminates the need for the user to learn to use a program and an interface just for the purpose of compression and archival, since the same interface can be used as for regular file management.

[edit] Technical information

ZIP is a fairly simple archive format that compresses every file separately. Compressing files separately allows for individual files to be retrieved without reading through other data; in theory, it may allow better compression by using different algorithms for different files. However a caveat to this is that archives containing a large number of small files end up significantly larger than if they were compressed as a single file (the classic example of the latter is the common tar.gz archive which consists of a TAR archive compressed using gzip).

The specification for ZIP indicates that files can be stored either uncompressed or using a variety of compression algorithms. However, in practice, ZIP is almost always used with Katz's DEFLATE algorithm, except when files being added are already compressed or are resistant to compression.

ZIP supports a simple password-based symmetric encryption system which is known to be seriously flawed. In particular it is vulnerable to known-plaintext attacks which are in some cases made worse by poor implementations of random number generators.<ref>Stay, Michael. "ZIP Attacks with Reduced Known Plaintext". http://math.ucr.edu/~mike/zipattacks.pdf</ref> It also supports spreading archives across multiple removable disks (generally floppy disks, but it could also be used with other removable media).

New features including new compression and encryption methods have been added to ZIP in more recent times, but these are not supported by many tools and are not in wide use.

The original zip format had a number of limits (uncompressed size of a file, compressed size of a file and total size of the zipfile to name a few) at 4GB. In version 4.5 of the specification pkware introduced the "zip64" extensions to get arround this limitations.

The FAT filesystem of DOS only has a timestamp granularity of two seconds; Zip file records mimic this. As a result, the timestamp granularity of files in a Zip archive is only two seconds.

The Info-ZIP implementations of the Zip format adds support for Unix filesystem features, such as user and group IDs, file permissions, and support for symbolic links. The Apache Ant implementation is aware of them to the extent that it can create files with predefined Unix permissions.

The Info-ZIP Windows tools also support NTFS filesystem permissions, and will make an attempt to translate from NTFS permissions to Unix permissions or vice-versa when extracting files. This is sometimes annoying, and can result in undesireable combinations, e.g. .exe files being created on NTFS volumes with executable permission denied.

[edit] Compression methods

The size for comparison figures were made using the contents of ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2 and maximum compression.^{[citation needed]}

Shrinking (method 1)

Shrinking is a variant of LZW with a few minor tweaks. As such it was affected by the LZW patent issue. It was never clear if the patent covered unshrinking but some open source projects (for example Info-ZIP) decided to play it safe and not include unshrinking support in the default builds.

Reducing (methods 2-5)

Reducing involves a combination of compressing repeated byte sequences then applying a probability-based encoding to the result.

Imploding (method 6)

Imploding involves compressing repeated byte sequences with a sliding window then compressing the result using multiple Shannon-Fano trees.

Tokenizing (Method 7)

This method number is reserved. The PKWARE specification does not define an algorithm for it. This is because the format was developed (as a non-proprietary open specification) by a third-party other than PKWARE for specialized usage.^{[citation needed]}

Deflate and enhanced deflate (methods 8 and 9)

These methods use the well-known deflate algorithm. Deflate allows a window up to 32 KiB. Enhanced deflate allows a window up to 64 KiB. The enhanced version performs slightly better but is not as widely supported.

Sizes for comparison (using pkzip 8.00.0038 for Windows):

Deflate: 52.1 MiB
Enhanced deflate: 51.8 MiB

PKWARE Data Compression Library Imploding (method 10)

The official ZIP format specification gives no further information on this.

Size for comparison: 61.6 MiB (pkzip 8.00.0038 for Windows in binary mode).

Method 11

This method number is reserved by PKWARE.

Bzip2 (method 12)

This method uses the well-known bzip2 algorithm. This algorithm performs better than deflate but is not widely supported, particularly by Windows-based tools.

Size for comparison: 50.6 MiB (pkzip 8.00.0038 for Windows).

Note that although both the original (tar inside bzip2, 34.6 MiB) and the comparison version (bzip2 as a ZIP method, 50.6 MiB) use the same compression algorithm, the ZIP version is 46% larger. This demonstrates the compression ratio advantage of a solid archive over ZIP's strategy of compressing each individual file separately when used to archive many (16,448) files.