Convert Bits per Second to Gigabytes per Second - Data Transfer Converter
This converter translates a data rate expressed in bits per second (bit/s) into gigabytes per second (GB/s) using SI (decimal) conventions by default. It clarifies the difference between decimal gigabytes (GB = 10^9 bytes) and binary gibibytes (GiB = 2^30 bytes) because both conventions are commonly encountered in networking and storage.
Use the tool for quick conversions when sizing links, estimating transfer times, or comparing advertised network speeds to observed throughput. For high-accuracy capacity planning, consider protocol overhead, encoding schemes, and whether reported values are 'bits on the wire' (physical layer) or 'goodput' (usable payload).
Governance
Record 0b1f962e8637 • Reviewed by Fidamen Standards Committee
Interactive Converter
Convert between bit per second and gigabyte per second with precision rounding.
Quick reference table
| Bit per Second | Gigabyte per Second |
|---|---|
| BPS 1 bps | 0 GB/s |
| BPS 5 bps | 0 GB/s |
| BPS 10 bps | 0 GB/s |
| BPS 25 bps | 0 GB/s |
| BPS 50 bps | 0 GB/s |
| BPS 100 bps | 0 GB/s |
Methodology
Base relationship: 1 byte = 8 bits. Converting bits per second to bytes per second requires dividing by 8. The choice of gigabyte unit changes the divisor: decimal GB uses 10^9, binary GiB uses 2^30.
Decimal (SI) convention — recommended for most networking equipment and marketing specifications: GB/s = bps ÷ (8 × 10^9). Binary (IEC) convention — used by some operating systems and storage contexts: GiB/s = bps ÷ (8 × 2^30).
When estimating real transfer time, subtract protocol overhead (Ethernet, IP, TCP/UDP headers, and any lower-layer encoding) because 'link rate' (line rate) differs from application-level throughput.
Key takeaways
To convert bit/s to GB/s (decimal): divide bps by 8 × 10^9. For binary GiB/s: divide by 8 × 2^30.
Always confirm whether a source uses decimal (GB) or binary (GiB) prefixes, and account for protocol and encoding overhead when estimating real-world transfer performance.
Worked examples
1 000 000 000 bit/s (1 Gbit/s) = 0.125 GB/s (decimal) ≈ 0.1164 GiB/s (binary).
10 000 000 000 bit/s (10 Gbit/s) = 1.25 GB/s (decimal) ≈ 1.164 GiB/s (binary).
100 000 000 bit/s (100 Mbit/s) = 0.0125 GB/s (decimal) ≈ 0.01164 GiB/s (binary).
F.A.Q.
What is the exact mathematical relationship used?
We use 1 byte = 8 bits. For decimal gigabytes: GB/s = bps ÷ (8 × 10^9). For binary gibibytes: GiB/s = bps ÷ (8 × 2^30).
Which convention should I use: GB (decimal) or GiB (binary)?
Use decimal GB (10^9 bytes) for networking and vendor-rated link speeds because most network specifications use SI prefixes. Use GiB (2^30 bytes) when working with OS-level storage reports or software that explicitly uses binary prefixes. Always check the context and label.
Will this conversion reflect real transfer speeds I observe?
No—this is a raw unit conversion. Real transfer speeds (goodput) are lower due to protocol headers, inter-frame gaps, encryption, retransmissions, and link-layer encoding. Subtract estimated overhead to approximate application-level throughput.
How should I handle precision and rounding?
For planning, round conservatively: present results to three significant digits for high rates (e.g., 1.25 GB/s) and keep extra precision for calculations. When comparing to measured device telemetry, align units exactly (GB vs GiB) before rounding.
Are there authoritative references for these conventions?
Yes. SI prefixes and the difference between decimal and binary prefixes are documented by national metrology institutes and international bodies. Refer to standards from NIST and BIPM for authoritative guidance.
Does this account for physical-layer encoding (e.g., 64b/66b or 8b/10b)?
No. Encoding schemes change the effective payload fraction; for example, 8b/10b adds 25% overhead. To get effective application throughput, multiply the line rate by the payload fraction after converting units.
How do I convert from bits per second to seconds per gigabyte (transfer time)?
Compute GB = bytes per gigabyte (decimal: 10^9 bytes) then seconds = (GB × 8 × 10^9) ÷ bps. Equivalently, seconds per GB = (8 × 10^9) ÷ bps for decimal GB; use 8 × 2^30 for binary GiB.
Sources & citations
- NIST — Binary and SI prefixes (discussion of bytes, octets, and binary prefixes) — https://physics.nist.gov/cuu/Units/binary.html
- BIPM — SI prefixes and the International System of Units (SI) — https://www.bipm.org/en/measurement-units/si-prefixes
- MIT OpenCourseWare — computing and networking fundamentals (reference material on data units and throughput) — https://ocw.mit.edu
- 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
External guidance
Versioning & Change Control
Audit record (versions, QA runs, reviewer sign-off, and evidence).
Record ID: 0b1f962e8637What changed (latest)
v1.0.0 • 2025-11-17 • 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-17 • 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 17, 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-17 • 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: b626e2e331b7