I have to download a file from this link. The file download is a zip file which I will have to unzip in the current folder.

Normally, I would download it first, then run the unzip command.

$ wget http://www.vim.org/scripts/download_script.php?src_id=11834 -O temp.zip
$ unzip temp.zip

But in this way, I need to execute two commands, wait for the completion of first one to execute the next one, also, I must know the name of the file temp.zip to give it to unzip.

Is it possible to redirect output of wget to unzip? Something like

$ unzip < `wget http://www.vim.org/scripts/download_script.php?src_id=11834`

But it didn't work.

bash: wget http://www.vim.org/scripts/download_script.php?src_id=11834 -O temp.zip: ambiguous redirect

Also, wget got executed twice, and downloaded the file twice.

  • In the latter example, wget probably was executed twice because the ? is a special character in the shell. Putting the URL in ""s should help. – p-static Oct 8 '10 at 0:32
  • This thread seems to have a solution. Haven't tried it myself though. serverfault.com/questions/26474/… – user37850 Apr 25 '13 at 13:00

You have to download your files to a temp file, because (quoting the unzip man page):

Archives read from standard input are not yet supported, except with funzip (and then only the first member of the archive can be extracted).

Just bring the commands together:

wget "http://www.vim.org/scripts/download_script.php?src_id=11834" -O temp.zip
unzip temp.zip
rm temp.zip

But in order to make it more flexible you should probably put it into a script so you save some typing and in order to make sure you don't accidentally overwrite something you could use the mktemp command to create a safe filename for your temp file:

wget "$1" -O $TMPFILE
unzip -d $PWD $TMPFILE
  • Is wget file.zip && unzip file.zip the same as wget file.zip; unzip file.zip or is one preferred over the other? Thanks :) – jaggedsoft Dec 3 '16 at 20:10
  • 10
    @NextLocal wget && unzip will run unzip only if wget succeeded. wget ; unzip will run unzip anyway, possibly pointing to non existent file. – temoto Feb 7 '17 at 11:37
  • 2
    funzip was the answer I was looking for. Terraform (for some reason) packages it's binary as a single file in a zip archive so this was perfect for me. – Asfand Qazi Nov 7 '18 at 22:52

This is a repost of my answer to a similar question:

The ZIP file format includes a directory (index) at the end of the archive. This directory says where, within the archive each file is located and thus allows for quick, random access, without reading the entire archive.

This would appear to pose a problem when attempting to read a ZIP archive through a pipe, in that the index is not accessed until the very end and so individual members cannot be correctly extracted until after the file has been entirely read and is no longer available. As such it appears unsurprising that most ZIP decompressors simply fail when the archive is supplied through a pipe.

The directory at the end of the archive is not the only location where file meta information is stored in the archive. In addition, individual entries also include this information in a local file header, for redundancy purposes.

Although not every ZIP decompressor will use local file headers when the index is unavailable, the tar and cpio front ends to libarchive (a.k.a. bsdtar and bsdcpio) can and will do so when reading through a pipe, meaning that the following is possible:

wget -qO- http://example.org/file.zip | bsdtar -xvf-
  • 2
    This is excellent! I would note that tar gives me some warnings about the uncompressed data being the wrong size (expected 0), but the files themselves appear to be undamaged. Guessing this is due to the lack of the index. – Wyatt8740 Mar 17 '18 at 7:50
  • 3
    I have a .zip-file here that contains files with executable permissions. When I download and pipe into bsdtar, the exec bits get thrown away. When I download to disk and extract with bsdtar or unzip then, the exec bits are honoured. – Golar Ramblar May 4 '18 at 16:02
  • // , @GolarRamblar, didst ever find out why? – Nathan Basanese Sep 27 '18 at 19:16
  • 2
    @NathanBasanese: here is the answer. In short: A ZIP archive has two places where it stores such information, that can be inconsistent, and depending if the file bsdtar opens is seekable or not it uses the one or the other place. – Golar Ramblar Dec 11 '18 at 15:54

If you have the JDK installed, you can use jar:

wget -qO- http://example.org/file.zip | jar xvf /dev/stdin
  • 7
    I just found that jar doesn't preserve file permissions. Nice trick otherwise. – phunehehe Dec 25 '16 at 10:15
  • 11
    You don't need to give a file param, just use | jar xv – OneCricketeer Aug 25 '17 at 15:55
  • I, too, was bitten by the assumption than jar could be used as a replacement for unzip; Unfortunately jar does not restore extracted files' permissions; – cueedee Mar 9 '20 at 13:22
  • 1
    Just use | jar x – korakot May 17 '20 at 1:50
  • jar is much nicer handling UTF-8 filenames. unzip mangled things. – Marcin Oct 12 '20 at 5:35

I don't think you even want to bother piping wget's output into unzip.

From the wikipedia "ZIP (file format)" article:

A ZIP file is identified by the presence of a central directory located at the end of the file.

wget has to completely finish the download before unzip can do any work, so they run sequentially, not interwoven as one might think.


Repost of my answer:

BusyBox's unzip can take stdin and extract all the files.

wget -qO- http://downloads.wordpress.org/plugin/akismet.2.5.3.zip | busybox unzip -

The dash after unzip is to use stdin as input.

You can even,

cat file.zip | busybox unzip -

But that's just redundant of unzip file.zip.

If your distro uses BusyBox by default (e.g. Alpine), just run unzip -.

  • further to @Saftever's answer, which i'm not allowed to comment on, busybox will work but versions older than 1.27.0 won't due to a redundant lseek, see changelog busybox.net – Andrzej Cichocki Dec 13 '20 at 16:43

The proper syntax would be:

$ unzip <(curl -sL https://www.winpcap.org/archive/1.0-docs.zip)

but it won't work, because of the error (Info-ZIP on Debian):

lseek(3, 0, SEEK_SET)                   = -1 ESPIPE (Illegal seek)

Archive:  /dev/fd/63
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /dev/fd/63 or
        /dev/fd/63.zip, and cannot find /dev/fd/63.ZIP, period.

or on BSD/OS X:

Trying to read large file (> 2 GiB) without large file support

This is, because the standard zip tools are mainly using lseek function in order to set the file offset at the end to read its end of central directory record. It is located at the end of the archive structure and it is required to read the list of the files (see: Zip file format structure). Therefore the file cannot be FIFO, pipe, terminal device or any other dynamic, because the input object cannot be positioned by the lseek function.

So you have the following workarounds:

  • use different kind of compression (e.g. tar.gz),
  • you have to use two separate commands,
  • use alternative tools (as suggested in other answers),
  • create an alias or function to use multiple commands.
  • I think it still could be a FIFO. You'd just have to keep reading from the FIFO until EOF (effectively buffering the whole FIFO in memory or in a temp file). Totally doable to ease script creation, but not very useful. – Evan Carroll Oct 9 '16 at 20:28

If there is only one file in zip, you can use zcat or gunzip :

wget -qO- http://www.vim.org/scripts/download_script.php?src_id=11834 | gunzip

FYI : Here are the definitions of gunzip and zcat on my system :

$ grep ^exec $(which gunzip zcat)
/bin/gunzip:exec gzip -d "$@"
/bin/zcat:exec gzip -cd "$@"

A zip archive is not sequential because it often has the table of contents at the end of the file, so it is difficult to stream-unzip it.

An alternative solution is to see if you can get another file format, like .tar.gz.

For example, if you're downloading a .zip file from GitHub, there is almost always a .tar.gz version available.

For example,

Notice the pattern -- just replace .zip with .tar.gz and pipe to | tar xzf -


This works for me quite well:

tar xvf <(curl -sL http://www.vim.org/scripts/download_script.php?src_id=11834)

jar xvf <(curl -sL http://www.vim.org/scripts/download_script.php?src_id=11834)

wget -qO- http://www.vim.org/scripts/download_script.php?src_id=11834 | tar xvf -

wget -qO- http://www.vim.org/scripts/download_script.php?src_id=11834 | jar xvf -

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.