Extending and deleting builds

A new version doesn’t replace the old one. Every build gets its own row in the project, its own link, and its own expiry countdown — see share links and expiry. This page is about what you can do with those rows.

Extend a build

Extendpushes a build’s expiry back out to a fresh 7 days (30 on Pro). It’s a Pro feature, and each build can only be extended a limited number of times — the button itself shows the remaining count once you’re near the cap.

Keep a build forever

Rather than extending repeatedly, Keep pins a build so it never expires. A pinned build shows no countdown and sits outside expiry cleanup entirely. Change your mind and Set expiry gives it a normal date again.

Restore an expired build

Expiry and deletion aren’t the same moment. When a countdown hits zero the file isn’t deleted straight away — that happens on the next cleanup pass. In between, the row shows Restoreinstead of Extend, and using it brings the build back with a fresh expiry. Once cleanup has purged the file there’s nothing left to restore, and the only way back is uploading that version again.

Delete a build

Any manager can delete a build from its row. This is immediate and permanent — file, link and record all go at once, without waiting for a cleanup pass.

The free plan’s 5-build limit

Free projects keep only the 5 most recent builds. Upload a 6th and the oldest is removed automatically — not hidden, fully deleted, file and all. Pro projects keep their whole history with no trimming.

Older builds still install

Any version that’s still around — not expired, not trimmed — stays fully installable from its own link, whatever the newest build is. Pointing a tester at an older release works exactly like pointing them at the latest one.