Installation limits & how OTA downloads are counted
Your No signup session includes 2 installations per upload without penalizing HTTP Range resume requests.
Included installations per upload
Each uploaded build starts with an installation allowance based on your account entitlements (currently 2 for No signup, and 2 for anonymous uploads).
Exactly when an installation is counted
BuildDrop counts one installation when a device begins downloading the signed .ipa or .apk payload (HTTP 200 full stream or initial Range: bytes=0-… request):
- Fetching
/i/{hash}or scanning the QR code does not decrementinstallations_left. - Apple
itunesstoredpreflightHEADrequests andmanifest.plistfetches do not decrementinstallations_left. - Subsequent mid-file
HTTP 206 Partial Contentresume chunks (Range: bytes=5242880-…) do not double-count an installation, even if the byte-0 request consumed the final remaining slot.
What happens when installations reach zero
When installations_left reaches 0, the link transitions to Exhausted (No installations left). Unlike expired builds, the binary archive is kept on disk until its expiry date, allowing the build owner to add +100 or +1000 installations (or reset to the plan default) from /dashboard/apps and immediately reactivate the same /i/{hash} link.