Build Artifact Size Calculator
Size build artifacts and the storage retention consumes.
About Build Artifact Size Calculator
Artifact storage grows as the product of build frequency and retention, which makes it easy to accumulate terabytes unnoticed. Layer deduplication removes most of the redundancy between consecutive builds. Shortening retention for feature branch builds while keeping release artifacts long-term captures most of the saving with no practical loss.
Formula
Build Artifact Size
Storage = builds per day × retention days × artifact size × (1 − deduplication saving)
- layer deduplication
- Shared layers between builds are stored once
Worked example
With the default values below, Build Artifact Size Calculator returns Storage Required of 131.250. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Size per artifactminimum 0 MB
- 320 MB
- Builds per dayminimum 0
- 40
- Retention periodminimum 0 days
- 30 days
- Saving from layer deduplicationaccepts 0–100 %
- 65 %
- Storage cost per GB per monthminimum 0
- 0.023
Results
- Storage Required
- 131.250 GB
- Artifacts Retained
- 1,200
- Storage Before Deduplication
- 375.000 GB
- Monthly Storage Cost
- $3.02
- Daily Storage Growth
- 4.3750 GB
Step by step
- 1Values used
- 2Build Artifact Size
- 3Storage Required= 131.250 GB
- 4Artifacts Retained= 1,200
- 5Storage Before Deduplication= 375.000 GB
- 6Monthly Storage Cost= 3.02
- 7Daily Storage Growth= 4.3750 GB
Assumptions and limits
- The result is derived only from the 5 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation or tax into account.
- Figures are rounded for display to 4 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is Build Artifact Size calculated?
Storage = builds per day × retention days × artifact size × (1 − deduplication saving) Artifact storage grows as the product of build frequency and retention, which makes it easy to accumulate terabytes unnoticed. Layer deduplication removes most of the redundancy between consecutive builds.
Why does Build Artifact Size matter?
Shortening retention for feature branch builds while keeping release artifacts long-term captures most of the saving with no practical loss.
What values do I need to enter?
This calculator takes 5 inputs: Size per artifact, Builds per day, Retention period, Saving from layer deduplication, Storage cost per GB per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.