| Kilooctets per second (ko/s) | Kibioctets per second (Kio/s) |
|---|---|
| 1 Kilooctet per second | 0.9765625 Kio/s |
| 2 Kilooctets per second | 1.953125 Kio/s |
| 3 Kilooctets per second | 2.9296875 Kio/s |
| 4 Kilooctets per second | 3.90625 Kio/s |
| 5 Kilooctets per second | 4.8828125 Kio/s |
| 10 Kilooctets per second | 9.765625 Kio/s |
| 20 Kilooctets per second | 19.53125 Kio/s |
| 25 Kilooctets per second | 24.4140625 Kio/s |
| 50 Kilooctets per second | 48.828125 Kio/s |
| 100 Kilooctets per second | 97.65625 Kio/s |
| Reference | Kilooctets per second (ko/s) | Kibioctets per second (Kio/s) |
|---|---|---|
| A dial-up modem | 7 ko/s | 6.83594 Kio/s |
| Typical home broadband | 12500 ko/s | 12207 Kio/s |
| Gigabit Ethernet | 125000 ko/s | 122070 Kio/s |
| Streaming a 4K film | 3125 ko/s | 3051.76 Kio/s |
The kilooctet per second is a unit of data transfer rate equal to one thousand octets per second, and therefore to eight kilobits per second. Its symbol is ko/s. It is the unit in which file transfers were reported through the whole of the dial-up era, and it still appears whenever a transfer is slow enough to need it.
The conversion from advertised connection speeds is the reason it matters. A 56-kilobit modem delivered about 7 kilooctets per second in practice, and users learned the relationship by watching progress bars: a one-megaoctet file took about two and a half minutes. The habit of dividing the advertised number by eight and then subtracting a bit for overhead dates from that period.
Storage devices of the era were similar. A floppy disc drive read at roughly 30 to 60 kilooctets per second, a single-speed compact-disc drive at 150, and an early hard drive at a few hundred. Loading a program from any of them was a matter of seconds to minutes, and software was written with that expectation in mind.
The unit still appears in serial communication. The classic serial port ran at rates up to 115,200 bits per second, which is 14.4 kilooctets per second, and equivalent rates are still used to talk to microcontrollers, scientific instruments and industrial equipment. A protocol designed for such a link cannot assume that a large message will arrive quickly.
It also appears at the bottom end of modern networking. A congested mobile connection, a distant satellite link or a heavily shared wireless network can fall to a few tens of kilooctets per second, and at that rate an ordinary web page — which now runs to a few megaoctets — takes a minute or more to load. The unit is a reminder of what the network assumes about its users.
For scale, one kilooctet per second moves a thousand characters of plain text each second, so a short letter transfers in a second and a novel in about ten minutes. Nothing about text has ever needed more than this; every increase in transfer rate since has been consumed by images, sound and video.
One kilooctet per second equals 1,000 octets per second, 8 kilobits per second, or about 0.9766 kibioctets per second.
The kibioctet per second is a unit of data transfer rate equal to 1,024 octets per second, and therefore to 8,192 bits per second. Its symbol is Kio/s. Unlike most of the binary rate units it is genuinely common, because the command-line tools that copy, download and synchronise files have reported in it for decades.
The reason is straightforward. Those tools count what they have moved in blocks, and blocks are powers of two. A program that reads in four-kibioctet pieces and divides the total by elapsed time produces a rate in kibioctets per second, and reporting it in decimal kilooctets would require an extra multiplication for no benefit. The unit is what the arithmetic naturally produces.
Anyone who has watched a file copy on a Unix-like system has seen the figure. Download utilities, archive tools, disc-writing commands and network file transfer programs all report progress in kibioctets or mebioctets per second, and most of them label it correctly with the lowercase i. It is one of the few places where the IEC prefixes are used consistently in everyday software.
For scale, a kibioctet per second moves about a thousand characters of text each second: a short letter in a second, a novel in about ten minutes. It is a rate at which a modern web page will not load in any reasonable time, so seeing it in a progress display usually means something has gone wrong with the connection rather than that the transfer is nearly finished.
The difference from a kilooctet per second is 2.4 per cent, which nobody notices. The value of using the binary unit here is not accuracy but honesty: the number came from a binary computation, and writing it with a binary prefix says so. A reader who wants the decimal figure can convert; a reader given a decimal label for a binary number cannot recover anything.
Comparing the reading with an advertised connection speed requires two steps: multiply by eight to get bits, and adjust by 2.4 per cent for the base. In practice the second step is beneath the noise of any real measurement, and the first is the one that matters.
One kibioctet per second equals 1,024 octets per second, 8,192 bits per second, or 1.024 kilooctets per second.