Ways to Batch Extract Multiple zip Files on CentOS

Ways to Batch Extract Multiple zip Files on CentOS

When you deploy websites on CentOS, the files you pull down from a backup center or object storage are often a pile of zip archives: theme packages, plugin packages, log archives, or a full-site backup from a given time window. Extracting them one by one is slow and easy to miss. This article rounds up four batch-extraction approaches covering scenarios from a few files to hundreds or thousands.

Before you start, confirm unzip is installed.

1. Install the Extraction Tools

yum install unzip -y

If you also need to extract rar files, install unrar as well:

yum install unrar -y

unzip is tiny and takes up almost no space, so it's worth having as a standard utility.

2. Enter the Directory Containing the Files

cd /path/to/zips

Then choose one of the methods below for your situation.

Method 1: Separate with Semicolons or && (suitable for a small number)

unzip a.zip && unzip b.zip && unzip c.zip

Or:

unzip a.zip; unzip b.zip; unzip c.zip

The difference: && only runs the next command if the previous one succeeded, so a corrupted archive stops the chain and alerts you to the problem; ; keeps going regardless of success or failure. With just three or five files, this is the most obvious approach.

Method 2: Use find with -exec

find . -name '*.zip' -exec unzip {} \;

This recursively finds all .zip files under the current directory and extracts them one by one — ideal when the archives are scattered across subdirectories. {} is find's placeholder, and \; runs the command once per result. If filenames may contain spaces, switch to find . -name '*.zip' -print0 | xargs -0 -n1 unzip -o instead.

Method 3: Use ls with xargs (recommended)

ls *.zip | xargs -n1 unzip -o

• -n1: pass only one filename to unzip at a time (note that this is the number 1, not the letter l);
• -o: extract in overwrite mode without prompting for confirmation.

To extract password-protected zip files, add the -P option:

ls *.zip | xargs -n1 unzip -o -P password

Note: putting a password directly on the command line leaves it in your shell history. Fine for quick one-offs, but prefer interactive input in production.

Method 4: Use a for Loop

for i in *.zip
do
    unzip -o $i
done

The advantage of a for loop is that you can add logic: create a directory before extracting, delete the source archive afterward, or count failures. Reach for it when you need flexibility.

Batch Extract Files with a Given Prefix

For example, to overwrite-extract all zip files starting with ab:

ls ab*.zip | xargs -n1 unzip -o

Summary

A Real-World Example

When you launch a new site, if the theme and plugins are all zip archives, a typical workflow looks like this:

cd /www/wwwroot/mysite/wp-content/themes
ls *.zip | xargs -n1 unzip -o
chown -R www:www /www/wwwroot

After extracting, fix the ownership in the same step so the site doesn't complain about unwritable directories. The same logic applies to log backups: extract to a temp directory first, verify integrity, then overwrite the live files — safer than extracting in place.

Extract to a Specified Directory

By default unzip writes files to the current directory, which can get tangled with the archive's internal folder structure. To collect everything in a target directory, use the -d option:

mkdir -p /www/wwwroot/uploads
ls *.zip | xargs -n1 unzip -o -d /www/wwwroot/uploads

Log and backup files then stay out of the current directory. Before a batch run, it's a good idea to extract one archive first to check its internal structure with unzip -l:

unzip -l a.zip | head -20

A Few Handy Options

Besides -o and -P, two more options get regular use:

• -q: quiet mode — suppress per-file detail while extracting, so the terminal isn't flooded when processing hundreds of archives;
• -n: extract only files that don't already exist in the target directory and skip the rest — handy for "topping up missing files" rather than overwriting everything.

You can also swap \; for + in the find -exec form, letting find hand multiple filenames to a single unzip process:

find . -name '*.zip' -exec unzip -o {} +

This reduces how many processes get spawned, which is noticeably faster when there are many archives.

Notes on Extracting Untrusted Files

Before extracting zips downloaded from the internet, watch out for path traversal (zip slip): a maliciously crafted archive can carry ../ entries that write files outside the target directory, even over system files. Run unzip -l first and inspect the entry paths; if any contain .., discard the whole archive. Get into this habit on production servers especially — a clobbered live directory costs far more than a slightly slower extraction.

Common Issues

Q: If one zip is corrupted during a batch run, does the process stop?
A: The find -exec and xargs approaches keep going with the remaining files; only the && chained method stops on error. To count failures after a batch, check exit codes in a for loop:

for i in *.zip; do
  if unzip -o "$i" > /dev/null 2>&1; then
    echo "OK: $i"
  else
    echo "FAIL: $i"
  fi
done

Q: What about filenames with spaces or Chinese characters?
A: find -print0 | xargs -0 handles paths with spaces reliably. If Chinese filenames come out garbled, it's usually a zip encoding issue — specify it with unzip -O gbk first.

Q: How do I check disk space before extracting?
A: Use du -ch *.zip | tail -1 for the total archive size, then compare with the free space from df -h. Heavily compressed log archives can expand severalfold, so don't blindly batch-extract when the disk is nearly full.

The xargs approach is the most convenient for batch extraction, and -n1 is the key option (the number 1, not the letter l). For batch compressing folders, refer to batch compressing folders in Linux. For more server operations content, see the cloud servers category.

Reference: the unzip manual page https://man7.org/linux/man-pages/man1/unzip.1.html; original post: https://www.cnblogs.com/cqzhuomi/articles/17284290.html (cnblogs.com CQZHUOMI, repost)