Petabyte to Mebibyte

1 petabyte (PB) = 1,000 terabytes (TB) in the SI decimal system. In the binary IEC system, 1 pebibyte (PiB) = 1,024 tebibytes (TiB) = 1,125,899,906,842,624 bytes. The distinction matters for enterprise storage procurement: a petabyte of raw disk capacity appears as about 909 TiB in an OS reporting binary units.

Petabyte-scale storage is common at: social media platforms (Facebook/Meta stores over 100 PB of photos alone), streaming services (Netflix's content library is estimated at 100+ PB), government agencies (US NSA, CERN particle physics data), genomic research institutions, and large financial exchanges storing tick-level trading data. Major cloud providers (AWS, Azure, GCP) collectively store zettabytes.

In 2024, cloud storage costs roughly $20–25 per TB per month (S3 standard tier), making 1 PB approximately $20,000–$25,000/month. Raw enterprise disk hardware for 1 PB runs about $20,000–$50,000 upfront (at $20–50 per TB for high-density drives), plus ongoing power, cooling, and management overhead. Tape-based archival storage is considerably cheaper at $2–5 per TB.

YouTube users upload approximately 500 hours of video per minute, or 720,000 hours per day. At an average compressed size of 1–2 GB per hour of HD video, that equates to roughly 720–1,440 TB (0.7–1.4 PB) of new video data per day — before YouTube re-encodes into multiple formats and quality levels, which multiplies storage requirements several-fold.

The SI prefix hierarchy above petabyte: exabyte (EB, 10¹⁸ bytes), zettabyte (ZB, 10²¹ bytes), yottabyte (YB, 10²⁴ bytes), ronnabyte (RB, 10²⁷ bytes), and quettabyte (QB, 10³⁰ bytes) — the last two added by the BIPM in 2022. Current global data storage is estimated in the hundreds of exabytes; no single organisation approaches yottabyte scale.

MB (megabyte) = 1,000,000 bytes (SI decimal). MiB (mebibyte) = 1,048,576 bytes (IEC binary). MiB is 4.86% larger. This gap is why a file manager on Linux showing "512 MiB" of free RAM and a marketing sheet showing "512 MB" of RAM are technically different: the marketing sheet refers to fewer bytes.

The original CD-ROM standard defined capacity as 74 minutes of audio or 650,000,000 bytes. Technically this is 650 MB in SI terms, or approximately 620 MiB (since 650,000,000 ÷ 1,048,576 ≈ 620). However, the CD industry loosely used "MB" to mean 650 × 10⁶ bytes. Some media used 700 MB (≈ 668 MiB). This inconsistency is a classic example of the pre-IEC ambiguity.

Docker reports image sizes in decimal MB (e.g., "docker images" shows 150 MB), but the underlying layer storage on disk uses binary-aligned block sizes. A "150 MB" Docker image actually occupies roughly 143 MiB on disk before compression. Compressed layers further complicate things: a 150 MB uncompressed image might only transfer 50 MB over the network. Container registries like Docker Hub display compressed sizes, while "docker images" shows uncompressed — leading to frequent confusion in CI/CD pipeline size budgets.

One mebibyte (1,048,576 bytes) holds about: one minute of MP3 audio at 128 kbps (≈ 960 kB, so slightly under 1 MiB), a medium-resolution JPEG photo (0.5–2 MiB), about 200 pages of plain text, or the complete text of a short novel. A typical Linux kernel image at boot is 8–12 MiB compressed.

RAM chips are physically organized as binary address grids — each address line doubles the capacity, so sizes must be exact powers of 2 (4 GiB = 2³² bytes, 8 GiB = 2³³ bytes). USB flash drives use NAND flash that is also binary internally, but manufacturers reserve variable amounts for wear levelling, bad block management, and controller firmware. A "64 GB" USB drive might have 64 GiB of raw NAND but only expose 59.6 GiB (64 × 10⁹ ÷ 2³⁰) to the user — the label uses decimal marketing, unlike RAM which honestly reflects binary sizing.