Install zxc with Homebrew

Project links

• Homepage

Commands and aliases

• unzxc
• zxc

Project history

The public repository starts in late 2025 and credits Bertrand Lebonnois and contributors. The README positions ZXC as a C library with official Rust, Python, Node.js, and Go bindings, hand-tuned SIMD paths, a seekable format, and a design focused on modern ARM and x86 pipelines.

Adoption history

Because ZXC is new, its adoption history is mostly early ecosystem seeding rather than long-term production lineage. The project highlights inclusion in lzbench and TurboBench benchmark suites, plus availability through C/C++ package ecosystems and language-specific bindings, as evidence that it is being made easy to test against existing codecs.

How it is used

ZXC targets assets and payloads compressed once and read many times: game assets, app bundles, firmware updates, content delivery, and embedded data. The CLI compresses and decompresses files, while the C API and language bindings let applications embed the codec directly.

Why package nerds care

For package nerds, ZXC is interesting less as a mature standard and more as a packaged experiment in codec trade-offs. It competes with the LZ4/Snappy/Zstd mental model by making decompression throughput and ratio at read time the headline package value.

Timeline

• 2025-12: Public git history begins and early 0.1.x releases appear.
• 2026-02: 0.6.0-era changes emphasize compression, ratio, and data-integrity improvements.
• 2026-06: 0.12.0-era release work extends signed release provenance and packaging polish.

Related projects

• LZ4 and LZ4HC: the speed-oriented family ZXC benchmarks against most directly.
• Zstd: the denser general-purpose codec ZXC contrasts with in its design discussion.
• lzbench and TurboBench: benchmark suites used to compare ZXC with other codecs.

Sources

• https://github.com/hellobertrand/zxc
• https://github.com/hellobertrand/zxc/releases
• https://github.com/inikep/lzbench
• https://github.com/powturbo/TurboBench