Megabyte per second to Kibibyte per second

Many USB drives use a small SLC cache for initial writes at high MB/s, then slow dramatically once the cache fills and data writes to slower TLC/QLC NAND. A drive that starts at 200 MB/s might drop to 20–30 MB/s after the first few gigabytes. Check sustained write speed reviews, not just peak numbers.

Editing 4K ProRes footage requires about 200–400 MB/s of sustained read speed. 8K RAW can demand 1,000+ MB/s. A SATA SSD (550 MB/s) handles 4K fine, but 8K workflows really need NVMe drives at 3,000+ MB/s. The timeline scrubbing experience directly correlates with MB/s.

Look at the capitalisation: lowercase "b" (Mbps) means megabits, uppercase "B" (MB/s) means megabytes. Most speed test websites (Speedtest by Ookla, fast.com) default to Mbps. If your result seems 8× lower than expected, you are probably reading MB/s where you expected Mbps.

PCIe 5.0 NVMe SSDs hit 12,000–14,000 MB/s sequential read speeds. That is fast enough to load an entire 50 GB game in about 4 seconds. PCIe 6.0 drives, expected soon, will double this again to roughly 25,000 MB/s.

Network transfers add latency, protocol overhead (SMB, NFS), and are limited by the network link speed. A file on a local NVMe SSD reads at 7,000 MB/s, but sharing it over a 1 Gbps network caps throughput at 125 MB/s. Even 10 GbE only gives 1,250 MB/s — a fraction of modern SSD capability.

Rsync follows IEC binary conventions because it deals with file sizes that are measured in binary units by the filesystem. Since files occupy whole filesystem blocks (typically 4 KiB), reporting transfer speed in KiB/s makes the math consistent with actual data moved on disk.

1 KiB/s (1,024 bytes/second) is 2.4% faster than 1 kB/s (1,000 bytes/second). The difference is tiny at this scale but matters when you are designing buffer sizes for embedded systems where every byte of RAM counts.

Microsoft started using binary units more consistently in Windows 10 after years of ambiguity where "KB" sometimes meant 1,000 and sometimes 1,024 bytes. The shift toward KiB follows IEC recommendations and reduces confusion, though the transition is still incomplete across all Windows tools.

A 3.5-inch floppy drive transferred data at about 31–62 KiB/s (250–500 kbps). Copying a full 1.44 MB floppy took roughly 25–50 seconds. For comparison, a modern NVMe SSD is about 100,000 times faster.

In embedded systems with tight memory constraints, confusing 1,024 with 1,000 can overflow a buffer. In network protocols, a spec written in KiB/s being implemented as kB/s means transmitting 2.4% less data than expected per second — enough to cause timing violations in real-time systems.