Megabyte to Terabit

A JPEG photo from a modern smartphone is typically 3–8 MB depending on resolution and compression settings. A RAW format photo from a DSLR or mirrorless camera is 20–50 MB per shot. A PNG screenshot at full HD (1920×1080) is about 1–3 MB; a compressed JPEG screenshot may be under 200 kB.

Video data usage depends heavily on quality: SD video uses roughly 700 MB per hour; HD (1080p) uses 1.5–3 GB per hour; 4K uses 7–20 GB per hour. These are byte-based measurements. In terms of bitrate: SD ≈ 1.5 Mbps, HD ≈ 5–8 Mbps, 4K ≈ 15–25 Mbps — where the "b" is bits, requiring division by 8 to convert to MB/s.

Compression algorithms like ZIP, GZIP, and ZSTD find and eliminate redundancy in data. Typical ratios vary dramatically by file type: plain text compresses to 20–30% of original size (a 10 MB log file becomes 2–3 MB); source code compresses to 25–35%; office documents (DOCX, XLSX) are already ZIP-compressed internally, so re-compressing gains little. JPEG, MP3, and H.264 video are already lossy-compressed and typically shrink by less than 5% with ZIP. A 100 MB folder of mixed files typically compresses to 40–60 MB. The key principle: compression removes statistical redundancy, so already-compressed or random data cannot be reduced further.

MB (megabyte) = 1,000,000 bytes (SI decimal). MiB (mebibyte) = 1,048,576 bytes (IEC binary). The difference is about 4.9%. Windows historically displayed storage in binary units but labelled them as "MB" — confusingly. Since Windows Vista, Microsoft has used the binary calculation consistently. macOS switched to SI decimal units in OS X 10.6 Snow Leopard (2009), matching the way hard drive manufacturers measure capacity.

Approximate data consumption per hour: web browsing = 60–100 MB, social media scrolling = 100–300 MB, music streaming (Spotify standard) = 40–50 MB, video calls (Zoom standard quality) = 300–500 MB, YouTube HD = 1,500–3,000 MB. These are rough averages and vary by content, settings, and network conditions.

One terabit per second (Tbps) equals 125 gigabytes per second — enough to transfer the entire contents of a 1 TB hard drive in about 8 seconds. At this speed, you could download the entire Netflix library (estimated at around 100 petabytes) in roughly 800,000 seconds, or about 9 days.

Submarine fiber optic cables (such as the transatlantic cables connecting Europe and the Americas), long-haul terrestrial fiber routes, and the internal switching fabric of the largest hyperscale cloud data centers (Google, Amazon, Microsoft) operate at terabit and multi-terabit speeds. These use wavelength-division multiplexing (WDM) to carry many 100 Gbps or 400 Gbps channels on a single fiber.

Not in the foreseeable future for a single household connection. Current consumer endpoints (laptops, phones, TVs) cannot process or use data at terabit speeds — Wi-Fi 7 tops out around 46 Gbps theoretically. Terabit access would require new hardware at every endpoint. The practical benefit would be minimal since content servers themselves are not yet able to deliver at terabit rates to a single user.

Global internet traffic is measured in exabytes per month. Estimates suggest the internet backbone carries over 1,000 Tbps (1 Pbps) in aggregate during peak hours. Major internet exchange points (IXPs) like DE-CIX in Frankfurt regularly see peak traffic above 10 Tbps, and the largest cloud providers' internal networks operate at multi-petabit scales.

Current 5G mmWave cells can deliver up to 10–20 Gbps aggregate capacity shared among users in a sector. Industry roadmaps for 6G (targeted around 2030) aim for 1 Tbps aggregate throughput per cell site using sub-terahertz frequencies (100–300 GHz), massive MIMO antenna arrays, and intelligent reflecting surfaces. Achieving terabit wireless capacity requires extremely dense small-cell deployments — potentially one access point every 50–100 meters in urban areas.