GB to TB Converter — Gigabytes to Terabytes

The Conversion: 1 TB = 1,024 GB

One terabyte (TB) equals 1,024 gigabytes (GB) in the binary system used by operating systems and computing tools. To convert gigabytes to terabytes, divide the number of gigabytes by 1,024.

• GB → TB: Divide by 1,024 (e.g., 2,048 GB ÷ 1,024 = 2 TB)
• TB → GB: Multiply by 1,024 (e.g., 4 TB × 1,024 = 4,096 GB)

Quick reference: 256 GB = 0.25 TB; 512 GB = 0.5 TB; 1,024 GB = 1 TB; 2,048 GB = 2 TB; 4,096 GB = 4 TB.

The storage manufacturer difference: When you buy a "2 TB" hard drive, the manufacturer uses the decimal definition: 2 TB = 2,000,000,000,000 bytes. Your operating system uses binary: 1 TB = 1,099,511,627,776 bytes. Result: that 2 TB drive appears as ~1.82 TB in Windows Explorer. This converter uses the binary definition (1 TB = 1,024 GB), matching what your OS reports.

GB to TB Conversion Table

Common gigabyte amounts converted to terabytes, with real-world context:

Why Terabytes: Understanding Modern Storage Scale

Storage capacity has grown exponentially over the past three decades. A standard floppy disk held 1.44 MB. The first 1 GB hard drives cost thousands of dollars in the early 1980s. Today, consumer hard drives routinely reach 16–20 TB, and enterprise drives push beyond 30 TB. Understanding the GB-to-TB relationship helps you navigate modern storage purchases and capacity planning.

The jump from GB to TB thinking happened gradually in the early 2010s when consumer hard drives crossed the 1 TB threshold at affordable prices. Before that, people talked about storage in hundreds of GB. Now, 1 TB is the baseline for desktop storage, and NAS users think in tens of terabytes. Cloud providers manage exabytes (1,000 petabytes = 1,000,000 terabytes).

Key storage milestones: a typical home user might accumulate 200–500 GB of photos, videos, and documents over years of digital life. A household with multiple people sharing a NAS easily accumulates 2–5 TB. A small business server with several years of data, backups, and user files often needs 10–50 TB. Video production companies working with 4K RAW footage might generate 10–100 GB per minute of footage, making TB-scale storage essential for active projects.

For developers and sysadmins, thinking in TB is increasingly necessary. A PostgreSQL database for a mid-sized web application might be 50–500 GB. A data warehouse at a growing startup might be 1–10 TB. A media streaming platform stores content in petabytes. Understanding that 1 TB = 1,024 GB is the foundation for all these capacity discussions.

Storage Technologies Compared: GB and TB in Context

Different storage technologies have different capacity profiles, and understanding GB-to-TB helps you compare options intelligently:

The price-per-GB (or price-per-TB) varies dramatically by technology. In 2024–2025, consumer HDDs reach approximately $0.02–0.03 per GB ($20–30 per TB). Consumer SSDs cost about $0.05–0.10 per GB ($50–100 per TB). Enterprise SSDs with NVMe interfaces can reach $0.20–0.50 per GB. Tape storage for archival, despite the access speed disadvantage, costs well under $0.01 per GB for large deployments.

Video Production Storage Needs in TB

Video content creators, filmmakers, and broadcasting professionals are among the heaviest storage consumers. Understanding GB-to-TB is critical for production planning:

• 4K H.264 (DSLR, consumer): ~1.5 GB per minute = 90 GB per hour. A feature-length 90-minute film at this quality: 135 GB = ~0.13 TB.
• 4K H.265 (efficient compression): ~0.75 GB per minute = 45 GB per hour. Same 90-minute film: ~67 GB = ~0.065 TB.
• 4K RAW (professional cinema cameras): ~10–50 GB per minute = 600 GB to 3 TB per hour. A 10-day film shoot with 8 hours of shooting per day: 48,000–240,000 GB = 47–234 TB of RAW footage.
• 1080p streaming (Twitch, YouTube): ~3–6 GB per hour recorded locally. A full-time streamer working 40 hours/week: 120–240 GB/week = ~6–12 TB/year of raw recordings.
• 8K RAW (high-end production): ~100+ GB per minute. Even short projects generate tens of TB of raw data.

Production studios use RAID arrays and SAN (Storage Area Network) systems providing hundreds of TB of fast storage for active productions. Post-production often requires fast (NVMe SSD) storage for the edit timeline plus slower (HDD) storage for the full media library. A mid-size production company might provision a 100 TB NAS array for active project storage, with cold archival storage adding hundreds more TB on cheaper HDDs or tape.

Cloud Storage and Data Centers: Thinking in TB

Cloud storage services are priced in GB but consumed in TB by organizations. Understanding the conversion helps with cost modeling:

Amazon S3 storage pricing (approximate):

• First 50 TB/month: ~$0.023 per GB = $23.55 per TB
• Next 450 TB/month: ~$0.022 per GB = $22.53 per TB
• Over 500 TB/month: ~$0.021 per GB = $21.50 per TB

A company storing 10 TB = 10,240 GB of data on S3: 10,240 × $0.023 = $235.52/month just for storage (before data transfer, requests, or other charges). At 100 TB: 102,400 GB × $0.023 = $2,355/month. At 1 PB (1,024 TB): ~$23,552/month. These numbers drive architectural decisions about what to store in cloud vs on-premises.

Data center capacity planning uses rack units and TB of storage per rack. A standard 42U server rack might hold 20–30 storage nodes, each with 24 disk bays. At 20 TB per drive × 24 drives per node × 25 nodes per rack = 12,000 TB = ~11.7 PB per rack (theoretical, before RAID overhead). Enterprise data centers managing hundreds of racks think in exabytes. The GB-to-TB conversion is just the beginning of the scale hierarchy they work with daily.

Home NAS and Personal Storage: Planning Your TB Budget

Home users, prosumers, and small businesses increasingly use Network Attached Storage (NAS) devices for centralized file storage, media libraries, and backups. Planning a NAS purchase requires thinking in terabytes while understanding the GB-level details of your data.

Typical home NAS scenarios:

A family of 4 with digital photos, videos, and general files might accumulate: 50,000 smartphone photos at 4 MB each = 200 GB; 200 hours of home videos at 5 GB/hour = 1,000 GB = ~1 TB; Documents, downloads, and miscellaneous files: ~100 GB. Total active data: ~1.3 TB. With RAID-1 mirroring (each drive holds an identical copy), you need at least 2.6 TB of raw drive capacity — practical recommendation: two 4 TB drives (4,096 GB each) giving 4 TB usable in RAID-1 with room for years of growth.

A media enthusiast with a ripped Blu-ray library: a single 4K Blu-ray rip (MKV) averages 50–80 GB. A 100-movie library: 5,000–8,000 GB = 4.9–7.8 TB of raw files. With RAID-5 across four 4 TB drives (12 TB usable), this library fits with room to grow. Adding 1080p TV series: a typical 10-episode season in 1080p averages 8–15 GB per episode = 80–150 GB per season. 50 seasons = 4,000–7,500 GB = ~3.9–7.3 TB. Combined: 8.8–15.1 TB total — requiring a larger array or upgrade path planning.

The 3-2-1 backup rule in TB: Best practice for data protection: 3 copies of data, 2 different media types, 1 offsite. For a 2 TB dataset: 2 TB on local NAS + 2 TB on separate local drive + 2 TB in cloud backup. Cloud backup cost: 2,048 GB × $0.023/GB (S3) = ~$47/month, or use a dedicated backup service like Backblaze ($9/month flat for unlimited personal backup). Understanding that your 2 TB dataset = 2,048 GB helps you evaluate backup service pricing and storage purchasing decisions accurately.

When planning storage growth over time, the rule of thumb for active data: people tend to accumulate roughly 100–500 GB of new files per year (excluding 4K video production). Over 5 years, that's 500 GB to 2.5 TB of new data. Buy storage with 2–3 years of headroom at minimum. With NAS systems, you can add drives or upgrade to higher-capacity drives as needed, but planning the initial build for your 3-year storage needs avoids premature upgrades. The GB-to-TB conversion — dividing by 1,024 — is the foundation of all these planning calculations.