The unit that refuses to die
By every measure of technological progress, Kbps should be obsolete. Consumer broadband starts at 50 Mbps and goes to 10,000 Mbps. A single 4K video stream outruns an entire T3 line. And yet — open any audio encoding settings panel, any IoT module datasheet, any satellite modem spec — and there it is: Kbps. Still alive. Still the right prefix for the job.
The reason is that the physical world has a floor. A low-power radio transmitter on a battery sending temperature data twice an hour doesn't need a megabit. It needs maybe 50 Kbps. Express that as 0.05 Mbps and you've made the number harder to scan while adding exactly zero information. The kilobit persists because it matches the natural scale of things that are power-constrained, range-constrained, or cost-constrained — which describes most of the hundred billion devices that will be online by 2030. The consumer web upgraded to Mbps and Gbps. The physical world stayed in Kbps, and the two meet in the aggregation layer.
What still runs at Kbps — and why
| Technology | Typical bitrate | In Mbps | Why it hasn't upgraded |
|---|---|---|---|
| G.711 VoIP call | 64 Kbps | 0.064 Mbps | Standardized in 1972. Still the PSTN baseline. Good enough for voice. |
| Zigbee (802.15.4) | 250 Kbps | 0.25 Mbps | Designed for battery-powered sensors. Speed costs power. |
| LoRaWAN | 0.3–50 Kbps | 0.0003–0.05 Mbps | Range trumps speed. A 50 Kbps LoRa link reaches 15 km. |
| T1 (DS1) circuit | 1,544 Kbps | 1.544 Mbps | Still in service for PBX voice trunks and rural backhaul. |
| Bluetooth LE Audio (LC3) | 160–345 Kbps | 0.16–0.345 Mbps | Excellent quality at a fraction of classic Bluetooth power. |
| GPS L1 C/A signal | 50 bps (0.05 Kbps) | 0.00005 Mbps | Navigates the world on a data rate slower than 1960s teletype. |
The GPS row is the one to stare at. The entire global navigation system — every plane landing, every ship docking, every Uber finding your street — runs on a signal that transmits 50 bits per second. Not kilobits. Bits. 0.05 Kbps. 0.00005 Mbps. The fact that any of these numbers can describe the same physical world is the whole argument for keeping both prefixes around.
Aggregation: when a thousand kilobits become a megabit
The only time Kbps-to-Mbps becomes a calculation you actually perform is aggregation. One Zigbee sensor at 250 Kbps is 0.25 Mbps — a rounding error on a gigabit network. A thousand of them is 250 Mbps — a quarter of a gigabit pipe. A smart building with 10,000 sensors, each chirping 10 Kbps of telemetry, generates 100 Mbps of aggregate traffic. The conversion is just ÷1,000 per sensor. The insight is what happens when you stop thinking about devices one at a time.
VoIP capacity planning. A G.711 call = 64 Kbps. A 100 Mbps WAN link with 20% reserved for voice has 20 Mbps = 20,000 Kbps for calls. 20,000 ÷ 64 = 312 simultaneous calls. Do this math in Kbps (where the call is 64 and the pipe is 100,000) and the units cancel cleanly. Mix Mbps and Kbps and the decimal point moves three places — the error that accidentally provisions bandwidth for a call center of 300 with capacity for 0.3.
Streaming server egress. An Icecast server streams 128 Kbps MP3 to 500 listeners. 128 × 500 = 64,000 Kbps = 64 Mbps of sustained egress. The colocation provider charges by Mbps (95th percentile billing). Expressing the stream in Kbps and the bill in Mbps is how you estimate cost: cross-multiply early, avoid unit-surprise in the invoice.
Fleet telemetry backhaul. A shipping company tracks 5,000 containers, each sending a 2 Kbps GPS/heartbeat message. Aggregate: 10,000 Kbps = 10 Mbps. The satellite backhaul is a 20 Mbps link. Without the Kbps-to-Mbps step, "2 Kbps × 5,000 = 10,000 Kbps" looks like a scary number, and the engineer might over-provision. Convert to 10 Mbps and it's clear: the link is half empty.
Frequently asked questions
Is the Kbps-to-Mbps conversion always ÷1,000?
Yes. Always. Networking uses decimal SI prefixes — kilo = 1,000, mega = 1,000,000. There is no 1,024 in bandwidth. The binary prefix debate (kilobyte vs kibibyte) is a storage problem, not a networking one. Apply ÷1,024 here and you're solving the wrong problem with the wrong factor.
If Kbps is obsolete for broadband, why learn this conversion?
Because the devices that will dominate the next decade of networking — sensors, trackers, wearables, embedded controllers — all live in Kbps. The skill isn't converting your home internet speed. It's aggregating a million low-bitrate devices into a coherent network plan without a decimal-point mistake.
What's the difference between Kbps and KB/s?
Factor of 8. Kbps = kilobits per second. KB/s = kilobytes per second. 1 KB/s = 8 Kbps. A file transfer at 100 KB/s uses 800 Kbps of bandwidth. ISPs sell in bits (Kbps/Mbps/Gbps); file managers display in bytes (KB/s, MB/s). The mismatch is the most persistent source of consumer confusion about internet speed, and it's why a 100 Mbps plan downloads at ~12.5 MB/s, not 100 MB/s.
Engineering Context
Kbps-to-Mbps is pure decimal: ÷1,000. The real risk isn't the math — it's mixing prefixes in the same calculation. An engineer who writes "200 Kbps + 2 Mbps = ?" without first converting has a 50% chance of being off by 10× depending on which prefix they normalize to. Standardize everything to the same prefix before doing arithmetic. In capacity planning, express the device in its native prefix and the aggregate in the prefix of the pipe; convert between them only in the final step. Reverse: Mbps to Kbps. Adjacent: Mbps to Gbps, KB to MB. Full reference: Data Storage Guide.