zip-a-folder vs adm-zip vs node-zip vs yazl vs zip-lib
Node.js Zip Libraries
zip-a-folderadm-zipnode-zipyazlzip-libSimilar Packages:

Node.js Zip Libraries

These libraries are designed for creating, reading, and manipulating ZIP files in Node.js applications. They provide various functionalities to handle file compression and decompression, making it easier for developers to manage file archives. Each library has its own strengths, catering to different use cases and performance requirements, allowing developers to choose the best fit for their specific needs.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
zip-a-folder177,55276212 kB05 days agoMIT
adm-zip02,161122 kB14419 days agoMIT
node-zip0217-2011 years ago-
yazl037558.7 kB19a year agoMIT
zip-lib04270.2 kB17 days agoMIT

Feature Comparison: zip-a-folder vs adm-zip vs node-zip vs yazl vs zip-lib

Ease of Use

  • zip-a-folder:

    zip-a-folder is extremely user-friendly, allowing developers to zip entire folders with just a single function call. This makes it an excellent choice for those who want to avoid dealing with individual file management.

  • adm-zip:

    adm-zip is known for its simplicity and ease of use. It provides a straightforward API that allows developers to quickly create and extract ZIP files without needing to understand the underlying complexities of the ZIP format.

  • node-zip:

    node-zip has a more complex API that may require a deeper understanding of ZIP file structures. While it offers flexibility, it may not be as user-friendly for beginners or those looking for quick implementations.

  • yazl:

    yazl is designed with performance in mind, but it also maintains a relatively simple API for creating ZIP files. It strikes a balance between ease of use and performance, making it accessible for most developers.

  • zip-lib:

    zip-lib offers a comprehensive API that may have a steeper learning curve but provides extensive functionality for advanced users. It is suitable for those who need more than basic zipping capabilities.

Performance

  • zip-a-folder:

    zip-a-folder is efficient for zipping directories but may not be as fast as yazl for large files. It is designed for convenience rather than raw performance, making it suitable for smaller tasks.

  • adm-zip:

    While adm-zip is easy to use, it may not be the most performant option for creating large ZIP files, as it loads everything into memory before writing to disk, which can lead to high memory usage.

  • node-zip:

    node-zip provides a good balance between performance and flexibility. It allows for more control over the compression process, which can lead to better performance in specific scenarios, especially when handling custom data.

  • yazl:

    yazl is optimized for performance, making it one of the fastest libraries for creating ZIP files. It uses streaming to handle large files efficiently, minimizing memory usage and speeding up the zipping process.

  • zip-lib:

    zip-lib offers good performance, especially with its support for streaming and encryption. It is suitable for applications that require both speed and advanced features.

File Handling Capabilities

  • zip-a-folder:

    zip-a-folder simplifies the process of zipping entire directories, but it does not provide options for manipulating individual files within the archive. It is best for straightforward zipping tasks.

  • adm-zip:

    adm-zip supports basic file operations such as adding, extracting, and deleting files within a ZIP archive. However, it lacks advanced features like streaming or encryption.

  • node-zip:

    node-zip allows for detailed control over file handling, including the ability to manipulate file headers and compression levels. This makes it suitable for developers who need to customize their ZIP files extensively.

  • yazl:

    yazl focuses on creating ZIP files efficiently but does not support reading ZIP files. It is primarily a one-way tool for zipping data, making it less versatile than some alternatives.

  • zip-lib:

    zip-lib excels in file handling capabilities, supporting both zipping and unzipping with advanced features like file encryption and streaming. It is ideal for complex applications that require robust file management.

Advanced Features

  • zip-a-folder:

    zip-a-folder is designed for simplicity and does not include advanced features, making it ideal for quick and easy zipping tasks without the need for complex configurations.

  • adm-zip:

    adm-zip lacks advanced features such as file encryption or streaming, making it suitable for basic use cases but limiting for more complex applications.

  • node-zip:

    node-zip does not offer advanced features like encryption or streaming, focusing instead on flexibility and control over the ZIP creation process.

  • yazl:

    yazl does not support reading ZIP files and lacks advanced features like encryption, focusing solely on efficient ZIP file creation.

  • zip-lib:

    zip-lib includes advanced features such as file encryption, streaming, and support for various compression methods, making it a powerful choice for applications that require robust file handling.

Community and Support

  • zip-a-folder:

    zip-a-folder has a limited community but offers straightforward documentation, making it easy for users to get started without much assistance.

  • adm-zip:

    adm-zip has a moderate user base and community support, with sufficient documentation and examples available for common use cases.

  • node-zip:

    node-zip has a smaller community, which may result in less available support and fewer resources compared to more popular libraries.

  • yazl:

    yazl has a growing community and is well-documented, providing good support for developers looking to implement its features effectively.

  • zip-lib:

    zip-lib has a strong community and extensive documentation, making it a reliable choice for developers who may need support or resources during implementation.

How to Choose: zip-a-folder vs adm-zip vs node-zip vs yazl vs zip-lib

  • zip-a-folder:

    Use zip-a-folder if you need a simple solution to zip entire directories easily. This library abstracts the complexity of zipping multiple files and folders, making it perfect for applications that need to package entire directories with minimal configuration.

  • adm-zip:

    Choose adm-zip if you need a straightforward and easy-to-use library for basic ZIP file operations. It supports both reading and writing ZIP files and is suitable for smaller projects or quick tasks where simplicity is key.

  • node-zip:

    Opt for node-zip if you require a more flexible and low-level approach to ZIP file manipulation. It allows for more control over the compression process and is ideal for developers who need to customize the ZIP creation process extensively.

  • yazl:

    Select yazl when performance is a priority, especially for creating large ZIP files. It is designed for speed and efficiency, making it suitable for applications that need to handle large amounts of data quickly and with minimal memory overhead.

  • zip-lib:

    Choose zip-lib for a comprehensive solution that supports both zipping and unzipping files with advanced features like streaming and file encryption. It is ideal for applications that require robust file handling capabilities and additional features.

README for zip-a-folder

NPM

CircleCI Codacy Badge Codacy Coverage Known Vulnerabilities

zip-a-folder

Compress a folder into ZIP/TAR/TGZ/BR/7z. This library is trying to with as less dependencies as possible to other libraries. For ZIP, TAR and Brotli archives it uses the native Node.js compression (zlib). 7z uses the pure JavaScript lzma-js library for LZMA compression.

Feature overview:

  • ZIP archives (with optional ZIP64)
  • TAR archives (optionally gzipped or brotli-compressed)
  • 7z archives with LZMA compression (via lzma-js)
  • Fine-grained zlib/gzip/brotli/LZMA control
  • Globs (single or comma-separated)
  • Parallel directory scanning (statConcurrency)
  • Custom write streams
  • Compression presets (high, medium, uncompressed)

Table of Contents


Incompatible Changes

Version 2

Added support for comma-separated glob lists. This may change the behavior for cases previously interpreted as "folder only".

Version 3

Dual-module support (CJS + ESM).

Version 3.1

Added support for destPath to control the internal path layout of created archives.

Version 4

A major rewrite using:

  • Fully native ZIP writer (no dependencies)
  • Native TAR + gzip writer
  • ZIP64 support for large archives
  • Parallel statting (statConcurrency)
  • Strict internal path normalization mirroring classic zip-a-folder behavior
  • Native glob handling via tinyglobby

Version 5

  • COMPRESSION_LEVEL is now a plain const object whose values are string literals ('uncompressed', 'medium', 'high') instead of a numeric enum. The public API (COMPRESSION_LEVEL.high, etc.) is unchanged — only the underlying type changed from a TypeScript enum to a const satisfies object. See PR #70 by @schplitt.
  • Added exclude option — an array of glob patterns for files/directories to omit from the archive. See issue #65 by @Pomax.

Version 6 (current)

  • Native Brotli compression support for TAR archives using Node.js built-in zlib.brotliCompressSync(). Create .tar.br files with the new compressionType: 'brotli' option. Brotli typically provides better compression ratios than gzip, especially for text-based content.
  • New 7z archive format support via the sevenZip() function. Uses pure JavaScript LZMA compression (via lzma-js library) — no external binaries required. Provides excellent compression ratios with the industry-standard 7z format.
  • New brotliOptions for fine-grained control over brotli compression parameters.
  • New compressionLevel option (1-9) for 7z archives to control LZMA compression level.

Installation

npm install zip-a-folder

Usage

Create a ZIP file

import { zip } from 'zip-a-folder';

await zip('/path/to/folder', '/path/to/archive.zip');

Create a GZIP-compressed TAR file (.tgz)

import { tar } from 'zip-a-folder';

await tar('/path/to/folder', '/path/to/archive.tgz');

Compression Handling

Supported compression levels:

COMPRESSION_LEVEL.high          // highest compression (default)
COMPRESSION_LEVEL.medium        // balanced
COMPRESSION_LEVEL.uncompressed  // STORE for zip, no-gzip for tar

v5: COMPRESSION_LEVEL is now a const object with string values ('high', 'medium', 'uncompressed'). The compression option accepts either the constant (COMPRESSION_LEVEL.high) or the plain string ('high') directly.

Example:

import { zip, COMPRESSION_LEVEL } from 'zip-a-folder';

await zip('/path/to/folder', '/path/to/archive.zip', {
    compression: COMPRESSION_LEVEL.medium  // or just 'medium'
});

ZIP Options

OptionTypeDescription
commentstringZIP file comment
forceLocalTimebooleanUse local timestamps instead of UTC
forceZip64booleanAlways include ZIP64 headers
namePrependSlashbooleanPrefix all ZIP entry names with /
storebooleanForce STORE method (no compression)
zlibZlibOptionsPassed directly to zlib.deflateRaw
statConcurrencynumberParallel stat workers (default: 4)
destPathstringPrefix inside the archive (>=3.1)
excludestring[]Glob patterns for paths to omit
customWriteStreamWriteStreamManually handle output

Example:

await zip('/dir', '/archive.zip', {
    comment: "Created by zip-a-folder",
    forceZip64: true,
    namePrependSlash: true,
    store: false,
    statConcurrency: 16,
    zlib: { level: 9 }
});

TAR / TGZ / TAR.BR Options

OptionTypeDescription
compressionType'none' | 'gzip' | 'brotli'Compression algorithm (default: 'gzip')
gzipbooleanEnable gzip compression (deprecated, use compressionType)
gzipOptionsZlibOptionsPassed to zlib.createGzip
brotliOptionsBrotliOptionsPassed to zlib.createBrotliCompress
statConcurrencynumberParallel stat workers
excludestring[]Glob patterns to omit
compressionCOMPRESSION_LEVELConvenience preset (high, medium, uncompressed)

Gzip Example

await tar('/dir', '/archive.tgz', {
    compressionType: 'gzip',
    gzipOptions: { level: 6 }
});

Brotli Example

Brotli compression is supported natively via Node.js zlib module (available since Node.js v10.16.0). Brotli typically provides better compression ratios than gzip, especially for text-based content.

import { tar, COMPRESSION_LEVEL } from 'zip-a-folder';
import * as zlib from 'zlib';

// Simple brotli compression
await tar('/dir', '/archive.tar.br', {
    compressionType: 'brotli'
});

// With compression level preset
await tar('/dir', '/archive.tar.br', {
    compressionType: 'brotli',
    compression: COMPRESSION_LEVEL.high
});

// With custom brotli options
await tar('/dir', '/archive.tar.br', {
    compressionType: 'brotli',
    brotliOptions: {
        params: {
            [zlib.constants.BROTLI_PARAM_QUALITY]: 11,  // 0-11, higher = better compression
            [zlib.constants.BROTLI_PARAM_MODE]: zlib.constants.BROTLI_MODE_TEXT
        }
    }
});

Uncompressed TAR

await tar('/dir', '/archive.tar', {
    compressionType: 'none'
});

7z Options

Create 7z archives with LZMA compression using the sevenZip() function.

OptionTypeDescription
compressionCOMPRESSION_LEVELConvenience preset (high, medium, uncompressed)
compressionLevelnumber (1-9)LZMA compression level (default: 5)
statConcurrencynumberParallel stat workers (default: 4)
excludestring[]Glob patterns to omit
customWriteStreamWriteStreamManually handle output

Basic Example

import { sevenZip } from 'zip-a-folder';

await sevenZip('/path/to/folder', '/path/to/archive.7z');

With Compression Level

import { sevenZip, COMPRESSION_LEVEL } from 'zip-a-folder';

// Using preset
await sevenZip('/dir', '/archive.7z', {
    compression: COMPRESSION_LEVEL.high
});

// Using explicit level (1-9)
await sevenZip('/dir', '/archive.7z', {
    compressionLevel: 9
});

With Glob Patterns

await sevenZip('src/**/*.ts', '/archive.7z');

With Exclusions

await sevenZip('/project', '/archive.7z', {
    exclude: ['node_modules/**', '**/*.log']
});

Note: 7z archives use LZMA compression via the lzma-js library. This provides excellent compression ratios, especially for text-based content. The 7z format stores files as a solid archive, meaning all file data is concatenated and compressed together for better compression efficiency.


Custom Write Streams

ZIP and TAR can be written into any stream. If customWriteStream is used, the targetFilePath can be empty or undefined.

import fs from 'fs';
import { zip } from 'zip-a-folder';

const ws = fs.createWriteStream('/tmp/output.zip');
await zip('/path/to/folder', undefined, { customWriteStream: ws });

Important: zip-a-folder does not validate custom streams. You must ensure:

  • parent directory exists
  • you're not writing into the source directory (to avoid recursion)

Glob Handling

The first parameter may be:

  • A path to a directory
  • A single glob
  • A comma-separated list of globs

Example:

await zip('**/*.json', '/archive.zip');
await zip('**/*.json, **/*.txt', '/archive2.zip');

If no files match, zip-a-folder throws:

Error: No glob match found

Destination Path Handling (destPath)

Adds a prefix inside the archive:

await zip('data/', '/archive.zip', { destPath: 'data/' });

Resulting ZIP layout:

data/file1.txt
data/subdir/file2.txt

Directory Root Inclusion Semantics

When passing a directory path as the first argument (e.g. zip('/path/to/folder', '/archive.zip')), the archive by default contains the contents of that directory at the archive root (i.e. you will see the files inside folder/, not a top-level folder/ directory itself).

Include the directory itself

If you want the archive to unpack into the named folder (so the top level of the archive contains folder/), set destPath to that folder name plus a trailing slash:

await zip('/path/to/folder', '/archive.zip', {
  destPath: 'folder/'
});

Result layout:

folder/file1.txt
folder/sub/file2.txt

Summary

  • Default: directory contents only (no enclosing folder)
  • To include the folder: use destPath: '<dirname>/'

This applies equally to tar().


Excluding Files and Directories (exclude)

The exclude option accepts an array of picomatch-style glob patterns. Matching entries (files and directories) are omitted from the archive entirely — when a directory is excluded its entire subtree is skipped.

import { zip } from 'zip-a-folder';

const packed = await zip('/path/to/project', '/path/to/archive.zip', {
  exclude: [
    // dot-files (.env, .DS_Store, …)
    '**/.*',
    // dot-directories (.git, .vscode, …) and their contents
    '**/.*/**',
    // build output and dependencies
    'dist/**',
    'dist/',
    'node_modules/**',
    'node_modules/',
  ]
});

Notes:

  • exclude is applied to directory sources and glob sources alike.
  • For glob sources, the patterns are passed as additional ignore entries to tinyglobby.
  • Patterns are matched against relative paths inside the source directory (POSIX-style).
  • To exclude a whole directory tree, add both dirname/ and dirname/** (or just dirname/**).

Inspired by issue #65 reported by @Pomax.


Module Import Structure

Note: As of v4 and the modernized build, all code is bundled into a single entry file. Do not import submodules (e.g. dist/lib/mjs/core/types). Always import from the main entry point:

import { zip, tar, COMPRESSION_LEVEL } from 'zip-a-folder';

If you need types, import from the main entry point as well:

import type { ZipArchiveOptions, TarArchiveOptions } from 'zip-a-folder';

Native Implementation Notes

  • ZIP and TAR are written using pure Node.js (zlib, raw buffering)
  • ZIP64 support included
  • File system scanning performed with a parallel stat queue
  • Globs handled via the tinyglobby package
  • Archive layout matches the original zip-a-folder for compatibility
  • ZIP writer supports dependency-free deflate and manual header construction
  • TAR writer produces POSIX ustar format with proper 512-byte block alignment

Unix Permissions Preservation in ZIP

A recent contribution restored correct handling of file modes for Unix systems inside ZIP archives:

  • The "Version Made By" field is now set to Unix (upper byte = 3) in the Central Directory.
  • File modes from fs.stat().mode are passed through to the ZIP entries and preserved.
  • Modes are mapped into the upper 16 bits of the "External File Attributes" field per the ZIP spec.

This brings parity back with v3 behavior and ensures executables and other POSIX permissions are preserved when packaging for Linux/Debian and similar environments.

See PR #66: https://github.com/maugenst/zip-a-folder/pull/66

Automated tests were added to validate:

  • Central Directory "Version Made By" upper byte is 3 (Unix).
  • External File Attributes store the POSIX mode (both files and directories), including directory flag.
  • FileCollector behavior and glob handling are fully covered, pushing coverage to 100% lines/functions.

Command Line Interface (CLI)

zip-a-folder includes a CLI for quick archive creation from the terminal.

Installation

# Global installation
npm install -g zip-a-folder

# Or use via npx
npx zip-a-folder ./folder ./archive.zip

Usage

zip-a-folder <source> <target> [options]

Supported Formats

ExtensionDescription
.zipZIP archive (deflate compression)
.tarTAR archive (uncompressed)
.tgzTAR archive with gzip compression
.tar.gzTAR archive with gzip compression
.tar.brTAR archive with brotli compression
.7z7z archive with LZMA compression

Options

OptionDescription
-h, --helpShow help message
-V, --versionShow version number
-v, --verboseShow detailed progress (files being processed)
-q, --quietSuppress all output except errors
-c, --compression <level>Compression preset: high, medium, uncompressed
-l, --level <number>Compression level (1-9, format-specific)
-e, --exclude <pattern>Glob pattern to exclude (can be used multiple times)
-d, --dest-path <path>Destination path prefix inside archive

Examples

# Create a ZIP archive
zip-a-folder ./my-folder ./archive.zip

# Create a gzipped TAR with verbose output
zip-a-folder ./src ./backup.tgz -v

# Create a 7z archive with maximum compression
zip-a-folder ./project ./project.7z -c high

# Create archive excluding node_modules
zip-a-folder ./app ./app.zip -e "node_modules/**" -e "**/*.log"

# Create brotli-compressed TAR
zip-a-folder ./data ./data.tar.br -v

# Use glob patterns
zip-a-folder "src/**/*.ts" ./source.zip

# Quiet mode (only errors)
zip-a-folder ./folder ./archive.zip -q

Output

By default, the CLI shows a summary with:

  • Source and target paths
  • Archive format
  • File count
  • Original and compressed sizes
  • Compression ratio
  • Processing time

Use -v for detailed file-by-file progress, or -q to suppress all output.


Running Tests

Tests are written in Vitest with full coverage (100% statements/branches/functions/lines):

npm test

Coverage is reported automatically via @vitest/coverage-v8.


Thanks

Special thanks to contributors:

  • @sole – initial work
  • @YOONBYEONGIN
  • @Wunschik
  • @ratbeard
  • @Xotabu4
  • @dallenbaldwin
  • @wiralegawa
  • @karan-gaur
  • @malthe
  • @nesvet
  • @schplitt – string-literal compression levels refactor (PR #70)
  • @Pomax – exclude option feature request (issue #65)

Additional thanks to everyone helping shape the native rewrite.