Cloud Units Converter

Cloud pricing and dashboards mix decimal and binary units. Convert common storage and bandwidth units, then compare baseline vs peak transfer estimates.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-02-07. Editorial policy and methodology.

Best next steps

Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.

Guide: egress costs Egress cost RPS to monthly requests

Inputs

GB
GiB
Mbps (megabits/sec)
~12.5 MB/s.
MB/s (megabytes/sec)
Utilization (%)
Hours/day
Days/month
Use 30.4 for an average month.
Scenario presets

Results

GB to GiB
931.32 GiB
GiB to GB
1,000 GB
Mbps to MB/s
12.5 MB/s
MB/s to Mbps
100 Mbps
Monthly transfer (estimate)
9,619 GB / month

Where unit mistakes distort cloud bills

This page is not just a convenience converter. It helps prevent the small unit mismatches that quietly break egress, storage, and request-based models before the pricing math even starts.

  • GB vs GiB: storage bills often use decimal units while system dashboards show binary units.
  • Mbps vs MB/s: throughput charts use bits while payload and transfer planning often need bytes.
  • Hours and utilization: monthly transfer estimates drift when teams start from peak throughput instead of sustained usage.

How to convert throughput into monthly transfer

Throughput-based budgeting works only when you explicitly separate the sustained rate from the short-lived peak. This page gives you a quick bridge between those two views.

  • Start from average throughput, not the highest spike visible in a dashboard.
  • Apply utilization and schedule assumptions that match the real service window.
  • Keep bits and bytes explicit so the conversion does not silently drift by 8x.

When the “average Mbps” shortcut fails

  • Download-heavy releases and cache misses can make the peak month look nothing like baseline.
  • Short business-hour workloads should not be modeled as 24x7 traffic.
  • Switching between GB and GiB mid-estimate makes later storage and transfer lines impossible to reconcile.

Quick unit checklist before you trust the output

  • Confirm whether dashboards report GB or GiB before converting.
  • Use average throughput, not peak, when estimating monthly transfer.
  • Match hours/day to real schedules (not always 24x7).
  • Keep bits vs bytes explicit when converting Mbps to MB/s.

Scenario planning

Scenario Mbps Utilization GB/month
Baseline Average Typical Derived
Peak High Same Higher

Next steps

Guides All calculators Guide: egress costs Egress cost RPS to monthly requests

Example scenario

  • 1,000 GB ~ 931.32 GiB.
  • 100 Mbps at 30% utilization over 24h/day ~ monthly transfer estimate (GB/month).
  • Peak 200% scenario shows the spike in monthly transfer.

Included

  • GB to GiB and Mbps to MB/s conversions.
  • Throughput to monthly transfer estimate for planning.
  • Days/month input to align with billing cycles.
  • Baseline vs peak scenario table for transfer spikes.

Not included

  • Protocol overhead and peak/diurnal patterns (use scenarios).
  • Provider-specific billing unit rounding rules.

How we calculate

  • GB to GiB uses 1 GiB = 1.073741824 GB.
  • Mbps to MB/s uses 8 bits = 1 byte.
  • Monthly transfer estimate multiplies throughput by utilization and time.
  • Use 30.4 days/month for an average month.

FAQ

Do providers bill GB or GiB?
Many providers bill decimal GB/TB, while OS tools often show GiB/TiB. Always check the billing unit in documentation.
Is the monthly transfer estimate exact?
No. It's a simplified estimate. Real workloads vary by peak/off-peak patterns and protocol overhead.

Related tools

Guide: egress costs Egress cost RPS to monthly requests

Related guides

Cloud CDN pricing (GCP): bandwidth, requests, and origin egress (cache fill)
A practical Cloud CDN cost model: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate by path, heavy-tail endpoints, and purge/deploy events that reduce hit rate.
Cloud cost estimation checklist: build a model Google (and finance) will trust
A practical checklist to estimate cloud cost without missing major line items: requests, compute, storage, logs/metrics, and network transfer. Includes a worksheet template, validation steps, and the most common double-counting traps.
Cloud Functions pricing (GCP): invocations, duration, egress, and log volume
A practical Cloud Functions cost model: invocations, execution time, outbound transfer, and logs. Includes a workflow to estimate baseline + peak and validate retries, cold starts, and log bytes per invocation.
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.
GCP Cloud Run Pricing Guide: Cost Calculator Inputs for Requests, CPU, and Egress
Estimate Cloud Run cost using requests, duration, concurrency, transfer, and logs, with practical calculator inputs and validation steps for retries, peak traffic, and noisy endpoints.
GCP Cloud Storage Pricing & Cost Guide
Understand GCP Cloud Storage cost drivers across storage class, operations, retrieval, replication, and egress, with estimation steps for request-heavy and archive-heavy workloads.

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. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .