zlib is a software library used for data compression. zlib was written by Jean-loup Gailly and Mark Adler and is an abstraction of the DEFLATE compression algorithm used in their gzip file compression program. zlib is also a crucial component of many software platforms, including Linux, macOS, and iOS. It has also been used in gaming consoles such as the PlayStation 4, PlayStation 3, Wii U, Wii, Xbox One and Xbox 360.

zlib logo
Initial release1 May 1995 (1995-05-01)
Stable release
1.2.11 / 15 January 2017; 4 years ago (2017-01-15)
Repository Edit this at Wikidata
Written inC
Operating systemCross-platform
TypeData compression
Licensezlib License

The first public version of zlib, 0.9, was released on 1 May 1995 and was originally intended for use with the libpng image library. It is free software, distributed under the zlib License.



zlib compressed data are typically written with a gzip or a zlib wrapper. The wrapper encapsulates the raw DEFLATE data by adding a header and trailer. This provides stream identification and error detection that are not provided by the raw DEFLATE data.

The gzip header, used in the ubiquitous gzip file format, is larger than the zlib header, as it stores a file name and other file system information.


As of September 2018, zlib only supports one algorithm, called DEFLATE, which uses a combination of a variation of LZ77 (Lempel–Ziv 1977) and Huffman coding.[1] This algorithm provides good compression on a wide variety of data with minimal use of system resources. This is also the algorithm used in the Zip archive format. The header makes allowance for other algorithms, but none are currently implemented.

Resource useEdit

zlib provides facilities for control of processor and memory use. A compression level value may be supplied that trades speed for compression. There are also facilities for conserving memory, useful in restricted memory environments, such as some embedded systems.


The compression can be optimized for specific types of data. If one is using the library to always compress specific types of data, then using a specific strategy may improve compression and performance. For example, if the data contain long lengths of repeated bytes, the run-length encoding (RLE) strategy may give good results at higher speed. For general data, the default strategy is preferred.

Error handlingEdit

Errors in compressed data may be detected and skipped. Further, if "full-flush" points are written to the compressed stream, then corrupt data can be skipped, and the decompression will resynchronize at the next flush point — although no error recovery of the corrupt data is provided. Full-flush points are useful for large data streams on unreliable channels, where some data loss is unimportant, such as in some multimedia applications. However, creating many flush points can affect the speed as well as amount (ratio) of compression.

Data lengthEdit

There is no limit to the length of data that can be compressed or decompressed. Repeated calls to the library allow an unlimited numbers of blocks of data to be handled. Some ancillary code (counters) may suffer from overflow for long data streams, but this does not affect the actual compression or decompression.

When compressing a long (or infinite) data stream, it is advisable to write regular full-flush points.


Today, zlib is something of a de facto standard, to the point that zlib and DEFLATE are often used interchangeably in standards documents, with thousands of applications relying on it for compression, either directly or indirectly.[2] These include:

zlib is also used in many embedded devices, such as the Apple iPhone and Sony PlayStation 3, because the code is portable, liberally licensed, and has a relatively small memory footprint.


A commonly used library built on an old code base, zlib is also frequently forked by third-parties that claim improvements to this library:

  • Intel has a high-performance fork of zlib.[6]
  • CloudFlare maintains a high-performance fork with "massive" improvements.[7]
  • Zlib-ng is a zlib replacement fork with optimizations for "next generation" systems.

See alsoEdit


  1. ^ https://tools.ietf.org/html/rfc1951
  2. ^ Gailly, Jean-loup; Adler, Mark (2002-04-18), zlib Applications
  3. ^ https://stackoverflow.com/questions/26244134/why-does-curl-use-zlib
  4. ^ https://blog.cloudera.com/orcfile-in-hdp-2-better-compression-better-performance/ cite orc.compress=Zlib as default.
  5. ^ System.IO.Compression.DeflateStream. MSDN Library.
  6. ^ "Intel® IPP ZLIB Coding Functions". Intel Software. 31 July 2019. Retrieved 18 January 2020.
  7. ^ "Fighting Cancer: The Unexpected Benefit Of Open Sourcing Our Code". The Cloudflare Blog. 8 July 2015.

External linksEdit