{ "mode": "man", "parameter": "zip", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/zip/1/json", "generated": "2026-06-03T00:25:14Z", "synopsis": "zip [-aABcdDeEfFghjklLmoqrRSTuvVwXyz!@$] [--longoption ...] [-b path] [-n suffixes] [-t\ndate] [-tt date] [zipfile [file ...]] [-xi list]\nzipcloak (see separate man page)\nzipnote (see separate man page)\nzipsplit (see separate man page)\nNote: Command line processing in zip has been changed to support long options and handle all\noptions and arguments more consistently. Some old command lines that depend on command line\ninconsistencies may no longer work.", "sections": { "NAME": { "content": "zip - package and compress (archive) files\n", "subsections": [] }, "SYNOPSIS": { "content": "zip [-aABcdDeEfFghjklLmoqrRSTuvVwXyz!@$] [--longoption ...] [-b path] [-n suffixes] [-t\ndate] [-tt date] [zipfile [file ...]] [-xi list]\n\nzipcloak (see separate man page)\n\nzipnote (see separate man page)\n\nzipsplit (see separate man page)\n\nNote: Command line processing in zip has been changed to support long options and handle all\noptions and arguments more consistently. Some old command lines that depend on command line\ninconsistencies may no longer work.\n", "subsections": [] }, "DESCRIPTION": { "content": "zip is a compression and file packaging utility for Unix, VMS, MSDOS, OS/2, Windows 9x/NT/XP,\nMinix, Atari, Macintosh, Amiga, and Acorn RISC OS. It is analogous to a combination of the\nUnix commands tar(1) and compress(1) and is compatible with PKZIP (Phil Katz's ZIP for MSDOS\nsystems).\n\nA companion program (unzip(1)) unpacks zip archives. The zip and unzip(1) programs can work\nwith archives produced by PKZIP (supporting most PKZIP features up to PKZIP version 4.6), and\nPKZIP and PKUNZIP can work with archives produced by zip (with some exceptions, notably\nstreamed archives, but recent changes in the zip file standard may facilitate better compati‐\nbility). zip version 3.0 is compatible with PKZIP 2.04 and also supports the Zip64 exten‐\nsions of PKZIP 4.5 which allow archives as well as files to exceed the previous 2 GB limit (4\nGB in some cases). zip also now supports bzip2 compression if the bzip2 library is included\nwhen zip is compiled. Note that PKUNZIP 1.10 cannot extract files produced by PKZIP 2.04 or\nzip 3.0. You must use PKUNZIP 2.04g or unzip 5.0p1 (or later versions) to extract them.\n\nSee the EXAMPLES section at the bottom of this page for examples of some typical uses of zip.\n\nLarge Archives and Zip64. zip automatically uses the Zip64 extensions when files larger than\n4 GB are added to an archive, an archive containing Zip64 entries is updated (if the result‐\ning archive still needs Zip64), the size of the archive will exceed 4 GB, or when the number\nof entries in the archive will exceed about 64K. Zip64 is also used for archives streamed\nfrom standard input as the size of such archives are not known in advance, but the option", "subsections": [ { "name": "-fz-", "content": "sions are not needed). You must use a PKZIP 4.5 compatible unzip, such as unzip 6.0 or\nlater, to extract files using the Zip64 extensions.\n\nIn addition, streamed archives, entries encrypted with standard encryption, or split archives\ncreated with the pause option may not be compatible with PKZIP as data descriptors are used\nand PKZIP at the time of this writing does not support data descriptors (but recent changes\nin the PKWare published zip standard now include some support for the data descriptor format\nzip uses).\n\n\nMac OS X. Though previous Mac versions had their own zip port, zip supports Mac OS X as part\nof the Unix port and most Unix features apply. References to \"MacOS\" below generally refer\nto MacOS versions older than OS X. Support for some Mac OS features in the Unix Mac OS X\nport, such as resource forks, is expected in the next zip release.\n\n\nFor a brief help on zip and unzip, run each without specifying any parameters on the command\nline.\n\n" } ] }, "USE": { "content": "The program is useful for packaging a set of files for distribution; for archiving files; and\nfor saving disk space by temporarily compressing unused files or directories.\n\nThe zip program puts one or more compressed files into a single zip archive, along with in‐\nformation about the files (name, path, date, time of last modification, protection, and check\ninformation to verify file integrity). An entire directory structure can be packed into a\nzip archive with a single command. Compression ratios of 2:1 to 3:1 are common for text\nfiles. zip has one compression method (deflation) and can also store files without compres‐\nsion. (If bzip2 support is added, zip can also compress using bzip2 compression, but such\nentries require a reasonably modern unzip to decompress. When bzip2 compression is selected,\nit replaces deflation as the default method.) zip automatically chooses the better of the\ntwo (deflation or store or, if bzip2 is selected, bzip2 or store) for each file to be com‐\npressed.\n\nCommand format. The basic command format is\n\nzip options archive inpath inpath ...\n\nwhere archive is a new or existing zip archive and inpath is a directory or file path option‐\nally including wildcards. When given the name of an existing zip archive, zip will replace\nidentically named entries in the zip archive (matching the relative names as stored in the\narchive) or add entries for new names. For example, if foo.zip exists and contains foo/file1\nand foo/file2, and the directory foo contains the files foo/file1 and foo/file3, then:\n\nzip -r foo.zip foo\n\nor more concisely\n\nzip -r foo foo\n\nwill replace foo/file1 in foo.zip and add foo/file3 to foo.zip. After this, foo.zip contains\nfoo/file1, foo/file2, and foo/file3, with foo/file2 unchanged from before.\n\nSo if before the zip command is executed foo.zip has:\n\nfoo/file1 foo/file2\n\nand directory foo has:\n\nfile1 file3\n\nthen foo.zip will have:\n\nfoo/file1 foo/file2 foo/file3\n\nwhere foo/file1 is replaced and foo/file3 is new.\n\n-@ file lists. If a file list is specified as -@ [Not on MacOS], zip takes the list of input\nfiles from standard input instead of from the command line. For example,\n\nzip -@ foo\n\nwill store the files listed one per line on stdin in foo.zip.\n\nUnder Unix, this option can be used to powerful effect in conjunction with the find (1) com‐\nmand. For example, to archive all the C source files in the current directory and its subdi‐\nrectories:\n\nfind . -name \"*.[ch]\" -print | zip source -@\n\n(note that the pattern must be quoted to keep the shell from expanding it).\n\nStreaming input and output. zip will also accept a single dash (\"-\") as the zip file name,\nin which case it will write the zip file to standard output, allowing the output to be piped\nto another program. For example:\n\nzip -r - . | dd of=/dev/nrst0 obs=16k\n\nwould write the zip output directly to a tape with the specified block size for the purpose\nof backing up the current directory.\n\nzip also accepts a single dash (\"-\") as the name of a file to be compressed, in which case it\nwill read the file from standard input, allowing zip to take input from another program. For\nexample:\n\ntar cf - . | zip backup -\n\nwould compress the output of the tar command for the purpose of backing up the current direc‐\ntory. This generally produces better compression than the previous example using the -r op‐\ntion because zip can take advantage of redundancy between files. The backup can be restored\nusing the command\n\nunzip -p backup | tar xf -\n\nWhen no zip file name is given and stdout is not a terminal, zip acts as a filter, compress‐\ning standard input to standard output. For example,\n\ntar cf - . | zip | dd of=/dev/nrst0 obs=16k\n\nis equivalent to\n\ntar cf - . | zip - - | dd of=/dev/nrst0 obs=16k\n\nzip archives created in this manner can be extracted with the program funzip which is pro‐\nvided in the unzip package, or by gunzip which is provided in the gzip package (but some gun‐\nzip may not support this if zip used the Zip64 extensions). For example:\n\ndd if=/dev/nrst0 ibs=16k | funzip | tar xvf -\n\nThe stream can also be saved to a file and unzip used.\n\nIf Zip64 support for large files and archives is enabled and zip is used as a filter, zip\ncreates a Zip64 archive that requires a PKZIP 4.5 or later compatible unzip to read it. This\nis to avoid ambiguities in the zip file structure as defined in the current zip standard\n(PKWARE AppNote) where the decision to use Zip64 needs to be made before data is written for\nthe entry, but for a stream the size of the data is not known at that point. If the data is\nknown to be smaller than 4 GB, the option -fz- can be used to prevent use of Zip64, but zip\nwill exit with an error if Zip64 was in fact needed. zip 3 and unzip 6 and later can read\narchives with Zip64 entries. Also, zip removes the Zip64 extensions if not needed when ar‐\nchive entries are copied (see the -U (--copy) option).\n\nWhen directing the output to another file, note that all options should be before the redi‐\nrection including -x. For example:\n\nzip archive \"*.h\" \"*.c\" -x donotinclude.h orthis.h > tofile\n\nZip files. When changing an existing zip archive, zip will write a temporary file with the\nnew contents, and only replace the old one when the process of creating the new version has\nbeen completed without error.\n\nIf the name of the zip archive does not contain an extension, the extension .zip is added. If\nthe name already contains an extension other than .zip, the existing extension is kept un‐\nchanged. However, split archives (archives split over multiple files) require the .zip ex‐\ntension on the last split.\n\nScanning and reading files. When zip starts, it scans for files to process (if needed). If\nthis scan takes longer than about 5 seconds, zip will display a \"Scanning files\" message and\nstart displaying progress dots every 2 seconds or every so many entries processed, whichever\ntakes longer. If there is more than 2 seconds between dots it could indicate that finding\neach file is taking time and could mean a slow network connection for example. (Actually the\ninitial file scan is a two-step process where the directory scan is followed by a sort and\nthese two steps are separated with a space in the dots. If updating an existing archive, a\nspace also appears between the existing file scan and the new file scan.) The scanning files\ndots are not controlled by the -ds dot size option, but the dots are turned off by the -q\nquiet option. The -sf show files option can be used to scan for files and get the list of\nfiles scanned without actually processing them.\n\nIf zip is not able to read a file, it issues a warning but continues. See the -MM option be‐\nlow for more on how zip handles patterns that are not matched and files that are not read‐\nable. If some files were skipped, a warning is issued at the end of the zip operation noting\nhow many files were read and how many skipped.\n\nCommand modes. zip now supports two distinct types of command modes, external and internal.\nThe external modes (add, update, and freshen) read files from the file system (as well as\nfrom an existing archive) while the internal modes (delete and copy) operate exclusively on\nentries in an existing archive.\n", "subsections": [ { "name": "add", "content": "Update existing entries and add new files. If the archive does not exist create it.\nThis is the default mode.\n\nupdate (-u)\nUpdate existing entries if newer on the file system and add new files. If the archive\ndoes not exist issue warning then create a new archive.\n\nfreshen (-f)\nUpdate existing entries of an archive if newer on the file system. Does not add new\nfiles to the archive.\n\ndelete (-d)\nSelect entries in an existing archive and delete them.\n\ncopy (-U)\nSelect entries in an existing archive and copy them to a new archive. This new mode\nis similar to update but command line patterns select entries in the existing archive\nrather than files from the file system and it uses the --out option to write the re‐\nsulting archive to a new file rather than update the existing archive, leaving the\noriginal archive unchanged.\n\nThe new File Sync option (-FS) is also considered a new mode, though it is similar to update.\nThis mode synchronizes the archive with the files on the OS, only replacing files in the ar‐\nchive if the file time or size of the OS file is different, adding new files, and deleting\nentries from the archive where there is no matching file. As this mode can delete entries\nfrom the archive, consider making a backup copy of the archive.\n\nAlso see -DF for creating difference archives.\n\nSee each option description below for details and the EXAMPLES section below for examples.\n\nSplit archives. zip version 3.0 and later can create split archives. A split archive is a\nstandard zip archive split over multiple files. (Note that split archives are not just ar‐\nchives split in to pieces, as the offsets of entries are now based on the start of each\nsplit. Concatenating the pieces together will invalidate these offsets, but unzip can usu‐\nally deal with it. zip will usually refuse to process such a spliced archive unless the -FF\nfix option is used to fix the offsets.)\n\nOne use of split archives is storing a large archive on multiple removable media. For a\nsplit archive with 20 split files the files are typically named (replace ARCHIVE with the\nname of your archive) ARCHIVE.z01, ARCHIVE.z02, ..., ARCHIVE.z19, ARCHIVE.zip. Note that the\nlast file is the .zip file. In contrast, spanned archives are the original multi-disk ar‐\nchive generally requiring floppy disks and using volume labels to store disk numbers. zip\nsupports split archives but not spanned archives, though a procedure exists for converting\nsplit archives of the right size to spanned archives. The reverse is also true, where each\nfile of a spanned archive can be copied in order to files with the above names to create a\nsplit archive.\n\nUse -s to set the split size and create a split archive. The size is given as a number fol‐\nlowed optionally by one of k (kB), m (MB), g (GB), or t (TB) (the default is m). The -sp op‐\ntion can be used to pause zip between splits to allow changing removable media, for example,\nbut read the descriptions and warnings for both -s and -sp below.\n\nThough zip does not update split archives, zip provides the new option -O (--output-file or\n--out) to allow split archives to be updated and saved in a new archive. For example,\n\nzip inarchive.zip foo.c bar.c --out outarchive.zip\n\nreads archive inarchive.zip, even if split, adds the files foo.c and bar.c, and writes the\nresulting archive to outarchive.zip. If inarchive.zip is split then outarchive.zip defaults\nto the same split size. Be aware that if outarchive.zip and any split files that are created\nwith it already exist, these are always overwritten as needed without warning. This may be\nchanged in the future.\n\nUnicode. Though the zip standard requires storing paths in an archive using a specific char‐\nacter set, in practice zips have stored paths in archives in whatever the local character set\nis. This creates problems when an archive is created or updated on a system using one char‐\nacter set and then extracted on another system using a different character set. When com‐\npiled with Unicode support enabled on platforms that support wide characters, zip now stores,\nin addition to the standard local path for backward compatibility, the UTF-8 translation of\nthe path. This provides a common universal character set for storing paths that allows these\npaths to be fully extracted on other systems that support Unicode and to match as close as\npossible on systems that don't.\n\nOn Win32 systems where paths are internally stored as Unicode but represented in the local\ncharacter set, it's possible that some paths will be skipped during a local character set di‐\nrectory scan. zip with Unicode support now can read and store these paths. Note that Win 9x\nsystems and FAT file systems don't fully support Unicode.\n\nBe aware that console windows on Win32 and Unix, for example, sometimes don't accurately show\nall characters due to how each operating system switches in character sets for display. How‐\never, directory navigation tools should show the correct paths if the needed fonts are\nloaded.\n\nCommand line format. This version of zip has updated command line processing and support for\nlong options.\n\nShort options take the form\n\n-s[-][s[-]...][value][=value][ value]\n\nwhere s is a one or two character short option. A short option that takes a value is last in\nan argument and anything after it is taken as the value. If the option can be negated and\n\"-\" immediately follows the option, the option is negated. Short options can also be given\nas separate arguments\n\n-s[-][value][=value][ value] -s[-][value][=value][ value] ...\n\nShort options in general take values either as part of the same argument or as the following\nargument. An optional = is also supported. So\n\n-ttmmddyyyy\n\nand\n\n-tt=mmddyyyy\n\nand\n\n-tt mmddyyyy\n\nall work. The -x and -i options accept lists of values and use a slightly different format\ndescribed below. See the -x and -i options.\n\nLong options take the form\n\n--longoption[-][=value][ value]\n\nwhere the option starts with --, has a multicharacter name, can include a trailing dash to\nnegate the option (if the option supports it), and can have a value (option argument) speci‐\nfied by preceding it with = (no spaces). Values can also follow the argument. So\n\n--before-date=mmddyyyy\n\nand\n\n--before-date mmddyyyy\n\nboth work.\n\nLong option names can be shortened to the shortest unique abbreviation. See the option de‐\nscriptions below for which support long options. To avoid confusion, avoid abbreviating a\nnegatable option with an embedded dash (\"-\") at the dash if you plan to negate it (the parser\nwould consider a trailing dash, such as for the option --some-option using --some- as the op‐\ntion, as part of the name rather than a negating dash). This may be changed to force the\nlast dash in --some- to be negating in the future.\n" } ] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-a", "content": "", "flag": "-a" }, { "name": "--ascii", "content": "[Systems using EBCDIC] Translate file to ASCII format.\n\n", "long": "--ascii" }, { "name": "-A", "content": "", "flag": "-A" }, { "name": "--adjust-sfx", "content": "Adjust self-extracting executable archive. A self-extracting executable archive is\ncreated by prepending the SFX stub to an existing archive. The -A option tells zip to\nadjust the entry offsets stored in the archive to take into account this \"preamble\"\ndata.\n\nNote: self-extracting archives for the Amiga are a special case. At present, only the Amiga\nport of zip is capable of adjusting or updating these without corrupting them. -J can be used\nto remove the SFX stub if other updates need to be made.\n\n", "long": "--adjust-sfx" }, { "name": "-AC", "content": "" }, { "name": "--archive-clear", "content": "[WIN32] Once archive is created (and tested if -T is used, which is recommended),\nclear the archive bits of files processed. WARNING: Once the bits are cleared they\nare cleared. You may want to use the -sf show files option to store the list of files\nprocessed in case the archive operation must be repeated. Also consider using the -MM\nmust match option. Be sure to check out -DF as a possibly better way to do incremen‐\ntal backups.\n\n", "long": "--archive-clear" }, { "name": "-AS", "content": "" }, { "name": "--archive-set", "content": "[WIN32] Only include files that have the archive bit set. Directories are not stored\nwhen -AS is used, though by default the paths of entries, including directories, are\nstored as usual and can be used by most unzips to recreate directories.\n\nThe archive bit is set by the operating system when a file is modified and, if used\nwith -AC, -AS can provide an incremental backup capability. However, other applica‐\ntions can modify the archive bit and it may not be a reliable indicator of which files\nhave changed since the last archive operation. Alternative ways to create incremental\nbackups are using -t to use file dates, though this won't catch old files copied to\ndirectories being archived, and -DF to create a differential archive.\n\n", "long": "--archive-set" }, { "name": "-B", "content": "", "flag": "-B" }, { "name": "--binary", "content": "[VM/CMS and MVS] force file to be read binary (default is text).\n\n", "long": "--binary" }, { "name": "-B", "content": "bit 0: Don't add delimiter (Edit/Enscribe)\nbit 1: Use LF rather than CR/LF as delimiter (Edit/Enscribe)\nbit 2: Space fill record to maximum record length (Enscribe)\nbit 3: Trim trailing space (Enscribe)\nbit 8: Force 30K (Expand) large read for unstructured files\n\n", "flag": "-B" }, { "name": "-b", "content": "--temp-path path\nUse the specified path for the temporary zip archive. For example:\n\nzip -b /tmp stuff *\n\nwill put the temporary zip archive in the directory /tmp, copying over stuff.zip to\nthe current directory when done. This option is useful when updating an existing ar‐\nchive and the file system containing this old archive does not have enough space to\nhold both old and new archives at the same time. It may also be useful when streaming\nin some cases to avoid the need for data descriptors. Note that using this option may\nrequire zip take additional time to copy the archive file when done to the destination\nfile system.\n\n", "flag": "-b" }, { "name": "-c", "content": "", "flag": "-c" }, { "name": "--entry-comments", "content": "Add one-line comments for each file. File operations (adding, updating) are done\nfirst, and the user is then prompted for a one-line comment for each file. Enter the\ncomment followed by return, or just return for no comment.\n\n", "long": "--entry-comments" }, { "name": "-C", "content": "", "flag": "-C" }, { "name": "--preserve-case", "content": "[VMS] Preserve case all on VMS. Negating this option (-C-) downcases.\n\n", "long": "--preserve-case" }, { "name": "-C2", "content": "" }, { "name": "--preserve-case-2", "content": "[VMS] Preserve case ODS2 on VMS. Negating this option (-C2-) downcases.\n\n", "long": "--preserve-case-2" }, { "name": "-C5", "content": "" }, { "name": "--preserve-case-5", "content": "[VMS] Preserve case ODS5 on VMS. Negating this option (-C5-) downcases.\n\n", "long": "--preserve-case-5" }, { "name": "-d", "content": "", "flag": "-d" }, { "name": "--delete", "content": "Remove (delete) entries from a zip archive. For example:\n\nzip -d foo foo/tom/junk foo/harry/\\* \\*.o\n\nwill remove the entry foo/tom/junk, all of the files that start with foo/harry/, and\nall of the files that end with .o (in any path). Note that shell pathname expansion\nhas been inhibited with backslashes, so that zip can see the asterisks, enabling zip\nto match on the contents of the zip archive instead of the contents of the current di‐\nrectory. (The backslashes are not used on MSDOS-based platforms.) Can also use\nquotes to escape the asterisks as in\n\nzip -d foo foo/tom/junk \"foo/harry/*\" \"*.o\"\n\nNot escaping the asterisks on a system where the shell expands wildcards could result\nin the asterisks being converted to a list of files in the current directory and that\nlist used to delete entries from the archive.\n\nUnder MSDOS, -d is case sensitive when it matches names in the zip archive. This re‐\nquires that file names be entered in upper case if they were zipped by PKZIP on an MS‐\nDOS system. (We considered making this case insensitive on systems where paths were\ncase insensitive, but it is possible the archive came from a system where case does\nmatter and the archive could include both Bar and bar as separate files in the ar‐\nchive.) But see the new option -ic to ignore case in the archive.\n\n", "long": "--delete" }, { "name": "-db", "content": "" }, { "name": "--display-bytes", "content": "Display running byte counts showing the bytes zipped and the bytes to go.\n\n", "long": "--display-bytes" }, { "name": "-dc", "content": "" }, { "name": "--display-counts", "content": "Display running count of entries zipped and entries to go.\n\n", "long": "--display-counts" }, { "name": "-dd", "content": "" }, { "name": "--display-dots", "content": "Display dots while each entry is zipped (except on ports that have their own progress\nindicator). See -ds below for setting dot size. The default is a dot every 10 MB of\ninput file processed. The -v option also displays dots (previously at a much higher\nrate than this but now -v also defaults to 10 MB) and this rate is also controlled by\n-ds.\n\n", "long": "--display-dots" }, { "name": "-df", "content": "" }, { "name": "--datafork", "content": "[MacOS] Include only data-fork of files zipped into the archive. Good for exporting\nfiles to foreign operating-systems. Resource-forks will be ignored at all.\n\n", "long": "--datafork" }, { "name": "-dg", "content": "" }, { "name": "--display-globaldots", "content": "Display progress dots for the archive instead of for each file. The command\n\nzip -qdgds 10m\n\nwill turn off most output except dots every 10 MB.\n\n", "long": "--display-globaldots" }, { "name": "-ds", "content": "--dot-size size\nSet amount of input file processed for each dot displayed. See -dd to enable display‐\ning dots. Setting this option implies -dd. Size is in the format nm where n is a\nnumber and m is a multiplier. Currently m can be k (KB), m (MB), g (GB), or t (TB),\nso if n is 100 and m is k, size would be 100k which is 100 KB. The default is 10 MB.\n\nThe -v option also displays dots and now defaults to 10 MB also. This rate is also\ncontrolled by this option. A size of 0 turns dots off.\n\nThis option does not control the dots from the \"Scanning files\" message as zip scans\nfor input files. The dot size for that is fixed at 2 seconds or a fixed number of en‐\ntries, whichever is longer.\n\n" }, { "name": "-du", "content": "" }, { "name": "--display-usize", "content": "Display the uncompressed size of each entry.\n\n", "long": "--display-usize" }, { "name": "-dv", "content": "" }, { "name": "--display-volume", "content": "Display the volume (disk) number each entry is being read from, if reading an existing\narchive, and being written to.\n\n", "long": "--display-volume" }, { "name": "-D", "content": "", "flag": "-D" }, { "name": "--no-dir-entries", "content": "Do not create entries in the zip archive for directories. Directory entries are cre‐\nated by default so that their attributes can be saved in the zip archive. The envi‐\nronment variable ZIPOPT can be used to change the default options. For example under\nUnix with sh:\n\nZIPOPT=\"-D\"; export ZIPOPT\n\n(The variable ZIPOPT can be used for any option, including -i and -x using a new op‐\ntion format detailed below, and can include several options.) The option -D is a\nshorthand for -x \"*/\" but the latter previously could not be set as default in the\nZIPOPT environment variable as the contents of ZIPOPT gets inserted near the beginning\nof the command line and the file list had to end at the end of the line.\n\nThis version of zip does allow -x and -i options in ZIPOPT if the form\n\n-x file file ... @\n\nis used, where the @ (an argument that is just @) terminates the list.\n\n", "long": "--no-dir-entries" }, { "name": "-DF", "content": "" }, { "name": "--difference-archive", "content": "Create an archive that contains all new and changed files since the original archive\nwas created. For this to work, the input file list and current directory must be the\nsame as during the original zip operation.\n\nFor example, if the existing archive was created using\n\nzip -r foofull .\n\nfrom the bar directory, then the command\n\nzip -r foofull . -DF --out foonew\n\nalso from the bar directory creates the archive foonew with just the files not in foo‐\nfull and the files where the size or file time of the files do not match those in foo‐\nfull.\n\nNote that the timezone environment variable TZ should be set according to the local\ntimezone in order for this option to work correctly. A change in timezone since the\noriginal archive was created could result in no times matching and all files being in‐\ncluded.\n\nA possible approach to backing up a directory might be to create a normal archive of\nthe contents of the directory as a full backup, then use this option to create incre‐\nmental backups.\n\n", "long": "--difference-archive" }, { "name": "-e", "content": "", "flag": "-e" }, { "name": "--encrypt", "content": "Encrypt the contents of the zip archive using a password which is entered on the ter‐\nminal in response to a prompt (this will not be echoed; if standard error is not a\ntty, zip will exit with an error). The password prompt is repeated to save the user\nfrom typing errors.\n\n", "long": "--encrypt" }, { "name": "-E", "content": "", "flag": "-E" }, { "name": "--longnames", "content": "[OS/2] Use the .LONGNAME Extended Attribute (if found) as filename.\n\n", "long": "--longnames" }, { "name": "-f", "content": "", "flag": "-f" }, { "name": "--freshen", "content": "Replace (freshen) an existing entry in the zip archive only if it has been modified\nmore recently than the version already in the zip archive; unlike the update option\n(-u) this will not add files that are not already in the zip archive. For example:\n\nzip -f foo\n\nThis command should be run from the same directory from which the original zip command\nwas run, since paths stored in zip archives are always relative.\n\nNote that the timezone environment variable TZ should be set according to the local\ntimezone in order for the -f, -u and -o options to work correctly.\n\nThe reasons behind this are somewhat subtle but have to do with the differences be‐\ntween the Unix-format file times (always in GMT) and most of the other operating sys‐\ntems (always local time) and the necessity to compare the two. A typical TZ value is\n``MET-1MEST'' (Middle European time with automatic adjustment for ``summertime'' or\nDaylight Savings Time).\n\nThe format is TTThhDDD, where TTT is the time zone such as MET, hh is the difference\nbetween GMT and local time such as -1 above, and DDD is the time zone when daylight\nsavings time is in effect. Leave off the DDD if there is no daylight savings time.\nFor the US Eastern time zone EST5EDT.\n\n", "long": "--freshen" }, { "name": "-F", "content": "", "flag": "-F" }, { "name": "--fix", "content": "", "long": "--fix" }, { "name": "-FF", "content": "" }, { "name": "--fixfix", "content": "Fix the zip archive. The -F option can be used if some portions of the archive are\nmissing, but requires a reasonably intact central directory. The input archive is\nscanned as usual, but zip will ignore some problems. The resulting archive should be\nvalid, but any inconsistent entries will be left out.\n\nWhen doubled as in -FF, the archive is scanned from the beginning and zip scans for\nspecial signatures to identify the limits between the archive members. The single -F\nis more reliable if the archive is not too much damaged, so try this option first.\n\nIf the archive is too damaged or the end has been truncated, you must use -FF. This\nis a change from zip 2.32, where the -F option is able to read a truncated archive.\nThe -F option now more reliably fixes archives with minor damage and the -FF option is\nneeded to fix archives where -F might have been sufficient before.\n\nNeither option will recover archives that have been incorrectly transferred in ascii\nmode instead of binary. After the repair, the -t option of unzip may show that some\nfiles have a bad CRC. Such files cannot be recovered; you can remove them from the ar‐\nchive using the -d option of zip.\n\nNote that -FF may have trouble fixing archives that include an embedded zip archive\nthat was stored (without compression) in the archive and, depending on the damage, it\nmay find the entries in the embedded archive rather than the archive itself. Try -F\nfirst as it does not have this problem.\n\nThe format of the fix commands have changed. For example, to fix the damaged archive\nfoo.zip,\n\nzip -F foo --out foofix\n\ntries to read the entries normally, copying good entries to the new archive\nfoofix.zip. If this doesn't work, as when the archive is truncated, or if some en‐\ntries you know are in the archive are missed, then try\n\nzip -FF foo --out foofixfix\n\nand compare the resulting archive to the archive created by -F. The -FF option may\ncreate an inconsistent archive. Depending on what is damaged, you can then use the -F\noption to fix that archive.\n\nA split archive with missing split files can be fixed using -F if you have the last\nsplit of the archive (the .zip file). If this file is missing, you must use -FF to\nfix the archive, which will prompt you for the splits you have.\n\nCurrently the fix options can't recover entries that have a bad checksum or are other‐\nwise damaged.\n\n", "long": "--fixfix" }, { "name": "-FI", "content": "--fifo [Unix] Normally zip skips reading any FIFOs (named pipes) encountered, as zip can\nhang if the FIFO is not being fed. This option tells zip to read the contents of any\nFIFO it finds.\n\n" }, { "name": "-FS", "content": "" }, { "name": "--filesync", "content": "Synchronize the contents of an archive with the files on the OS. Normally when an ar‐\nchive is updated, new files are added and changed files are updated but files that no\nlonger exist on the OS are not deleted from the archive. This option enables a new\nmode that checks entries in the archive against the file system. If the file time and\nfile size of the entry matches that of the OS file, the entry is copied from the old\narchive instead of being read from the file system and compressed. If the OS file has\nchanged, the entry is read and compressed as usual. If the entry in the archive does\nnot match a file on the OS, the entry is deleted. Enabling this option should create\narchives that are the same as new archives, but since existing entries are copied in‐\nstead of compressed, updating an existing archive with -FS can be much faster than\ncreating a new archive. Also consider using -u for updating an archive.\n\nFor this option to work, the archive should be updated from the same directory it was\ncreated in so the relative paths match. If few files are being copied from the old\narchive, it may be faster to create a new archive instead.\n\nNote that the timezone environment variable TZ should be set according to the local\ntimezone in order for this option to work correctly. A change in timezone since the\noriginal archive was created could result in no times matching and recompression of\nall files.\n\nThis option deletes files from the archive. If you need to preserve the original ar‐\nchive, make a copy of the archive first or use the --out option to output the updated\narchive to a new file. Even though it may be slower, creating a new archive with a\nnew archive name is safer, avoids mismatches between archive and OS paths, and is pre‐\nferred.\n\n", "long": "--filesync" }, { "name": "-g", "content": "", "flag": "-g" }, { "name": "--grow", "content": "Grow (append to) the specified zip archive, instead of creating a new one. If this op‐\neration fails, zip attempts to restore the archive to its original state. If the\nrestoration fails, the archive might become corrupted. This option is ignored when\nthere's no existing archive or when at least one archive member must be updated or\ndeleted.\n\n", "long": "--grow" }, { "name": "-h", "content": "-?", "flag": "-h" }, { "name": "--help", "content": "Display the zip help information (this also appears if zip is run with no arguments).\n\n", "long": "--help" }, { "name": "-h2", "content": "" }, { "name": "--more-help", "content": "Display extended help including more on command line format, pattern matching, and\nmore obscure options.\n\n", "long": "--more-help" }, { "name": "-i", "content": "--include files\nInclude only the specified files, as in:\n\nzip -r foo . -i \\*.c\n\nwhich will include only the files that end in .c in the current directory and its sub‐\ndirectories. (Note for PKZIP users: the equivalent command is\n\npkzip -rP foo *.c\n\nPKZIP does not allow recursion in directories other than the current one.) The back‐\nslash avoids the shell filename substitution, so that the name matching is performed\nby zip at all directory levels. [This is for Unix and other systems where \\ escapes\nthe next character. For other systems where the shell does not process * do not use \\\nand the above is\n\nzip -r foo . -i *.c\n\nExamples are for Unix unless otherwise specified.] So to include dir, a directory di‐\nrectly under the current directory, use\n\nzip -r foo . -i dir/\\*\n\nor\n\nzip -r foo . -i \"dir/*\"\n\nto match paths such as dir/a and dir/b/file.c [on ports without wildcard expansion in\nthe shell such as MSDOS and Windows\n\nzip -r foo . -i dir/*\n\nis used.] Note that currently the trailing / is needed for directories (as in\n\nzip -r foo . -i dir/\n\nto include directory dir).\n\nThe long option form of the first example is\n\nzip -r foo . --include \\*.c\n\nand does the same thing as the short option form.\n\nThough the command syntax used to require -i at the end of the command line, this ver‐\nsion actually allows -i (or --include) anywhere. The list of files terminates at the\nnext argument starting with -, the end of the command line, or the list terminator @\n(an argument that is just @). So the above can be given as\n\nzip -i \\*.c @ -r foo .\n\nfor example. There must be a space between the option and the first file of a list.\nFor just one file you can use the single value form\n\nzip -i\\*.c -r foo .\n\n(no space between option and value) or\n\nzip --include=\\*.c -r foo .\n\nas additional examples. The single value forms are not recommended because they can\nbe confusing and, in particular, the -ifile format can cause problems if the first\nletter of file combines with i to form a two-letter option starting with i. Use -sc\nto see how your command line will be parsed.\n\nAlso possible:\n\nzip -r foo . -i@include.lst\n\nwhich will only include the files in the current directory and its subdirectories that\nmatch the patterns in the file include.lst.\n\nFiles to -i and -x are patterns matching internal archive paths. See -R for more on\npatterns.\n\n", "flag": "-i" }, { "name": "-I", "content": "", "flag": "-I" }, { "name": "--no-image", "content": "[Acorn RISC OS] Don't scan through Image files. When used, zip will not consider Im‐\nage files (eg. DOS partitions or Spark archives when SparkFS is loaded) as directories\nbut will store them as single files.\n\nFor example, if you have SparkFS loaded, zipping a Spark archive will result in a zip‐\nfile containing a directory (and its content) while using the 'I' option will result\nin a zipfile containing a Spark archive. Obviously this second case will also be ob‐\ntained (without the 'I' option) if SparkFS isn't loaded.\n\n", "long": "--no-image" }, { "name": "-ic", "content": "" }, { "name": "--ignore-case", "content": "[VMS, WIN32] Ignore case when matching archive entries. This option is only available\non systems where the case of files is ignored. On systems with case-insensitive file\nsystems, case is normally ignored when matching files on the file system but is not\nignored for -f (freshen), -d (delete), -U (copy), and similar modes when matching\nagainst archive entries (currently -f ignores case on VMS) because archive entries can\nbe from systems where case does matter and names that are the same except for case can\nexist in an archive. The -ic option makes all matching case insensitive. This can\nresult in multiple archive entries matching a command line pattern.\n\n", "long": "--ignore-case" }, { "name": "-j", "content": "", "flag": "-j" }, { "name": "--junk-paths", "content": "Store just the name of a saved file (junk the path), and do not store directory names.\nBy default, zip will store the full path (relative to the current directory).\n\n", "long": "--junk-paths" }, { "name": "-jj", "content": "" }, { "name": "--absolute-path", "content": "[MacOS] record Fullpath (+ Volname). The complete path including volume will be\nstored. By default the relative path will be stored.\n\n", "long": "--absolute-path" }, { "name": "-J", "content": "", "flag": "-J" }, { "name": "--junk-sfx", "content": "Strip any prepended data (e.g. a SFX stub) from the archive.\n", "long": "--junk-sfx" }, { "name": "-k", "content": "", "flag": "-k" }, { "name": "--DOS-names", "content": "Attempt to convert the names and paths to conform to MSDOS, store only the MSDOS at‐\ntribute (just the user write attribute from Unix), and mark the entry as made under\nMSDOS (even though it was not); for compatibility with PKUNZIP under MSDOS which can‐\nnot handle certain names such as those with two dots.\n", "long": "--DOS-names" }, { "name": "-l", "content": "", "flag": "-l" }, { "name": "--to-crlf", "content": "Translate the Unix end-of-line character LF into the MSDOS convention CR LF. This op‐\ntion should not be used on binary files. This option can be used on Unix if the zip\nfile is intended for PKUNZIP under MSDOS. If the input files already contain CR LF,\nthis option adds an extra CR. This is to ensure that unzip -a on Unix will get back an\nexact copy of the original file, to undo the effect of zip -l. See -ll for how binary\nfiles are handled.\n", "long": "--to-crlf" }, { "name": "-la", "content": "" }, { "name": "--log-append", "content": "Append to existing logfile. Default is to overwrite.\n", "long": "--log-append" }, { "name": "-lf", "content": "--logfile-path logfilepath\nOpen a logfile at the given path. By default any existing file at that location is\noverwritten, but the -la option will result in an existing file being opened and the\nnew log information appended to any existing information. Only warnings and errors\nare written to the log unless the -li option is also given, then all information mes‐\nsages are also written to the log.\n" }, { "name": "-li", "content": "" }, { "name": "--log-info", "content": "Include information messages, such as file names being zipped, in the log. The de‐\nfault is to only include the command line, any warnings and errors, and the final sta‐\ntus.\n", "long": "--log-info" }, { "name": "-ll", "content": "" }, { "name": "--from-crlf", "content": "Translate the MSDOS end-of-line CR LF into Unix LF. This option should not be used on\nbinary files. This option can be used on MSDOS if the zip file is intended for unzip\nunder Unix. If the file is converted and the file is later determined to be binary a\nwarning is issued and the file is probably corrupted. In this release if -ll detects\nbinary in the first buffer read from a file, zip now issues a warning and skips line\nend conversion on the file. This check seems to catch all binary files tested, but\nthe original check remains and if a converted file is later determined to be binary\nthat warning is still issued. A new algorithm is now being used for binary detection\nthat should allow line end conversion of text files in UTF-8 and similar encodings.\n", "long": "--from-crlf" }, { "name": "-L", "content": "", "flag": "-L" }, { "name": "--license", "content": "Display the zip license.\n", "long": "--license" }, { "name": "-m", "content": "", "flag": "-m" }, { "name": "--move", "content": "Move the specified files into the zip archive; actually, this deletes the target di‐\nrectories/files after making the specified zip archive. If a directory becomes empty\nafter removal of the files, the directory is also removed. No deletions are done until\nzip has created the archive without error. This is useful for conserving disk space,\nbut is potentially dangerous so it is recommended to use it in combination with -T to\ntest the archive before removing all input files.\n", "long": "--move" }, { "name": "-MM", "content": "" }, { "name": "--must-match", "content": "All input patterns must match at least one file and all input files found must be\nreadable. Normally when an input pattern does not match a file the \"name not matched\"\nwarning is issued and when an input file has been found but later is missing or not\nreadable a missing or not readable warning is issued. In either case zip continues\ncreating the archive, with missing or unreadable new files being skipped and files al‐\nready in the archive remaining unchanged. After the archive is created, if any files\nwere not readable zip returns the OPEN error code (18 on most systems) instead of the\nnormal success return (0 on most systems). With -MM set, zip exits as soon as an in‐\nput pattern is not matched (whenever the \"name not matched\" warning would be issued)\nor when an input file is not readable. In either case zip exits with an OPEN error\nand no archive is created.\n\nThis option is useful when a known list of files is to be zipped so any missing or un‐\nreadable files will result in an error. It is less useful when used with wildcards,\nbut zip will still exit with an error if any input pattern doesn't match at least one\nfile and if any matched files are unreadable. If you want to create the archive any‐\nway and only need to know if files were skipped, don't use -MM and just check the re‐\nturn code. Also -lf could be useful.\n", "long": "--must-match" }, { "name": "-n", "content": "--suffixes suffixes\nDo not attempt to compress files named with the given suffixes. Such files are simply\nstored (0% compression) in the output zip file, so that zip doesn't waste its time\ntrying to compress them. The suffixes are separated by either colons or semicolons.\nFor example:\n\nzip -rn .Z:.zip:.tiff:.gif:.snd foo foo\n\nwill copy everything from foo into foo.zip, but will store any files that end in .Z,\n.zip, .tiff, .gif, or .snd without trying to compress them (image and sound files of‐\nten have their own specialized compression methods). By default, zip does not com‐\npress files with extensions in the list .Z:.zip:.zoo:.arc:.lzh:.arj. Such files are\nstored directly in the output archive. The environment variable ZIPOPT can be used to\nchange the default options. For example under Unix with csh:\n\nsetenv ZIPOPT \"-n .gif:.zip\"\n\nTo attempt compression on all files, use:\n\nzip -n : foo\n\nThe maximum compression option -9 also attempts compression on all files regardless of\nextension.\n\nOn Acorn RISC OS systems the suffixes are actually filetypes (3 hex digit format). By\ndefault, zip does not compress files with filetypes in the list DDC:D96:68E (i.e. Ar‐\nchives, CFS files and PackDir files).\n", "flag": "-n" }, { "name": "-nw", "content": "" }, { "name": "--no-wild", "content": "Do not perform internal wildcard processing (shell processing of wildcards is still\ndone by the shell unless the arguments are escaped). Useful if a list of paths is be‐\ning read and no wildcard substitution is desired.\n", "long": "--no-wild" }, { "name": "-N", "content": "", "flag": "-N" }, { "name": "--notes", "content": "[Amiga, MacOS] Save Amiga or MacOS filenotes as zipfile comments. They can be restored\nby using the -N option of unzip. If -c is used also, you are prompted for comments\nonly for those files that do not have filenotes.\n", "long": "--notes" }, { "name": "-o", "content": "", "flag": "-o" }, { "name": "--latest-time", "content": "Set the \"last modified\" time of the zip archive to the latest (oldest) \"last modified\"\ntime found among the entries in the zip archive. This can be used without any other\noperations, if desired. For example:\n\nzip -o foo\n\nwill change the last modified time of foo.zip to the latest time of the entries in\nfoo.zip.\n", "long": "--latest-time" }, { "name": "-O", "content": "--output-file output-file\nProcess the archive changes as usual, but instead of updating the existing archive,\noutput the new archive to output-file. Useful for updating an archive without chang‐\ning the existing archive and the input archive must be a different file than the out‐\nput archive.\n\nThis option can be used to create updated split archives. It can also be used with -U\nto copy entries from an existing archive to a new archive. See the EXAMPLES section\nbelow.\n\nAnother use is converting zip files from one split size to another. For instance, to\nconvert an archive with 700 MB CD splits to one with 2 GB DVD splits, can use:\n\nzip -s 2g cd-split.zip --out dvd-split.zip\n\nwhich uses copy mode. See -U below. Also:\n\nzip -s 0 split.zip --out unsplit.zip\n\nwill convert a split archive to a single-file archive.\n\nCopy mode will convert stream entries (using data descriptors and which should be com‐\npatible with most unzips) to normal entries (which should be compatible with all un‐\nzips), except if standard encryption was used. For archives with encrypted entries,\nzipcloak will decrypt the entries and convert them to normal entries.\n", "flag": "-O" }, { "name": "-p", "content": "", "flag": "-p" }, { "name": "--paths", "content": "Include relative file paths as part of the names of files stored in the archive. This\nis the default. The -j option junks the paths and just stores the names of the files.\n", "long": "--paths" }, { "name": "-P", "content": "--password password\nUse password to encrypt zipfile entries (if any). THIS IS INSECURE! Many multi-user\noperating systems provide ways for any user to see the current command line of any\nother user; even on stand-alone systems there is always the threat of over-the-shoul‐\nder peeking. Storing the plaintext password as part of a command line in an automated\nscript is even worse. Whenever possible, use the non-echoing, interactive prompt to\nenter passwords. (And where security is truly important, use strong encryption such\nas Pretty Good Privacy instead of the relatively weak standard encryption provided by\nzipfile utilities.)\n", "flag": "-P" }, { "name": "-q", "content": "", "flag": "-q" }, { "name": "--quiet", "content": "Quiet mode; eliminate informational messages and comment prompts. (Useful, for exam‐\nple, in shell scripts and background tasks).\n", "long": "--quiet" }, { "name": "-Q", "content": "--Q-flag n\n[QDOS] store information about the file in the file header with n defined as\nbit 0: Don't add headers for any file\nbit 1: Add headers for all files\nbit 2: Don't wait for interactive key press on exit\n", "flag": "-Q" }, { "name": "-r", "content": "", "flag": "-r" }, { "name": "--recurse-paths", "content": "Travel the directory structure recursively; for example:\n\nzip -r foo.zip foo\n\nor more concisely\n\nzip -r foo foo\n\nIn this case, all the files and directories in foo are saved in a zip archive named\nfoo.zip, including files with names starting with \".\", since the recursion does not\nuse the shell's file-name substitution mechanism. If you wish to include only a spe‐\ncific subset of the files in directory foo and its subdirectories, use the -i option\nto specify the pattern of files to be included. You should not use -r with the name\n\".*\", since that matches \"..\" which will attempt to zip up the parent directory\n(probably not what was intended).\n\nMultiple source directories are allowed as in\n\nzip -r foo foo1 foo2\n\nwhich first zips up foo1 and then foo2, going down each directory.\n\nNote that while wildcards to -r are typically resolved while recursing down directo‐\nries in the file system, any -R, -x, and -i wildcards are applied to internal archive\npathnames once the directories are scanned. To have wildcards apply to files in sub‐\ndirectories when recursing on Unix and similar systems where the shell does wildcard\nsubstitution, either escape all wildcards or put all arguments with wildcards in\nquotes. This lets zip see the wildcards and match files in subdirectories using them\nas it recurses.\n", "long": "--recurse-paths" }, { "name": "-R", "content": "", "flag": "-R" }, { "name": "--recurse-patterns", "content": "Travel the directory structure recursively starting at the current directory; for ex‐\nample:\n\nzip -R foo \"*.c\"\n\nIn this case, all the files matching *.c in the tree starting at the current directory\nare stored into a zip archive named foo.zip. Note that *.c will match file.c,\na/file.c and a/b/.c. More than one pattern can be listed as separate arguments. Note\nfor PKZIP users: the equivalent command is\n\npkzip -rP foo *.c\n\nPatterns are relative file paths as they appear in the archive, or will after zipping,\nand can have optional wildcards in them. For example, given the current directory is\nfoo and under it are directories foo1 and foo2 and in foo1 is the file bar.c,\n\nzip -R foo/*\n\nwill zip up foo, foo/foo1, foo/foo1/bar.c, and foo/foo2.\n\nzip -R */bar.c\n\nwill zip up foo/foo1/bar.c. See the note for -r on escaping wildcards.\n\n", "long": "--recurse-patterns" }, { "name": "-RE", "content": "" }, { "name": "--regex", "content": "[WIN32] Before zip 3.0, regular expression list matching was enabled by default on\nWindows platforms. Because of confusion resulting from the need to escape \"[\" and \"]\"\nin names, it is now off by default for Windows so \"[\" and \"]\" are just normal charac‐\nters in names. This option enables [] matching again.\n\n", "long": "--regex" }, { "name": "-s", "content": "--split-size splitsize\nEnable creating a split archive and set the split size. A split archive is an archive\nthat could be split over many files. As the archive is created, if the size of the\narchive reaches the specified split size, that split is closed and the next split\nopened. In general all splits but the last will be the split size and the last will\nbe whatever is left. If the entire archive is smaller than the split size a single-\nfile archive is created.\n\nSplit archives are stored in numbered files. For example, if the output archive is\nnamed archive and three splits are required, the resulting archive will be in the\nthree files archive.z01, archive.z02, and archive.zip. Do not change the numbering of\nthese files or the archive will not be readable as these are used to determine the or‐\nder the splits are read.\n\nSplit size is a number optionally followed by a multiplier. Currently the number must\nbe an integer. The multiplier can currently be one of k (kilobytes), m (megabytes), g\n(gigabytes), or t (terabytes). As 64k is the minimum split size, numbers without mul‐\ntipliers default to megabytes. For example, to create a split archive called foo with\nthe contents of the bar directory with splits of 670 MB that might be useful for burn‐\ning on CDs, the command:\n\nzip -s 670m -r foo bar\n\ncould be used.\n\nCurrently the old splits of a split archive are not excluded from a new archive, but\nthey can be specifically excluded. If possible, keep the input and output archives\nout of the path being zipped when creating split archives.\n\nUsing -s without -sp as above creates all the splits where foo is being written, in\nthis case the current directory. This split mode updates the splits as the archive is\nbeing created, requiring all splits to remain writable, but creates split archives\nthat are readable by any unzip that supports split archives. See -sp below for en‐\nabling split pause mode which allows splits to be written directly to removable media.\n\nThe option -sv can be used to enable verbose splitting and provide details of how the\nsplitting is being done. The -sb option can be used to ring the bell when zip pauses\nfor the next split destination.\n\nSplit archives cannot be updated, but see the -O (--out) option for how a split ar‐\nchive can be updated as it is copied to a new archive. A split archive can also be\nconverted into a single-file archive using a split size of 0 or negating the -s op‐\ntion:\n\nzip -s 0 split.zip --out single.zip\n\nAlso see -U (--copy) for more on using copy mode.\n", "flag": "-s" }, { "name": "-sb", "content": "" }, { "name": "--split-bell", "content": "If splitting and using split pause mode, ring the bell when zip pauses for each split\ndestination.\n", "long": "--split-bell" }, { "name": "-sc", "content": "" }, { "name": "--show-command", "content": "Show the command line starting zip as processed and exit. The new command parser per‐\nmutes the arguments, putting all options and any values associated with them before\nany non-option arguments. This allows an option to appear anywhere in the command\nline as long as any values that go with the option go with it. This option displays\nthe command line as zip sees it, including any arguments from the environment such as\nfrom the ZIPOPT variable. Where allowed, options later in the command line can over‐\nride options earlier in the command line.\n", "long": "--show-command" }, { "name": "-sf", "content": "" }, { "name": "--show-files", "content": "Show the files that would be operated on, then exit. For instance, if creating a new\narchive, this will list the files that would be added. If the option is negated,\n-sf-, output only to an open log file. Screen display is not recommended for large\nlists.\n", "long": "--show-files" }, { "name": "-so", "content": "" }, { "name": "--show-options", "content": "Show all available options supported by zip as compiled on the current system. As\nthis command reads the option table, it should include all options. Each line in‐\ncludes the short option (if defined), the long option (if defined), the format of any\nvalue that goes with the option, if the option can be negated, and a small descrip‐\ntion. The value format can be no value, required value, optional value, single char‐\nacter value, number value, or a list of values. The output of this option is not in‐\ntended to show how to use any option but only show what options are available.\n", "long": "--show-options" }, { "name": "-sp", "content": "" }, { "name": "--split-pause", "content": "If splitting is enabled with -s, enable split pause mode. This creates split archives\nas -s does, but stream writing is used so each split can be closed as soon as it is\nwritten and zip will pause between each split to allow changing split destination or\nmedia.\n\nThough this split mode allows writing splits directly to removable media, it uses\nstream archive format that may not be readable by some unzips. Before relying on\nsplits created with -sp, test a split archive with the unzip you will be using.\n\nTo convert a stream split archive (created with -sp) to a standard archive see the\n--out option.\n", "long": "--split-pause" }, { "name": "-su", "content": "" }, { "name": "--show-unicode", "content": "As -sf, but also show Unicode version of the path if exists.\n", "long": "--show-unicode" }, { "name": "-sU", "content": "" }, { "name": "--show-just-unicode", "content": "As -sf, but only show Unicode version of the path if exists, otherwise show the stan‐\ndard version of the path.\n", "long": "--show-just-unicode" }, { "name": "-sv", "content": "" }, { "name": "--split-verbose", "content": "Enable various verbose messages while splitting, showing how the splitting is being\ndone.\n", "long": "--split-verbose" }, { "name": "-S", "content": "", "flag": "-S" }, { "name": "--system-hidden", "content": "[MSDOS, OS/2, WIN32 and ATARI] Include system and hidden files.\n[MacOS] Includes finder invisible files, which are ignored otherwise.\n", "long": "--system-hidden" }, { "name": "-t", "content": "--from-date mmddyyyy\nDo not operate on files modified prior to the specified date, where mm is the month\n(00-12), dd is the day of the month (01-31), and yyyy is the year. The ISO 8601 date\nformat yyyy-mm-dd is also accepted. For example:\n\nzip -rt 12071991 infamy foo\n\nzip -rt 1991-12-07 infamy foo\n\nwill add all the files in foo and its subdirectories that were last modified on or af‐\nter 7 December 1991, to the zip archive infamy.zip.\n", "flag": "-t" }, { "name": "-tt", "content": "--before-date mmddyyyy\nDo not operate on files modified after or at the specified date, where mm is the month\n(00-12), dd is the day of the month (01-31), and yyyy is the year. The ISO 8601 date\nformat yyyy-mm-dd is also accepted. For example:\n\nzip -rtt 11301995 infamy foo\n\nzip -rtt 1995-11-30 infamy foo\n\nwill add all the files in foo and its subdirectories that were last modified before 30\nNovember 1995, to the zip archive infamy.zip.\n" }, { "name": "-T", "content": "", "flag": "-T" }, { "name": "--test", "content": "Test the integrity of the new zip file. If the check fails, the old zip file is un‐\nchanged and (with the -m option) no input files are removed.\n", "long": "--test" }, { "name": "-TT", "content": "--unzip-command cmd\nUse command cmd instead of 'unzip -tqq' to test an archive when the -T option is used.\nOn Unix, to use a copy of unzip in the current directory instead of the standard sys‐\ntem unzip, could use:\n\nzip archive file1 file2 -T -TT \"./unzip -tqq\"\n\nIn cmd, {} is replaced by the name of the temporary archive, otherwise the name of the\narchive is appended to the end of the command. The return code is checked for success\n(0 on Unix).\n" }, { "name": "-u", "content": "", "flag": "-u" }, { "name": "--update", "content": "Replace (update) an existing entry in the zip archive only if it has been modified\nmore recently than the version already in the zip archive. For example:\n\nzip -u stuff *\n\nwill add any new files in the current directory, and update any files which have been\nmodified since the zip archive stuff.zip was last created/modified (note that zip will\nnot try to pack stuff.zip into itself when you do this).\n\nNote that the -u option with no input file arguments acts like the -f (freshen) op‐\ntion.\n", "long": "--update" }, { "name": "-U", "content": "", "flag": "-U" }, { "name": "--copy-entries", "content": "Copy entries from one archive to another. Requires the --out option to specify a dif‐\nferent output file than the input archive. Copy mode is the reverse of -d delete.\nWhen delete is being used with --out, the selected entries are deleted from the ar‐\nchive and all other entries are copied to the new archive, while copy mode selects the\nfiles to include in the new archive. Unlike -u update, input patterns on the command\nline are matched against archive entries only and not the file system files. For in‐\nstance,\n\nzip inarchive \"*.c\" --copy --out outarchive\n\ncopies entries with names ending in .c from inarchive to outarchive. The wildcard\nmust be escaped on some systems to prevent the shell from substituting names of files\nfrom the file system which may have no relevance to the entries in the archive.\n\nIf no input files appear on the command line and --out is used, copy mode is assumed:\n\nzip inarchive --out outarchive\n\nThis is useful for changing split size for instance. Encrypting and decrypting en‐\ntries is not yet supported using copy mode. Use zipcloak for that.\n", "long": "--copy-entries" }, { "name": "-UN", "content": "--unicode v\nDetermine what zip should do with Unicode file names. zip 3.0, in addition to the\nstandard file path, now includes the UTF-8 translation of the path if the entry path\nis not entirely 7-bit ASCII. When an entry is missing the Unicode path, zip reverts\nback to the standard file path. The problem with using the standard path is this path\nis in the local character set of the zip that created the entry, which may contain\ncharacters that are not valid in the character set being used by the unzip. When zip\nis reading an archive, if an entry also has a Unicode path, zip now defaults to using\nthe Unicode path to recreate the standard path using the current local character set.\n\nThis option can be used to determine what zip should do with this path if there is a\nmismatch between the stored standard path and the stored UTF-8 path (which can happen\nif the standard path was updated). In all cases, if there is a mismatch it is assumed\nthat the standard path is more current and zip uses that. Values for v are\n\nq - quit if paths do not match\n\nw - warn, continue with standard path\n\ni - ignore, continue with standard path\n\nn - no Unicode, do not use Unicode paths\n\nThe default is to warn and continue.\n\nCharacters that are not valid in the current character set are escaped as #Uxxxx and\n#Lxxxxxx, where x is an ASCII character for a hex digit. The first is used if a\n16-bit character number is sufficient to represent the Unicode character and the sec‐\nond if the character needs more than 16 bits to represent it's Unicode character code.\nSetting -UN to\n\ne - escape\n\nas in\n\nzip archive -sU -UN=e\n\nforces zip to escape all characters that are not printable 7-bit ASCII.\n\nNormally zip stores UTF-8 directly in the standard path field on systems where UTF-8\nis the current character set and stores the UTF-8 in the new extra fields otherwise.\nThe option\n\nu - UTF-8\n\nas in\n\nzip archive dir -r -UN=UTF8\n\nforces zip to store UTF-8 as native in the archive. Note that storing UTF-8 directly\nis the default on Unix systems that support it. This option could be useful on Win‐\ndows systems where the escaped path is too large to be a valid path and the UTF-8 ver‐\nsion of the path is smaller, but native UTF-8 is not backward compatible on Windows\nsystems.\n\n" }, { "name": "-v", "content": "", "flag": "-v" }, { "name": "--verbose", "content": "Verbose mode or print diagnostic version info.\n\nNormally, when applied to real operations, this option enables the display of a\nprogress indicator during compression (see -dd for more on dots) and requests verbose\ndiagnostic info about zipfile structure oddities.\n\nHowever, when -v is the only command line argument a diagnostic screen is printed in‐\nstead. This should now work even if stdout is redirected to a file, allowing easy\nsaving of the information for sending with bug reports to Info-ZIP. The version\nscreen provides the help screen header with program name, version, and release date,\nsome pointers to the Info-ZIP home and distribution sites, and shows information about\nthe target environment (compiler type and version, OS version, compilation date and\nthe enabled optional features used to create the zip executable).\n", "long": "--verbose" }, { "name": "-V", "content": "", "flag": "-V" }, { "name": "--VMS-portable", "content": "[VMS] Save VMS file attributes. (Files are truncated at EOF.) When a -V archive is\nunpacked on a non-VMS system, some file types (notably StreamLF text files and\npure binary files like fixed-512) should be extracted intact. Indexed files and file\ntypes with embedded record sizes (notably variable-length record types) will probably\nbe seen as corrupt elsewhere.\n", "long": "--VMS-portable" }, { "name": "-VV", "content": "" }, { "name": "--VMS-specific", "content": "[VMS] Save VMS file attributes, and all allocated blocks in a file, including any\ndata beyond EOF. Useful for moving ill-formed files among VMS systems. When a -VV\narchive is unpacked on a non-VMS system, almost all files will appear corrupt.\n", "long": "--VMS-specific" }, { "name": "-w", "content": "", "flag": "-w" }, { "name": "--VMS-versions", "content": "[VMS] Append the version number of the files to the name, including multiple versions\nof files. Default is to use only the most recent version of a specified file.\n", "long": "--VMS-versions" }, { "name": "-ww", "content": "" }, { "name": "--VMS-dot-versions", "content": "[VMS] Append the version number of the files to the name, including multiple versions\nof files, using the .nnn format. Default is to use only the most recent version of a\nspecified file.\n", "long": "--VMS-dot-versions" }, { "name": "-ws", "content": "" }, { "name": "--wild-stop-dirs", "content": "Wildcards match only at a directory level. Normally zip handles paths as strings and\ngiven the paths\n\n/foo/bar/dir/file1.c\n\n/foo/bar/file2.c\n\nan input pattern such as\n\n/foo/bar/*\n\nnormally would match both paths, the * matching dir/file1.c and file2.c. Note that in\nthe first case a directory boundary (/) was crossed in the match. With -ws no direc‐\ntory bounds will be included in the match, making wildcards local to a specific direc‐\ntory level. So, with -ws enabled, only the second path would be matched.\n\nWhen using -ws, use to match across directory boundaries as * does normally.\n", "long": "--wild-stop-dirs" }, { "name": "-x", "content": "--exclude files\nExplicitly exclude the specified files, as in:\n\nzip -r foo foo -x \\*.o\n\nwhich will include the contents of foo in foo.zip while excluding all the files that\nend in .o. The backslash avoids the shell filename substitution, so that the name\nmatching is performed by zip at all directory levels.\n\nAlso possible:\n\nzip -r foo foo -x@exclude.lst\n\nwhich will include the contents of foo in foo.zip while excluding all the files that\nmatch the patterns in the file exclude.lst.\n\nThe long option forms of the above are\n\nzip -r foo foo --exclude \\*.o\n\nand\n\nzip -r foo foo --exclude @exclude.lst\n\nMultiple patterns can be specified, as in:\n\nzip -r foo foo -x \\*.o \\*.c\n\nIf there is no space between -x and the pattern, just one value is assumed (no list):\n\nzip -r foo foo -x\\*.o\n\nSee -i for more on include and exclude.\n", "flag": "-x" }, { "name": "-X", "content": "", "flag": "-X" }, { "name": "--no-extra", "content": "Do not save extra file attributes (Extended Attributes on OS/2, uid/gid and file times\non Unix). The zip format uses extra fields to include additional information for each\nentry. Some extra fields are specific to particular systems while others are applica‐\nble to all systems. Normally when zip reads entries from an existing archive, it\nreads the extra fields it knows, strips the rest, and adds the extra fields applicable\nto that system. With -X, zip strips all old fields and only includes the Unicode and\nZip64 extra fields (currently these two extra fields cannot be disabled).\n\nNegating this option, -X-, includes all the default extra fields, but also copies over\nany unrecognized extra fields.\n", "long": "--no-extra" }, { "name": "-y", "content": "", "flag": "-y" }, { "name": "--symlinks", "content": "For UNIX and VMS (V8.3 and later), store symbolic links as such in the zip archive,\ninstead of compressing and storing the file referred to by the link. This can avoid\nmultiple copies of files being included in the archive as zip recurses the directory\ntrees and accesses files directly and by links.\n", "long": "--symlinks" }, { "name": "-z", "content": "", "flag": "-z" }, { "name": "--archive-comment", "content": "Prompt for a multi-line comment for the entire zip archive. The comment is ended by a\nline containing just a period, or an end of file condition (^D on Unix, ^Z on MSDOS,\nOS/2, and VMS). The comment can be taken from a file:\n\nzip -z foo < foowhat\n", "long": "--archive-comment" }, { "name": "-Z", "content": "--compression-method cm\nSet the default compression method. Currently the main methods supported by zip are\nstore and deflate. Compression method can be set to:\n\nstore - Setting the compression method to store forces zip to store entries with no\ncompression. This is generally faster than compressing entries, but results in no\nspace savings. This is the same as using -0 (compression level zero).\n\ndeflate - This is the default method for zip. If zip determines that storing is bet‐\nter than deflation, the entry will be stored instead.\n\nbzip2 - If bzip2 support is compiled in, this compression method also becomes avail‐\nable. Only some modern unzips currently support the bzip2 compression method, so test\nthe unzip you will be using before relying on archives using this method (compression\nmethod 12).\n\nFor example, to add bar.c to archive foo using bzip2 compression:\n\nzip -Z bzip2 foo bar.c\n\nThe compression method can be abbreviated:\n\nzip -Zb foo bar.c\n\n-#", "flag": "-Z" }, { "name": "(-0, -1, -2, -3, -4, -5, -6, -7, -8, -9)", "content": "Regulate the speed of compression using the specified digit #, where -0 indicates no\ncompression (store all files), -1 indicates the fastest compression speed (less com‐\npression) and -9 indicates the slowest compression speed (optimal compression, ignores\nthe suffix list). The default compression level is -6.\n\nThough still being worked, the intention is this setting will control compression\nspeed for all compression methods. Currently only deflation is controlled.\n\n-!" }, { "name": "--use-privileges", "content": "[WIN32] Use privileges (if granted) to obtain all aspects of WinNT security.\n\n-@", "long": "--use-privileges" }, { "name": "--names-stdin", "content": "Take the list of input files from standard input. Only one filename per line.\n\n-$", "long": "--names-stdin" }, { "name": "--volume-label", "content": "[MSDOS, OS/2, WIN32] Include the volume label for the drive holding the first file to\nbe compressed. If you want to include only the volume label or to force a specific\ndrive, use the drive name as first file name, as in:\n\nzip -$ foo a: c:bar\n", "long": "--volume-label" } ] }, "EXAMPLES": { "content": "The simplest example:\n\nzip stuff *\n\ncreates the archive stuff.zip (assuming it does not exist) and puts all the files in the cur‐\nrent directory in it, in compressed form (the .zip suffix is added automatically, unless the\narchive name contains a dot already; this allows the explicit specification of other suf‐\nfixes).\n\nBecause of the way the shell on Unix does filename substitution, files starting with \".\" are\nnot included; to include these as well:\n\nzip stuff .* *\n\nEven this will not include any subdirectories from the current directory.\n\nTo zip up an entire directory, the command:\n\nzip -r foo foo\n\ncreates the archive foo.zip, containing all the files and directories in the directory foo\nthat is contained within the current directory.\n\nYou may want to make a zip archive that contains the files in foo, without recording the di‐\nrectory name, foo. You can use the -j option to leave off the paths, as in:\n\nzip -j foo foo/*\n\nIf you are short on disk space, you might not have enough room to hold both the original di‐\nrectory and the corresponding compressed zip archive. In this case, you can create the ar‐\nchive in steps using the -m option. If foo contains the subdirectories tom, dick, and harry,\nyou can:\n\nzip -rm foo foo/tom\nzip -rm foo foo/dick\nzip -rm foo foo/harry\n\nwhere the first command creates foo.zip, and the next two add to it. At the completion of\neach zip command, the last created archive is deleted, making room for the next zip command\nto function.\n\n\n\n\nUse -s to set the split size and create a split archive. The size is given as a number fol‐\nlowed optionally by one of k (kB), m (MB), g (GB), or t (TB). The command\n\nzip -s 2g -r split.zip foo\n\ncreates a split archive of the directory foo with splits no bigger than 2 GB each. If foo\ncontained 5 GB of contents and the contents were stored in the split archive without compres‐\nsion (to make this example simple), this would create three splits, split.z01 at 2 GB,\nsplit.z02 at 2 GB, and split.zip at a little over 1 GB.\n\nThe -sp option can be used to pause zip between splits to allow changing removable media, for\nexample, but read the descriptions and warnings for both -s and -sp below.\n\nThough zip does not update split archives, zip provides the new option -O (--output-file) to\nallow split archives to be updated and saved in a new archive. For example,\n\nzip inarchive.zip foo.c bar.c --out outarchive.zip\n\nreads archive inarchive.zip, even if split, adds the files foo.c and bar.c, and writes the\nresulting archive to outarchive.zip. If inarchive.zip is split then outarchive.zip defaults\nto the same split size. Be aware that outarchive.zip and any split files that are created\nwith it are always overwritten without warning. This may be changed in the future.\n\n\n\n\n", "subsections": [] }, "PATTERN MATCHING": { "content": "This section applies only to Unix. Watch this space for details on MSDOS and VMS operation.\nHowever, the special wildcard characters * and [] below apply to at least MSDOS also.\n\nThe Unix shells (sh, csh, bash, and others) normally do filename substitution (also called\n\"globbing\") on command arguments. Generally the special characters are:\n\n? match any single character\n\n* match any number of characters (including none)\n\n[] match any character in the range indicated within the brackets (example: [a-f],\n[0-9]). This form of wildcard matching allows a user to specify a list of characters\nbetween square brackets and if any of the characters match the expression matches.\nFor example:\n\nzip archive \"*.[hc]\"\n\nwould archive all files in the current directory that end in .h or .c.\n\nRanges of characters are supported:\n\nzip archive \"[a-f]*\"\n\nwould add to the archive all files starting with \"a\" through \"f\".\n\nNegation is also supported, where any character in that position not in the list\nmatches. Negation is supported by adding ! or ^ to the beginning of the list:\n\nzip archive \"*.[!o]\"\n\nmatches files that don't end in \".o\".\n\nOn WIN32, [] matching needs to be turned on with the -RE option to avoid the confusion\nthat names with [ or ] have caused.\n\n\nWhen these characters are encountered (without being escaped with a backslash or quotes), the\nshell will look for files relative to the current path that match the pattern, and replace\nthe argument with a list of the names that matched.\n\nThe zip program can do the same matching on names that are in the zip archive being modified\nor, in the case of the -x (exclude) or -i (include) options, on the list of files to be oper‐\nated on, by using backslashes or quotes to tell the shell not to do the name expansion. In\ngeneral, when zip encounters a name in the list of files to do, it first looks for the name\nin the file system. If it finds it, it then adds it to the list of files to do. If it does\nnot find it, it looks for the name in the zip archive being modified (if it exists), using\nthe pattern matching characters described above, if present. For each match, it will add\nthat name to the list of files to be processed, unless this name matches one given with the", "subsections": [ { "name": "-x -i", "content": "The pattern matching includes the path, and so patterns like \\*.o match names that end in\n\".o\", no matter what the path prefix is. Note that the backslash must precede every special\ncharacter (i.e. ?*[]), or the entire argument must be enclosed in double quotes (\"\").\n\nIn general, use backslashes or double quotes for paths that have wildcards to make zip do the\npattern matching for file paths, and always for paths and strings that have spaces or wild‐\ncards for -i, -x, -R, -d, and -U and anywhere zip needs to process the wildcards.\n", "flag": "-i" } ] }, "ENVIRONMENT": { "content": "The following environment variables are read and used by zip as described.\n\nZIPOPT\ncontains default options that will be used when running zip. The contents of this en‐\nvironment variable will get added to the command line just after the zip command.\n\nZIP\n[Not on RISC OS and VMS] see ZIPOPT\n", "subsections": [ { "name": "Zip$Options", "content": "[RISC OS] see ZIPOPT\n" }, { "name": "Zip$Exts", "content": "[RISC OS] contains extensions separated by a : that will cause native filenames with\none of the specified extensions to be added to the zip file with basename and exten‐\nsion swapped.\n\nZIPOPTS\n[VMS] see ZIPOPT\n" } ] }, "SEE ALSO": { "content": "compress(1), shar(1), tar(1), unzip(1), gzip(1)\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\n2 unexpected end of zip file.\n\n3 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\n4 zip was unable to allocate memory for one or more buffers during program ini‐\ntialization.\n\n5 a severe error in the zipfile format was detected. Processing probably failed\nimmediately.\n\n6 entry too large to be processed (such as input files larger than 2 GB when not\nusing Zip64 or trying to read an existing archive that is too large) or entry\ntoo large to be split with zipsplit\n\n7 invalid comment format\n\n8 zip -T failed or out of memory\n\n9 the user aborted zip prematurely with control-C (or similar)\n\n10 zip encountered an error while using a temp file\n\n11 read or seek error\n\n12 zip has nothing to do\n\n13 missing or empty zip file\n\n14 error writing to a file\n\n15 zip was unable to create a file to write to\n\n16 bad command line parameters\n\n18 zip could not open a specified file to read\n\n19 zip was compiled with options not supported on this system\n\nVMS interprets standard Unix (or PC) return values as other, scarier-looking things, so zip\ninstead maps them into VMS-style status codes. In general, zip sets VMS Facility = 1955\n(0x07A3), Code = 2* Unixstatus, and an appropriate Severity (as specified in ziperr.h).\nMore details are included in the VMS-specific documentation. See [.vms]NOTES.TXT and\n[.vms]vmsmsggen.c.\n", "subsections": [] }, "BUGS": { "content": "zip 3.0 is not compatible with PKUNZIP 1.10. Use zip 1.1 to produce zip files which can be\nextracted by PKUNZIP 1.10.\n\nzip files produced by zip 3.0 must not be updated by zip 1.1 or PKZIP 1.10, if they contain\nencrypted members or if they have been produced in a pipe or on a non-seekable device. The\nold versions of zip or PKZIP would create an archive with an incorrect format. The old ver‐\nsions can list the contents of the zip file but cannot extract it anyway (because of the new\ncompression algorithm). If you do not use encryption and use regular disk files, you do not\nhave to care about this problem.\n\nUnder VMS, not all of the odd file formats are treated properly. Only stream-LF format zip\nfiles are expected to work with zip. Others can be converted using Rahul Dhesi's BILF pro‐\ngram. This version of zip handles some of the conversion internally. When using Kermit to\ntransfer zip files from VMS to MSDOS, type \"set file type block\" on VMS. When transferring\nfrom MSDOS to VMS, type \"set file type fixed\" on VMS. In both cases, type \"set file type bi‐\nnary\" on MSDOS.\n\nUnder some older VMS versions, zip may hang for file specifications that use DECnet syntax\nfoo::*.*.\n\nOn OS/2, zip cannot match some names, such as those including an exclamation mark or a hash\nsign. This is a bug in OS/2 itself: the 32-bit DosFindFirst/Next don't find such names.\nOther programs such as GNU tar are also affected by this bug.\n\nUnder OS/2, the amount of Extended Attributes displayed by DIR is (for compatibility) the\namount returned by the 16-bit version of DosQueryPathInfo(). Otherwise OS/2 1.3 and 2.0 would\nreport different EA sizes when DIRing a file. However, the structure layout returned by the\n32-bit DosQueryPathInfo() is a bit different, it uses extra padding bytes and link pointers\n(it's a linked list) to have all fields on 4-byte boundaries for portability to future RISC\nOS/2 versions. Therefore the value reported by zip (which uses this 32-bit-mode size) differs\nfrom that reported by DIR. zip stores the 32-bit format for portability, even the 16-bit MS-\nC-compiled version running on OS/2 1.3, so even this one shows the 32-bit-mode size.\n", "subsections": [] }, "AUTHORS": { "content": "Copyright (C) 1997-2008 Info-ZIP.\n\nCurrently distributed under the Info-ZIP license.\n\nCopyright (C) 1990-1997 Mark Adler, Richard B. Wales, Jean-loup Gailly, Onno van der Linden,\nKai Uwe Rommel, Igor Mandrichenko, John Bush and Paul Kienitz.\n\nOriginal copyright:\n\nPermission is granted to any individual or institution to use, copy, or redistribute this\nsoftware so long as all of the original files are included, that it is not sold for profit,\nand that this copyright notice is retained.\n\nLIKE ANYTHING ELSE THAT'S FREE, ZIP AND ITS ASSOCIATED UTILITIES ARE PROVIDED AS IS AND COME\nWITH NO WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. IN NO EVENT WILL THE COPYRIGHT\nHOLDERS BE LIABLE FOR ANY DAMAGES RESULTING FROM THE USE OF THIS SOFTWARE.\n\nPlease send bug reports and comments using the web page at: www.info-zip.org. For bug re‐\nports, please include the version of zip (see zip -h), the make options used to compile it\n(see zip -v), the machine and operating system in use, and as much additional information as\npossible.\n", "subsections": [] }, "ACKNOWLEDGEMENTS": { "content": "Thanks to R. P. Byrne for his Shrink.Pas program, which inspired this project, and from which\nthe shrink algorithm was stolen; to Phil Katz for placing in the public domain the zip file\nformat, compression format, and .ZIP filename extension, and for accepting minor changes to\nthe file format; to Steve Burg for clarifications on the deflate format; to Haruhiko Okumura\nand Leonid Broukhis for providing some useful ideas for the compression algorithm; to Keith\nPetersen, Rich Wales, Hunter Goatley and Mark Adler for providing a mailing list and ftp site\nfor the Info-ZIP group to use; and most importantly, to the Info-ZIP group itself (listed in\nthe file infozip.who) without whose tireless testing and bug-fixing efforts a portable zip\nwould not have been possible. Finally we should thank (blame) the first Info-ZIP moderator,\nDavid Kirschbaum, for getting us into this mess in the first place. The manual page was\nrewritten for Unix by R. P. C. Rodgers and updated by E. Gordon for zip 3.0.\n\n\n\nInfo-ZIP 16 June 2008 (v3.0) ZIP(1)", "subsections": [] } }, "summary": "zip - package and compress (archive) files", "flags": [ { "flag": "-a", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--ascii", "arg": null, "description": "[Systems using EBCDIC] Translate file to ASCII format." }, { "flag": "-A", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--adjust-sfx", "arg": null, "description": "Adjust self-extracting executable archive. A self-extracting executable archive is created by prepending the SFX stub to an existing archive. The -A option tells zip to adjust the entry offsets stored in the archive to take into account this \"preamble\" data. Note: self-extracting archives for the Amiga are a special case. At present, only the Amiga port of zip is capable of adjusting or updating these without corrupting them. -J can be used to remove the SFX stub if other updates need to be made." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--archive-clear", "arg": null, "description": "[WIN32] Once archive is created (and tested if -T is used, which is recommended), clear the archive bits of files processed. WARNING: Once the bits are cleared they are cleared. You may want to use the -sf show files option to store the list of files processed in case the archive operation must be repeated. Also consider using the -MM must match option. Be sure to check out -DF as a possibly better way to do incremen‐ tal backups." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--archive-set", "arg": null, "description": "[WIN32] Only include files that have the archive bit set. Directories are not stored when -AS is used, though by default the paths of entries, including directories, are stored as usual and can be used by most unzips to recreate directories. The archive bit is set by the operating system when a file is modified and, if used with -AC, -AS can provide an incremental backup capability. However, other applica‐ tions can modify the archive bit and it may not be a reliable indicator of which files have changed since the last archive operation. Alternative ways to create incremental backups are using -t to use file dates, though this won't catch old files copied to directories being archived, and -DF to create a differential archive." }, { "flag": "-B", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--binary", "arg": null, "description": "[VM/CMS and MVS] force file to be read binary (default is text)." }, { "flag": "-B", "long": null, "arg": null, "description": "bit 0: Don't add delimiter (Edit/Enscribe) bit 1: Use LF rather than CR/LF as delimiter (Edit/Enscribe) bit 2: Space fill record to maximum record length (Enscribe) bit 3: Trim trailing space (Enscribe) bit 8: Force 30K (Expand) large read for unstructured files" }, { "flag": "-b", "long": null, "arg": null, "description": "--temp-path path Use the specified path for the temporary zip archive. For example: zip -b /tmp stuff * will put the temporary zip archive in the directory /tmp, copying over stuff.zip to the current directory when done. This option is useful when updating an existing ar‐ chive and the file system containing this old archive does not have enough space to hold both old and new archives at the same time. It may also be useful when streaming in some cases to avoid the need for data descriptors. Note that using this option may require zip take additional time to copy the archive file when done to the destination file system." }, { "flag": "-c", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--entry-comments", "arg": null, "description": "Add one-line comments for each file. File operations (adding, updating) are done first, and the user is then prompted for a one-line comment for each file. Enter the comment followed by return, or just return for no comment." }, { "flag": "-C", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--preserve-case", "arg": null, "description": "[VMS] Preserve case all on VMS. Negating this option (-C-) downcases." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--preserve-case-2", "arg": null, "description": "[VMS] Preserve case ODS2 on VMS. Negating this option (-C2-) downcases." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--preserve-case-5", "arg": null, "description": "[VMS] Preserve case ODS5 on VMS. Negating this option (-C5-) downcases." }, { "flag": "-d", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--delete", "arg": null, "description": "Remove (delete) entries from a zip archive. For example: zip -d foo foo/tom/junk foo/harry/\\* \\*.o will remove the entry foo/tom/junk, all of the files that start with foo/harry/, and all of the files that end with .o (in any path). Note that shell pathname expansion has been inhibited with backslashes, so that zip can see the asterisks, enabling zip to match on the contents of the zip archive instead of the contents of the current di‐ rectory. (The backslashes are not used on MSDOS-based platforms.) Can also use quotes to escape the asterisks as in zip -d foo foo/tom/junk \"foo/harry/*\" \"*.o\" Not escaping the asterisks on a system where the shell expands wildcards could result in the asterisks being converted to a list of files in the current directory and that list used to delete entries from the archive. Under MSDOS, -d is case sensitive when it matches names in the zip archive. This re‐ quires that file names be entered in upper case if they were zipped by PKZIP on an MS‐ DOS system. (We considered making this case insensitive on systems where paths were case insensitive, but it is possible the archive came from a system where case does matter and the archive could include both Bar and bar as separate files in the ar‐ chive.) But see the new option -ic to ignore case in the archive." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--display-bytes", "arg": null, "description": "Display running byte counts showing the bytes zipped and the bytes to go." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--display-counts", "arg": null, "description": "Display running count of entries zipped and entries to go." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--display-dots", "arg": null, "description": "Display dots while each entry is zipped (except on ports that have their own progress indicator). See -ds below for setting dot size. The default is a dot every 10 MB of input file processed. The -v option also displays dots (previously at a much higher rate than this but now -v also defaults to 10 MB) and this rate is also controlled by -ds." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--datafork", "arg": null, "description": "[MacOS] Include only data-fork of files zipped into the archive. Good for exporting files to foreign operating-systems. Resource-forks will be ignored at all." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--display-globaldots", "arg": null, "description": "Display progress dots for the archive instead of for each file. The command zip -qdgds 10m will turn off most output except dots every 10 MB." }, { "flag": "", "long": null, "arg": null, "description": "--dot-size size Set amount of input file processed for each dot displayed. See -dd to enable display‐ ing dots. Setting this option implies -dd. Size is in the format nm where n is a number and m is a multiplier. Currently m can be k (KB), m (MB), g (GB), or t (TB), so if n is 100 and m is k, size would be 100k which is 100 KB. The default is 10 MB. The -v option also displays dots and now defaults to 10 MB also. This rate is also controlled by this option. A size of 0 turns dots off. This option does not control the dots from the \"Scanning files\" message as zip scans for input files. The dot size for that is fixed at 2 seconds or a fixed number of en‐ tries, whichever is longer." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--display-usize", "arg": null, "description": "Display the uncompressed size of each entry." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--display-volume", "arg": null, "description": "Display the volume (disk) number each entry is being read from, if reading an existing archive, and being written to." }, { "flag": "-D", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--no-dir-entries", "arg": null, "description": "Do not create entries in the zip archive for directories. Directory entries are cre‐ ated by default so that their attributes can be saved in the zip archive. The envi‐ ronment variable ZIPOPT can be used to change the default options. For example under Unix with sh: ZIPOPT=\"-D\"; export ZIPOPT (The variable ZIPOPT can be used for any option, including -i and -x using a new op‐ tion format detailed below, and can include several options.) The option -D is a shorthand for -x \"*/\" but the latter previously could not be set as default in the ZIPOPT environment variable as the contents of ZIPOPT gets inserted near the beginning of the command line and the file list had to end at the end of the line. This version of zip does allow -x and -i options in ZIPOPT if the form -x file file ... @ is used, where the @ (an argument that is just @) terminates the list." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--difference-archive", "arg": null, "description": "Create an archive that contains all new and changed files since the original archive was created. For this to work, the input file list and current directory must be the same as during the original zip operation. For example, if the existing archive was created using zip -r foofull . from the bar directory, then the command zip -r foofull . -DF --out foonew also from the bar directory creates the archive foonew with just the files not in foo‐ full and the files where the size or file time of the files do not match those in foo‐ full. Note that the timezone environment variable TZ should be set according to the local timezone in order for this option to work correctly. A change in timezone since the original archive was created could result in no times matching and all files being in‐ cluded. A possible approach to backing up a directory might be to create a normal archive of the contents of the directory as a full backup, then use this option to create incre‐ mental backups." }, { "flag": "-e", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--encrypt", "arg": null, "description": "Encrypt the contents of the zip archive using a password which is entered on the ter‐ minal in response to a prompt (this will not be echoed; if standard error is not a tty, zip will exit with an error). The password prompt is repeated to save the user from typing errors." }, { "flag": "-E", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--longnames", "arg": null, "description": "[OS/2] Use the .LONGNAME Extended Attribute (if found) as filename." }, { "flag": "-f", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--freshen", "arg": null, "description": "Replace (freshen) an existing entry in the zip archive only if it has been modified more recently than the version already in the zip archive; unlike the update option (-u) this will not add files that are not already in the zip archive. For example: zip -f foo This command should be run from the same directory from which the original zip command was run, since paths stored in zip archives are always relative. Note that the timezone environment variable TZ should be set according to the local timezone in order for the -f, -u and -o options to work correctly. The reasons behind this are somewhat subtle but have to do with the differences be‐ tween the Unix-format file times (always in GMT) and most of the other operating sys‐ tems (always local time) and the necessity to compare the two. A typical TZ value is ``MET-1MEST'' (Middle European time with automatic adjustment for ``summertime'' or Daylight Savings Time). The format is TTThhDDD, where TTT is the time zone such as MET, hh is the difference between GMT and local time such as -1 above, and DDD is the time zone when daylight savings time is in effect. Leave off the DDD if there is no daylight savings time. For the US Eastern time zone EST5EDT." }, { "flag": "-F", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--fix", "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--fixfix", "arg": null, "description": "Fix the zip archive. The -F option can be used if some portions of the archive are missing, but requires a reasonably intact central directory. The input archive is scanned as usual, but zip will ignore some problems. The resulting archive should be valid, but any inconsistent entries will be left out. When doubled as in -FF, the archive is scanned from the beginning and zip scans for special signatures to identify the limits between the archive members. The single -F is more reliable if the archive is not too much damaged, so try this option first. If the archive is too damaged or the end has been truncated, you must use -FF. This is a change from zip 2.32, where the -F option is able to read a truncated archive. The -F option now more reliably fixes archives with minor damage and the -FF option is needed to fix archives where -F might have been sufficient before. Neither option will recover archives that have been incorrectly transferred in ascii mode instead of binary. After the repair, the -t option of unzip may show that some files have a bad CRC. Such files cannot be recovered; you can remove them from the ar‐ chive using the -d option of zip. Note that -FF may have trouble fixing archives that include an embedded zip archive that was stored (without compression) in the archive and, depending on the damage, it may find the entries in the embedded archive rather than the archive itself. Try -F first as it does not have this problem. The format of the fix commands have changed. For example, to fix the damaged archive foo.zip, zip -F foo --out foofix tries to read the entries normally, copying good entries to the new archive foofix.zip. If this doesn't work, as when the archive is truncated, or if some en‐ tries you know are in the archive are missed, then try zip -FF foo --out foofixfix and compare the resulting archive to the archive created by -F. The -FF option may create an inconsistent archive. Depending on what is damaged, you can then use the -F option to fix that archive. A split archive with missing split files can be fixed using -F if you have the last split of the archive (the .zip file). If this file is missing, you must use -FF to fix the archive, which will prompt you for the splits you have. Currently the fix options can't recover entries that have a bad checksum or are other‐ wise damaged." }, { "flag": "", "long": null, "arg": null, "description": "--fifo [Unix] Normally zip skips reading any FIFOs (named pipes) encountered, as zip can hang if the FIFO is not being fed. This option tells zip to read the contents of any FIFO it finds." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--filesync", "arg": null, "description": "Synchronize the contents of an archive with the files on the OS. Normally when an ar‐ chive is updated, new files are added and changed files are updated but files that no longer exist on the OS are not deleted from the archive. This option enables a new mode that checks entries in the archive against the file system. If the file time and file size of the entry matches that of the OS file, the entry is copied from the old archive instead of being read from the file system and compressed. If the OS file has changed, the entry is read and compressed as usual. If the entry in the archive does not match a file on the OS, the entry is deleted. Enabling this option should create archives that are the same as new archives, but since existing entries are copied in‐ stead of compressed, updating an existing archive with -FS can be much faster than creating a new archive. Also consider using -u for updating an archive. For this option to work, the archive should be updated from the same directory it was created in so the relative paths match. If few files are being copied from the old archive, it may be faster to create a new archive instead. Note that the timezone environment variable TZ should be set according to the local timezone in order for this option to work correctly. A change in timezone since the original archive was created could result in no times matching and recompression of all files. This option deletes files from the archive. If you need to preserve the original ar‐ chive, make a copy of the archive first or use the --out option to output the updated archive to a new file. Even though it may be slower, creating a new archive with a new archive name is safer, avoids mismatches between archive and OS paths, and is pre‐ ferred." }, { "flag": "-g", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--grow", "arg": null, "description": "Grow (append to) the specified zip archive, instead of creating a new one. If this op‐ eration fails, zip attempts to restore the archive to its original state. If the restoration fails, the archive might become corrupted. This option is ignored when there's no existing archive or when at least one archive member must be updated or deleted." }, { "flag": "-h", "long": null, "arg": null, "description": "-?" }, { "flag": "", "long": "--help", "arg": null, "description": "Display the zip help information (this also appears if zip is run with no arguments)." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--more-help", "arg": null, "description": "Display extended help including more on command line format, pattern matching, and more obscure options." }, { "flag": "-i", "long": null, "arg": null, "description": "--include files Include only the specified files, as in: zip -r foo . -i \\*.c which will include only the files that end in .c in the current directory and its sub‐ directories. (Note for PKZIP users: the equivalent command is pkzip -rP foo *.c PKZIP does not allow recursion in directories other than the current one.) The back‐ slash avoids the shell filename substitution, so that the name matching is performed by zip at all directory levels. [This is for Unix and other systems where \\ escapes the next character. For other systems where the shell does not process * do not use \\ and the above is zip -r foo . -i *.c Examples are for Unix unless otherwise specified.] So to include dir, a directory di‐ rectly under the current directory, use zip -r foo . -i dir/\\* or zip -r foo . -i \"dir/*\" to match paths such as dir/a and dir/b/file.c [on ports without wildcard expansion in the shell such as MSDOS and Windows zip -r foo . -i dir/* is used.] Note that currently the trailing / is needed for directories (as in zip -r foo . -i dir/ to include directory dir). The long option form of the first example is zip -r foo . --include \\*.c and does the same thing as the short option form. Though the command syntax used to require -i at the end of the command line, this ver‐ sion actually allows -i (or --include) anywhere. The list of files terminates at the next argument starting with -, the end of the command line, or the list terminator @ (an argument that is just @). So the above can be given as zip -i \\*.c @ -r foo . for example. There must be a space between the option and the first file of a list. For just one file you can use the single value form zip -i\\*.c -r foo . (no space between option and value) or zip --include=\\*.c -r foo . as additional examples. The single value forms are not recommended because they can be confusing and, in particular, the -ifile format can cause problems if the first letter of file combines with i to form a two-letter option starting with i. Use -sc to see how your command line will be parsed. Also possible: zip -r foo . -i@include.lst which will only include the files in the current directory and its subdirectories that match the patterns in the file include.lst. Files to -i and -x are patterns matching internal archive paths. See -R for more on patterns." }, { "flag": "-I", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--no-image", "arg": null, "description": "[Acorn RISC OS] Don't scan through Image files. When used, zip will not consider Im‐ age files (eg. DOS partitions or Spark archives when SparkFS is loaded) as directories but will store them as single files. For example, if you have SparkFS loaded, zipping a Spark archive will result in a zip‐ file containing a directory (and its content) while using the 'I' option will result in a zipfile containing a Spark archive. Obviously this second case will also be ob‐ tained (without the 'I' option) if SparkFS isn't loaded." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--ignore-case", "arg": null, "description": "[VMS, WIN32] Ignore case when matching archive entries. This option is only available on systems where the case of files is ignored. On systems with case-insensitive file systems, case is normally ignored when matching files on the file system but is not ignored for -f (freshen), -d (delete), -U (copy), and similar modes when matching against archive entries (currently -f ignores case on VMS) because archive entries can be from systems where case does matter and names that are the same except for case can exist in an archive. The -ic option makes all matching case insensitive. This can result in multiple archive entries matching a command line pattern." }, { "flag": "-j", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--junk-paths", "arg": null, "description": "Store just the name of a saved file (junk the path), and do not store directory names. By default, zip will store the full path (relative to the current directory)." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--absolute-path", "arg": null, "description": "[MacOS] record Fullpath (+ Volname). The complete path including volume will be stored. By default the relative path will be stored." }, { "flag": "-J", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--junk-sfx", "arg": null, "description": "Strip any prepended data (e.g. a SFX stub) from the archive." }, { "flag": "-k", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--DOS-names", "arg": null, "description": "Attempt to convert the names and paths to conform to MSDOS, store only the MSDOS at‐ tribute (just the user write attribute from Unix), and mark the entry as made under MSDOS (even though it was not); for compatibility with PKUNZIP under MSDOS which can‐ not handle certain names such as those with two dots." }, { "flag": "-l", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--to-crlf", "arg": null, "description": "Translate the Unix end-of-line character LF into the MSDOS convention CR LF. This op‐ tion should not be used on binary files. This option can be used on Unix if the zip file is intended for PKUNZIP under MSDOS. If the input files already contain CR LF, this option adds an extra CR. This is to ensure that unzip -a on Unix will get back an exact copy of the original file, to undo the effect of zip -l. See -ll for how binary files are handled." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--log-append", "arg": null, "description": "Append to existing logfile. Default is to overwrite." }, { "flag": "", "long": null, "arg": null, "description": "--logfile-path logfilepath Open a logfile at the given path. By default any existing file at that location is overwritten, but the -la option will result in an existing file being opened and the new log information appended to any existing information. Only warnings and errors are written to the log unless the -li option is also given, then all information mes‐ sages are also written to the log." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--log-info", "arg": null, "description": "Include information messages, such as file names being zipped, in the log. The de‐ fault is to only include the command line, any warnings and errors, and the final sta‐ tus." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--from-crlf", "arg": null, "description": "Translate the MSDOS end-of-line CR LF into Unix LF. This option should not be used on binary files. This option can be used on MSDOS if the zip file is intended for unzip under Unix. If the file is converted and the file is later determined to be binary a warning is issued and the file is probably corrupted. In this release if -ll detects binary in the first buffer read from a file, zip now issues a warning and skips line end conversion on the file. This check seems to catch all binary files tested, but the original check remains and if a converted file is later determined to be binary that warning is still issued. A new algorithm is now being used for binary detection that should allow line end conversion of text files in UTF-8 and similar encodings." }, { "flag": "-L", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--license", "arg": null, "description": "Display the zip license." }, { "flag": "-m", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--move", "arg": null, "description": "Move the specified files into the zip archive; actually, this deletes the target di‐ rectories/files after making the specified zip archive. If a directory becomes empty after removal of the files, the directory is also removed. No deletions are done until zip has created the archive without error. This is useful for conserving disk space, but is potentially dangerous so it is recommended to use it in combination with -T to test the archive before removing all input files." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--must-match", "arg": null, "description": "All input patterns must match at least one file and all input files found must be readable. Normally when an input pattern does not match a file the \"name not matched\" warning is issued and when an input file has been found but later is missing or not readable a missing or not readable warning is issued. In either case zip continues creating the archive, with missing or unreadable new files being skipped and files al‐ ready in the archive remaining unchanged. After the archive is created, if any files were not readable zip returns the OPEN error code (18 on most systems) instead of the normal success return (0 on most systems). With -MM set, zip exits as soon as an in‐ put pattern is not matched (whenever the \"name not matched\" warning would be issued) or when an input file is not readable. In either case zip exits with an OPEN error and no archive is created. This option is useful when a known list of files is to be zipped so any missing or un‐ readable files will result in an error. It is less useful when used with wildcards, but zip will still exit with an error if any input pattern doesn't match at least one file and if any matched files are unreadable. If you want to create the archive any‐ way and only need to know if files were skipped, don't use -MM and just check the re‐ turn code. Also -lf could be useful." }, { "flag": "-n", "long": null, "arg": null, "description": "--suffixes suffixes Do not attempt to compress files named with the given suffixes. Such files are simply stored (0% compression) in the output zip file, so that zip doesn't waste its time trying to compress them. The suffixes are separated by either colons or semicolons. For example: zip -rn .Z:.zip:.tiff:.gif:.snd foo foo will copy everything from foo into foo.zip, but will store any files that end in .Z, .zip, .tiff, .gif, or .snd without trying to compress them (image and sound files of‐ ten have their own specialized compression methods). By default, zip does not com‐ press files with extensions in the list .Z:.zip:.zoo:.arc:.lzh:.arj. Such files are stored directly in the output archive. The environment variable ZIPOPT can be used to change the default options. For example under Unix with csh: setenv ZIPOPT \"-n .gif:.zip\" To attempt compression on all files, use: zip -n : foo The maximum compression option -9 also attempts compression on all files regardless of extension. On Acorn RISC OS systems the suffixes are actually filetypes (3 hex digit format). By default, zip does not compress files with filetypes in the list DDC:D96:68E (i.e. Ar‐ chives, CFS files and PackDir files)." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--no-wild", "arg": null, "description": "Do not perform internal wildcard processing (shell processing of wildcards is still done by the shell unless the arguments are escaped). Useful if a list of paths is be‐ ing read and no wildcard substitution is desired." }, { "flag": "-N", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--notes", "arg": null, "description": "[Amiga, MacOS] Save Amiga or MacOS filenotes as zipfile comments. They can be restored by using the -N option of unzip. If -c is used also, you are prompted for comments only for those files that do not have filenotes." }, { "flag": "-o", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--latest-time", "arg": null, "description": "Set the \"last modified\" time of the zip archive to the latest (oldest) \"last modified\" time found among the entries in the zip archive. This can be used without any other operations, if desired. For example: zip -o foo will change the last modified time of foo.zip to the latest time of the entries in foo.zip." }, { "flag": "-O", "long": null, "arg": null, "description": "--output-file output-file Process the archive changes as usual, but instead of updating the existing archive, output the new archive to output-file. Useful for updating an archive without chang‐ ing the existing archive and the input archive must be a different file than the out‐ put archive. This option can be used to create updated split archives. It can also be used with -U to copy entries from an existing archive to a new archive. See the EXAMPLES section below. Another use is converting zip files from one split size to another. For instance, to convert an archive with 700 MB CD splits to one with 2 GB DVD splits, can use: zip -s 2g cd-split.zip --out dvd-split.zip which uses copy mode. See -U below. Also: zip -s 0 split.zip --out unsplit.zip will convert a split archive to a single-file archive. Copy mode will convert stream entries (using data descriptors and which should be com‐ patible with most unzips) to normal entries (which should be compatible with all un‐ zips), except if standard encryption was used. For archives with encrypted entries, zipcloak will decrypt the entries and convert them to normal entries." }, { "flag": "-p", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--paths", "arg": null, "description": "Include relative file paths as part of the names of files stored in the archive. This is the default. The -j option junks the paths and just stores the names of the files." }, { "flag": "-P", "long": null, "arg": null, "description": "--password password Use password to encrypt zipfile entries (if any). THIS IS INSECURE! Many multi-user operating systems provide ways for any user to see the current command line of any other user; even on stand-alone systems there is always the threat of over-the-shoul‐ der peeking. Storing the plaintext password as part of a command line in an automated script is even worse. Whenever possible, use the non-echoing, interactive prompt to enter passwords. (And where security is truly important, use strong encryption such as Pretty Good Privacy instead of the relatively weak standard encryption provided by zipfile utilities.)" }, { "flag": "-q", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--quiet", "arg": null, "description": "Quiet mode; eliminate informational messages and comment prompts. (Useful, for exam‐ ple, in shell scripts and background tasks)." }, { "flag": "-Q", "long": null, "arg": null, "description": "--Q-flag n [QDOS] store information about the file in the file header with n defined as bit 0: Don't add headers for any file bit 1: Add headers for all files bit 2: Don't wait for interactive key press on exit" }, { "flag": "-r", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--recurse-paths", "arg": null, "description": "Travel the directory structure recursively; for example: zip -r foo.zip foo or more concisely zip -r foo foo In this case, all the files and directories in foo are saved in a zip archive named foo.zip, including files with names starting with \".\", since the recursion does not use the shell's file-name substitution mechanism. If you wish to include only a spe‐ cific subset of the files in directory foo and its subdirectories, use the -i option to specify the pattern of files to be included. You should not use -r with the name \".*\", since that matches \"..\" which will attempt to zip up the parent directory (probably not what was intended). Multiple source directories are allowed as in zip -r foo foo1 foo2 which first zips up foo1 and then foo2, going down each directory. Note that while wildcards to -r are typically resolved while recursing down directo‐ ries in the file system, any -R, -x, and -i wildcards are applied to internal archive pathnames once the directories are scanned. To have wildcards apply to files in sub‐ directories when recursing on Unix and similar systems where the shell does wildcard substitution, either escape all wildcards or put all arguments with wildcards in quotes. This lets zip see the wildcards and match files in subdirectories using them as it recurses." }, { "flag": "-R", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--recurse-patterns", "arg": null, "description": "Travel the directory structure recursively starting at the current directory; for ex‐ ample: zip -R foo \"*.c\" In this case, all the files matching *.c in the tree starting at the current directory are stored into a zip archive named foo.zip. Note that *.c will match file.c, a/file.c and a/b/.c. More than one pattern can be listed as separate arguments. Note for PKZIP users: the equivalent command is pkzip -rP foo *.c Patterns are relative file paths as they appear in the archive, or will after zipping, and can have optional wildcards in them. For example, given the current directory is foo and under it are directories foo1 and foo2 and in foo1 is the file bar.c, zip -R foo/* will zip up foo, foo/foo1, foo/foo1/bar.c, and foo/foo2. zip -R */bar.c will zip up foo/foo1/bar.c. See the note for -r on escaping wildcards." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--regex", "arg": null, "description": "[WIN32] Before zip 3.0, regular expression list matching was enabled by default on Windows platforms. Because of confusion resulting from the need to escape \"[\" and \"]\" in names, it is now off by default for Windows so \"[\" and \"]\" are just normal charac‐ ters in names. This option enables [] matching again." }, { "flag": "-s", "long": null, "arg": null, "description": "--split-size splitsize Enable creating a split archive and set the split size. A split archive is an archive that could be split over many files. As the archive is created, if the size of the archive reaches the specified split size, that split is closed and the next split opened. In general all splits but the last will be the split size and the last will be whatever is left. If the entire archive is smaller than the split size a single- file archive is created. Split archives are stored in numbered files. For example, if the output archive is named archive and three splits are required, the resulting archive will be in the three files archive.z01, archive.z02, and archive.zip. Do not change the numbering of these files or the archive will not be readable as these are used to determine the or‐ der the splits are read. Split size is a number optionally followed by a multiplier. Currently the number must be an integer. The multiplier can currently be one of k (kilobytes), m (megabytes), g (gigabytes), or t (terabytes). As 64k is the minimum split size, numbers without mul‐ tipliers default to megabytes. For example, to create a split archive called foo with the contents of the bar directory with splits of 670 MB that might be useful for burn‐ ing on CDs, the command: zip -s 670m -r foo bar could be used. Currently the old splits of a split archive are not excluded from a new archive, but they can be specifically excluded. If possible, keep the input and output archives out of the path being zipped when creating split archives. Using -s without -sp as above creates all the splits where foo is being written, in this case the current directory. This split mode updates the splits as the archive is being created, requiring all splits to remain writable, but creates split archives that are readable by any unzip that supports split archives. See -sp below for en‐ abling split pause mode which allows splits to be written directly to removable media. The option -sv can be used to enable verbose splitting and provide details of how the splitting is being done. The -sb option can be used to ring the bell when zip pauses for the next split destination. Split archives cannot be updated, but see the -O (--out) option for how a split ar‐ chive can be updated as it is copied to a new archive. A split archive can also be converted into a single-file archive using a split size of 0 or negating the -s op‐ tion: zip -s 0 split.zip --out single.zip Also see -U (--copy) for more on using copy mode." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--split-bell", "arg": null, "description": "If splitting and using split pause mode, ring the bell when zip pauses for each split destination." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--show-command", "arg": null, "description": "Show the command line starting zip as processed and exit. The new command parser per‐ mutes the arguments, putting all options and any values associated with them before any non-option arguments. This allows an option to appear anywhere in the command line as long as any values that go with the option go with it. This option displays the command line as zip sees it, including any arguments from the environment such as from the ZIPOPT variable. Where allowed, options later in the command line can over‐ ride options earlier in the command line." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--show-files", "arg": null, "description": "Show the files that would be operated on, then exit. For instance, if creating a new archive, this will list the files that would be added. If the option is negated, -sf-, output only to an open log file. Screen display is not recommended for large lists." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--show-options", "arg": null, "description": "Show all available options supported by zip as compiled on the current system. As this command reads the option table, it should include all options. Each line in‐ cludes the short option (if defined), the long option (if defined), the format of any value that goes with the option, if the option can be negated, and a small descrip‐ tion. The value format can be no value, required value, optional value, single char‐ acter value, number value, or a list of values. The output of this option is not in‐ tended to show how to use any option but only show what options are available." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--split-pause", "arg": null, "description": "If splitting is enabled with -s, enable split pause mode. This creates split archives as -s does, but stream writing is used so each split can be closed as soon as it is written and zip will pause between each split to allow changing split destination or media. Though this split mode allows writing splits directly to removable media, it uses stream archive format that may not be readable by some unzips. Before relying on splits created with -sp, test a split archive with the unzip you will be using. To convert a stream split archive (created with -sp) to a standard archive see the --out option." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--show-unicode", "arg": null, "description": "As -sf, but also show Unicode version of the path if exists." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--show-just-unicode", "arg": null, "description": "As -sf, but only show Unicode version of the path if exists, otherwise show the stan‐ dard version of the path." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--split-verbose", "arg": null, "description": "Enable various verbose messages while splitting, showing how the splitting is being done." }, { "flag": "-S", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--system-hidden", "arg": null, "description": "[MSDOS, OS/2, WIN32 and ATARI] Include system and hidden files. [MacOS] Includes finder invisible files, which are ignored otherwise." }, { "flag": "-t", "long": null, "arg": null, "description": "--from-date mmddyyyy Do not operate on files modified prior to the specified date, where mm is the month (00-12), dd is the day of the month (01-31), and yyyy is the year. The ISO 8601 date format yyyy-mm-dd is also accepted. For example: zip -rt 12071991 infamy foo zip -rt 1991-12-07 infamy foo will add all the files in foo and its subdirectories that were last modified on or af‐ ter 7 December 1991, to the zip archive infamy.zip." }, { "flag": "", "long": null, "arg": null, "description": "--before-date mmddyyyy Do not operate on files modified after or at the specified date, where mm is the month (00-12), dd is the day of the month (01-31), and yyyy is the year. The ISO 8601 date format yyyy-mm-dd is also accepted. For example: zip -rtt 11301995 infamy foo zip -rtt 1995-11-30 infamy foo will add all the files in foo and its subdirectories that were last modified before 30 November 1995, to the zip archive infamy.zip." }, { "flag": "-T", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--test", "arg": null, "description": "Test the integrity of the new zip file. If the check fails, the old zip file is un‐ changed and (with the -m option) no input files are removed." }, { "flag": "", "long": null, "arg": null, "description": "--unzip-command cmd Use command cmd instead of 'unzip -tqq' to test an archive when the -T option is used. On Unix, to use a copy of unzip in the current directory instead of the standard sys‐ tem unzip, could use: zip archive file1 file2 -T -TT \"./unzip -tqq\" In cmd, {} is replaced by the name of the temporary archive, otherwise the name of the archive is appended to the end of the command. The return code is checked for success (0 on Unix)." }, { "flag": "-u", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--update", "arg": null, "description": "Replace (update) an existing entry in the zip archive only if it has been modified more recently than the version already in the zip archive. For example: zip -u stuff * will add any new files in the current directory, and update any files which have been modified since the zip archive stuff.zip was last created/modified (note that zip will not try to pack stuff.zip into itself when you do this). Note that the -u option with no input file arguments acts like the -f (freshen) op‐ tion." }, { "flag": "-U", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--copy-entries", "arg": null, "description": "Copy entries from one archive to another. Requires the --out option to specify a dif‐ ferent output file than the input archive. Copy mode is the reverse of -d delete. When delete is being used with --out, the selected entries are deleted from the ar‐ chive and all other entries are copied to the new archive, while copy mode selects the files to include in the new archive. Unlike -u update, input patterns on the command line are matched against archive entries only and not the file system files. For in‐ stance, zip inarchive \"*.c\" --copy --out outarchive copies entries with names ending in .c from inarchive to outarchive. The wildcard must be escaped on some systems to prevent the shell from substituting names of files from the file system which may have no relevance to the entries in the archive. If no input files appear on the command line and --out is used, copy mode is assumed: zip inarchive --out outarchive This is useful for changing split size for instance. Encrypting and decrypting en‐ tries is not yet supported using copy mode. Use zipcloak for that." }, { "flag": "", "long": null, "arg": null, "description": "--unicode v Determine what zip should do with Unicode file names. zip 3.0, in addition to the standard file path, now includes the UTF-8 translation of the path if the entry path is not entirely 7-bit ASCII. When an entry is missing the Unicode path, zip reverts back to the standard file path. The problem with using the standard path is this path is in the local character set of the zip that created the entry, which may contain characters that are not valid in the character set being used by the unzip. When zip is reading an archive, if an entry also has a Unicode path, zip now defaults to using the Unicode path to recreate the standard path using the current local character set. This option can be used to determine what zip should do with this path if there is a mismatch between the stored standard path and the stored UTF-8 path (which can happen if the standard path was updated). In all cases, if there is a mismatch it is assumed that the standard path is more current and zip uses that. Values for v are q - quit if paths do not match w - warn, continue with standard path i - ignore, continue with standard path n - no Unicode, do not use Unicode paths The default is to warn and continue. Characters that are not valid in the current character set are escaped as #Uxxxx and #Lxxxxxx, where x is an ASCII character for a hex digit. The first is used if a 16-bit character number is sufficient to represent the Unicode character and the sec‐ ond if the character needs more than 16 bits to represent it's Unicode character code. Setting -UN to e - escape as in zip archive -sU -UN=e forces zip to escape all characters that are not printable 7-bit ASCII. Normally zip stores UTF-8 directly in the standard path field on systems where UTF-8 is the current character set and stores the UTF-8 in the new extra fields otherwise. The option u - UTF-8 as in zip archive dir -r -UN=UTF8 forces zip to store UTF-8 as native in the archive. Note that storing UTF-8 directly is the default on Unix systems that support it. This option could be useful on Win‐ dows systems where the escaped path is too large to be a valid path and the UTF-8 ver‐ sion of the path is smaller, but native UTF-8 is not backward compatible on Windows systems." }, { "flag": "-v", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--verbose", "arg": null, "description": "Verbose mode or print diagnostic version info. Normally, when applied to real operations, this option enables the display of a progress indicator during compression (see -dd for more on dots) and requests verbose diagnostic info about zipfile structure oddities. However, when -v is the only command line argument a diagnostic screen is printed in‐ stead. This should now work even if stdout is redirected to a file, allowing easy saving of the information for sending with bug reports to Info-ZIP. The version screen provides the help screen header with program name, version, and release date, some pointers to the Info-ZIP home and distribution sites, and shows information about the target environment (compiler type and version, OS version, compilation date and the enabled optional features used to create the zip executable)." }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--VMS-portable", "arg": null, "description": "[VMS] Save VMS file attributes. (Files are truncated at EOF.) When a -V archive is unpacked on a non-VMS system, some file types (notably StreamLF text files and pure binary files like fixed-512) should be extracted intact. Indexed files and file types with embedded record sizes (notably variable-length record types) will probably be seen as corrupt elsewhere." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--VMS-specific", "arg": null, "description": "[VMS] Save VMS file attributes, and all allocated blocks in a file, including any data beyond EOF. Useful for moving ill-formed files among VMS systems. When a -VV archive is unpacked on a non-VMS system, almost all files will appear corrupt." }, { "flag": "-w", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--VMS-versions", "arg": null, "description": "[VMS] Append the version number of the files to the name, including multiple versions of files. Default is to use only the most recent version of a specified file." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--VMS-dot-versions", "arg": null, "description": "[VMS] Append the version number of the files to the name, including multiple versions of files, using the .nnn format. Default is to use only the most recent version of a specified file." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--wild-stop-dirs", "arg": null, "description": "Wildcards match only at a directory level. Normally zip handles paths as strings and given the paths /foo/bar/dir/file1.c /foo/bar/file2.c an input pattern such as /foo/bar/* normally would match both paths, the * matching dir/file1.c and file2.c. Note that in the first case a directory boundary (/) was crossed in the match. With -ws no direc‐ tory bounds will be included in the match, making wildcards local to a specific direc‐ tory level. So, with -ws enabled, only the second path would be matched. When using -ws, use to match across directory boundaries as * does normally." }, { "flag": "-x", "long": null, "arg": null, "description": "--exclude files Explicitly exclude the specified files, as in: zip -r foo foo -x \\*.o which will include the contents of foo in foo.zip while excluding all the files that end in .o. The backslash avoids the shell filename substitution, so that the name matching is performed by zip at all directory levels. Also possible: zip -r foo foo -x@exclude.lst which will include the contents of foo in foo.zip while excluding all the files that match the patterns in the file exclude.lst. The long option forms of the above are zip -r foo foo --exclude \\*.o and zip -r foo foo --exclude @exclude.lst Multiple patterns can be specified, as in: zip -r foo foo -x \\*.o \\*.c If there is no space between -x and the pattern, just one value is assumed (no list): zip -r foo foo -x\\*.o See -i for more on include and exclude." }, { "flag": "-X", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--no-extra", "arg": null, "description": "Do not save extra file attributes (Extended Attributes on OS/2, uid/gid and file times on Unix). The zip format uses extra fields to include additional information for each entry. Some extra fields are specific to particular systems while others are applica‐ ble to all systems. Normally when zip reads entries from an existing archive, it reads the extra fields it knows, strips the rest, and adds the extra fields applicable to that system. With -X, zip strips all old fields and only includes the Unicode and Zip64 extra fields (currently these two extra fields cannot be disabled). Negating this option, -X-, includes all the default extra fields, but also copies over any unrecognized extra fields." }, { "flag": "-y", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--symlinks", "arg": null, "description": "For UNIX and VMS (V8.3 and later), store symbolic links as such in the zip archive, instead of compressing and storing the file referred to by the link. This can avoid multiple copies of files being included in the archive as zip recurses the directory trees and accesses files directly and by links." }, { "flag": "-z", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--archive-comment", "arg": null, "description": "Prompt for a multi-line comment for the entire zip archive. The comment is ended by a line containing just a period, or an end of file condition (^D on Unix, ^Z on MSDOS, OS/2, and VMS). The comment can be taken from a file: zip -z foo < foowhat" }, { "flag": "-Z", "long": null, "arg": null, "description": "--compression-method cm Set the default compression method. Currently the main methods supported by zip are store and deflate. Compression method can be set to: store - Setting the compression method to store forces zip to store entries with no compression. This is generally faster than compressing entries, but results in no space savings. This is the same as using -0 (compression level zero). deflate - This is the default method for zip. If zip determines that storing is bet‐ ter than deflation, the entry will be stored instead. bzip2 - If bzip2 support is compiled in, this compression method also becomes avail‐ able. Only some modern unzips currently support the bzip2 compression method, so test the unzip you will be using before relying on archives using this method (compression method 12). For example, to add bar.c to archive foo using bzip2 compression: zip -Z bzip2 foo bar.c The compression method can be abbreviated: zip -Zb foo bar.c -#" }, { "flag": "", "long": "--use-privileges", "arg": null, "description": "[WIN32] Use privileges (if granted) to obtain all aspects of WinNT security. -@" }, { "flag": "", "long": "--names-stdin", "arg": null, "description": "Take the list of input files from standard input. Only one filename per line. -$" }, { "flag": "", "long": "--volume-label", "arg": null, "description": "[MSDOS, OS/2, WIN32] Include the volume label for the drive holding the first file to be compressed. If you want to include only the volume label or to force a specific drive, use the drive name as first file name, as in: zip -$ foo a: c:bar" } ], "examples": [ "The simplest example:", "zip stuff *", "creates the archive stuff.zip (assuming it does not exist) and puts all the files in the cur‐", "rent directory in it, in compressed form (the .zip suffix is added automatically, unless the", "archive name contains a dot already; this allows the explicit specification of other suf‐", "fixes).", "Because of the way the shell on Unix does filename substitution, files starting with \".\" are", "not included; to include these as well:", "zip stuff .* *", "Even this will not include any subdirectories from the current directory.", "To zip up an entire directory, the command:", "zip -r foo foo", "creates the archive foo.zip, containing all the files and directories in the directory foo", "that is contained within the current directory.", "You may want to make a zip archive that contains the files in foo, without recording the di‐", "rectory name, foo. You can use the -j option to leave off the paths, as in:", "zip -j foo foo/*", "If you are short on disk space, you might not have enough room to hold both the original di‐", "rectory and the corresponding compressed zip archive. In this case, you can create the ar‐", "chive in steps using the -m option. If foo contains the subdirectories tom, dick, and harry,", "you can:", "zip -rm foo foo/tom", "zip -rm foo foo/dick", "zip -rm foo foo/harry", "where the first command creates foo.zip, and the next two add to it. At the completion of", "each zip command, the last created archive is deleted, making room for the next zip command", "to function.", "Use -s to set the split size and create a split archive. The size is given as a number fol‐", "lowed optionally by one of k (kB), m (MB), g (GB), or t (TB). The command", "zip -s 2g -r split.zip foo", "creates a split archive of the directory foo with splits no bigger than 2 GB each. If foo", "contained 5 GB of contents and the contents were stored in the split archive without compres‐", "sion (to make this example simple), this would create three splits, split.z01 at 2 GB,", "split.z02 at 2 GB, and split.zip at a little over 1 GB.", "The -sp option can be used to pause zip between splits to allow changing removable media, for", "example, but read the descriptions and warnings for both -s and -sp below.", "Though zip does not update split archives, zip provides the new option -O (--output-file) to", "allow split archives to be updated and saved in a new archive. For example,", "zip inarchive.zip foo.c bar.c --out outarchive.zip", "reads archive inarchive.zip, even if split, adds the files foo.c and bar.c, and writes the", "resulting archive to outarchive.zip. If inarchive.zip is split then outarchive.zip defaults", "to the same split size. Be aware that outarchive.zip and any split files that are created", "with it are always overwritten without warning. This may be changed in the future." ], "see_also": [ { "name": "compress", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/compress/1/json" }, { "name": "shar", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/shar/1/json" }, { "name": "tar", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/tar/1/json" }, { "name": "unzip", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/unzip/1/json" }, { "name": "gzip", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/gzip/1/json" } ], "tldr": { "source": "official", "description": "Package and compress (archive) files into a Zip archive.", "examples": [ { "description": "Add files/directories to a specific archive", "command": "zip {{-r|--recurse-paths}} {{path/to/compressed.zip}} {{path/to/file_or_directory1 path/to/file_or_directory2 ...}}" }, { "description": "Remove files/directories from a specific archive", "command": "zip {{-d|--delete}} {{path/to/compressed.zip}} {{path/to/file_or_directory1 path/to/file_or_directory2 ...}}" }, { "description": "Archive files/directories excluding specified ones", "command": "zip {{-r|--recurse-paths}} {{path/to/compressed.zip}} {{path/to/file_or_directory1 path/to/file_or_directory2 ...}} {{-x|--exclude}} {{path/to/excluded_files_or_directories}}" }, { "description": "Archive files/directories with a specific compression level (`0` - the lowest, `9` - the highest)", "command": "zip {{-r|--recurse-paths}} -{{0..9}} {{path/to/compressed.zip}} {{path/to/file_or_directory1 path/to/file_or_directory2 ...}}" }, { "description": "Create an encrypted archive with a specific password", "command": "zip {{-re|--recurse-paths --encrypt}} {{path/to/compressed.zip}} {{path/to/file_or_directory1 path/to/file_or_directory2 ...}}" }, { "description": "Archive files/directories to a multi-part split Zip archive (e.g. 3 GB parts)", "command": "zip {{-rs|--recurse-paths --split-size}} {{3g}} {{path/to/compressed.zip}} {{path/to/file_or_directory1 path/to/file_or_directory2 ...}}" }, { "description": "Print a specific archive contents", "command": "zip {{-sf|--split-size --freshen}} {{path/to/compressed.zip}}" } ] } }