How delta patching works
A patch is small when the build changes in a way the engine can see. This guide explains what Chisel does with your files, so you can organise content and builds to get the best result.
Content-defined chunks
Chisel does not diff whole files. It walks every file with a rolling hash and cuts a boundary wherever the hash matches a pattern, giving chunks of 64 KiB on average (16 KiB minimum, 256 KiB maximum). Because boundaries depend on content and not offsets, inserting a few bytes at the front of a file moves one boundary and leaves the rest of the chunks identical.
Each chunk is addressed by its BLAKE3 hash. The manifest for a release is the list of files and, for each file, the ordered list of chunk hashes. A client that has release A and wants release B downloads exactly the chunks in B that are not in A.
Executables get a second pass
A recompiled executable changes in thousands of places because call targets shift. For PE, ELF and Mach-O files, Chisel normalises relative branch targets before chunking, then stores the normalisation as a small side table. On our benchmark set this brings a 140 MB executable down to a 2 to 6 MB patch where plain chunking would send 40 MB.
What typically shrinks
| Change | Full build | Typical patch |
|---|---|---|
| Balance and config changes | 38.2 GB | 40 to 120 MB |
| New level, packed assets | 38.2 GB | 1.5 to 3 GB |
| Engine upgrade, executables rebuilt | 38.2 GB | 4 to 7 GB |
| Textures re-exported with new compression | 38.2 GB | 20 GB or more |
Direct deltas and chains
For each release, Chisel precomputes direct deltas from the six previous releases on the same channel. Players on older versions fetch the full manifest diff instead, which is still chunk-level and usually far smaller than a fresh install. You can change the window per title:
ash delta window hollowmere --releases 10
ash delta report hollowmere 1.8.2
# from 1.8.1 1.9 GB (95.0% saved)
# from 1.8.0 2.4 GB (93.7% saved)
# from 1.7.4 4.1 GB (89.3% saved)Compression
Chunks are stored zstd-compressed. A new release is first compressed at level 9 so the first player does not wait. Once a release has served 5% of its expected audience, a background job recompresses to level 19, which usually saves another 8 to 11% of bytes on the wire. Already-compressed media (video, some audio) is detected and stored as-is.
Limits
- Maximum file size: 64 GiB. Maximum files per release: 2,000,000.
- Maximum chunks per release: 4 million.
- Delta computation for a typical 40 GB build takes 4 to 9 minutes after upload.