Gibibyte to Megabyte

GB (gigabyte) = 10⁹ bytes = 1,000,000,000 bytes (SI decimal). GiB (gibibyte) = 2³⁰ bytes = 1,073,741,824 bytes (IEC binary). GiB is 7.37% larger. This is why a 1 TB hard drive labelled by the manufacturer (using 10¹² bytes) appears as approximately 931 GiB in Windows or Linux (which divide by 1,073,741,824). Neither value is wrong; they use different counting systems.

Early PC games (1990s) fit on a few floppy disks — under 10 MiB. CD-era games (late 1990s) reached 650 MiB. DVD-era titles hit 4–8 GiB. Modern AAA games like Call of Duty or Flight Simulator now exceed 100–200 GiB due to uncompressed 4K textures, high-fidelity audio in multiple languages, and pre-rendered cinematics. The growth rate has outpaced Moore's Law: storage needs roughly double every 2–3 years for top-tier games, driven primarily by texture resolution increases that scale quadratically with pixel count.

A module sold as "16 GB" RAM by manufacturers means 16 × 10⁹ = 16,000,000,000 bytes? No — RAM is actually built in binary powers. A "16 GB" RAM module contains exactly 2³⁴ = 17,179,869,184 bytes = 16 GiB. In this case, the manufacturer is using "GB" to mean GiB — unlike hard drives, where manufacturers genuinely use decimal GB. RAM capacities are always powers of 2 in gibibytes.

A 512 GB SSD (decimal, as labelled by the manufacturer) holds 512,000,000,000 bytes. Divide by 1,073,741,824 to get GiB: 512,000,000,000 ÷ 1,073,741,824 ≈ 476.8 GiB. After OS overhead and firmware reserved space, the usable capacity shown in the OS is typically 450–465 GiB for a nominally 512 GB drive.

Yes — GiB is the technically correct unit for binary memory. RAM, CPU cache, and GPU memory are all physically organized in powers of 2, making GiB the natural unit. The JEDEC memory standard (the body that defines RAM specifications) officially uses the IEC GiB notation, even though product packaging often says "GB" for commercial reasons. In engineering and OS development contexts, GiB is the preferred term.

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.