Gigabits to Terabytes
Snapshot
1 Gigabit equals 0.000125 Terabytes. Conversion Encyclopedia uses the same fixed conversion basis across the calculator, common values, and reverse page for this page.
- Reference basis: This conversion uses exact bit-based digital storage definitions.
- Example: For 2 Gigabits, the result equals 0.00025 Terabytes.
- Use the reverse page if you need the opposite direction with the same basis.
Use the interactive calculator below for custom values and the common-value table for quick checks.
Converter Calculator
0.000125 Terabytes (TB)
SwitchExplanation
Formula: Terabytes = Gigabits × 0.000125. Why: byte-side storage units normalize through bits using the exact identity 1 byte = 8 bits, then apply the relevant decimal or binary prefix model.
Gigabits: a data-storage unit in this family that converts through exact bit normalization.
Terabytes (TB): a decimal byte unit equal to 10^12 bytes, common in storage device marketing.
This route is useful when switching between bit and byte representations for storage planning, throughput specifications, and memory sizing.
This conversion is purely multiplicative because both units reduce through exact bit definitions, then apply decimal or binary prefix scaling with no offset.
Common Conversion Values
| Gigabits (Gb) | Terabytes (TB) |
|---|---|
| 1 | 0.000125 |
| 2 | 0.00025 |
| 5 | 0.000625 |
| 10 | 0.00125 |
| 16 | 0.002 |
| 32 | 0.004 |
| 64 | 0.008 |
| 100 | 0.0125 |
| 256 | 0.032 |
| 512 | 0.064 |
| 1,024 | 0.128 |
Frequently Asked Questions
How is Gigabits to Terabytes calculated?
The factor is derived by reducing both units to exact bit counts, including the fixed relationship 1 byte = 8 bits before the source and target prefixes are applied.
Is there a reverse page for Terabytes to Gigabits?
Yes. Use the mirror Terabytes to Gigabits page to apply the inverse relationship with the same exact bit-based storage model.
Can I use this for storage size rather than transfer rate?
Yes. This cluster converts data size only. If you need a per-second result, use the data-rate cluster instead.