google/zopfli

Zopfli Compression Algorithm is a compression library programmed in C to perform very good, but slow, deflate or zlib compression.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 21st, 2026
Created on March 9th, 2015
Open Issues & Pull Requests: 120 (+0)
GitHub issues: Enabled
Number of forks: 356
Total Stargazers: 3,596 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 622 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Zopfli is a compression library that performs deflate and zlib compression with a focus on achieving high compression ratios at the cost of slower encoding speed.

The tool addresses the problem of file size reduction where maximum compression density matters more than encoding performance. It implements a deflate-compatible compression algorithm that prioritizes output size by using more sophisticated analysis during the compression process. Rather than optimizing for speed like standard deflate implementations, Zopfli trades encoding time for better compression ratios, making compressed files smaller while remaining compatible with standard decompression tools.

Zopfli suits scenarios where compression happens offline or infrequently, such as distributing static assets, archiving data, or preparing files for transmission where bandwidth is constrained. It works well for projects where the one-time cost of slower compression is justified by the ongoing benefit of smaller file sizes. The tool is particularly valuable when targeting web delivery or storage-constrained environments where every byte saved has measurable impact. It should not be chosen for real-time compression needs or applications requiring fast encoding, as the slower speed is an inherent characteristic of its algorithm rather than an implementation detail that could be optimized away.

Development activity shows consistent maintenance with regular commits addressing bug fixes and improvements. The project receives pull requests that are reviewed and integrated into the codebase. Issues are tracked and addressed by maintainers, indicating active engagement with user-reported problems. The codebase remains actively updated with refinements to the compression algorithm and compatibility improvements.