Artifact Registry Storage Calculator
Estimate Artifact Registry storage from image size, retained versions and layer sharing, plus egress and scanning.
Inputs
Monthly Cost
$617.95
Stored Data
1 TiB
Billed Storage
1,299.50GB
Storage Charge
$129.95
Egress Charge
$384.00
Vulnerability Scanning Charge
$104.00
Storage Avoided by Layer Sharing
2,700.00GB
Cost per Retained Image
$1.2359
Step by step
Values used
Distinct images = 500 images; Average image size = 0.8000 GB; Versions retained per image = 10 versions; Layers shared between versions = 75 %; Storage price per GB = 0.1000 USD/GB-month; Free storage allotment = 0.5000 GB; Image pulls per month = 20,000 pulls; Pulls that cross a region or leave Google = 20 %; Egress price per GB = 0.1200 USD/GB; Images scanned for vulnerabilities = 400 scans; Price per image scan = 0.2600 USD
Artifact Registry Storage
stored GB = images × size × (1 + (versions − 1) × (1 − layer sharing)); cost = (stored GB − free allotment) × storage price + pulled GB crossing a region × egress price + scans × scan price.
Monthly Cost
= 617.95
Stored Data
= 1,300,000,000,000
Billed Storage
= 1,299.50 GB
Storage Charge
= 129.95
Egress Charge
= 384.00
Vulnerability Scanning Charge
= 104.00
How it works
Container layers are content-addressed and stored once, so retaining ten versions of an image costs far less than ten times one image — only the changed layers add bytes. Egress, not storage, is usually the larger line once a CI system or a multi-region GKE fleet pulls the same image repeatedly from outside the registry's region. Registries grow without anyone owning them, and the two effective controls are a cleanup policy on old versions and putting the registry in the same region as the clusters that pull from it. Confirm storage, egress and scanning prices in the Google Cloud pricing calculator before budgeting.
Formula
Artifact Registry Storage
stored GB = images × size × (1 + (versions − 1) × (1 − layer sharing)); cost = (stored GB − free allotment) × storage price + pulled GB crossing a region × egress price + scans × scan price.
- layer sharing
- Fraction of each new version already present as an existing layer
- versions
- Tags or digests retained per image before a cleanup policy deletes them
- egress share
- Pulls that leave the registry's region and therefore attract network charges
Frequently Asked Questions
How is Artifact Registry Storage calculated?
stored GB = images × size × (1 + (versions − 1) × (1 − layer sharing)); cost = (stored GB − free allotment) × storage price + pulled GB crossing a region × egress price + scans × scan price. Container layers are content-addressed and stored once, so retaining ten versions of an image costs far less than ten times one image — only the changed layers add bytes. Egress, not storage, is usually the larger line once a CI system or a multi-region GKE fleet pulls the same image repeatedly from outside the registry's region.
Why does Artifact Registry Storage matter?
Registries grow without anyone owning them, and the two effective controls are a cleanup policy on old versions and putting the registry in the same region as the clusters that pull from it. Confirm storage, egress and scanning prices in the Google Cloud pricing calculator before budgeting.
What values do I need to enter?
This calculator takes 11 inputs: Distinct images, Average image size, Versions retained per image, Layers shared between versions, Storage price per GB, Free storage allotment, Image pulls per month, Pulls that cross a region or leave Google, Egress price per GB, Images scanned for vulnerabilities, Price per image scan. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Does deleting a tag free up storage?
Only if no other tag references the same layers. Because layers are shared, removing one version of an image frequently reclaims very little — sustained savings come from cleanup policies that retire whole generations of base images.
You might also need
- Container Registry Migration CalculatorCommonly used together
- Cloud Storage Cost CalculatorCommonly used together
- Cloud Build Cost CalculatorCommonly used together
- Google Kubernetes Engine (GKE) CalculatorCommonly used together
- Cloud Run Cost CalculatorAlso in Google Cloud
- BigQuery Cost CalculatorAlso in Google Cloud