Clavem

Delta update

A delta update is an update file that contains only the differences between two versions of an app, so users download a small patch instead of the whole installer.

How it works

When you release version 3.2.1, you compare it with an older build, 3.2.0, and write down only what differs: changed files, new files, removed files and binary patches for the files that changed. The result is the delta. An app on 3.2.0 downloads it, applies it to its own copy and ends with exactly 3.2.1.

Sparkle, the macOS update framework, supports this. As of November 2026, its documentation says:

  • For each new version you can provide .delta files in addition to the full archive.
  • Each .delta upgrades from a single older version.
  • If the user runs a version you published no delta for, or the patch does not apply cleanly, they get the full update.
  • Its generate_appcast tool generates and signs delta updates automatically.
  • Each delta is listed in the release’s <sparkle:deltas> element, with a sparkle:deltaFrom attribute naming the version it applies to.

Example: who downloads what

An illustrative release. Version 3.2.1 has a 50 MB full archive. You publish deltas from the last two versions, and the numbers below are made up for the arithmetic:

User is on Download Size
3.2.0 Delta from 3.2.0 4 MB
3.1.0 Delta from 3.1.0 9 MB
3.0.0 No delta, full archive 50 MB

If 1,000 users update, and 700 are on 3.2.0, 200 on 3.1.0 and 100 on 3.0.0, the transfer is 700 x 4 + 200 x 9 + 100 x 50 = 9,600 MB instead of 50,000 MB. The trade-off is that you build, sign and host one delta per supported old version, for every release.

Delta update versus full update

A full update is simple and always works: one file per release, one code path in the app. A delta saves bandwidth and time, and it matters most for large apps and for users on slow connections. It costs extra build steps and storage, and it needs the fallback to a full download. Small apps often skip it.

How Clavem handles it

Clavem does not generate or choose deltas. It stores any file you upload to a release (up to 5 GiB each) and serves it through a signed link that is valid for one hour, with byte-range support so a download that stops can resume. A .delta would be an ordinary file in the release, with a platform label of your choosing. Your app, or the update framework, has to pick the right file for the version the user is on.

The releases endpoint also returns a file list rather than a Sparkle feed, so a Sparkle-style delta setup needs your own feed that points at stable URLs; see appcast. Download links are covered in Releases and downloads, and auto-update explains the check itself.

Questions

Does a delta update replace the full download?

No. A delta is an optimization on top of a full release. Sparkle's documentation says that if no delta exists for the user's version, or the patch does not apply cleanly, the user gets the full update instead.

Can Clavem create delta updates?

No. Clavem stores and serves files you upload. Creating the delta is done by your update framework or build tooling.

Sources

  1. Sparkle, Delta Updates (checked November 2026)
  2. Sparkle, Publishing an update (checked November 2026)