Byte per second to Kibibit per second

Files are stored in bytes because CPUs address memory in byte-sized (8-bit) chunks — the smallest unit a program can read or write. Networks measure in bits because physical signals on a wire or fiber are serial: one bit at a time, clocked at a specific frequency. A 1 GHz signal produces 1 Gbps, not 1 GBps. The two worlds evolved independently and neither adopted the other's convention, leaving users to divide by 8 forever.

In modern computing, yes — a byte is universally 8 bits. Historically, some architectures used 6, 7, or 9-bit bytes, which is why the unambiguous term "octet" exists in networking standards. But for all practical bandwidth conversions today, 1 byte = 8 bits.

Network protocols add overhead — TCP headers, encryption (TLS), error correction, and packet framing all consume bandwidth without contributing to file data. A 100 Mbps connection might deliver 11 MB/s instead of the theoretical 12.5 MB/s because 10–15% goes to protocol overhead.

USB 3.0 has a theoretical maximum of 625 MB/s (5 Gbps ÷ 8), but real-world sustained transfers hit 300–400 MB/s due to protocol overhead and controller limitations. USB 3.2 Gen 2 doubles this to about 700–900 MB/s in practice.

The bit came first, coined by Claude Shannon in 1948. The byte was introduced at IBM in the mid-1950s by Werner Buchholz to describe the smallest addressable group of bits in the IBM Stretch computer. Originally it could be any size; the 8-bit byte became standard with the IBM System/360 in 1964.

Because "kilo" was used to mean both 1,000 and 1,024 depending on context, causing real confusion. RAM manufacturers used 1,024 (binary) while network engineers used 1,000 (decimal). The IEC created kibi (Ki) in 1998 to unambiguously mean 1,024, leaving kilo for exactly 1,000.

Very few people outside of standards bodies and kernel developers. Linux kernel networking code sometimes uses binary units internally, and some IEC-compliant technical documents use Kibps. But consumer networking has fully standardized on decimal kilobits (kbps), making kibibits a niche pedantic distinction.

At the kibi/kilo level, only 2.4%. But the gap compounds — mebi vs mega is 4.86%, gibi vs giga is 7.37%, and tebi vs tera is 9.95%. A "1 TB" hard drive holds only 931 GiB in binary terms, which is why your new drive looks smaller than advertised in Windows.

Hard drives are built from sectors of arbitrary size, so decimal marketing (1 TB = 1,000 GB) is natural and makes drives look bigger. RAM is addressed in powers of 2 because of how binary memory chips work, so binary units (GiB) reflect actual hardware architecture. Neither side wants to change.

Almost certainly not. Networking adopted decimal (×1000) from the beginning because serial link speeds are clock-derived and have nothing to do with powers of 2. Ethernet has always been 10/100/1000 Mbps. Binary prefixes solve a storage problem that networking never had.