What’s Changing
Starting 31 March 2026, we’re updating our artifact retention periods to align with industry standards and how most teams actually use their build data. Here’s what’s changing:
| Artifact | New retention period | Previous retention period |
|---|---|---|
| Standard artifacts (build logs, test results, etc) | 90 days | 365 days |
| Installable artifacts (.ipa, .apk, .aab files) | 150 days | 365 days |
| HTML reports | 7 days | 7 days (unchanged) |
| Pipeline intermediate files (files passed between workflows in a pipeline) | 7 days | 365 days |
Artifacts created before 31 March 2026 will keep the old retention period. All artifacts generated on or after this date will fall under the new policy. Once artifacts are removed from Bitrise storage, they are permanently deleted with no chance of recovery.
Archiving artifacts to your own storage
If you’d like to keep your build artifacts for longer, use the Bitrise API to download and store artifacts. For a detailed walkthrough, check out the guide.
Longer or shorter retention periods
Enterprise customers can request to change their default retention period. Please contact your Customer Success Manager to discuss.
- Shorter retention: No extra charge (useful for managing storage costs)
- Extended retention: Available for an additional fee
Please note that a longer or short retention period applies to standard artifacts and installable artifiacts only (does not include HTML reports or pipeline intermediate file).
If you currently have an extended retention period as part of your Bitrise plan, this will stay in place as usual after 31 March.
FAQ
Why is Bitrise making this change?
Our data shows 99% of artifact access happens within 90 days, and so the updated policy will have no impact on the vast majority of our users. This change aligns our retention with actual usage patterns and industry standards (comparable to GitHub Actions, CircleCI, and other CI/CD platforms).
Will this affect artifacts I’ve already created?
Artifacts created before 31 March 2026 will keep the original retention period. Only artifacts generated from 31 March onwards will be subject to the updated policy.
How do I know which artifacts I should archive?
Review your team’s workflow. If you regularly access artifacts older than 90 days (or 150 days for installables), consider setting up automated archiving.
What if I need longer retention for compliance reasons?
This is available as a paid add-on. Contact your Customer Success Manager to discuss extended retention options.
Can I get a shorter retention period?
Yes, Enterprise customers can request shorter retention at no additional cost. This is useful for reducing storage costs.