Megabytes to Terabytes (MB to TB)
Last updated:
Converting megabytes to terabytes runs every time someone tries to estimate how much of their multi-terabyte drive a folder of MB-scale files actually consumes, or projects long-term backup growth from current per-document sizes against a TB-tier storage purchase. The factor is a clean ×0.000001 in decimal SI (1 TB = 1,000,000 MB) — six orders of magnitude. The arithmetic is trivial but the conceptual gap between MB-denominated documents and TB-denominated drives is enormous, which is why backup planners and IT-asset managers run this conversion as part of their forward-projection spreadsheets.
How to convert Megabytes to Terabytes
Formula
TB = MB × 0.000001
To convert megabytes to terabytes in decimal SI, multiply the MB figure by 0.000001 (or equivalently divide by 1,000,000). One terabyte equals 1,000,000 megabytes by definition in the decimal convention used by drive manufacturers, cloud storage vendors, and file-system tools on macOS and modern Linux. The arithmetic is trivial — six orders of magnitude — but the practical implication is that MB-denominated files take a long time to fill a TB-denominated drive. The binary IEC convention (1 TiB = 1,048,576 MiB) is used by Windows file properties and produces results 4.9% larger across the prefix step; for binary work multiply MB by 1/1,048,576 instead and label the result TiB explicitly to avoid downstream confusion when mixing storage figures from different sources.
Worked examples
Example 1 — 500 MB
500 MB — about 100 high-resolution photos or a compressed two-hour movie download — equals 0.0005 TB. That's only 0.05% of a 1 TB drive, illustrating how individual files barely register against multi-terabyte storage tiers and why drive consumption tends to come from sustained accumulation of MB-scale items rather than single huge files.
Example 2 — 100000 MB
100,000 MB equals exactly 0.1 TB or 100 GB — roughly the size of one fully-loaded modern AAA game install or a few hundred hours of HD streaming-cached video. The figure represents the threshold at which casual consumer storage starts noticeably impacting available drive space on common 256 GB or 500 GB consumer SSDs.
Example 3 — 1000000 MB
1,000,000 MB equals exactly 1 TB by definition in decimal SI — the unit relationship that drives the entire convention. A typical 1 TB external drive holds about 200,000 MP3 files, 250,000 photos, or 250 standard-definition movies. The exact correspondence between 1,000,000 MB and 1 TB is what makes the MB-to-TB conversion mathematically clean compared to the binary alternative.
MB to TB conversion table
| MB | TB |
|---|---|
| 1 MB | 0 TB |
| 2 MB | 0 TB |
| 3 MB | 0 TB |
| 4 MB | 0 TB |
| 5 MB | 0 TB |
| 6 MB | 0 TB |
| 7 MB | 0 TB |
| 8 MB | 0 TB |
| 9 MB | 0 TB |
| 10 MB | 0 TB |
| 15 MB | 0 TB |
| 20 MB | 0 TB |
| 25 MB | 0 TB |
| 30 MB | 0 TB |
| 40 MB | 0 TB |
| 50 MB | 0 TB |
| 75 MB | 0.0001 TB |
| 100 MB | 0.0001 TB |
| 150 MB | 0.0001 TB |
| 200 MB | 0.0002 TB |
| 250 MB | 0.0003 TB |
| 500 MB | 0.0005 TB |
| 750 MB | 0.0008 TB |
| 1000 MB | 0.001 TB |
| 2500 MB | 0.0025 TB |
| 5000 MB | 0.005 TB |
Common MB to TB conversions
- 100 MB=0.0001 TB
- 500 MB=0.0005 TB
- 1000 MB=0.001 TB
- 5000 MB=0.005 TB
- 10000 MB=0.01 TB
- 50000 MB=0.05 TB
- 100000 MB=0.1 TB
- 500000 MB=0.5 TB
- 1000000 MB=1 TB
- 5000000 MB=5 TB
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.
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 Megabytes to Terabytes
Photographer and videographer asset-archive sizing
Wedding photographers, event videographers, and stock-footage producers project annual archive growth from per-shoot MB and GB figures against TB-scale long-term storage purchases. A typical wedding shoot generates 30-50 GB of raw photo and video data; 200 weddings per year fills 6-10 TB of archive space annually. The MB-to-TB conversion shapes whether a freelancer's NAS purchase needs to be 8 TB, 16 TB, or 32 TB in capacity for multi-year archive retention.
Genomics sequencing data archival
Modern whole-genome sequencing produces 100-150 GB of compressed FASTQ files per human sample, with research projects routinely accumulating 50-500 sample sequencing runs that aggregate into multi-TB archives within a single calendar year. Bioinformatics labs converting per-sample MB and GB metadata against TB-denominated archival tape and S3 Glacier tier sizing run this conversion in their data-management plans submitted alongside grant applications, and again at every quarterly archive-tier review when older samples migrate to colder, cheaper storage classes.
Surveillance and CCTV footage retention compliance
Commercial surveillance systems retaining 30-90 days of multi-camera 1080p or 4K footage produce roughly 1-5 GB per camera per day, aggregating into 10-50 TB archives for typical retail or industrial installations across the retention window. Compliance auditors and IT integrators converting daily MB-throughput figures against monthly and annual TB-storage budgets use the MB-to-TB conversion in spec'ing NVR and video-management-system storage hardware against contractual retention windows, with municipal regulations in many jurisdictions specifying minimum retention periods that drive the TB-tier sizing decision.
When to use Terabytes instead of Megabytes
Use terabytes when discussing drive capacities, NAS storage, cloud archive tiers, or any aggregate-storage figure where the MB scale would produce uncomfortably large numbers. Stay in megabytes when working at the per-file or per-folder granularity where individual file sizes are the relevant unit. The conversion is essential for forward-projection sizing: if you're accumulating GB-per-day or MB-per-hour, and you need to know how long a TB-tier drive will last, you need the MB-to-TB factor as a stepping stone. The choice between MB and TB is a granularity question, not a correctness question — both describe the same physical storage at different scales, and the right scale is the one that produces the most legible figure for the audience and decision context at hand.
Common mistakes converting MB to TB
- Confusing TB with TiB. A "4 TB" external drive in decimal SI holds 4,000,000 MB; the same drive labelled in binary IEC reads as 3.64 TiB or 3,725,290 MiB. The 9% gap between TB and TiB compounds across multiple conversion steps and shows up dramatically in backup-storage projections that span the prefix.
- Multiplying by 1,000,000 instead of 0.000001 in the wrong direction. The factor 1,000,000 applies in the inverse direction (TB to MB). Going from MB to TB always uses the small ×0.000001 multiplier — the result should be a small number, not a six-orders-of-magnitude larger one. The error usually surfaces immediately because the wrong direction produces nonsensical magnitudes.
Frequently asked questions
How many MB in 1 TB?
1 TB equals 1,000,000 MB in decimal SI, the convention used by storage vendors and cloud-platform billing. In binary IEC, 1 TiB equals 1,048,576 MiB, but vendors don't sell in TiB so the decimal figure applies for any commercial-storage calculation. The clean six-order-of-magnitude relationship is what makes the prefix arithmetic intuitive in decimal SI.
Will my MB-scale files ever fill a TB drive?
Yes, given enough time and accumulation. Photos and videos at MB-scale individually accumulate into GB-scale folders over months and TB-scale archives over years. A photographer shooting 50 GB of raw files per month fills a 1 TB drive in 20 months; a videographer at 200 GB per month fills it in 5 months. Drive purchases should account for accumulated multi-year throughput, not single-day consumption.
How does this conversion handle compressed vs uncompressed files?
Identically — the conversion is purely a unit relationship and doesn't depend on file content or compression ratio. A 500 MB compressed video and a 500 MB uncompressed Excel file both convert to 0.0005 TB. Compression affects how much physical content fits in a given MB count but doesn't change how MB convert to TB. For storage-budget planning, what matters is final on-disk size, regardless of how compression got it there.
Is this the same conversion for memory as for storage?
No. RAM and on-die memory are universally specified in binary IEC even when labelled "MB" or "TB," so 32 GB of RAM is actually 32 GiB = 34,359,738,368 bytes. Storage drives and cloud archives use decimal SI (32 GB = 32,000,000,000 bytes). The 0.000001 MB-to-TB factor applies to storage; for memory aggregation use the binary equivalent (1 / 1,048,576) instead.
How big is 1 TB in everyday terms?
1 TB holds about 250,000 standard-quality photos, 200,000 MP3 songs, 500 hours of HD video, 30 hours of 4K video, or 130 typical AAA games at modern install sizes. The figure is large enough that consumer drives at 1-2 TB rarely fill from any single use case — they fill instead from accumulating mixed media over years. Enterprise storage scales up from there into multi-TB and multi-petabyte territory.