{ "mode": "man", "parameter": "UNZIP", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/UNZIP/1/json", "generated": "2026-05-30T06:10:33Z", "synopsis": "unzip [-Z] [-cflptTuvz[abjnoqsCDKLMUVWX$/:^]] file[.zip] [file(s) ...] [-x xfile(s) ...]\n[-d exdir]", "sections": { "NAME": { "content": "unzip - list, test and extract compressed files in a ZIP archive\n", "subsections": [] }, "SYNOPSIS": { "content": "unzip [-Z] [-cflptTuvz[abjnoqsCDKLMUVWX$/:^]] file[.zip] [file(s) ...] [-x xfile(s) ...]\n[-d exdir]\n", "subsections": [] }, "DESCRIPTION": { "content": "unzip will list, test, or extract files from a ZIP archive, commonly found on MS-DOS systems.\nThe default behavior (with no options) is to extract into the current directory (and subdi‐\nrectories below it) all files from the specified ZIP archive. A companion program, zip(1),\ncreates ZIP archives; both programs are compatible with archives created by PKWARE's PKZIP\nand PKUNZIP for MS-DOS, but in many cases the program options or default behaviors differ.\n", "subsections": [] }, "ARGUMENTS": { "content": "file[.zip]\nPath of the ZIP archive(s). If the file specification is a wildcard, each matching\nfile is processed in an order determined by the operating system (or file system).\nOnly the filename can be a wildcard; the path itself cannot. Wildcard expressions are\nsimilar to those supported in commonly used Unix shells (sh, ksh, csh) and may con‐\ntain:\n\n* matches a sequence of 0 or more characters\n\n? matches exactly 1 character\n\n[...] matches any single character found inside the brackets; ranges are specified by\na beginning character, a hyphen, and an ending character. If an exclamation\npoint or a caret (`!' or `^') follows the left bracket, then the range of char‐\nacters within the brackets is complemented (that is, anything except the char‐\nacters inside the brackets is considered a match). To specify a verbatim left\nbracket, the three-character sequence ``[[]'' has to be used.\n\n(Be sure to quote any character that might otherwise be interpreted or modified by the\noperating system, particularly under Unix and VMS.) If no matches are found, the\nspecification is assumed to be a literal filename; and if that also fails, the suffix\n.zip is appended. Note that self-extracting ZIP files are supported, as with any\nother ZIP archive; just specify the .exe suffix (if any) explicitly.\n\n[file(s)]\nAn optional list of archive members to be processed, separated by spaces. (VMS ver‐\nsions compiled with VMSCLI defined must delimit files with commas instead. See -v in\nOPTIONS below.) Regular expressions (wildcards) may be used to match multiple mem‐\nbers; see above. Again, be sure to quote expressions that would otherwise be expanded\nor modified by the operating system.\n\n[-x xfile(s)]\nAn optional list of archive members to be excluded from processing. Since wildcard\ncharacters normally match (`/') directory separators (for exceptions see the option\n-W), this option may be used to exclude any files that are in subdirectories. For ex‐\nample, ``unzip foo *.[ch] -x */*'' would extract all C source files in the main direc‐\ntory, but none in any subdirectories. Without the -x option, all C source files in\nall directories within the zipfile would be extracted.\n\n[-d exdir]\nAn optional directory to which to extract files. By default, all files and subdirec‐\ntories are recreated in the current directory; the -d option allows extraction in an\narbitrary directory (always assuming one has permission to write to the directory).\nThis option need not appear at the end of the command line; it is also accepted before\nthe zipfile specification (with the normal options), immediately after the zipfile\nspecification, or between the file(s) and the -x option. The option and directory may\nbe concatenated without any white space between them, but note that this may cause\nnormal shell behavior to be suppressed. In particular, ``-d ~'' (tilde) is expanded\nby Unix C shells into the name of the user's home directory, but ``-d~'' is treated as\na literal subdirectory ``~'' of the current directory.\n", "subsections": [] }, "OPTIONS": { "content": "Note that, in order to support obsolescent hardware, unzip's usage screen is limited to 22 or\n23 lines and should therefore be considered only a reminder of the basic unzip syntax rather\nthan an exhaustive list of all possible flags. The exhaustive list follows:\n", "subsections": [ { "name": "-Z -Z", "content": "are taken to be zipinfo(1) options. See the appropriate manual page for a description\nof these options.\n", "flag": "-Z" }, { "name": "-A", "content": "", "flag": "-A" }, { "name": "-c -p", "content": "cept that the name of each file is printed as it is extracted, the -a option is al‐\nlowed, and ASCII-EBCDIC conversion is automatically performed if appropriate. This\noption is not listed in the unzip usage screen.\n", "flag": "-p" }, { "name": "-f", "content": "that are newer than the disk copies. By default unzip queries before overwriting, but\nthe -o option may be used to suppress the queries. Note that under many operating\nsystems, the TZ (timezone) environment variable must be set correctly in order for -f\nand -u to work properly (under Unix the variable is usually set automatically). The\nreasons for this are somewhat subtle but have to do with the differences between DOS-\nformat file times (always local time) and Unix-format times (always in GMT/UTC) and\nthe necessity to compare the two. A typical TZ value is ``PST8PDT'' (US Pacific time\nwith automatic adjustment for Daylight Savings Time or ``summer time'').\n", "flag": "-f" }, { "name": "-l", "content": "tion dates and times of the specified files are printed, along with totals for all\nfiles specified. If UnZip was compiled with OS2EAS defined, the -l option also lists\ncolumns for the sizes of stored OS/2 extended attributes (EAs) and OS/2 access control\nlists (ACLs). In addition, the zipfile comment and individual file comments (if any)\nare displayed. If a file was archived from a single-case file system (for example,\nthe old MS-DOS FAT file system) and the -L option was given, the filename is converted\nto lowercase and is prefixed with a caret (^).\n", "flag": "-l" }, { "name": "-p", "content": "files are always extracted in binary format, just as they are stored (no conversions).\n", "flag": "-p" }, { "name": "-t", "content": "the CRC (cyclic redundancy check, an enhanced checksum) of the expanded file with the\noriginal file's stored CRC value.\n", "flag": "-t" }, { "name": "-T", "content": "one. This corresponds to zip's -go option except that it can be used on wildcard zip‐\nfiles (e.g., ``unzip -T \\*.zip'') and is much faster.\n", "flag": "-T" }, { "name": "-u", "content": "function as the -f option, extracting (with query) files that are newer than those\nwith the same name on disk, and in addition it extracts those files that do not al‐\nready exist on disk. See -f above for information on setting the timezone properly.\n", "flag": "-u" }, { "name": "-v", "content": "evolved and now behaves as both an option and a modifier. As an option it has two\npurposes: when a zipfile is specified with no other options, -v lists archive files\nverbosely, adding to the basic -l info the compression method, compressed size, com‐\npression ratio and 32-bit CRC. In contrast to most of the competing utilities, unzip\nremoves the 12 additional header bytes of encrypted entries from the compressed size\nnumbers. Therefore, compressed size and compression ratio figures are independent of\nthe entry's encryption status and show the correct compression performance. (The com‐\nplete size of the encrypted compressed data stream for zipfile entries is reported by\nthe more verbose zipinfo(1) reports, see the separate manual.) When no zipfile is\nspecified (that is, the complete command is simply ``unzip -v''), a diagnostic screen\nis printed. In addition to the normal header with release date and version, unzip\nlists the home Info-ZIP ftp site and where to find a list of other ftp and non-ftp\nsites; the target operating system for which it was compiled, as well as (possibly)\nthe hardware on which it was compiled, the compiler and version used, and the compila‐\ntion date; any special compilation options that might affect the program's operation\n(see also DECRYPTION below); and any options stored in environment variables that\nmight do the same (see ENVIRONMENT OPTIONS below). As a modifier it works in conjunc‐\ntion with other options (e.g., -t) to produce more verbose or debugging output; this\nis not yet fully implemented but will be in future releases.\n", "flag": "-v" }, { "name": "-z", "content": "", "flag": "-z" } ] }, "MODIFIERS": { "content": "", "subsections": [ { "name": "-a", "content": "``binary'' files). The -a option causes files identified by zip as text files (those\nwith the `t' label in zipinfo listings, rather than `b') to be automatically extracted\nas such, converting line endings, end-of-file characters and the character set itself\nas necessary. (For example, Unix files use line feeds (LFs) for end-of-line (EOL) and\nhave no end-of-file (EOF) marker; Macintoshes use carriage returns (CRs) for EOLs; and\nmost PC operating systems use CR+LF for EOLs and control-Z for EOF. In addition, IBM\nmainframes and the Michigan Terminal System use EBCDIC rather than the more common\nASCII character set, and NT supports Unicode.) Note that zip's identification of text\nfiles is by no means perfect; some ``text'' files may actually be binary and vice\nversa. unzip therefore prints ``[text]'' or ``[binary]'' as a visual check for each\nfile it extracts when using the -a option. The -aa option forces all files to be ex‐\ntracted as text, regardless of the supposed file type. On VMS, see also -S.\n", "flag": "-a" }, { "name": "-b", "content": "---a.\n", "flag": "-b" }, { "name": "-b", "content": "tries marked as \"text\". (On Tandem, -a is enabled by default, see above).\n", "flag": "-b" }, { "name": "-b -a", "content": "mat. Doubling the option (-bb) forces all files to be extracted in this format. When\nextracting to standard output (-c or -p option in effect), the default conversion of\ntext record delimiters is disabled for binary (-b) resp. all (-bb) files.\n", "flag": "-a" }, { "name": "-B", "content": "The backup file is gets the name of the target file with a tilde and optionally a\nunique sequence number (up to 5 digits) appended. The sequence number is applied\nwhenever another file with the original name plus tilde already exists. When used to‐\ngether with the \"overwrite all\" option -o, numbered backup files are never created. In\nthis case, all backup files are named as the original file with an appended tilde, ex‐\nisting backup files are deleted without notice. This feature works similarly to the\ndefault behavior of emacs(1) in many locations.\n\nExample: the old copy of ``foo'' is renamed to ``foo~''.\n\nWarning: Users should be aware that the -B option does not prevent loss of existing\ndata under all circumstances. For example, when unzip is run in overwrite-all mode,\nan existing ``foo~'' file is deleted before unzip attempts to rename ``foo'' to\n``foo~''. When this rename attempt fails (because of a file locks, insufficient priv‐\nileges, or ...), the extraction of ``foo~'' gets cancelled, but the old backup file is\nalready lost. A similar scenario takes place when the sequence number range for num‐\nbered backup files gets exhausted (99999, or 65535 for 16-bit systems). In this case,\nthe backup file with the maximum sequence number is deleted and replaced by the new\nbackup version without notice.\n", "flag": "-B" }, { "name": "-C", "content": "line list of extract selection patterns. unzip's philosophy is ``you get what you ask\nfor'' (this is also responsible for the -L/-U change; see the relevant options below).\nBecause some file systems are fully case-sensitive (notably those under the Unix oper‐\nating system) and because both ZIP archives and unzip itself are portable across plat‐\nforms, unzip's default behavior is to match both wildcard and literal filenames case-\nsensitively. That is, specifying ``makefile'' on the command line will only match\n``makefile'' in the archive, not ``Makefile'' or ``MAKEFILE'' (and similarly for wild‐\ncard specifications). Since this does not correspond to the behavior of many other\noperating/file systems (for example, OS/2 HPFS, which preserves mixed case but is not\nsensitive to it), the -C option may be used to force all filename matches to be case-\ninsensitive. In the example above, all three files would then match ``makefile'' (or\n``make*'', or similar). The -C option affects file specs in both the normal file list\nand the excluded-file list (xlist).\n\nPlease note that the -C option does neither affect the search for the zipfile(s) nor\nthe matching of archive entries to existing files on the extraction path. On a case-\nsensitive file system, unzip will never try to overwrite a file ``FOO'' when extract‐\ning an entry ``foo''!\n", "flag": "-C" }, { "name": "-D", "content": "all meta-information for extracted items that are supplied in the Zip archive (and do\nnot require privileges or impose a security risk). By specifying -D, unzip is told to\nsuppress restoration of timestamps for directories explicitly created from Zip archive\nentries. This option only applies to ports that support setting timestamps for direc‐\ntories (currently ATheOS, BeOS, MacOS, OS/2, Unix, VMS, Win32, for other unzip ports,\n-D has no effect). The duplicated option -DD forces suppression of timestamp restora‐\ntion for all extracted entries (files and directories). This option results in set‐\nting the timestamps for all extracted entries to the current time.\n\nOn VMS, the default setting for this option is -D for consistency with the behaviour\nof BACKUP: file timestamps are restored, timestamps of extracted directories are left\nat the current time. To enable restoration of directory timestamps, the negated op‐\ntion --D should be specified. On VMS, the option -D disables timestamp restoration\nfor all extracted Zip archive items. (Here, a single -D on the command line combines\nwith the default -D to do what an explicit -DD does on other systems.)\n", "flag": "-D" }, { "name": "-E", "content": "", "flag": "-E" }, { "name": "-F", "content": "", "flag": "-F" }, { "name": "-F", "content": "piled with ACORNFTYPENFS defined] translate filetype information from ACORN RISC OS\nextra field blocks into a NFS filetype extension and append it to the names of the ex‐\ntracted files. (When the stored filename appears to already have an appended NFS\nfiletype extension, it is replaced by the info from the extra field.)\n", "flag": "-F" }, { "name": "-i", "content": "ble filename stored in the generic part of the entry's header is used.\n", "flag": "-i" }, { "name": "-j", "content": "posited in the extraction directory (by default, the current one).\n", "flag": "-j" }, { "name": "-J", "content": "just the file's data.\n", "flag": "-J" }, { "name": "-J", "content": "fork and resource-fork are restored as separate files.\n", "flag": "-J" }, { "name": "-K", "content": "these attribute bits are cleared for security reasons.\n", "flag": "-K" }, { "name": "-L", "content": "file system. (This was unzip's default behavior in releases prior to 5.11; the new\ndefault behavior is identical to the old behavior with the -U option, which is now ob‐\nsolete and will be removed in a future release.) Depending on the archiver, files\narchived under single-case file systems (VMS, old MS-DOS FAT, etc.) may be stored as\nall-uppercase names; this can be ugly or inconvenient when extracting to a case-pre‐\nserving file system such as OS/2 HPFS or a case-sensitive one such as under Unix. By\ndefault unzip lists and extracts such filenames exactly as they're stored (excepting\ntruncation, conversion of unsupported characters, etc.); this option causes the names\nof all files from certain systems to be converted to lowercase. The -LL option forces\nconversion of every filename to lowercase, regardless of the originating file system.\n", "flag": "-L" }, { "name": "-M", "content": "end of a screenful of output, unzip pauses with a ``--More--'' prompt; the next\nscreenful may be viewed by pressing the Enter (Return) key or the space bar. unzip\ncan be terminated by pressing the ``q'' key and, on some systems, the Enter/Return\nkey. Unlike Unix more(1), there is no forward-searching or editing capability. Also,\nunzip doesn't notice if long lines wrap at the edge of the screen, effectively result‐\ning in the printing of two or more lines and the likelihood that some text will scroll\noff the top of the screen before being viewed. On some systems the number of avail‐\nable lines on the screen is not detected, in which case unzip assumes the height is 24\nlines.\n", "flag": "-M" }, { "name": "-n", "content": "file without prompting. By default unzip queries before extracting any file that al‐\nready exists; the user may choose to overwrite only the current file, overwrite all\nfiles, skip extraction of the current file, skip extraction of all existing files, or\nrename the current file.\n", "flag": "-n" }, { "name": "-N", "content": "-c option of zip(1), or with the -N option of the Amiga port of zip(1), which stores\nfilenotes as comments.\n", "flag": "-N" }, { "name": "-o", "content": "with care. (It is often used with -f, however, and is the only way to overwrite di‐\nrectory EAs under OS/2.)\n", "flag": "-o" }, { "name": "-P", "content": "use password to decrypt encrypted zipfile entries (if any). THIS IS INSECURE! Many\nmulti-user operating systems provide ways for any user to see the current command line\nof any other user; even on stand-alone systems there is always the threat of over-the-\nshoulder peeking. Storing the plaintext password as part of a command line in an au‐\ntomated script is even worse. Whenever possible, use the non-echoing, interactive\nprompt to enter passwords. (And where security is truly important, use strong encryp‐\ntion such as Pretty Good Privacy instead of the relatively weak encryption provided by\nstandard zipfile utilities.)\n", "flag": "-P" }, { "name": "-q -qq", "content": "the files it's extracting or testing, the extraction methods, any file or zipfile com‐\nments that may be stored in the archive, and possibly a summary when finished with\neach archive. The -q[q] options suppress the printing of some or all of these mes‐\nsages.\n", "flag": "-q" }, { "name": "-s", "content": "systems allow spaces in filenames, unzip by default extracts filenames with spaces in‐\ntact (e.g., ``EA DATA. SF''). This can be awkward, however, since MS-DOS in particu‐\nlar does not gracefully support spaces in filenames. Conversion of spaces to under‐\nscores can eliminate the awkwardness in some cases.\n", "flag": "-s" }, { "name": "-S -a -aa", "content": "file default, variable-length record format. (StreamLF is the default record format\nof VMS unzip. It is applied unless conversion (-a, -aa and/or -b, -bb) is requested or\na VMS-specific entry is processed.)\n", "flag": "-a" }, { "name": "-U", "content": "available, the option -U forces unzip to escape all non-ASCII characters from UTF-8\ncoded filenames as ``#Uxxxx'' (for UCS-2 characters, or ``#Lxxxxxx'' for unicode code‐\npoints needing 3 octets). This option is mainly provided for debugging purpose when\nthe fairly new UTF-8 support is suspected to mangle up extracted filenames.\n\nThe option -UU allows to entirely disable the recognition of UTF-8 encoded filenames.\nThe handling of filename codings within unzip falls back to the behaviour of previous\nversions.\n\n[old, obsolete usage] leave filenames uppercase if created under MS-DOS, VMS, etc.\nSee -L above.\n", "flag": "-U" }, { "name": "-V", "content": "the format file.ext;##. By default the ``;##'' version numbers are stripped, but this\noption allows them to be retained. (On file systems that limit filenames to particu‐\nlarly short lengths, the version numbers may be truncated or stripped regardless of\nthis option.)\n", "flag": "-V" }, { "name": "-W", "content": "routine so that both `?' (single-char wildcard) and `*' (multi-char wildcard) do not\nmatch the directory separator character `/'. (The two-character sequence ``'' acts\nas a multi-char wildcard that includes the directory separator in its matched charac‐\nters.) Examples:\n\n\"*.c\" matches \"foo.c\" but not \"mydir/foo.c\"\n\".c\" matches both \"foo.c\" and \"mydir/foo.c\"\n\"*/*.c\" matches \"bar/foo.c\" but not \"baz/bar/foo.c\"\n\"??*/*\" matches \"ab/foo\" and \"abc/foo\"\nbut not \"a/foo\" or \"a/b/foo\"\n\nThis modified behaviour is equivalent to the pattern matching style used by the shells\nof some of UnZip's supported target OSs (one example is Acorn RISC OS). This option\nmay not be available on systems where the Zip archive's internal directory separator\ncharacter `/' is allowed as regular character in native operating system filenames.\n(Currently, UnZip uses the same pattern matching rules for both wildcard zipfile spec‐\nifications and zip entry selection patterns in most ports. For systems allowing `/'\nas regular filename character, the -W option would not work as expected on a wildcard\nzipfile specification.)\n", "flag": "-W" }, { "name": "-X", "content": "der VMS, or user and group info (UID/GID) under Unix, or access control lists (ACLs)\nunder certain network-enabled versions of OS/2 (Warp Server with IBM LAN Server/Re‐\nquester 3.0 to 5.0; Warp Connect with IBM Peer 1.0), or security ACLs under Windows\nNT. In most cases this will require special system privileges, and doubling the op‐\ntion (-XX) under NT instructs unzip to use privileges for extraction; but under Unix,\nfor example, a user who belongs to several groups can restore files owned by any of\nthose groups, as long as the user IDs match his or her own. Note that ordinary file\nattributes are always restored--this option applies only to optional, extra ownership\ninfo available on some operating systems. [NT's access control lists do not appear to\nbe especially compatible with OS/2's, so no attempt is made at cross-platform porta‐\nbility of access privileges. It is not clear under what conditions this would ever be\nuseful anyway.]\n", "flag": "-X" }, { "name": "-Y", "content": "ber) as if they were VMS version numbers (``;nnn''). (The default is to treat them as\nfile types.) Example:\n\"a.b.3\" -> \"a.b;3\".\n\n-$ [MS-DOS, OS/2, NT] restore the volume label if the extraction medium is removable\n(e.g., a diskette). Doubling the option (-$$) allows fixed media (hard disks) to be\nlabelled as well. By default, volume labels are ignored.\n\n-/ extensions\n[Acorn only] overrides the extension list supplied by Unzip$Ext environment variable.\nDuring extraction, filename extensions that match one of the items in this extension\nlist are swapped in front of the base name of the extracted file.\n\n-: [all but Acorn, VM/CMS, MVS, Tandem] allows to extract archive members into locations\noutside of the current `` extraction root folder''. For security reasons, unzip nor‐\nmally removes ``parent dir'' path components (``../'') from the names of extracted\nfile. This safety feature (new for version 5.50) prevents unzip from accidentally\nwriting files to ``sensitive'' areas outside the active extraction folder tree head.\nThe -: option lets unzip switch back to its previous, more liberal behaviour, to allow\nexact extraction of (older) archives that used ``../'' components to create multiple\ndirectory trees at the level of the current extraction folder. This option does not\nenable writing explicitly to the root directory (``/''). To achieve this, it is nec‐\nessary to set the extraction target folder to root (e.g. -d / ). However, when the -:\noption is specified, it is still possible to implicitly write to the root directory by\nspecifying enough ``../'' path components within the zip archive. Use this option\nwith extreme caution.\n\n-^ [Unix only] allow control characters in names of extracted ZIP archive entries. On\nUnix, a file name may contain any (8-bit) character code with the two exception '/'\n(directory delimiter) and NUL (0x00, the C string termination indicator), unless the\nspecific file system has more restrictive conventions. Generally, this allows to em‐\nbed ASCII control characters (or even sophisticated control sequences) in file names,\nat least on 'native' Unix file systems. However, it may be highly suspicious to make\nuse of this Unix \"feature\". Embedded control characters in file names might have\nnasty side effects when displayed on screen by some listing code without sufficient\nfiltering. And, for ordinary users, it may be difficult to handle such file names\n(e.g. when trying to specify it for open, copy, move, or delete operations). There‐\nfore, unzip applies a filter by default that removes potentially dangerous control\ncharacters from the extracted file names. The -^ option allows to override this filter\nin the rare case that embedded filename control characters are to be intentionally re‐\nstored.\n", "flag": "-Y" }, { "name": "-2", "content": "default is to exploit the destination file system, preserving case and extended file\nname characters on an ODS5 destination file system; and applying the ODS2-compatibil‐\nity file name filtering on an ODS2 destination file system.\n", "flag": "-2" } ] }, "ENVIRONMENT OPTIONS": { "content": "unzip's default behavior may be modified via options placed in an environment variable. This\ncan be done with any option, but it is probably most useful with the -a, -L, -C, -q, -o, or", "subsections": [ { "name": "-n", "content": "uppercase systems to lowercase, make it match names case-insensitively, make it quieter, or\nmake it always overwrite or never overwrite files as it extracts them. For example, to make\nunzip act as quietly as possible, only reporting errors, one would use one of the following\ncommands:\n\nUnix Bourne shell:\nUNZIP=-qq; export UNZIP\n\nUnix C shell:\nsetenv UNZIP -qq\n\nOS/2 or MS-DOS:\nset UNZIP=-qq\n\nVMS (quotes for lowercase):\ndefine UNZIPOPTS \"-qq\"\n\nEnvironment options are, in effect, considered to be just like any other command-line op‐\ntions, except that they are effectively the first options on the command line. To override\nan environment option, one may use the ``minus operator'' to remove it. For instance, to\noverride one of the quiet-flags in the example above, use the command\n\nunzip --q[other options] zipfile\n\nThe first hyphen is the normal switch character, and the second is a minus sign, acting on\nthe q option. Thus the effect here is to cancel one quantum of quietness. To cancel both\nquiet flags, two (or more) minuses may be used:\n\nunzip -t--q zipfile\nunzip ---qt zipfile\n\n(the two are equivalent). This may seem awkward or confusing, but it is reasonably intu‐\nitive: just ignore the first hyphen and go from there. It is also consistent with the be‐\nhavior of Unix nice(1).\n\nAs suggested by the examples above, the default variable names are UNZIPOPTS for VMS (where\nthe symbol used to install unzip as a foreign command would otherwise be confused with the\nenvironment variable), and UNZIP for all other operating systems. For compatibility with\nzip(1), UNZIPOPT is also accepted (don't ask). If both UNZIP and UNZIPOPT are defined, how‐\never, UNZIP takes precedence. unzip's diagnostic option (-v with no zipfile name) can be\nused to check the values of all four possible unzip and zipinfo environment variables.\n\nThe timezone variable (TZ) should be set according to the local timezone in order for the -f\nand -u to operate correctly. See the description of -f above for details. This variable may\nalso be necessary to get timestamps of extracted files to be set correctly. The WIN32\n(Win9x/ME/NT4/2K/XP/2K3) port of unzip gets the timezone configuration from the registry, as‐\nsuming it is correctly set in the Control Panel. The TZ variable is ignored for this port.\n", "flag": "-n" } ] }, "DECRYPTION": { "content": "Encrypted archives are fully supported by Info-ZIP software, but due to United States export\nrestrictions, de-/encryption support might be disabled in your compiled binary. However,\nsince spring 2000, US export restrictions have been liberated, and our source archives do now\ninclude full crypt code. In case you need binary distributions with crypt support enabled,\nsee the file ``WHERE'' in any Info-ZIP source or binary distribution for locations both in‐\nside and outside the US.\n\nSome compiled versions of unzip may not support decryption. To check a version for crypt\nsupport, either attempt to test or extract an encrypted archive, or else check unzip's diag‐\nnostic screen (see the -v option above) for ``[decryption]'' as one of the special compila‐\ntion options.\n\nAs noted above, the -P option may be used to supply a password on the command line, but at a\ncost in security. The preferred decryption method is simply to extract normally; if a zip‐\nfile member is encrypted, unzip will prompt for the password without echoing what is typed.\nunzip continues to use the same password as long as it appears to be valid, by testing a\n12-byte header on each file. The correct password will always check out against the header,\nbut there is a 1-in-256 chance that an incorrect password will as well. (This is a security\nfeature of the PKWARE zipfile format; it helps prevent brute-force attacks that might other‐\nwise gain a large speed advantage by testing only the header.) In the case that an incorrect\npassword is given but it passes the header test anyway, either an incorrect CRC will be gen‐\nerated for the extracted data or else unzip will fail during the extraction because the ``de‐\ncrypted'' bytes do not constitute a valid compressed data stream.\n\nIf the first password fails the header check on some file, unzip will prompt for another\npassword, and so on until all files are extracted. If a password is not known, entering a\nnull password (that is, just a carriage return or ``Enter'') is taken as a signal to skip all\nfurther prompting. Only unencrypted files in the archive(s) will thereafter be extracted.\n(In fact, that's not quite true; older versions of zip(1) and zipcloak(1) allowed null pass‐\nwords, so unzip checks each encrypted file to see if the null password works. This may re‐\nsult in ``false positives'' and extraction errors, as noted above.)\n\nArchives encrypted with 8-bit passwords (for example, passwords with accented European char‐\nacters) may not be portable across systems and/or other archivers. This problem stems from\nthe use of multiple encoding methods for such characters, including Latin-1 (ISO 8859-1) and\nOEM code page 850. DOS PKZIP 2.04g uses the OEM code page; Windows PKZIP 2.50 uses Latin-1\n(and is therefore incompatible with DOS PKZIP); Info-ZIP uses the OEM code page on DOS, OS/2\nand Win3.x ports but ISO coding (Latin-1 etc.) everywhere else; and Nico Mak's WinZip 6.x\ndoes not allow 8-bit passwords at all. UnZip 5.3 (or newer) attempts to use the default\ncharacter set first (e.g., Latin-1), followed by the alternate one (e.g., OEM code page) to\ntest passwords. On EBCDIC systems, if both of these fail, EBCDIC encoding will be tested as\na last resort. (EBCDIC is not tested on non-EBCDIC systems, because there are no known\narchivers that encrypt using EBCDIC encoding.) ISO character encodings other than Latin-1\nare not supported. The new addition of (partially) Unicode (resp. UTF-8) support in UnZip\n6.0 has not yet been adapted to the encryption password handling in unzip. On systems that\nuse UTF-8 as native character encoding, unzip simply tries decryption with the native UTF-8\nencoded password; the built-in attempts to check the password in translated encoding have not\nyet been adapted for UTF-8 support and will consequently fail.\n", "subsections": [] }, "EXAMPLES": { "content": "To use unzip to extract all members of the archive letters.zip into the current directory and\nsubdirectories below it, creating any subdirectories as necessary:\n\nunzip letters\n\nTo extract all members of letters.zip into the current directory only:\n\nunzip -j letters\n\nTo test letters.zip, printing only a summary message indicating whether the archive is OK or\nnot:\n\nunzip -tq letters\n\nTo test all zipfiles in the current directory, printing only the summaries:\n\nunzip -tq \\*.zip\n\n(The backslash before the asterisk is only required if the shell expands wildcards, as in\nUnix; double quotes could have been used instead, as in the source examples below.) To ex‐\ntract to standard output all members of letters.zip whose names end in .tex, auto-converting\nto the local end-of-line convention and piping the output into more(1):\n\nunzip -ca letters \\*.tex | more\n\nTo extract the binary file paper1.dvi to standard output and pipe it to a printing program:\n\nunzip -p articles paper1.dvi | dvips\n\nTo extract all FORTRAN and C source files--*.f, *.c, *.h, and Makefile--into the /tmp direc‐\ntory:\n\nunzip source.zip \"*.[fch]\" Makefile -d /tmp\n\n(the double quotes are necessary only in Unix and only if globbing is turned on). To extract\nall FORTRAN and C source files, regardless of case (e.g., both *.c and *.C, and any makefile,\nMakefile, MAKEFILE or similar):\n\nunzip -C source.zip \"*.[fch]\" makefile -d /tmp\n\nTo extract any such files but convert any uppercase MS-DOS or VMS names to lowercase and con‐\nvert the line-endings of all of the files to the local standard (without respect to any files\nthat might be marked ``binary''):\n\nunzip -aaCL source.zip \"*.[fch]\" makefile -d /tmp\n\nTo extract only newer versions of the files already in the current directory, without query‐\ning (NOTE: be careful of unzipping in one timezone a zipfile created in another--ZIP ar‐\nchives other than those created by Zip 2.1 or later contain no timezone information, and a\n``newer'' file from an eastern timezone may, in fact, be older):\n\nunzip -fo sources\n\nTo extract newer versions of the files already in the current directory and to create any\nfiles not already there (same caveat as previous example):\n\nunzip -uo sources\n\nTo display a diagnostic screen showing which unzip and zipinfo options are stored in environ‐\nment variables, whether decryption support was compiled in, the compiler with which unzip was\ncompiled, etc.:\n\nunzip -v\n\nIn the last five examples, assume that UNZIP or UNZIPOPTS is set to -q. To do a singly\nquiet listing:\n\nunzip -l file.zip\n\nTo do a doubly quiet listing:\n\nunzip -ql file.zip\n\n(Note that the ``.zip'' is generally not necessary.) To do a standard listing:\n\nunzip --ql file.zip\nor\nunzip -l-q file.zip\nor\nunzip -l--q file.zip\n(Extra minuses in options don't hurt.)\n", "subsections": [] }, "TIPS": { "content": "The current maintainer, being a lazy sort, finds it very useful to define a pair of aliases:\ntt for ``unzip -tq'' and ii for ``unzip -Z'' (or ``zipinfo''). One may then simply type ``tt\nzipfile'' to test an archive, something that is worth making a habit of doing. With luck un‐\nzip will report ``No errors detected in compressed data of zipfile.zip,'' after which one may\nbreathe a sigh of relief.\n\nThe maintainer also finds it useful to set the UNZIP environment variable to ``-aL'' and is\ntempted to add ``-C'' as well. His ZIPINFO variable is set to ``-z''.\n", "subsections": [] }, "DIAGNOSTICS": { "content": "The exit status (or error level) approximates the exit codes defined by PKWARE and takes on\nthe following values, except under VMS:\n\n0 normal; no errors or warnings detected.\n\n1 one or more warning errors were encountered, but processing completed success‐\nfully anyway. This includes zipfiles where one or more files was skipped due\nto unsupported compression method or encryption with an unknown password.\n\n2 a generic error in the zipfile format was detected. Processing may have com‐\npleted successfully anyway; some broken zipfiles created by other archivers\nhave simple work-arounds.\n\n3 a severe error in the zipfile format was detected. Processing probably failed\nimmediately.\n\n4 unzip was unable to allocate memory for one or more buffers during program ini‐\ntialization.\n\n5 unzip was unable to allocate memory or unable to obtain a tty to read the de‐\ncryption password(s).\n\n6 unzip was unable to allocate memory during decompression to disk.\n\n7 unzip was unable to allocate memory during in-memory decompression.\n\n8 [currently not used]\n\n9 the specified zipfiles were not found.\n\n10 invalid options were specified on the command line.\n\n11 no matching files were found.\n\n50 the disk is (or was) full during extraction.\n\n51 the end of the ZIP archive was encountered prematurely.\n\n80 the user aborted unzip prematurely with control-C (or similar)\n\n81 testing or extraction of one or more files failed due to unsupported compres‐\nsion methods or unsupported decryption.\n\n82 no files were found due to bad decryption password(s). (If even one file is\nsuccessfully processed, however, the exit status is 1.)\n\nVMS interprets standard Unix (or PC) return values as other, scarier-looking things, so unzip\ninstead maps them into VMS-style status codes. The current mapping is as follows: 1 (suc‐\ncess) for normal exit, 0x7fff0001 for warning errors, and (0x7fff000? + 16*normalun‐\nzipexitstatus) for all other errors, where the `?' is 2 (error) for unzip values 2, 9-11\nand 80-82, and 4 (fatal error) for the remaining ones (3-8, 50, 51). In addition, there is a\ncompilation option to expand upon this behavior: defining RETURNCODES results in a human-\nreadable explanation of what the error status means.\n", "subsections": [] }, "BUGS": { "content": "Multi-part archives are not yet supported, except in conjunction with zip. (All parts must\nbe concatenated together in order, and then ``zip -F'' (for zip 2.x) or ``zip -FF'' (for zip\n3.x) must be performed on the concatenated archive in order to ``fix'' it. Also, zip 3.0 and\nlater can combine multi-part (split) archives into a combined single-file archive using ``zip\n-s- inarchive -O outarchive''. See the zip 3 manual page for more information.) This will\ndefinitely be corrected in the next major release.\n\nArchives read from standard input are not yet supported, except with funzip (and then only\nthe first member of the archive can be extracted).\n\nArchives encrypted with 8-bit passwords (e.g., passwords with accented European characters)\nmay not be portable across systems and/or other archivers. See the discussion in DECRYPTION\nabove.\n\nunzip's -M (``more'') option tries to take into account automatic wrapping of long lines.\nHowever, the code may fail to detect the correct wrapping locations. First, TAB characters\n(and similar control sequences) are not taken into account, they are handled as ordinary\nprintable characters. Second, depending on the actual system / OS port, unzip may not detect\nthe true screen geometry but rather rely on \"commonly used\" default dimensions. The correct\nhandling of tabs would require the implementation of a query for the actual tabulator setup\non the output console.\n\nDates, times and permissions of stored directories are not restored except under Unix. (On\nWindows NT and successors, timestamps are now restored.)\n\n[MS-DOS] When extracting or testing files from an archive on a defective floppy diskette, if\nthe ``Fail'' option is chosen from DOS's ``Abort, Retry, Fail?'' message, older versions of\nunzip may hang the system, requiring a reboot. This problem appears to be fixed, but con‐\ntrol-C (or control-Break) can still be used to terminate unzip.\n\nUnder DEC Ultrix, unzip would sometimes fail on long zipfiles (bad CRC, not always repro‐\nducible). This was apparently due either to a hardware bug (cache memory) or an operating\nsystem bug (improper handling of page faults?). Since Ultrix has been abandoned in favor of\nDigital Unix (OSF/1), this may not be an issue anymore.\n\n[Unix] Unix special files such as FIFO buffers (named pipes), block devices and character de‐\nvices are not restored even if they are somehow represented in the zipfile, nor are hard-\nlinked files relinked. Basically the only file types restored by unzip are regular files,\ndirectories and symbolic (soft) links.\n\n[OS/2] Extended attributes for existing directories are only updated if the -o (``overwrite\nall'') option is given. This is a limitation of the operating system; because directories\nonly have a creation time associated with them, unzip has no way to determine whether the\nstored attributes are newer or older than those on disk. In practice this may mean a two-\npass approach is required: first unpack the archive normally (with or without freshening/up‐\ndating existing files), then overwrite just the directory entries (e.g., ``unzip -o foo\n*/'').\n\n[VMS] When extracting to another directory, only the [.foo] syntax is accepted for the -d op‐\ntion; the simple Unix foo syntax is silently ignored (as is the less common VMS foo.dir syn‐\ntax).\n\n[VMS] When the file being extracted already exists, unzip's query only allows skipping, over‐\nwriting or renaming; there should additionally be a choice for creating a new version of the\nfile. In fact, the ``overwrite'' choice does create a new version; the old version is not\noverwritten or deleted.\n", "subsections": [] }, "SEE ALSO": { "content": "funzip(1), zip(1), zipcloak(1), zipgrep(1), zipinfo(1), zipnote(1), zipsplit(1)\n", "subsections": [] }, "URL": { "content": "The Info-ZIP home page is currently at\nhttp://www.info-zip.org/pub/infozip/\nor\nftp://ftp.info-zip.org/pub/infozip/ .\n", "subsections": [] }, "AUTHORS": { "content": "The primary Info-ZIP authors (current semi-active members of the Zip-Bugs workgroup) are: Ed\nGordon (Zip, general maintenance, shared code, Zip64, Win32, Unix, Unicode); Christian\nSpieler (UnZip maintenance coordination, VMS, MS-DOS, Win32, shared code, general Zip and Un‐\nZip integration and optimization); Onno van der Linden (Zip); Mike White (Win32, Windows GUI,\nWindows DLLs); Kai Uwe Rommel (OS/2, Win32); Steven M. Schweda (VMS, Unix, support of new\nfeatures); Paul Kienitz (Amiga, Win32, Unicode); Chris Herborth (BeOS, QNX, Atari); Jonathan\nHudson (SMS/QDOS); Sergio Monesi (Acorn RISC OS); Harald Denker (Atari, MVS); John Bush (So‐\nlaris, Amiga); Hunter Goatley (VMS, Info-ZIP Site maintenance); Steve Salisbury (Win32);\nSteve Miller (Windows CE GUI), Johnny Lee (MS-DOS, Win32, Zip64); and Dave Smith (Tandem\nNSK).\n\nThe following people were former members of the Info-ZIP development group and provided major\ncontributions to key parts of the current code: Greg ``Cave Newt'' Roelofs (UnZip, unshrink\ndecompression); Jean-loup Gailly (deflate compression); Mark Adler (inflate decompression,\nfUnZip).\n\nThe author of the original unzip code upon which Info-ZIP's was based is Samuel H. Smith;\nCarl Mascott did the first Unix port; and David P. Kirschbaum organized and led Info-ZIP in\nits early days with Keith Petersen hosting the original mailing list at WSMR-SimTel20. The\nfull list of contributors to UnZip has grown quite large; please refer to the CONTRIBS file\nin the UnZip source distribution for a relatively complete version.\n", "subsections": [] }, "VERSIONS": { "content": "v1.2 15 Mar 89 Samuel H. Smith\nv2.0 9 Sep 89 Samuel H. Smith\nv2.x fall 1989 many Usenet contributors\nv3.0 1 May 90 Info-ZIP (DPK, consolidator)\nv3.1 15 Aug 90 Info-ZIP (DPK, consolidator)\nv4.0 1 Dec 90 Info-ZIP (GRR, maintainer)\nv4.1 12 May 91 Info-ZIP\nv4.2 20 Mar 92 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.0 21 Aug 92 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.01 15 Jan 93 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.1 7 Feb 94 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.11 2 Aug 94 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.12 28 Aug 94 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.2 30 Apr 96 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.3 22 Apr 97 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.31 31 May 97 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.32 3 Nov 97 Info-ZIP (Zip-Bugs subgroup, GRR)\nv5.4 28 Nov 98 Info-ZIP (Zip-Bugs subgroup, SPC)\nv5.41 16 Apr 00 Info-ZIP (Zip-Bugs subgroup, SPC)\nv5.42 14 Jan 01 Info-ZIP (Zip-Bugs subgroup, SPC)\nv5.5 17 Feb 02 Info-ZIP (Zip-Bugs subgroup, SPC)\nv5.51 22 May 04 Info-ZIP (Zip-Bugs subgroup, SPC)\nv5.52 28 Feb 05 Info-ZIP (Zip-Bugs subgroup, SPC)\nv6.0 20 Apr 09 Info-ZIP (Zip-Bugs subgroup, SPC)\n\n\n\nInfo-ZIP 20 April 2009 (v6.0) UNZIP(1)", "subsections": [] } }, "summary": "unzip - list, test and extract compressed files in a ZIP archive", "flags": [ { "flag": "-Z", "long": null, "arg": null, "description": "are taken to be zipinfo(1) options. See the appropriate manual page for a description of these options." }, { "flag": "-A", "long": null, "arg": null, "description": "" }, { "flag": "-p", "long": null, "arg": null, "description": "cept that the name of each file is printed as it is extracted, the -a option is al‐ lowed, and ASCII-EBCDIC conversion is automatically performed if appropriate. This option is not listed in the unzip usage screen." }, { "flag": "-f", "long": null, "arg": null, "description": "that are newer than the disk copies. By default unzip queries before overwriting, but the -o option may be used to suppress the queries. Note that under many operating systems, the TZ (timezone) environment variable must be set correctly in order for -f and -u to work properly (under Unix the variable is usually set automatically). The reasons for this are somewhat subtle but have to do with the differences between DOS- format file times (always local time) and Unix-format times (always in GMT/UTC) and the necessity to compare the two. A typical TZ value is ``PST8PDT'' (US Pacific time with automatic adjustment for Daylight Savings Time or ``summer time'')." }, { "flag": "-l", "long": null, "arg": null, "description": "tion dates and times of the specified files are printed, along with totals for all files specified. If UnZip was compiled with OS2EAS defined, the -l option also lists columns for the sizes of stored OS/2 extended attributes (EAs) and OS/2 access control lists (ACLs). In addition, the zipfile comment and individual file comments (if any) are displayed. If a file was archived from a single-case file system (for example, the old MS-DOS FAT file system) and the -L option was given, the filename is converted to lowercase and is prefixed with a caret (^)." }, { "flag": "-p", "long": null, "arg": null, "description": "files are always extracted in binary format, just as they are stored (no conversions)." }, { "flag": "-t", "long": null, "arg": null, "description": "the CRC (cyclic redundancy check, an enhanced checksum) of the expanded file with the original file's stored CRC value." }, { "flag": "-T", "long": null, "arg": null, "description": "one. This corresponds to zip's -go option except that it can be used on wildcard zip‐ files (e.g., ``unzip -T \\*.zip'') and is much faster." }, { "flag": "-u", "long": null, "arg": null, "description": "function as the -f option, extracting (with query) files that are newer than those with the same name on disk, and in addition it extracts those files that do not al‐ ready exist on disk. See -f above for information on setting the timezone properly." }, { "flag": "-v", "long": null, "arg": null, "description": "evolved and now behaves as both an option and a modifier. As an option it has two purposes: when a zipfile is specified with no other options, -v lists archive files verbosely, adding to the basic -l info the compression method, compressed size, com‐ pression ratio and 32-bit CRC. In contrast to most of the competing utilities, unzip removes the 12 additional header bytes of encrypted entries from the compressed size numbers. Therefore, compressed size and compression ratio figures are independent of the entry's encryption status and show the correct compression performance. (The com‐ plete size of the encrypted compressed data stream for zipfile entries is reported by the more verbose zipinfo(1) reports, see the separate manual.) When no zipfile is specified (that is, the complete command is simply ``unzip -v''), a diagnostic screen is printed. In addition to the normal header with release date and version, unzip lists the home Info-ZIP ftp site and where to find a list of other ftp and non-ftp sites; the target operating system for which it was compiled, as well as (possibly) the hardware on which it was compiled, the compiler and version used, and the compila‐ tion date; any special compilation options that might affect the program's operation (see also DECRYPTION below); and any options stored in environment variables that might do the same (see ENVIRONMENT OPTIONS below). As a modifier it works in conjunc‐ tion with other options (e.g., -t) to produce more verbose or debugging output; this is not yet fully implemented but will be in future releases." }, { "flag": "-z", "long": null, "arg": null, "description": "" } ], "examples": [ "To use unzip to extract all members of the archive letters.zip into the current directory and", "subdirectories below it, creating any subdirectories as necessary:", "unzip letters", "To extract all members of letters.zip into the current directory only:", "unzip -j letters", "To test letters.zip, printing only a summary message indicating whether the archive is OK or", "not:", "unzip -tq letters", "To test all zipfiles in the current directory, printing only the summaries:", "unzip -tq \\*.zip", "(The backslash before the asterisk is only required if the shell expands wildcards, as in", "Unix; double quotes could have been used instead, as in the source examples below.) To ex‐", "tract to standard output all members of letters.zip whose names end in .tex, auto-converting", "to the local end-of-line convention and piping the output into more(1):", "unzip -ca letters \\*.tex | more", "To extract the binary file paper1.dvi to standard output and pipe it to a printing program:", "unzip -p articles paper1.dvi | dvips", "To extract all FORTRAN and C source files--*.f, *.c, *.h, and Makefile--into the /tmp direc‐", "tory:", "unzip source.zip \"*.[fch]\" Makefile -d /tmp", "(the double quotes are necessary only in Unix and only if globbing is turned on). To extract", "all FORTRAN and C source files, regardless of case (e.g., both *.c and *.C, and any makefile,", "Makefile, MAKEFILE or similar):", "unzip -C source.zip \"*.[fch]\" makefile -d /tmp", "To extract any such files but convert any uppercase MS-DOS or VMS names to lowercase and con‐", "vert the line-endings of all of the files to the local standard (without respect to any files", "that might be marked ``binary''):", "unzip -aaCL source.zip \"*.[fch]\" makefile -d /tmp", "To extract only newer versions of the files already in the current directory, without query‐", "ing (NOTE: be careful of unzipping in one timezone a zipfile created in another--ZIP ar‐", "chives other than those created by Zip 2.1 or later contain no timezone information, and a", "``newer'' file from an eastern timezone may, in fact, be older):", "unzip -fo sources", "To extract newer versions of the files already in the current directory and to create any", "files not already there (same caveat as previous example):", "unzip -uo sources", "To display a diagnostic screen showing which unzip and zipinfo options are stored in environ‐", "ment variables, whether decryption support was compiled in, the compiler with which unzip was", "compiled, etc.:", "unzip -v", "In the last five examples, assume that UNZIP or UNZIPOPTS is set to -q. To do a singly", "quiet listing:", "unzip -l file.zip", "To do a doubly quiet listing:", "unzip -ql file.zip", "(Note that the ``.zip'' is generally not necessary.) To do a standard listing:", "unzip --ql file.zip", "or", "unzip -l-q file.zip", "or", "unzip -l--q file.zip", "(Extra minuses in options don't hurt.)" ], "see_also": [ { "name": "funzip", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/funzip/1/json" }, { "name": "zip", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zip/1/json" }, { "name": "zipcloak", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zipcloak/1/json" }, { "name": "zipgrep", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zipgrep/1/json" }, { "name": "zipinfo", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zipinfo/1/json" }, { "name": "zipnote", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zipnote/1/json" }, { "name": "zipsplit", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zipsplit/1/json" } ] }