Skip to content
ENExplore Calculators

Container Image Size Savings Calculator

Work out container image size savings instantly with clear inputs, formula shown and shareable results.

About Container Image Size Savings Calculator

Image size affects pull time on every cold start, autoscaling event and node replacement, so a 1.2 GB image is a direct latency tax on elasticity. Multi-stage builds, distroless or Alpine bases, and removing build toolchains and package caches routinely cut images by 80 percent or more, which shortens both scale-out time and the vulnerability surface.

Formula

Image savings

saved per pull = current - optimised; daily transfer saved = saved x pulls; pull time = size / bandwidth

Worked example

With the default values below, Container Image Size Savings Calculator returns Network transfer saved per day of 3.71 TiB. Change any input above and every figure here is recalculated in your browser.

Inputs used

Current image sizeminimum 1 MB
1,200 MB
Optimised image sizeminimum 1 MB
180 MB
Image pulls per dayminimum 1
4,000
Pull bandwidthminimum 0.1 MB/s
400 MB/s

Results

Network transfer saved per day
3.71 TiB
Image size reduction
85.0%
Pull time saved per pull
2.55 s
Pull time after optimisation
0.45 s

Step by step

  1. 1Values used
  2. 2Image savings
  3. 3Network transfer saved per day= 4,080,000,000,000
  4. 4Image size reduction= 85.0
  5. 5Pull time saved per pull= 2.55 s
  6. 6Pull time after optimisation= 0.45 s

Assumptions and limits

  • The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
  • Figures are rounded for display to 2 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

Does layer caching make image size irrelevant?

Only on nodes that already have the layers. Autoscaling onto fresh nodes and spot replacements pull the whole image, which is exactly when startup latency matters most.

What gives the biggest size reduction?

A multi-stage build that copies only the compiled artefact into a minimal runtime base. That single change often removes most of the image.

Related Calculators

Container Image Size Savings Calculator | Calcrivo