Gb to Tb

💾 Storage Tool

GB to TB
Calculator

Convert gigabytes to terabytes instantly — with binary/decimal toggle, device capacity comparison, content estimator, and full storage chain from PB down to bits.

💾 Storage Accurate
⚡ Instant Results
☁️ Cloud Ready
Direction
Gigabytes (GB)
 
Common sizes (GB)
Formula
—
TB
—
GB
—
MB
—
PB
—
Bytes
—
Bits
—
—
—
—
—
📊 Device capacity comparison
📐 Calculation
💾 Storage insight:
—
ℹ️ Decimal (SI): 1 TB = 1,000 GB (manufacturers, macOS). Binary (IEC): 1 TiB = 1,024 GiB (Windows, Linux). Toggle “Binary” to switch standards.

GB to TB Calculator: Convert Storage Instantly

Converting gigabytes to terabytes is essential for storage planning, device comparison, and understanding cloud storage quotas. The conversion is straightforward — divide GB by 1,000 (decimal/SI standard) or by 1,024 (binary/IEC standard) — but the two competing standards create confusion that this calculator resolves with a simple toggle. A 500 GB SSD is 0.5 TB (decimal); Windows displays it as approximately 465 “GB” (actually 465 GiB) because Windows uses binary values with decimal labels. This calculator handles both standards, displays the result across six units (PB through bits), estimates content capacity (photos, songs, video, games), and shows a visual comparison against common device sizes.

💾 The formulas:
Decimal (SI): TB = GB ÷ 1,000 → 500 GB = 0.5 TB
Binary (IEC): TiB = GiB ÷ 1,024 → 512 GiB = 0.5 TiB
The confusion: A “1 TB” drive (1,000 GB) shows as “931 GB” in Windows (actually 931 GiB = 1,000 GB)
Reverse: 1 TB = 1,000 GB (decimal) · 1 TiB = 1,024 GiB (binary)

Storage Conversion Reference

SizeDecimal TBBinary TiBWindows showsHolds ≈
💾 128 GB0.1280.125119 “GB”25,600 photos
💾 256 GB0.2560.250238 “GB”51,200 photos
💾 500 GB0.5000.488465 “GB”100,000 photos
💾 1,000 GB1.0000.977931 “GB”200,000 photos
💾 2,000 GB2.0001.9531,863 “GB”400,000 photos
💾 4,000 GB4.0003.9063,725 “GB”800,000 photos
💾 8,000 GB8.0007.8137,450 “GB”1.6M photos

Decimal vs Binary: The Two Standards

🔢

Decimal (SI): ÷1,000

1 TB = 1,000 GB = 1,000,000 MB. Used by drive manufacturers, Apple macOS, and the International System of Units. Produces clean round numbers for marketed capacities.

💻

Binary (IEC): ÷1,024

1 TiB = 1,024 GiB = 1,048,576 MiB. Used by Windows, Linux, and memory (RAM). Aligns with how computers address memory in powers of 2.

⚠️

The “missing space” myth

A 1 TB drive shows as 931 GB in Windows. No storage is missing — Windows displays 931 GiB (binary) but labels it “GB.” 931 GiB = exactly 1,000 GB = 1 TB. Both numbers represent the same physical storage.

🍎

Apple’s approach

Since macOS 10.6, Apple uses decimal units: a 1 TB drive shows as “1 TB” in macOS. This matches the manufacturer’s label, avoiding the confusion Windows creates by showing binary values with decimal labels.

Why the GB-to-TB Conversion Matters

The terabyte has become the standard unit for discussing storage capacity in the 2020s, replacing the gigabyte as the primary reference point. Consumer SSDs now commonly offer 1 TB, 2 TB, and 4 TB capacities. External hard drives start at 1 TB and reach 24 TB for desktop models. Cloud storage plans are quoted in TB (Google One 2 TB, iCloud 2/6/12 TB). NAS devices typically hold 2–100+ TB across multiple drives. Understanding how many GB equal a TB — and which standard applies in your context — is fundamental to comparing storage options and planning capacity.

SSD Capacity Planning

Solid-state drives are the primary storage in modern computers, and their GB-to-TB relationship affects purchasing decisions. A 256 GB SSD = 0.256 TB — adequate for a Chromebook or light-use laptop (OS + documents + browser). A 512 GB SSD = 0.512 TB — sufficient for most general-purpose users (OS + Office + moderate photo library + a few games). A 1 TB SSD = 1.0 TB — the sweet spot for power users (OS + full software suite + large photo library + several games). A 2 TB SSD = 2.0 TB — ideal for video editors, gamers with large libraries, and professionals with large datasets. The calculator converts any SSD capacity to TB for quick comparison and helps buyers understand how their current GB usage translates to TB-scale purchasing decisions.

Cloud Storage Plans Compared

Cloud storage providers sell plans in both GB and TB, requiring conversion for cost comparison. Google One: 100 GB ($1.99/mo), 200 GB ($2.99/mo), 2 TB ($9.99/mo). The jump from 200 GB to 2 TB (0.2 TB to 2.0 TB — a 10× increase) costs only 3.3× more — making 2 TB the best value per GB. iCloud+: 50 GB ($0.99/mo), 200 GB ($2.99/mo), 2 TB ($9.99/mo), 6 TB ($29.99/mo), 12 TB ($59.99/mo). Dropbox: 2 TB Plus ($11.99/mo), 3 TB Professional ($19.99/mo). OneDrive: 100 GB ($1.99/mo), 1 TB ($6.99/mo with Microsoft 365). The calculator converts any plan’s GB to TB (or vice versa) for normalised cost-per-TB comparison across providers.

Gaming Storage Requirements

Modern AAA games make the GB-to-TB conversion critical for gamers. Call of Duty: Modern Warfare III: ~149 GB (0.149 TB). Baldur’s Gate 3: ~120 GB (0.12 TB). Red Dead Redemption 2: ~120 GB (0.12 TB). Starfield: ~125 GB (0.125 TB). A 1 TB SSD holds approximately 6–8 large games plus the OS. A 2 TB SSD holds 13–16 games. The trend toward 100+ GB games means gamers increasingly think in TB rather than GB — a 1 TB drive that seemed enormous a decade ago now fills up with fewer than 10 modern titles. The calculator converts individual game sizes (GB) to their TB fraction for planning total storage needs.

Video Production Storage

Video professionals generate enormous amounts of data where the GB-to-TB conversion is daily arithmetic. 1080p H.264: approximately 12 GB per hour (0.012 TB/hr). 4K ProRes 422: approximately 110 GB per hour (0.11 TB/hr). 8K RAW: approximately 500+ GB per hour (0.5+ TB/hr). A typical wedding video project: 5 hours of multi-camera 4K footage = approximately 550 GB (0.55 TB) of raw footage + 200 GB of project files + 50 GB of deliverables = ~800 GB (0.8 TB) total. Over a year of 50 weddings: 40 TB of accumulated project data. The calculator converts any video storage requirement from GB to TB for drive purchasing and archive planning.

NAS and Server Storage

Network-attached storage devices aggregate multiple drives, making TB the natural planning unit. A 4-bay NAS with 4 TB drives provides 16 TB raw capacity — or 12 TB usable in RAID 5 (one drive’s worth of redundancy). Converting project sizes from GB to TB helps NAS owners plan: a 500 GB photo library (0.5 TB) uses 4.2% of a 12 TB NAS. A full TimeMachine backup of a 2 TB Mac requires 4–6 TB of NAS space (historical snapshots). Enterprise NAS scales to 100+ TB: a Synology RS3621RPxs with 12 × 18 TB drives provides 216 TB raw / ~180 TB usable in RAID 6. The calculator converts any file collection from GB to TB for proportional capacity planning.

Backup and Disaster Recovery

Backup storage planning requires accurate GB-to-TB conversion. A company with 500 GB of active data (0.5 TB) maintaining 30 daily backups (with incremental compression) needs approximately 1.5–3 TB of backup storage. Adding off-site replication doubles this: 3–6 TB. Personal backup: a household with 2 TB of combined data across computers, phones, and tablets needs at least 4 TB of backup storage (primary + secondary copy). Time Machine on macOS stores multiple versions, typically requiring 2–3× the source data size. The calculator helps convert individual data sources (measured in GB on each device) to aggregate TB requirements for backup infrastructure sizing.

Data Centre and Enterprise Storage

Enterprise storage systems operate at TB and PB (petabyte) scale. Small business file server: 2–10 TB. Medium business database: 10–100 TB. Enterprise data warehouse: 100 TB–10 PB. Hyperscale cloud (AWS, Azure, GCP): exabytes of total storage. A department generating 50 GB of data per day accumulates 18.25 TB per year (50 × 365 = 18,250 GB ÷ 1,000 = 18.25 TB). Over 5 years with retention: 91.25 TB. The calculator converts daily/monthly GB generation rates to annual and multi-year TB requirements for storage procurement and budgeting.

Photography Storage

Photographers accumulate storage over years of shooting. A professional shooting 500 RAW photos per wedding at 50 MB each generates 25 GB (0.025 TB) per event. Over 50 weddings per year: 1,250 GB = 1.25 TB of new photos annually. In 10 years: 12.5 TB. Adding edited versions, exports, and catalog files: approximately 20 TB total. Landscape photographers shooting 100 images per outing at 80 MB RAW (61 MP sensor): 8 GB per session. Weekly outings for 5 years: ~2,080 GB = 2.08 TB. The calculator converts any shooting pattern from GB to TB for long-term storage planning and NAS/cloud sizing.

Streaming and Media Libraries

Personal media libraries are measured in TB. A movie collection of 200 films at 4 GB each (1080p) = 800 GB (0.8 TB). At 20 GB each (4K HDR): 4,000 GB = 4 TB. A music collection of 10,000 songs at 10 MB (FLAC lossless): 100 GB (0.1 TB). Audiobook libraries of 500 titles at 300 MB each: 150 GB (0.15 TB). A Plex media server with 500 movies (4K) + 50 TV series + 20,000 songs might total 12–15 TB. The calculator helps media enthusiasts convert their collections from GB to TB for drive selection and NAS capacity planning.

The Windows Display Discrepancy

This deserves emphasis because it generates more confusion than any other storage topic. Example: you buy a “2 TB” external hard drive. You plug it into your Windows PC. Windows shows “1,863 GB.” You think 137 GB is missing. What actually happened: the manufacturer measured 2,000 GB (decimal). Windows calculated 2,000,000,000,000 bytes ÷ 1,024³ = 1,862.645 GiB — but labelled it “1,863 GB.” Both numbers describe the same physical storage: 2,000,000,000,000 bytes. The calculator demonstrates this: enter 2000 GB in decimal mode → 2.000 TB. Toggle to binary mode → the calculator now reads that same “2000” as 2000 GiB and shows 1.9531 TiB. (To see what 2000 decimal GB equals in true binary terms — the number Windows would actually display — look at the reference table below: 2,000 GB shows as 1,863 “GB” i.e. GiB in Windows.) No storage is missing; the units are simply different sizes.

Common GB-to-TB Mistakes

  • Using ÷1024 when ÷1000 is correct (or vice versa). Decimal (÷1000): for drive capacity labels, cloud storage plans, macOS displays. Binary (÷1024): for Windows/Linux displays, RAM specifications. Using the wrong divisor causes a 2.4% error per level.
  • Thinking your drive lost storage. A 1 TB drive showing 931 GB in Windows has all its bytes — Windows uses binary values (GiB) but labels them “GB.” Toggle the calculator to binary mode to see Windows-equivalent values.
  • Confusing GB (gigabytes) with Gb (gigabits). Uppercase B = bytes (storage). Lowercase b = bits (networking). 1 GB = 8 Gb. A “10 Gb” Ethernet card transfers 1.25 GB per second, not 10 GB.
  • Forgetting formatting overhead. A 1 TB drive formatted with NTFS provides approximately 930–970 GB usable; ext4 with default 5% reserved blocks provides approximately 950 GB. The raw mathematical conversion assumes unformatted capacity.

Related Storage Calculators

Frequently Asked Questions

How many GB are in 1 TB?
Using the decimal (SI) standard: 1 TB = 1,000 GB exactly. Using the binary (IEC) standard: 1 TiB = 1,024 GiB. Storage manufacturers, Apple macOS, and most consumer contexts use decimal (1,000). Windows and Linux use binary (1,024) but confusingly label the result “GB” instead of “GiB.”
How do I convert GB to TB?
Divide the GB value by 1,000 (decimal) or 1,024 (binary). Example: 500 GB ÷ 1,000 = 0.5 TB. Use decimal for drive capacity and cloud storage; use binary when matching Windows file explorer displays. The calculator supports both with a simple toggle.
Why do manufacturers use 1000?
Storage manufacturers follow the International System of Units (SI), where “tera” = 10¹² (1,000,000,000,000). This is consistent with all other SI prefixes (kilogram, kilometer, etc.). It also produces larger marketed numbers: “1 TB” sounds bigger than “931 GB” (the Windows binary display of the same drive).
Why does Windows use 1024?
Computer memory is physically addressed in powers of 2 (2¹⁰ = 1,024). Early computing adopted “kilobyte” = 1,024 bytes for convenience. Windows maintains this convention for backward compatibility. The IEC created unambiguous terms (KiB, MiB, GiB, TiB) in 1998, but Windows still labels binary values with decimal names (GB instead of GiB).
What is TiB?
TiB (tebibyte) is the IEC binary unit: 1 TiB = 1,024 GiB = 1,099,511,627,776 bytes. It unambiguously represents 2⁴⁰ bytes, while TB (terabyte) represents 10¹² = 1,000,000,000,000 bytes. 1 TiB is approximately 9.95% larger than 1 TB. Windows displays TiB values but labels them “TB.”
What is GiB?
GiB (gibibyte) is the IEC binary unit: 1 GiB = 1,024 MiB = 1,073,741,824 bytes (2³⁰). It’s 7.37% larger than 1 GB (1,000,000,000 bytes). There are 1,024 GiB in 1 TiB (binary) versus 1,000 GB in 1 TB (decimal). The calculator shows both conversions when you toggle binary mode.
Is this calculator accurate?
Yes — the calculator uses exact arithmetic: ÷1,000 for decimal and ÷1,024 for binary. Both standards are mathematically exact with no rounding. The toggle lets you choose which standard applies to your context. Results are displayed to 6 decimal places for precision.
Can I convert PB?
Yes — enter large GB values (1,000,000 GB = 1 PB) and the calculator shows the result in TB and PB. The full chain is displayed: PB → TB → GB → MB → bytes → bits. For binary: 1 PiB = 1,024 TiB = 1,048,576 GiB.
How much storage do I need?
Typical needs: basic use (email, browsing) 128–256 GB (0.13–0.26 TB). Moderate (photos, apps, some games) 512 GB–1 TB. Heavy (many games, video editing) 2–4 TB. Professional (video production, large datasets) 4–16 TB. The calculator’s content estimator shows how many photos, songs, minutes of video, and games fit in any capacity.
Is GB the same as GiB?
No. GB (gigabyte, SI) = 1,000,000,000 bytes. GiB (gibibyte, IEC) = 1,073,741,824 bytes. A GiB is 7.37% larger than a GB. At the TB level: 1 TB = 1,000 GB; 1 TiB = 1,024 GiB. The confusion exists because Windows uses GiB values but labels them “GB.”
Can I compare storage devices?
Yes — the calculator shows a visual bar chart comparing your value against four devices (256 GB SSD, 1 TB SSD, 2 TB SSD, 4 TB HDD). A red line marks your entered value on each bar for instant visual context.
Which standard should I use?
Decimal (÷1000) for: drive capacity labels, cloud storage plans, macOS, marketing materials, and general communication. Binary (÷1024) for: matching Windows file explorer, Linux df output, RAM specifications, and technical documentation that references GiB/TiB explicitly. When in doubt, decimal is the more common consumer standard.
Why are SSD capacities different from HDDs?
SSDs and HDDs use the same decimal standard for marketed capacity (both use “TB” = 1,000 GB). The available sizes differ because of manufacturing: SSDs come in powers of 2 (128, 256, 512, 1024 GB) due to NAND flash chip organization, while HDDs come in rounder numbers (500, 1000, 2000, 4000 GB) based on platter density. Both display the same way in Windows (with the binary/decimal discrepancy).
What is a byte?
A byte is 8 bits — the fundamental unit of digital storage. One byte stores one ASCII character. File sizes use bytes (KB, MB, GB, TB). Storage chains: 1 TB = 1,000 GB = 1,000,000 MB = 1,000,000,000 KB = 1,000,000,000,000 bytes (decimal). The calculator displays the complete chain for any conversion.
What is a bit?
A bit (binary digit) is the smallest data unit — a single 0 or 1. Eight bits = one byte. Networking uses bits (Mbps, Gbps); storage uses bytes (MB, GB, TB). The calculator shows both: entering 1 TB displays 8,000,000,000,000 bits (decimal) or 8,796,093,022,208 bits (binary).

Scientific and Research Data at TB Scale

Scientific research generates data at scales where the GB-to-TB conversion is constant arithmetic. Genome sequencing: a single whole-genome sequencing run produces 100–500 GB (0.1–0.5 TB) of raw data. A genomics lab running 20 sequences per week generates 2,000–10,000 GB (2–10 TB) weekly — 100–500 TB annually. Astronomical surveys: the Vera C. Rubin Observatory will generate approximately 20 TB of raw data per night of operation, accumulating 60 PB (60,000 TB) over its 10-year survey. Climate modelling: a single high-resolution global climate simulation can generate 10–100 TB of output data. Particle physics: CERN’s Large Hadron Collider experiments generate approximately 1 PB (1,000 TB = 1,000,000 GB) per year. The calculator converts individual experiment outputs from GB to TB for storage procurement proposals and grant budgets.

Surveillance and Security Camera Storage

Security camera systems require careful storage planning in TB. A single 1080p IP camera recording 24/7 at medium quality generates approximately 15–30 GB per day (0.015–0.03 TB/day). A 4K camera generates 40–80 GB per day. For a 16-camera 1080p system with 30-day retention: 16 cameras × 20 GB/day × 30 days = 9,600 GB = 9.6 TB minimum. For 4K cameras: 16 × 60 GB × 30 = 28,800 GB = 28.8 TB. NVR (Network Video Recorder) systems are typically sold with 2–16 TB of storage — the calculator helps security installers convert per-camera daily GB generation to total TB requirements for the retention period, ensuring adequate NVR capacity before installation.

Music Production and Audio Engineering

Professional audio projects accumulate storage over sessions and years. A multi-track recording session in a professional studio (24 tracks at 96 kHz/24-bit): approximately 1.5 GB per minute of recording = 90 GB per hour. A typical album project with 100 hours of tracked material: 9,000 GB = 9 TB of raw session files. Adding mix bounces, stems, and masters: approximately 10–12 TB per album. A busy studio producing 10 albums per year accumulates 100–120 TB annually. Even home producers working with 16-bit/44.1 kHz sessions generate 500 MB per minute across 16 tracks: a year of weekly 4-hour sessions = approximately 6,200 GB = 6.2 TB. The calculator converts project sizes from GB to TB for archive drive purchasing and cloud backup sizing.

Virtual Machine and Container Storage

Virtualisation environments require TB-scale storage planning. A Windows Server VM typically needs 80–120 GB for the OS plus application data. A Linux server VM needs 20–40 GB base. Running 50 VMs averaging 100 GB each = 5,000 GB = 5 TB. Adding VM snapshots (one per VM, averaging 20 GB each) = 1,000 GB = 1 TB additional. Total: 6 TB. Container images are smaller (100–500 MB each) but high-density deployments running 500+ containers still accumulate: 500 × 300 MB = 150,000 MB = 150 GB. Kubernetes persistent volumes for databases and stateful applications add 10–100 GB each. The calculator converts individual VM/container sizes from GB to aggregate TB for SAN/NAS/cloud storage provisioning.

Email and Communication Archives

Enterprise email archives grow steadily from GB into TB territory. A typical corporate email account generates 2–5 GB per year per user. An organisation with 1,000 employees retaining 7 years of email: 1,000 × 3.5 GB × 7 = 24,500 GB = 24.5 TB. Microsoft 365 E3 provides 50 GB per user mailbox + 1.5 TB shared archive: for 1,000 users, that is 50,000 GB (50 TB) of mailbox allocation. Slack workspaces accumulate 1–5 GB per user per year including file uploads. Teams/SharePoint: 1 TB per organisation + 10 GB per user. The calculator converts per-user GB allocations to organisation-wide TB totals for capacity planning, compliance storage, and backup infrastructure sizing.

Drone and Aerial Photography

Commercial and recreational drones generate significant storage requirements. A DJI Mavic 3 Pro shooting 5.1K video produces approximately 150 MB per minute = 9 GB per hour. A commercial mapping drone capturing high-resolution photos covers approximately 100 images per flight at 20 MB each = 2 GB per flight. A professional aerial survey company conducting 10 flights per day, 5 days per week: 10 × 9 GB × 5 × 52 = 23,400 GB = 23.4 TB per year of raw video, plus 10 × 2 GB × 5 × 52 = 5,200 GB = 5.2 TB of photo data. Combined: approximately 28.6 TB annually. The calculator converts per-flight GB to annual TB for storage infrastructure and cloud archive budgeting.

Autonomous Vehicle Data

Self-driving vehicle development generates extreme storage requirements where GB-to-TB conversion operates at massive scale. A single autonomous test vehicle equipped with cameras, LiDAR, radar, and GPS generates approximately 1–5 TB of sensor data per hour of driving. A fleet of 100 test vehicles driving 8 hours per day: 100 × 3 TB × 8 = 2,400 TB per day = 2.4 PB daily. Annual storage: approximately 876 PB. Even after filtering and compression (keeping ~10% of raw data), retention requirements reach tens of petabytes. While these numbers exceed most users’ needs, they illustrate the TB-to-PB transition that the calculator’s full unit chain (PB→TB→GB→MB→bytes) handles seamlessly.

The Device Capacity Comparison

The calculator displays an SVG bar chart comparing your entered GB value against four reference devices: a 256 GB SSD, a 1 TB SSD, a 2 TB SSD, and a 4 TB HDD. Each grey bar represents the device’s full capacity, with a red vertical marker line at your value’s position on the scale. This provides instant visual context: entering 500 GB shows the red line beyond the 256 GB SSD bar (exceeding it), at the halfway point of the 1 TB bar, at one-quarter of the 2 TB bar, and at one-eighth of the 4 TB bar. The chart auto-scales if your value exceeds all reference devices. This visualization helps buyers immediately understand how a specific GB amount relates to available drive sizes.

File System and Formatting Overhead

The mathematical conversion from GB to TB gives raw capacity, but formatted drives have less usable space. NTFS (Windows): approximately 0.5–2% overhead for master file table, journal, and metadata. A 2 TB drive provides approximately 1,960–1,990 GB usable. APFS (macOS): minimal overhead, typically under 1%. ext4 (Linux): reserves 5% by default for the root user (adjustable with tune2fs). A 4 TB drive formatted ext4 provides approximately 3,800 GB usable unless the reserved percentage is reduced. ZFS (FreeBSD, TrueNAS): metadata overhead of 1–3% plus optional compression that can effectively increase usable capacity. RAID overhead further reduces usable space: RAID 5 loses one drive’s worth of capacity; RAID 6 loses two drives. A 4-drive RAID 5 array with 4 TB drives: 16 TB raw – 4 TB parity = 12 TB usable (minus formatting overhead). The calculator shows raw mathematical conversion; subtract formatting and RAID overhead for actual usable capacity. For precise planning, the general rule is to provision 10–15% more raw capacity than your calculated TB requirement to account for formatting, metadata, RAID parity, and future growth margin.

Convert your storage now 💾

Binary/decimal toggle, content estimator, device comparison — enter any GB for instant TB conversion.

Convert now ↑