Measured - byte-exact - 2026

Pedulli vs Zopfli

measured head-to-head - structured data classes - byte-exact SHA-256 verified

TL;DR - honest
Zopfli is Google's ultra-slow DEFLATE compressor (about 100x slower than gzip) that produces fully gzip-compatible output. The Pedulli Orchestrator is a best-of-N racer: it races xz, zstd, brotli and your data's SRD math, then keeps the smallest verified output, always byte-exact (SHA-256 roundtrip) with a +1 byte never-worse floor on its own output. So it is never larger than the best standard codec it races (worst case +1 byte): it wins outright on structured data and ties the best codec on already-optimal or random data. Use Zopfli only if you must emit .gz that decodes everywhere; use Pedulli otherwise.

The measured table

All numbers measured on this server, roundtrip-verified SHA-256 byte-exact. Proofs available on request.

InputZopfli --i100Pedulli (best-of-N)Δ
1 MiB of zeros1,029 B13 Bmuch smaller (redundant input)
JSON 31 KB4,389 B1,265 B-71.2%
HTML 161 KB47,932 B38,757 B-19.1%
MP4 master 10 MB9,732,140 B9,430,108 B-302 KB
Random bytes 1 MB1,048,759 B (+183 B)1,048,577 B (+1 B)182 B less overhead

What Zopfli does better (honest)

What Pedulli does that Zopfli does not

When to switch

Use Zopfli when consumers need bit-compatible .gz output (CDN-friendly, browser-friendly). Use Pedulli when you control both ends and ratio matters, plus the per-file +1 byte never-worse floor.

More comparisons: zstd - xz - 7-Zip - brotli - gzip