Kilobyte per second to Kibibyte per second

A typical 4 MB MP3 file at 7 kB/s took about 9–10 minutes to download. Napster users in 1999 would queue up songs before bed and hope the phone line stayed connected overnight. A single disconnection meant starting over from scratch.

Lowercase "k" with uppercase "B" (kB/s) means 1,000 bytes per second (SI decimal). Uppercase "K" with uppercase "B" (KB/s) traditionally meant 1,024 bytes per second (binary). In practice, most software uses them interchangeably, and the difference is only 2.4%.

Apps display kB/s when transfer speeds are genuinely that slow — downloading over congested mobile networks, tethering in rural areas, or transferring tiny files where the connection never ramps up. It is also common in SSH/SCP transfers that display instantaneous speed during small file copies.

The first consumer ADSL plans offered 256 kbps downstream, delivering about 32 kB/s — roughly 4.5× faster than a 56k modem. A 512 kbps plan gave 64 kB/s. That first jump from 7 to 32 kB/s felt revolutionary, cutting a 10-minute download to about 2 minutes.

An SMS is limited to 140 bytes (160 characters in GSM-7 encoding), and the signalling channel transmits it almost instantly. But if you think of SMS throughput over a sustained period, the practical rate is about 0.1–0.5 kB/s because of the overhead between messages.

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.