1 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article explains how to enable bundle diffing in your Expo project to reduce update download sizes. By setting a configuration option, your app can receive smaller patches instead of full bundles when updates are published. It also outlines prerequisites and current limitations of the feature.
If you do, here's more
Bundle diffing for EAS Update allows developers to reduce the size of app updates by delivering only the differences between the current and new bundle. This feature is currently in beta and has certain limitations. To implement it, your app needs to use Expo SDK 55 or later. You enable bundle diffing by setting `updates.enableBsdiffPatchSupport` to true in your app's configuration.
When a new update is published, EAS Update utilizes the bsdiff algorithm to create a patch file, which is significantly smaller than the full bundle. However, a patch will only be served if it meets two criteria: it must be meaningfully smaller than the full bundle, and it must be computationally efficient to generate. If these conditions arenβt met, the full bundle will be delivered instead.
There are specific limitations to be aware of. For instance, embedded bundles cannot be patched. Devices need to have a previously published update to receive a patch. Also, when a new update is published, the patch is only precomputed against the second-newest update. If a device is running a different version, it will initially download the full bundle. Lastly, there may be a delay of a few minutes after publishing before a patch is available, during which time devices will also receive the full bundle.
Questions about this article
No questions yet.