Zip, RAR, 7-Zip ou Crate?

General-purpose zippers were built for documents and code. They do shrink an audio session — and then they stop, because a waveform is a wall of random bytes to them. Crate was built for one job: moving audio sessions. It reads the stems, packs them to roughly half the size of a zip, and proves every byte arrived perfectly.

Try it yourself: take a finished multitrack session, zip it, then pack it with Crate. Across the twenty real client sessions in our benchmark, the zip came out between 1.38 and 2.46 times the size of the .crate package. The zip is not doing nothing — it saved a median of 51.5% (per-session range 15–88%). It simply runs out of things to find, because a byte-level compressor never sees the waveform underneath.

O Crate não compacta bytes. Ele decodifica o áudio, recodifica sem perdas (FLAC para inteiro, WavPack para float), deduplica takes e bounces repetidos entre arquivos e reconstrói um gêmeo exato do outro lado, conferido amostra por amostra com SHA-256.

Lado a lado

 ZipRAR7-ZipCrate
Entende áudio———Sim
Tamanho empacotado, fração do original45.2%30.9%35.1%25.2%
Prova que a cópia é bit a bit———SHA-256
Deduplica takes entre arquivos——parcialSim
Abre um arquivo compactado arrastado e empacota o áudio dentro dele———Sim
Divide em volumes do tamanho do upload—SimSimSim
Dados de recuperação para transferências instáveis—Sim—Sim
Grátis para o destinatário abrirSimSimSimSim
Arquivos saem da sua máquinanãonãonãonão

Percentages are the packed size as a share of the original session — lower is smaller. Figures are pooled across the eleven mixed sessions of the current benchmark, every archiver at its strongest setting (zip -9, RAR -m5 -s -md1g, 7-Zip -mx=9, Crate on Smallest), every result restored and compared byte for byte. Per-session ranges are wider — the Impact page carries them lane by lane.

O benchmark

One run, one machine, nothing else running. Twenty real client sessions — mixed, loop-heavy, stem exports and dense live recordings — each packed by Crate on both of its presets and by ten other archiver configurations set for maximum compression, every run restored and compared byte for byte. Sessions are pooled into four material classes so no one session can stand in for the rest. The full tables are on the Impact page, engine by engine.

1.38–2.46×
the size of a zip of the same session, across all twenty measured
5.5–8.8×
faster to pack than RAR at maximum settings, on the pilot corpus measured at these documented settings
72%
typical reduction on a session of 1 GB or more, across 301 production packs
The ranges overlap because the sessions differ, not because the engines do — every engine packed the same twenty sessions. Pooled on the mixed-class lane, the zip came out 1.79 times the size of the .crate package. Same files, same machine, same clock.

Por que a diferença existe

A zipper looks for repeated byte patterns, and a session does hold some: headers, long stretches of silence, whole files that appear twice. That is worth the 15 to 88% a zip finds on audio sessions — about half, at the median — and then the search is over, because the low bits of a 24-bit WAV are noise to it. Crate instead does what an audio engineer would: it reads the actual waveform, stores it in a lossless audio codec, notices when two tracks are the same take (on by default) and — on the Smallest preset — when a bus is the sum of its stems, keeping only what's unique. Then it reassembles a byte-identical copy and proves it.

É também por isso que o Crate pode ser honesto sobre ser sem perdas: “sem perdas” não é uma promessa na caixa, é uma checagem SHA-256 em cada arquivo, toda vez.

Quando o zip resolve

Se você vai mandar uns MP3s, um PDF ou uma pasta de código, use o zip: está em todo lugar e a economia não faria diferença. O Crate ganha o lugar dele no momento em que você move uma sessão de verdade: muitas pistas, WAVs grandes, uma conexão lenta ou cara e um prazo que não sobrevive a um upload corrompido.

Grátis para baixar e para receber. $25 uma vez para empacotar; sem conta, nunca.