Terabyte to Mebibit

1 terabyte (TB) = 1,000 gigabytes (GB) in the SI decimal system. In the binary IEC system, 1 tebibyte (TiB) = 1,024 gibibytes (GiB). Consumer hard drives and SSDs are labelled in decimal TB; operating systems may display available space in either GB or GiB depending on the OS and version, leading to a discrepancy of up to ~7% between the label and the OS display.

A 1 TB SSD holds approximately: 200,000 JPEG photos (at 5 MB each), 250 HD movies (at 4 GB each), 200+ modern AAA games (at 50 GB average), or enough for about 100 hours of 4K video footage from a modern camera. In practice, the OS and drive firmware overhead reduce usable capacity to roughly 900–930 GB as reported by the operating system.

A terabyte (TB) = 10¹² bytes = 1,000,000,000,000 bytes. A tebibyte (TiB) = 2⁴⁰ bytes = 1,099,511,627,776 bytes. The TiB is about 9.95% larger. This gap is why a 1 TB hard drive appears as 931 GiB (≈ 0.909 TiB) in Windows. The IEC formally defined TiB in 1998 to eliminate this naming ambiguity.

Timeline depends heavily on use case: continuous 4K video recording fills 1 TB in about 2–3 hours (at 1 GB/min). Typical laptop use (documents, photos, apps) might take 3–5 years to fill 1 TB. A game library of 20 modern AAA titles uses 500 GB–1 TB. Home security camera systems recording 24/7 at 1080p use about 1 TB every 10–15 days per camera.

For most individuals, 1 TB of cloud storage is generous: it holds 200,000+ photos, years of documents, and even video libraries. Google One offers 2 TB for €9.99/month; iCloud offers 2 TB for £6.99/month. Power users — especially photographers and videographers — may need 2–5 TB. Family sharing plans can make 2 TB cost-effective across multiple users.

A megabit (Mb) = 1,000,000 bits (SI decimal). A mebibit (Mibit) = 1,048,576 bits (IEC binary = 2²⁰ bits). The mebibit is 4.857% larger. Network speeds use megabits (Mb); embedded memory and flash storage specifications use mebibits when binary precision is required.

Mebibit appears primarily in microcontroller and microprocessor datasheets (e.g. "2 Mibit flash memory"), FPGA configuration file sizes, and some wireless protocol standards (802.11 frame size limits, Bluetooth payload specifications). It is rarely seen in consumer-facing applications but is common in embedded systems engineering documentation.

Yes. In 2007, a class-action settlement required Western Digital to pay $2.1 million because their hard drives advertised capacity in decimal megabits/gigabits while operating systems reported binary values — making drives appear ~7% smaller than labeled. Similar suits hit Seagate and Samsung. These lawsuits accelerated industry adoption of IEC prefixes and pushed Apple (2009) and later Windows (2021) to clarify their capacity labeling.

SPI flash chips are addressed at the bit level during serial communication — the programr shifts data in one bit at a time over the SPI bus. Datasheets specify capacity in mebibits (e.g. W25Q16 = 16 Mibit = 2 MiB) because the serial interface operates on bits, not bytes. Calculating transfer time requires bit-level math: reading a full 16 Mibit chip at 80 MHz SPI clock takes about 0.2 seconds.

Flash memory chips organise storage in binary-aligned blocks (sectors, pages) whose sizes are powers of 2. Specifying capacity in mebibits (1,048,576 bits per Mibit) maps precisely to the physical organisation of the memory array. Using decimal megabits would result in non-integer block counts, making datasheet specifications harder to verify against hardware design.