Terabytes to Megabytes (TB to MB)
Last updated:
Converting terabytes to megabytes is the natural inverse to MB-to-TB and is most useful for working backward from a known storage budget into per-file or per-folder limits. If you have a 4 TB backup drive and want to know how many MB-scale items it accommodates, the ×1,000,000 multiplier produces the answer directly. The conversion runs whenever a system administrator or user needs to translate large-scale storage allocations into the file-level granularity at which actual usage happens. Decimal SI applies universally for storage hardware; binary IEC applies for memory.
How to convert Terabytes to Megabytes
Formula
MB = TB × 1,000,000
To convert terabytes to megabytes in decimal SI, multiply the TB figure by 1,000,000. The factor follows directly from the prefix definitions: tera = 10^12, mega = 10^6, so the ratio is 10^6 = 1,000,000. The conversion is exact and applies universally in storage-hardware, cloud-billing, and mobile-network contexts. The arithmetic is trivial — multiply by one million — but the practical scale of the result is what matters: a single TB equals a million MB, so per-file thinking at the MB level is several orders of magnitude removed from per-drive thinking at the TB level. For binary IEC contexts (rare in storage, common in memory) the factor is 1,048,576 instead, but the binary convention almost never applies to commercial storage figures and should be avoided unless the source data is explicitly labelled with binary prefixes.
Worked examples
Example 1 — 1 TB
1 TB equals 1 × 1,000,000 = 1,000,000 MB in decimal SI. That capacity holds about 200,000 MP3 files at 5 MB each, 250,000 photos at 4 MB each, or 250 standard-definition movies at 4 GB each. The figure makes the abstract "1 TB drive" tangible in terms of countable file populations.
Example 2 — 4 TB
4 TB — a typical external backup drive sold for under $100 in 2026 — equals 4,000,000 MB. At the average smartphone photo size of 4 MB, the drive holds approximately 1 million photos; at the average HD movie of 1.5 GB, about 2,667 movies. The conversion shows why 4 TB is the practical sweet spot for personal backup: it accommodates a lifetime of accumulated MB-scale media.
Example 3 — 100 TB
100 TB — an enterprise-tier NAS or small office data centre — equals 100,000,000 MB. At the typical genomics sequencing output of 100 GB (100,000 MB) per human sample, that's 1,000 sample archives — about a year of throughput for a mid-sized research lab. The TB-to-MB conversion makes the storage budget legible at the per-sample granularity that actually drives usage.
TB to MB conversion table
| TB | MB |
|---|---|
| 1 TB | 1000000 MB |
| 2 TB | 2000000 MB |
| 3 TB | 3000000 MB |
| 4 TB | 4000000 MB |
| 5 TB | 5000000 MB |
| 6 TB | 6000000 MB |
| 7 TB | 7000000 MB |
| 8 TB | 8000000 MB |
| 9 TB | 9000000 MB |
| 10 TB | 10000000 MB |
| 15 TB | 15000000 MB |
| 20 TB | 20000000 MB |
| 25 TB | 25000000 MB |
| 30 TB | 30000000 MB |
| 40 TB | 40000000 MB |
| 50 TB | 50000000 MB |
| 75 TB | 75000000 MB |
| 100 TB | 100000000 MB |
| 150 TB | 150000000 MB |
| 200 TB | 200000000 MB |
| 250 TB | 250000000 MB |
| 500 TB | 500000000 MB |
| 750 TB | 750000000 MB |
| 1000 TB | 1000000000 MB |
| 2500 TB | 2500000000 MB |
| 5000 TB | 5000000000 MB |
Common TB to MB conversions
- 0.5 TB=500000 MB
- 1 TB=1000000 MB
- 2 TB=2000000 MB
- 4 TB=4000000 MB
- 8 TB=8000000 MB
- 16 TB=16000000 MB
- 32 TB=32000000 MB
- 64 TB=64000000 MB
- 100 TB=100000000 MB
- 1000 TB=1000000000 MB
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.
What is a Megabyte?
One megabyte (MB) equals 1,000,000 bytes under the SI decimal convention or 1,048,576 bytes (= 2²⁰) under the historical binary convention. The IEC 80000-13:2008 standard names the binary 1,048,576-byte quantity the mebibyte (MiB), reserving "megabyte" for the decimal value, but consumer software, file managers, and most desktop operating systems before 2009 reported 1 MB = 1,048,576 bytes. The 4.9% gap between the two conventions is roughly twice the kilobyte-level gap and noticeable on any storage label: a 700 MB CD-ROM holds 734,003,200 bytes if "MB" is read as binary mebibytes, or 700,000,000 bytes if read as decimal megabytes — and CD-ROM capacities were originally specified in binary mebibytes, the source of every "but my disc shows 698 MB free" report from the CD-burning era. The megabyte symbol MB (uppercase B) is distinct from the megabit symbol Mb (lowercase b), the unit used for network throughput; the 8:1 ratio between them is the source of the "100 Mbps gives me 12.5 MB/s downloads" pattern covered under bit and mbps.
The megabyte became the consumer-relevant unit of digital storage during the late 1990s and dominated the consumer-digital decade roughly from 1999 through 2010 — the iPod, Napster, digital-camera, CD-burner and early-smartphone era during which a generation learned to estimate file sizes in megabytes by intuition. The unit's defining cultural artefact is the MP3 audio file: the MPEG-1 Audio Layer III codec, finalised by the Moving Picture Experts Group in 1991 and 1992 with foundational research by Karlheinz Brandenburg's team at the Fraunhofer Institute for Integrated Circuits in Erlangen, achieved roughly 11:1 compression at 128 kbps stereo — putting a typical four-minute pop song at about 3.8 MB. Fraunhofer registered the .mp3 file extension in July 1995, and the format went mainstream with Winamp 1.0 (April 1997) and Napster (June 1999). Apple's first-generation iPod, launched 23 October 2001, advertised "1,000 songs in your pocket" against a 5 GB hard drive on the assumption of roughly 5 MB per song — a single calculation that fixed the MB as the consumer's mental unit of music storage for the next decade. The other defining megabyte-era artefact is the CD-ROM, standardised in the Yellow Book by Philips and Sony in 1988: a Mode 1 disc holds about 650 MB at the 74-minute audio length and 700 MB at the 80-minute length, the capacity that defined what could be distributed as a single physical software product through the 1990s. CompactFlash (SanDisk, 1994) and Secure Digital (the SD Association, 1999) shipped removable camera storage in MB-precision capacities through the late 1990s and early 2000s before transitioning to GB.
Digital audio remains the megabyte's most legible everyday domain. A typical four-minute pop song encoded as 320 kbps MP3 — the Spotify Premium "very high quality" stream — is about 9.6 MB; the same song at the iPod-era 128 kbps default is 3.8 MB; an iTunes Store AAC purchase at 256 kbps is 7.7 MB. A full studio album of 12 tracks at 256 kbps AAC runs roughly 90 MB, the rough capacity-planning figure used by Apple Music and Spotify when sizing offline-listening download budgets on mobile devices. Lossless audio (FLAC, ALAC) at CD-quality 16-bit/44.1 kHz averages 25–35 MB per song; high-resolution 24-bit/96 kHz lossless can exceed 100 MB per song. Digital photography is the megabyte's other defining domain. A 24-megapixel mirrorless or DSLR JPEG at the camera's "Fine" quality setting averages 8–15 MB; the same scene as a 14-bit RAW file (Nikon NEF, Canon CR3, Sony ARW) runs 25–55 MB; a typical iPhone HEIC photograph runs 1.5–3 MB and the same image transcoded to JPEG for email or web upload runs 3–6 MB. CompactFlash, Secure Digital, and microSD cards in the 1–8 MB range powered the early consumer-digital-camera era through the 2000s before transitioning to multi-GB capacities; legacy professional photo workflows still expose JPEG and TIFF working-file sizes in MB through Adobe Bridge, Lightroom and Capture One. Email and software distribution still anchor on MB-precision limits. Gmail's per-message attachment limit has been 25 MB since 2007; Microsoft 365 Outlook caps mailbox-to-mailbox attachments at 20 MB by default and 150 MB administratively; iCloud Mail, Yahoo, and most enterprise SMTP servers cluster around 20–25 MB. The Base64 MIME encoding required for binary email attachments adds 37% overhead, so a 20 MB photo travels as ~27 MB across the wire and frequently bounces against tighter relay limits at the receiving end. Mobile-app store binaries sit in the same MB-tier: a typical iOS app downloaded over cellular cannot exceed 200 MB without explicit "OK to download large file" confirmation (the App Store's longstanding cellular cap, raised from 100 MB in 2017 and from 150 MB in 2019), and Android Play Store APKs face similar Play-Console size warnings around 100 MB before requiring split delivery. Early-mobile-data plans of the 2G GPRS and 3G era were denominated in MB exclusively. The first US "unlimited" iPhone data plans of 2007 were not actually unlimited beyond a soft 5 GB threshold, but most contemporary GSM/EDGE prepaid plans worldwide (Vodafone, Orange, MTN) sold in 50 MB, 100 MB, 250 MB, and 500 MB monthly buckets through roughly 2012 — the MB era of mobile data, before the 4G LTE transition pushed plan sizes into GB.
Real-world uses for Terabytes to Megabytes
Backup window and bandwidth-throughput estimation
IT administrators planning nightly backup windows convert TB-denominated source-data size into MB-throughput figures to compare against network-link megabits-per-second capacity. A 5 TB nightly backup over a 1 Gbps link transfers 5,000,000 MB at a theoretical maximum of 125 MB/s, requiring at least 11.1 hours — typically extending to 14-16 hours after protocol overhead. The conversion drives whether nightly windows fit between business-hours brackets.
Database transaction-log and snapshot sizing
Database administrators sizing transaction-log retention and snapshot policies convert TB-scale total database volumes into MB-per-hour growth rates to validate that snapshot frequency and log-rollover schedules align with per-snapshot MB-throughput limits. Postgres and MySQL transaction logs grow at hundreds of MB per hour on busy production systems, so projecting a multi-TB monthly growth rate against per-MB log-segment limits requires the explicit TB-to-MB conversion.
Email-archive and e-discovery storage planning
Legal e-discovery and email-archive systems sizing storage for multi-year retention windows convert TB-scale archive budgets into MB-per-mailbox limits to compute supportable user counts. A 50 TB e-discovery archive divided across 10,000 employee mailboxes allows 5,000 MB (5 GB) per mailbox — generous for typical corporate email retention but tight for users with significant attachment volumes. The TB-to-MB conversion runs in capacity-planning spreadsheets at every legal-tech vendor.
When to use Megabytes instead of Terabytes
Use megabytes when working at the per-file, per-folder, or per-transfer granularity — backup throughput, individual download sizes, attachment limits, log-segment files. Stay in terabytes for aggregate storage allocations, drive capacities, archive sizes, or any quantity where six-figure-or-larger MB numbers would obscure the underlying scale. The TB-to-MB conversion is the right direction whenever a storage budget is denominated in TB and the operational metric is MB-per-something — bandwidth-throughput planning is the canonical example. The choice between TB and MB at the reporting layer is a question of the audience's mental model, not of physical correctness; both describe the same byte count at different magnifications.
Common mistakes converting TB to MB
- Treating a 1 TB drive as exactly 1,000,000 MB after Windows has shown it as "931 GB." Windows uses binary GiB labelling, so its "931 GB" is actually 931 × 1024 = 953,344 MiB, not 1,000,000 MB. The two figures describe the same physical drive but in different unit conventions; mixing them in a backup-throughput spreadsheet introduces a 5% error compounding across the prefix.
- Using the binary 1,048,576 multiplier for storage. Decimal SI applies universally to commercial storage products — drives, SSDs, cloud quotas, NAS capacities — and the 1,000,000 figure is correct for those contexts. Reserve the binary multiplier strictly for memory aggregation (RAM, on-die cache) where the binary convention is native.
Frequently asked questions
How many MB in 1 TB?
1 TB equals 1,000,000 MB in decimal SI. The conversion is exact and applies to all commercial storage products. In binary IEC the equivalent prefix step is 1 TiB = 1,048,576 MiB — about 4.9% larger — but binary prefixes are not used in storage marketing or billing. The decimal figure is the right one for nearly every consumer or enterprise storage calculation.
How long does it take to transfer 1 TB over a typical home internet connection?
1 TB equals 1,000,000 MB or 8,000,000 megabits. Over a 1 Gbps fibre link at theoretical maximum, the transfer takes 8,000 seconds or 2.2 hours; over a 100 Mbps cable connection, 22 hours; over a 25 Mbps DSL connection, 89 hours (3.7 days). Real-world transfers run 30-50% slower due to TCP overhead, ISP throttling, and bandwidth contention.
How many photos fit in 1 TB?
At the typical modern smartphone photo size of 4-5 MB, 1 TB holds 200,000 to 250,000 photos. Raw DSLR photos at 25 MB each yield about 40,000 raw frames per TB. The figures shape personal-archive planning for photographers — a 4 TB external drive accommodates roughly a million casual photos or 160,000 raw frames, which is more than most non-professional photographers will ever shoot.
Can a network really transfer at the rated MB-per-second speed?
Theoretical maximums apply only on uncongested links with no protocol overhead. Real-world throughput typically lands at 60-85% of theoretical, depending on TCP window scaling, latency, packet loss, and link saturation. A "Gigabit" Ethernet link typically delivers 100-110 MB/s of usable file-transfer throughput, not the 125 MB/s the 1 Gbps figure implies, which extends multi-TB transfer times beyond the back-of-envelope estimate.
Why does my "100 TB" cloud quota seem to fill faster than expected?
Cloud-quota accounting often counts file metadata, versioned snapshots, and pending-deletion objects against the quota, so the 100 TB nominal allocation may correspond to only 70-90 TB of actively stored user data. Backup retention policies that keep multiple snapshots per file inflate the on-quota figure further. Read the cloud vendor's quota-accounting policy carefully — the headline TB figure is usually larger than the usable working-storage figure.