← Cloud Egress Cost Calculator

This calculator vs. estimating egress in a spreadsheet

Storage-and-egress arithmetic looks simple enough to do in one spreadsheet cell: multiply the outbound gigabytes by the per-GB rate on the quote. The arithmetic is not wrong -- the formula is just simpler than the price sheet it is pricing, in two specific ways that both push the estimate higher than the real bill.

StepCommon spreadsheet shortcutWhat this calculator does
The free monthly allowance Bills every outbound gigabyte from the first one, because a flat =volume*rate formula has no cell for "the first N GB are free." Subtracts your entered free-egress allowance before any rate is applied, for both options.
Graduated rate steps Applies one rate to the whole billable volume, when the published sheet is usually "next 10,240 GB at $X, everything beyond at a lower $Y." Walks a pasted multi-band rate sheet the same way the provider bills it, cheaper bands and all.
The break-even outbound volume Requires solving a piecewise crossing between two multi-segment curves by hand for every new pair of quotes. Computes the outbound GB where the two options bill the same, honoring both options' allowances and bands.
Does anything I type get uploaded anywhere? N/A No. The comparison runs entirely in your browser; nothing you enter is sent to a server.

A worked example

Take a workload of 2,000 GB stored, 8 million requests/month, and 15,000 GB of outbound transfer, priced at $0.023/GB storage and $0.40/million requests on both approaches. The only difference is how the egress line is billed:

ApproachEgress lineTotal
Flat spreadsheet formula 15,000 GB × $0.09/GB, no free allowance $1,399.20
This calculator 100 GB free, then 10,240 GB at $0.09 and 4,660 GB at $0.085 $1,366.90

The gap is $32.30/month -- $387.60/year -- on rates that were never typed in wrong, only applied one step more simply than the price sheet actually bills them. Paste the rate sheet you were actually quoted, including any free allowance and graduated bands, and the calculator applies all of it.

Common questions

What does a quick spreadsheet formula usually get wrong about egress?

Two things, both because a single =volume*rate cell is the easiest formula to write, not because the price sheet actually works that way. First, it bills from the first byte, when every major provider gives some GB of outbound transfer free each month before the per-GB rate starts. Second, it applies one flat rate to the whole volume, when the published rate steps down as volume grows -- "the next 10,240 GB at $0.09, everything beyond at $0.085" is how a real sheet reads, not one number for every gigabyte.

How much difference does that actually make?

On a workload of 2,000 GB stored, 8 million requests, and 15,000 GB of outbound transfer a month, a flat $0.09/GB spreadsheet formula totals $1,399.20. The same workload against a sheet with a 100 GB free allowance and a $0.085/GB step past 10,240 billable GB totals $1,366.90 -- $32.30/month, $387.60/year, on rates that were never wrong, only applied more simply than the provider actually bills them.

Can a spreadsheet formula just add the free allowance and the rate steps itself?

Yes, and a careful one often does for a single quote. What it does not do without real effort is the break-even: the outbound volume at which a cheaper-storage, pricier-egress option stops winning against the alternative. That is a piecewise crossing between two multi-segment curves, not a single-cell formula, and re-deriving it by hand for every new pair of rate sheets is exactly the kind of one-off arithmetic this calculator exists to skip.

Does this page publish any provider's actual current rates?

No. The $0.09/$0.085 rate step and the 100 GB free allowance in the worked example above are illustrative figures chosen to show the arithmetic, not a quotation of any provider's published price list. Paste in the rates from your own current quote; this calculator computes from what you enter and fetches nobody's price sheet.

Open the Cloud Egress Cost Calculator to run this on your own rate sheet, or see how it handles a CDN in front of the same store, a cross-region replica, or infrequent-access storage.