Storage Pricing Calculator
Object storage pricing usually comes from three buckets: (1) stored GB (GB-month), (2) request fees (GET/PUT/LIST), and (3) data egress. This page helps you estimate the first two directly, plus a simple egress estimate if you want a fuller picture.
1) Storage + requests
Use this section for S3-like object storage. Enter average stored GB (GB-month) and request counts for your main operations.
If you're searching for a "storage pricing calculator", this section covers the core billing units most providers use: GB-month and request fees.
Inputs
Average stored (GB)
Approx 4.88 TB-month.
Starting storage (GB)
Monthly growth (%)
Months in period
Est 4,340 GB-month avg.
Storage price ($ / GB-month)
GET requests (per month)
Approx 1.9 req/sec.
Avg GET RPS
PUT requests (per month)
Approx 0.19 req/sec.
Avg PUT RPS
Est 5,253,120 GETs and 525,312 PUTs/month.
Request mix presets
GET price ($ / 1k)
PUT price ($ / 1k)
Scenario presets
Results
Estimated monthly total
$119.50
Storage cost
$115.00
GET request cost
$2.00
PUT request cost
$2.50
Inputs summary
| Item | Value |
|---|---|
| Average stored | 5,000 GB |
| GET requests | 5,000,000 |
| PUT requests | 500,000 |
2) Optional: egress
If your workload downloads data out of the cloud or across regions, add an egress line item here.
Inputs
Egress from storage (GB / month)
Avg throughput: 1.52 Mbps.
Avg throughput (Mbps)
Est 24,624 GB/month.
Pricing mode
Use tiered mode when pricing changes by volume.
Egress price ($ / GB)
Enter your provider's effective $/GB for the region/path/tier.
Scenario presets
Results
Estimated monthly cost
$45.00
Egress
500 GB
Price
$0.09 / GB
3) When copy storage pricing matters
If you replicate across regions, run backups, or copy data into another system, the biggest surprises are usually (a) extra destination storage and (b) transfer/egress line items. Use the copy storage pricing checklist to avoid missing costs.
How to get your inputs
- Inputs: use billing exports, metrics, or logs to get real counts/GB where possible.
- Units: convert throughput (Mbps) or rates (RPS) into monthly units when needed.
- Scenarios: build a baseline and a high-usage scenario to avoid under-budgeting.
Result interpretation
- GB-month is usually the main driver; request fees show up when you have very high request volume.
- If egress is included, it can dominate; separate it so you know what to optimize first.
Common mistakes
- Using a single average and ignoring peak/incident scenarios.
- Double-counting or missing adjacent line items (transfer, logs, retries).
Advanced inputs to capture
- Average stored GB and growth rate set the baseline.
- Request mix matters when you have high request volume.
- Separate egress from cross-region transfer line items.
- Include lifecycle transitions and retrievals if used.
Scenario planning
| Scenario | Stored GB | Requests | Egress |
|---|---|---|---|
| Baseline | Average | Typical | Expected |
| Peak | High | Spike | High |
Validate after changes
- Compare your estimate to the first real bill and adjust assumptions.
- Track the primary driver metric (requests/GB/count) over time.
Next steps
Advertisement
Example scenario
- 5,000 GB stored at $0.023/GB-month -> ~$115/month (storage only). Add request fees if you do millions of requests.
- 20 TB stored with low request volume -> storage dominates; egress may dominate if you download a lot.
Included
- Storage estimate from average stored GB and $/GB-month pricing.
- Request fees estimate for GET/PUT (and similar) using per-1k pricing.
- Optional egress estimate from GB/month and $/GB pricing.
Not included
- Lifecycle transitions, retrieval fees, and tiered/region pricing unless you model them with blended rates.
- Replication costs (use Storage Replication and Cross-region Transfer calculators).
How we calculate
- Storage cost = average stored GB x $/GB-month.
- Request cost = (requests / 1,000) x $ per 1,000 (per request class).
- Egress cost (optional) = GB/month downloaded x $/GB.
- For tiered or regional pricing, use effective blended rates or run scenarios and sum.
FAQ
Why do you use average stored GB?
Storage is billed per GB-month. If usage grows over time, average (midpoint) is closer than end-of-month GB.
Do requests matter?
Often they're small, but at very high request volume (or many small objects), request fees can be material.
Is egress part of storage pricing?
Sometimes egress is the biggest cost. This page includes an optional egress estimate; model replication and cross-region separately.
What about different storage classes (standard, IA, archive)?
Different classes can have different storage, request, and retrieval pricing. If you use multiple classes, estimate each separately and add them up.
How do I estimate the cost of copying or replicating objects?
Copying often adds transfer/feature fees, additional destination storage, and extra requests. Start with the copy storage pricing guide, then model replication and transfer separately.
Are lifecycle transitions and retrieval fees included?
No. If you use infrequent access or archive tiers, retrieval and transition fees can matter; model those separately.
Related tools
Related guides
Aurora pricing (what to include): compute, storage, I/O, and backups
A practical checklist for estimating Aurora costs: instance hours (or ACUs), storage growth, I/O-heavy workloads, backups/retention, and the line items that commonly surprise budgets.
Azure SQL Database pricing: a practical estimate (compute, storage, backups, transfer)
Model Azure SQL Database cost without memorizing price tables: compute baseline (vCore/DTU), storage GB-month + growth, backup retention, and network transfer. Includes a validation checklist and common sizing traps.
Bigtable cost estimation: nodes, storage growth, and transfer (practical model)
A driver-based Bigtable estimate: provisioned capacity (node-hours), stored GB-month + growth, and network transfer. Includes validation steps for hotspots, compactions, and peak throughput that force over-provisioning.
Cloud Spanner cost estimation: capacity, storage, backups, and multi-region traffic
Estimate Spanner cost using measurable drivers: provisioned capacity (baseline + peak), stored GB-month (data + indexes), backups/retention, and multi-region/network patterns. Includes a worked template, common pitfalls, and validation steps.
Cloud SQL pricing: instance-hours, storage, backups, and network (practical estimate)
A driver-based Cloud SQL estimate: instance-hours (HA + replicas), storage GB-month, backups/retention, and data transfer. Includes a worked template, common pitfalls, and validation steps for peak sizing and growth.
Database costs explained: compute, storage growth, backups, and network
A practical framework to estimate managed database bills: baseline compute, storage GB-month growth, backups/snapshots, and the network patterns that cause surprises.
Advertisement
Disclaimer
Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.
Last updated: 2026-02-07