Gigabytes to Terabytes (GB to TB)
Last updated:
Gigabytes-to-terabytes conversions roll the GB-scale storage figures of individual VMs, photo libraries, database tables, and streaming media catalogs up into the TB-scale numbers cloud-storage contracts, NAS-array specs, and enterprise-backup ledgers actually quote. Cloud architects sizing per-VM GB allocations against an org-wide TB commit, photo and video professionals tracking per-project GB against multi-TB archive disks, database administrators aggregating per-table GB into per-database TB capacity plans, and streaming-media engineers cataloguing per-asset GB encodes against TB-scale CDN inventories all run this conversion at every capacity-planning cycle. The math is a clean three-decimal-place shift in decimal SI.
How to convert Gigabytes to Terabytes
Formula
TB = GB × 0.001
To convert gigabytes to terabytes in decimal SI, divide the GB figure by 1000 — equivalently, multiply by 0.001. The relationship is exact in the decimal interpretation (1 TB = 1000 GB) used by cloud vendors, HDD marketing, and most enterprise inventory systems. The binary interpretation (1 TiB = 1024 GiB) gives a slightly different figure and appears occasionally in OS file-size displays and SSD-interface bandwidth specs. For most modern enterprise and cloud usage the decimal SI conversion is the right one. The mental math is a three-decimal-place shift: 1000 GB = 1 TB, 8500 GB = 8.5 TB, 96,000 GB = 96 TB.
Worked examples
Example 1 — 1000 GB
One thousand gigabytes converts to 1000 × 0.001 = 1 TB in decimal SI. That is the canonical "1 TB equals 1000 GB" relationship used in cloud-storage dashboards, HDD marketing labels, and most modern enterprise inventory systems. Below 1000 GB the dashboard typically displays in GB; at and above the threshold most reports switch to TB for readability.
Example 2 — 500 GB
Five hundred gigabytes converts to 500 × 0.001 = 0.5 TB. That is half a terabyte, the typical mid-range external SSD capacity in 2026, the size of a large per-VM data volume, or the rough disk footprint of a single high-volume database table after a few years of operation. Most reports display this as "500 GB" rather than "0.5 TB" because the GB figure reads more naturally below the 1 TB threshold.
Example 3 — 15000 GB
Fifteen thousand gigabytes converts to 15,000 × 0.001 = 15 TB. That is a year of professional photography or videography archive accumulation, a mid-size multi-tenant database total, or a typical small OTT catalogue. The 15 TB figure sits comfortably below the 18 TB or 20 TB capacity of a typical archive RAID set, leaving headroom for the next capacity-planning cycle.
GB to TB conversion table
| GB | TB |
|---|---|
| 1 GB | 0.001 TB |
| 2 GB | 0.002 TB |
| 3 GB | 0.003 TB |
| 4 GB | 0.004 TB |
| 5 GB | 0.005 TB |
| 6 GB | 0.006 TB |
| 7 GB | 0.007 TB |
| 8 GB | 0.008 TB |
| 9 GB | 0.009 TB |
| 10 GB | 0.01 TB |
| 15 GB | 0.015 TB |
| 20 GB | 0.02 TB |
| 25 GB | 0.025 TB |
| 30 GB | 0.03 TB |
| 40 GB | 0.04 TB |
| 50 GB | 0.05 TB |
| 75 GB | 0.075 TB |
| 100 GB | 0.1 TB |
| 150 GB | 0.15 TB |
| 200 GB | 0.2 TB |
| 250 GB | 0.25 TB |
| 500 GB | 0.5 TB |
| 750 GB | 0.75 TB |
| 1000 GB | 1 TB |
| 2500 GB | 2.5 TB |
| 5000 GB | 5 TB |
Common GB to TB conversions
- 500 GB=0.5 TB
- 1000 GB=1 TB
- 2000 GB=2 TB
- 5000 GB=5 TB
- 10000 GB=10 TB
- 25000 GB=25 TB
- 50000 GB=50 TB
- 100000 GB=100 TB
- 500000 GB=500 TB
- 1000000 GB=1000 TB
What is a Gigabyte?
One gigabyte (GB) equals 1,000,000,000 bytes (= 10⁹) under the SI decimal convention or 1,073,741,824 bytes (= 2³⁰) under the historical binary convention used by Microsoft Windows file managers and most pre-2009 operating-system tooling. The IEC 80000-13:2008 standard names the binary 1,073,741,824-byte quantity the gibibyte (GiB), reserving "gigabyte" for the decimal 10⁹ value. The 7.4% gap between the two conventions is now the consumer-visible source of the "my 128 GB iPhone only shows 119 GB available" pattern — Apple labels device capacity in decimal GB matching the SSD vendor's marketed capacity, and a 128 × 10⁹-byte drive read under binary GiB conventions reports 128,000,000,000 ÷ 1,073,741,824 ≈ 119.2 GiB. Apple's macOS realigned to the SI decimal convention in OS X 10.6 Snow Leopard (2009), so on a Mac the figures match; iOS, iPadOS and the Settings → General → iPhone Storage screen also report decimal GB; Microsoft Windows still reports binary gibibytes labelled as "GB" through the file-properties dialog and the Storage Spaces UI. The gigabyte symbol GB (uppercase B) is distinct from the gigabit symbol Gb (lowercase b), the unit used for high-speed networking — Ethernet, fibre and 5G — covered under bit, mbps and gbps.
The gigabyte arrived in consumer computing in the mid-1990s and crossed into mass-market relevance with the broadband and smartphone transitions of 2005–2010 — and is the unit in which essentially every consumer-facing digital quantity is now measured. The first 1 GB hard drive was IBM's 0663 "Corsair" in 1991, a 5.25-inch full-height drive with a list price near $2,500; the first sub-$1-per-MB consumer drives crossed the 1 GB barrier in 1996, and by the time Microsoft Windows XP shipped in October 2001 a typical retail PC included a 20–40 GB drive. The gigabyte's defining cultural moment is the 1 April 2004 launch of Gmail with a 1 GB inbox per user — a free quantity hundreds of times larger than the 2–10 MB free email-storage limits that Yahoo Mail and Hotmail had offered until that morning. Gmail's launch was widely assumed at first to be an April Fool's joke; it was not, and within five years every major free webmail service had moved to multi-gigabyte default quotas. The same period saw Dropbox launch in September 2008 with a 2 GB free tier, Apple's iCloud launch in October 2011 with 5 GB free (still the iCloud Free baseline in 2026), and Google Drive launch in April 2012 unifying Gmail and document storage into a 15 GB shared free quota that has remained unchanged for over a decade. Mobile devices completed the transition. The first iPhone (June 2007) shipped at 4 GB and 8 GB; the iPhone 15 Pro (2023) ships at 128 GB, 256 GB, 512 GB and 1 TB. Apple Music, Spotify and Netflix Mobile all expose offline-download budgets in GB through their settings panels, and the consumer "how much storage do I need?" decision is now denominated entirely in gigabytes.
Smartphone and tablet storage is the gigabyte's most universally-recognised application. iPhone storage tiers in 2026 are 128, 256, 512 GB and 1 TB; Samsung Galaxy S-series tiers cluster at 128, 256, 512 GB and 1 TB; Google Pixel 8 and 8 Pro tiers are 128, 256, 512 GB and 1 TB. The "Storage" screen on every modern smartphone reports per-app, per-category and total available capacity in gigabytes to one decimal place, and the cross-platform user mental model — "I need a 256 GB phone because my Photos library is 80 GB" — runs entirely in GB units. Console storage (PlayStation 5 internal SSD 825 GB raw / ~667 GB usable, Xbox Series X 1 TB / ~802 GB usable, Nintendo Switch 32 GB or OLED-model 64 GB internal) is reported in GB through every per-game-uninstall confirmation dialog. Mobile-data plans completed their transition from MB to GB during the 4G LTE rollout of 2012–2015. Verizon, AT&T and T-Mobile sell tiered plans denominated in GB (5 GB, 10 GB, 30 GB, 50 GB, "Unlimited" with deprioritisation thresholds at 50 GB or 100 GB monthly); EU operators sell 5 GB, 10 GB, 50 GB, 100 GB monthly buckets with EU-roaming inclusions reported separately in GB; pay-as-you-go and prepaid plans worldwide quote both daily and monthly allowances in GB. Mobile-data settings screens on iOS (Settings → Cellular → Cellular Data) and Android (Settings → Network & internet → Data usage) report consumption in GB to two decimal places. AAA game download sizes have ballooned into the high-GB tier and are the largest single consumer-relevant downloads. Call of Duty: Modern Warfare III (2023) requires 149 GB on PS5 and over 200 GB on PC; Red Dead Redemption 2 is roughly 120 GB; Microsoft Flight Simulator 2024 is 50–150 GB depending on installed photogrammetry packs and DLC. Steam, the PlayStation Store, Xbox Live and Battle.net expose download-progress UIs that report transfer speed in MB/s and remaining size in GB, and the broadband-data-cap conflict — Comcast's 1.2 TB monthly cap, Cox's 1.25 TB cap — is the consumer-visible pressure point where game-download GB and streaming GB compete with each other for monthly allowance. Streaming-video data consumption is the other large household-level GB load. Netflix HD 1080p streams at roughly 3 GB per hour; Netflix 4K HDR at 7 GB per hour; YouTube 4K averages 2.5 GB per hour at the standard VP9 bitrate; Disney+ 4K HDR titles average 7–10 GB per hour. The "Cellular Data Use" toggle in every major streaming app caps mobile streaming below 1 GB per hour by default, the figure publishers use to keep a single full-length feature film below the 5 GB free tier most prepaid plans include. Cloud-storage free tiers have become the household-finance pressure point of the gigabyte era. Google Drive 15 GB free shared across Gmail, Drive and Google Photos; iCloud 5 GB free; Microsoft OneDrive 5 GB free; Dropbox 2 GB free. The paid-tier upsells — iCloud+ 50 GB / 200 GB / 2 TB / 6 TB / 12 TB; Google One 100 GB / 200 GB / 2 TB; OneDrive 100 GB / 1 TB — all denominate at the gigabyte level until the multi-terabyte tiers.
What is a Terabyte?
One terabyte (TB) equals 1,000,000,000,000 bytes (= 10¹²) under the SI decimal convention or 1,099,511,627,776 bytes (= 2⁴⁰) under the historical binary convention. The IEC 80000-13:2008 standard names the binary 2⁴⁰-byte quantity the tebibyte (TiB), reserving "terabyte" for the decimal 10¹² value, and the gap between the two is now 9.95% — the largest at any prefix level the consumer encounters routinely. The terabyte is the dominant unit for consumer secondary storage (mechanical hard drives, internal and external SSDs, network-attached storage), for cloud-storage paid tiers above the gigabyte free-tier ceiling, and for video-production and surveillance-archival capacity planning. The terabyte symbol TB (uppercase B) is distinct from the terabit symbol Tb (lowercase b), the unit used in long-haul fibre-optic backbone capacity quotes and in data-centre interconnect bandwidth — a 400 Gbps single-wavelength DWDM channel sustained for 24 hours transfers 4.32 TB, and aggregate undersea-cable capacities are now quoted in Tbps with cumulative-traffic figures in TB per day. The consumer cloud-storage market quotes paid tiers in decimal TB universally (iCloud+ 2 TB, Google One 2 TB, OneDrive bundled 1 TB, Backblaze unlimited).
The terabyte became consumer-purchasable on a single drive in January 2007, when Hitachi Global Storage Technologies shipped the Deskstar 7K1000 — a 3.5-inch 7,200 RPM hard drive containing five 200 GB perpendicular-recording platters and selling at launch for $399. Western Digital, Seagate and Samsung followed within the year, and by 2010 the 1 TB internal drive had displaced the 500 GB tier as the mainstream desktop default. Drive density has continued to climb: helium-filled mechanical drives introduced by HGST in 2013 reduced internal turbulence enough to enable 8 TB and then 14 TB capacities; shingled magnetic recording (SMR) and energy-assisted magnetic recording (EAMR) lifted the per-platter ceiling further; Seagate's HAMR-based Mozaic 3+ platform began shipping 30 TB drives to hyperscaler customers in 2024 with a 50 TB roadmap. The terabyte is also the scale at which the binary/decimal prefix split moves from footnote to consumer complaint. At the kilobyte level the gap is 2.4%; at the megabyte 4.9%; at the gigabyte 7.4%; at the terabyte the cumulative gap reaches 9.95%, and a "1 TB" drive labelled in decimal terabytes by the manufacturer reports as 931.32 "GB" in Microsoft Windows file-properties dialogs that interpret GB as binary gibibytes. The discrepancy generated multiple US class-action lawsuits in the mid-2000s — Cho v. Seagate (2007, settled 2008 with a $1.375 million settlement and a 5% credit toward future Seagate purchases for affected customers), and parallel cases against Western Digital, Hitachi and Apple — none of which forced a labelling change. The consumer-facing fix in 2026 is still imperfect: storage marketing remains decimal, Windows remains binary, and the 69-GB-missing figure is the most-asked storage question on consumer-tech support forums.
Mechanical hard drives in 2026 are sold almost exclusively in TB-tier capacities. WD Blue and Seagate Barracuda consumer 3.5-inch desktop drives ship at 1, 2, 4, 6 and 8 TB; the WD Red Pro and Seagate IronWolf NAS-grade drives at 4, 8, 12, 16, 20 and 24 TB; helium-filled enterprise CMR drives at 18, 20, 22, 24, 26 and 30 TB; the HAMR-based hyperscaler-tier drives at 30 TB and the announced 32 TB and 36 TB SKUs that began sampling to AWS, Azure and Google Cloud in 2024. Consumer SSDs span 250 GB through 4 TB on the M.2 NVMe form factor with 8 TB SKUs from Samsung, WD and Crucial; enterprise U.2 and E1.S NVMe SSDs reach 30.72 TB per drive (Samsung PM1733a), with 61.44 TB and 122.88 TB SKUs from Solidigm shipping for AI-training and analytics workloads. Network-attached storage (Synology, QNAP, TerraMaster) is the consumer-and-prosumer segment most defined by terabyte budgets. A typical 4-bay home NAS populated with 4× 8 TB drives in RAID 5 or SHR yields ~24 TB of usable capacity; an 8-bay Synology DS1823xs+ populated with 8× 20 TB enterprise drives in SHR-2 yields ~120 TB usable; and the buying decision — drive count, redundancy level, scrub schedule — is conducted entirely in TB units. The "Plex media server" hobbyist segment, the Linux ISO archivists, the 4K-Blu-ray remuxers, and the surveillance-camera home-installer market all denominate storage in TB; QNAP and Synology marketing pages spec usable capacity in TB to one decimal place under each RAID-mode configuration. Cloud-storage pricing has converged on per-TB-month tiers above the gigabyte free band. Amazon S3 Standard is priced at roughly $0.023/GB-month ($23/TB-month) in US-East-1 for the first 50 TB and tiers downward; S3 Glacier Deep Archive is $0.00099/GB-month (~$1/TB-month). Backblaze B2 is $6/TB-month. Wasabi is $6.99/TB-month flat with no egress. Backblaze Personal is $99/year for unlimited consumer-PC backup. iCloud+ 2 TB is $9.99/month, iCloud+ 6 TB is $29.99/month, iCloud+ 12 TB is $59.99/month — the consumer pricing ladder where the per-TB unit becomes the visible decision variable. Video production sits at the high end of the terabyte tier. Apple ProRes 422 HQ at 4K UHD records about 880 GB per hour; ProRes 4444 XQ at 4K records 1.85 TB per hour; ARRI ALEXA 35 ARRIRAW 4K records 2.4 TB per hour; RED V-Raptor 8K VV REDCODE 8:1 records 2.6 TB per hour. A typical feature-film day generates 4–10 TB of camera-original footage, and a complete production season for a streaming series can accumulate 1–5 PB of source material. Surveillance and physical-security retention requirements (HIPAA-aligned hospital systems, retail and logistics, smart-city traffic and ALPR programmes) routinely specify 90-day or 365-day retention windows on multi-camera installations that translate to multi-TB or multi-PB local archives.
Real-world uses for Gigabytes to Terabytes
Cloud architects sizing per-VM GB against org-wide TB commits
Cloud-architecture teams sizing AWS EC2, Azure VM, or GCP Compute Engine deployments allocate per-VM disk in GB increments (a 200 GB boot volume, a 500 GB data volume per VM) but contract for org-wide capacity in TB-scale Reserved Capacity or Committed Use Discount agreements. A 200-VM deployment averaging 700 GB per VM rolls up to 140,000 GB or 140 TB of provisioned storage, which feeds into the multi-year TB-scale capacity commit and the per-month TB-tier spend report. Cost optimisation runs constantly across the GB-VM and TB-org layers.
Photo and video professionals against multi-TB archive disks
Professional photographers and videographers cataloguing per-project shoots in GB-scale folders (a 500 GB wedding shoot, a 2000 GB documentary footage day, a 1500 GB commercial b-roll archive) aggregate into multi-TB working drives and offsite backup arrays. A studio's 2024 archive accumulating 15,000 GB of shoot folders rolls up to 15 TB of total project storage, sized against an 18 TB archive RAID. Backup-rotation software tracks per-project GB against the array's TB capacity to flag impending capacity ceilings.
Database administrators aggregating per-table GB into per-database TB
DBAs running PostgreSQL, MySQL, MS SQL Server, and Oracle databases track per-table storage in GB (a 250 GB customer table, an 800 GB transaction history, a 1200 GB analytics fact table) and aggregate into per-database TB capacity plans. A multi-tenant analytics database accumulating 8,500 GB across all tables rolls up to 8.5 TB on the capacity dashboard, which drives storage-tier upgrade decisions and partitioning-strategy reviews. Per-table growth-rate tracking against the per-database TB ceiling is the foundation of database capacity planning.
Streaming-media engineers cataloguing per-asset GB against TB CDN
Streaming-media services (Netflix, Disney+, HBO Max, regional OTT platforms) encode each title at multiple bitrates and resolutions, with per-asset disk footprints in GB (a 5 GB 4K episode encode, a 2 GB 1080p episode, a 500 MB mobile encode) and aggregate library sizes in TB-scale CDN inventory totals. A regional OTT catalogue with 12,000 titles averaging 8 GB per title rolls up to 96,000 GB or 96 TB of total CDN storage, sized against the regional CDN's contracted TB-scale capacity.
When to use Terabytes instead of Gigabytes
Use terabytes when the figure is naturally TB-scale — cloud-storage commit tiers, NAS-array totals, multi-TB archive disks, OTT-platform CDN inventories. Stay in gigabytes when the working precision is at the per-VM, per-project, per-table, or per-asset level. The boundary is at the capacity-rollup transaction: per-VM disk allocations stay in GB on the cloud console, per-project shoot folders stay in GB on the editing-workstation file browser, per-table storage stays in GB on the database admin tool. The aggregate roll-up to TB happens at the org-wide capacity-planning report, the contract renewal, the backup-strategy review. Both layers are kept: GB in the operational view, TB in the strategic view.
Common mistakes converting GB to TB
- Confusing decimal SI TB (1000 GB) with binary TiB (1024 GiB) in capacity-planning calculations. A 100 TB cloud-storage commitment in decimal SI is exactly 100,000 GB; the same 100 TiB in binary is 102,400 GiB — about 2.4% larger. Confusing the two on a multi-year capacity contract introduces percent-level cost discrepancies that compound over the contract term.
- Treating a marketing "1 TB" SSD as exactly 1000 GiB of usable space. The decimal SI 1 TB drive contains 1,000,000,000,000 bytes, which the OS displays as 0.909 TiB or 931 GiB after binary conversion — and after filesystem overhead the user-accessible space is typically around 920 GiB. The "missing" 80 GiB is unit-system difference plus filesystem overhead, not a defective drive.
Frequently asked questions
How many TB in 1000 GB?
One thousand gigabytes equals 1 terabyte in the decimal/SI interpretation used by cloud-storage vendors, HDD marketing, and most modern enterprise dashboards. The binary interpretation (1 TiB = 1024 GiB) gives a slightly different figure. The binary unit is less common in modern usage outside specific OS contexts.
Is 1 TB exactly 1000 GB or 1024 GB?
It depends on the convention. The SI/decimal interpretation defines 1 TB as exactly 1000 GB; the binary interpretation defines 1 TiB as exactly 1024 GiB. Cloud-storage vendors, HDD manufacturers, and most modern dashboards use decimal SI throughout. The two conventions differ by about 9.5% at the TB scale, and the difference matters in multi-TB capacity-planning calculations.
How many TB in 500 GB?
Five hundred gigabytes equals 0.5 TB in decimal SI. Most dashboards display this as "500 GB" rather than "0.5 TB" because the GB figure reads more naturally below the 1 TB threshold. Capacity reports typically switch to TB display only when the figure crosses 1000 GB.
How many TB in 5000 GB?
Five thousand gigabytes equals 5 TB in decimal SI. That is the rough size of a multi-year photo archive, a mid-size database, or a small OTT-platform regional catalogue. The 5 TB figure is also a common consumer external-HDD size, sold at decimal-SI capacity labelling.
When should I report storage in GB versus TB?
Use gigabytes for per-VM, per-project, per-table, and per-asset precision. Use terabytes for org-wide aggregates, cloud commits, NAS-array totals, and any figure that crosses the 1 TB threshold. Most modern dashboards switch automatically at 1000 GB; manual reports follow the same convention to keep the figures human-readable.
How do I convert GB to TB in my head?
Divide by 1000 in decimal SI — a clean three-decimal-place shift. For 8500 GB that gives 8.5 TB; for 96,000 GB it gives 96 TB; for 250 GB it gives 0.25 TB. The mental math is trivial and is the basis for most everyday capacity-aggregation reporting.
How precise should GB-to-TB conversion be in capacity planning?
For commit-tier and contract-renewal calculations, keep two decimal places in TB because cost-per-TB pricing is typically quoted to that precision. An 8500 GB org total converts to 8.50 TB precisely, and a 12,750 GB total becomes 12.75 TB. Round-number TB figures (10 TB, 50 TB, 100 TB) appear in contract tiers, with the GB-precision underlying the actual usage measurement.