Convert Megabits per Second to Gigabytes per Second - Data Transfer Converter
This converter translates a transfer rate expressed in megabits per second (Mbps) into gigabytes per second (GB/s). It supports the common decimal interpretation used in networking and explains the binary (GiB) alternative used sometimes for storage.
Use this tool when you need to compare network link speeds (usually specified in bits per second) with application-level or storage throughput numbers (commonly expressed in bytes per second). The page includes method notes, worked examples, and references to standards to help you choose the correct interpretation.
Governance
Record b07645d360ff • Reviewed by Fidamen Standards Committee
Interactive Converter
Convert between megabit per second and gigabyte per second with precision rounding.
Quick reference table
| Megabit per Second | Gigabyte per Second |
|---|---|
| 1 Mbps | 0 GB/s |
| 5 Mbps | 0 GB/s |
| 10 Mbps | 0 GB/s |
| 25 Mbps | 0 GB/s |
| 50 Mbps | 0.01 GB/s |
| 100 Mbps | 0.01 GB/s |
Methodology
Network speeds are typically specified in bits per second and use SI (decimal) prefixes: mega = 10^6, giga = 10^9. Bytes are 8 bits. The standard, recommended default for network conversions is the decimal approach.
Storage contexts sometimes use binary prefixes (mebi, gibi) where 1 mebibyte = 2^20 bytes and 1 gibibyte = 2^30 bytes. This converter shows both decimal GB and binary GiB results and explains when each is appropriate.
Accuracy and reporting: round results to a sensible number of significant digits for your use case (for example, three decimal places for GB/s in performance summaries). For compliance, calibration, or contractual metrics, follow the measurement and reporting practices in applicable standards and test methodologies.
Worked examples
1000 Mbps → decimal GB/s: 1000 × 0.000125 = 0.125 GB/s.
50000 Mbps → decimal GB/s: 50000 × 0.000125 = 6.25 GB/s.
1000 Mbps → binary GiB/s: 1000 × 0.0001220703125 ≈ 0.12207 GiB/s.
F.A.Q.
Which interpretation should I use: decimal GB/s or binary GiB/s?
For network link speeds and most WAN/LAN measurements use the decimal SI prefixes (mega = 10^6, giga = 10^9). Use binary (mebi/gibi) when the context, tooling, or vendor explicitly uses binary prefixes for storage capacity or memory.
How do I convert Gbps (gigabits per second) to GB/s?
Apply the same steps: convert bits to bytes by dividing by 8, then apply the prefix conversion. For decimal: GB/s = Gbps × 10^9 / 8 / 10^9 = Gbps / 8. So 1 Gbps = 0.125 GB/s (decimal).
What rounding or precision is recommended?
Round to a level appropriate for the audience. For operational dashboards, two to three decimal places for GB/s is common. For contractual measurements, preserve the precision required by the agreement and document the prefix convention used.
Are there regulatory or standards references for these units?
Yes. Use SI (decimal) prefixes per national metrology guidance and ISO/IEC/IEC standards for unit naming conventions. For networking equipment and link definitions refer to relevant IEEE standards such as IEEE 802.3 for Ethernet. Consult your organization's measurement and reporting requirements for compliance.
What causes discrepancies between advertised link rates and observed throughput?
Advertised link rates are physical-layer maximums (bits/s). Observed application throughput is affected by protocol overhead (headers, retransmissions), encoding, congestion, and the difference between bit vs byte reporting. Always convert using the same prefix rules and account for protocol overhead when comparing.
Is this converter exact?
The mathematical conversion between bits and bytes is exact (8 bits = 1 byte). Differences arise from prefix interpretation (decimal vs binary) and measurement/rounding. See accuracy caveats in the citations and consider test method precision for critical measurements.
Sources & citations
- NIST — Metric SI and unit guidance — https://www.nist.gov/pml/weights-and-measures/metric-si
- ISO — International Organization for Standardization (units and quantities) — https://www.iso.org
- IEEE 802.3 Ethernet Standards (for link speed definitions and measurement context) — https://standards.ieee.org/standard/802_3-2018.html
- IEC — Binary prefixes and related standards — https://www.iec.ch
- OSHA — General workplace compliance and recordkeeping (see local requirements for test procedures and safety) — https://www.osha.gov
- IEC 80000-13:2008 — Information science and technology — https://www.iso.org/standard/31898.html
- NIST SP 811 — Guide for the Use of the International System of Units — https://www.nist.gov/pml/special-publication-811
Further resources
Related tools
Versioning & Change Control
Audit record (versions, QA runs, reviewer sign-off, and evidence).
Record ID: b07645d360ffWhat changed (latest)
v1.0.0 • 2025-11-05 • MINOR
Initial publication and governance baseline.
Why: Published with reviewed formulas, unit definitions, and UX controls.
Public QA status
PASS — golden 25 + edge 120
Last run: 2026-01-23 • Run: golden-edge-2026-01-23
Versioning & Change Control
Audit record (versions, QA runs, reviewer sign-off, and evidence).
What changed (latest)
v1.0.0 • 2025-11-05 • MINOR
Initial publication and governance baseline.
Why: Published with reviewed formulas, unit definitions, and UX controls.
Public QA status
PASS — golden 25 + edge 120
Last run: 2026-01-23 • Run: golden-edge-2026-01-23
Engine
v1.0.0
Data
Baseline (no external datasets)
Content
v1.0.0
UI
v1.0.0
Governance
Last updated: Nov 5, 2025
Reviewed by: Fidamen Standards Committee (Review board)
Credentials: Internal QA
Risk level: low
Reviewer profile (entity)
Fidamen Standards Committee
Review board
Internal QA
Entity ID: https://fidamen.com/reviewers/fidamen-standards-committee#person
Semantic versioning
- MAJOR: Calculation outputs can change for the same inputs (formula, rounding policy, assumptions).
- MINOR: New features or fields that do not change existing outputs for the same inputs.
- PATCH: Bug fixes, copy edits, or accessibility changes that do not change intended outputs except for previously incorrect cases.
Review protocol
- Verify formulas and unit definitions against primary standards or datasets.
- Run golden-case regression suite and edge-case suite.
- Record reviewer sign-off with credentials and scope.
- Document assumptions, limitations, and jurisdiction applicability.
Assumptions & limitations
- Uses exact unit definitions from the Fidamen conversion library.
- Internal calculations use double precision; display rounding follows the unit's configured decimal places.
- Not a substitute for calibrated instruments in regulated contexts.
- Jurisdiction-specific rules may require official guidance.
Change log
v1.0.0 • 2025-11-05 • MINOR
Initial publication and governance baseline.
Why: Published with reviewed formulas, unit definitions, and UX controls.
Areas: engine, content, ui • Reviewer: Fidamen Standards Committee • Entry ID: 872373c33411