| Gibioctets (Gio) | Kilooctets (ko) |
|---|---|
| 1 Gibioctet | 1073741.824 ko |
| 2 Gibioctets | 2147483.648 ko |
| 3 Gibioctets | 3221225.472 ko |
| 4 Gibioctets | 4294967.296 ko |
| 5 Gibioctets | 5368709.12 ko |
| 10 Gibioctets | 10737418.24 ko |
| 20 Gibioctets | 21474836.48 ko |
| 25 Gibioctets | 26843545.6 ko |
| 50 Gibioctets | 53687091.2 ko |
| 100 Gibioctets | 107374182.4 ko |
| Reference | Gibioctets (Gio) | Kilooctets (ko) |
|---|---|---|
| A plain text message (160 characters) | 0.000000149012 Gio | 0.16 ko |
| A three-minute MP3 | 0.00279397 Gio | 3000 ko |
| A smartphone photo | 0.00372529 Gio | 4000 ko |
| A high-definition film | 3.72529 Gio | 4000000 ko |
| A dual-layer Blu-ray disc | 46.5661 Gio | 50000000 ko |
The gibioctet is a unit of digital information equal to 1,073,741,824 octets, which is 1,024 mebioctets. Its symbol is Gio. It is the binary counterpart of the gigaoctet, and the 7.4 per cent difference between them is the single most common cause of confusion about data units.
This is the unit in which computer memory is actually sold, whatever the packaging says. A module labelled 8 GB holds 8 gibioctets, which is 8.59 gigaoctets. It could not hold anything else: memory addressing is binary, and a module with a decimal capacity would leave part of its address range unpopulated. The label is a convenient shorthand rather than a measurement.
Storage, by contrast, is genuinely decimal. A drive sold as 500 gigaoctets holds five hundred thousand million octets, and the operating system divides that by 1,024 three times and reports 465.7 gibioctets. The two figures describe the same hardware. Neither party is being dishonest; they are simply counting in different bases, and the labelling convention differs by industry.
Cloud computing has made the distinction visible in contracts. Virtual machine sizes, container memory limits and the parameters that control how much memory a program may use are all specified in gibioctets, because they map onto real memory pages. A limit of 4 GB set in a decimal-minded tool and 4 GiB set in a binary one differ by nearly three hundred megaoctets, which is enough to change whether a program runs.
For everyday scale, a gibioctet holds about a thousand books as plain text, a few hundred photographs, or twenty minutes of high-definition video. It is roughly what a modern web browser occupies in memory with a dozen pages open, which is a fair illustration of how the standard for what counts as a small amount has moved.
The correct symbol is Gio, and it appears in system tools, in virtualisation documentation and in standards. Where a document writes GB for memory, the safe reading is gibioctets; where it writes GB for a disc or a network, the safe reading is gigaoctets. The habit of checking which is meant costs a second and prevents a seven per cent error.
One gibioctet equals 1,073,741,824 octets, 1,024 mebioctets, 8 gibibits, or about 1.074 gigaoctets.
The kilooctet is a unit of digital information equal to one thousand octets, and therefore to eight thousand bits. Its symbol is ko. It is the smallest of the everyday storage units, and for two decades it was the unit in which the whole capacity of a computer was described.
A kilooctet holds a thousand characters of unaccented text, which is about two hundred words, or a third of a page. The plain-text file of a short letter is a few kilooctets. Almost nothing else in modern computing is this small: an empty document from a word processor is already tens of kilooctets, because the file format carries formatting, fonts and metadata around the text.
The historical importance of the unit is hard to overstate. The Apple II shipped with 4 kilooctets of memory, the Commodore 64 was named for its 64, and the first IBM personal computer could address 640. Programs of real complexity — spreadsheets, word processors, games with graphics and sound — were written to fit inside those numbers, which required a discipline that has largely disappeared.
The kilooctet is also where the decimal and binary confusion began. Memory came in 1,024-octet units because addressing is binary, and everyone called that a kilooctet. Disc manufacturers counted in true thousands. The two conventions differ by 2.4 per cent, which was negligible at this scale, but the same error compounds at each step upward and reaches 10 per cent by the teraoctet.
The IEC resolved the ambiguity in 1998 by defining the kibioctet as 1,024 octets and leaving the kilooctet at exactly 1,000. Operating systems have adopted this unevenly: some report file sizes in true kilooctets, others still divide by 1,024 while writing ko, and a few now write Kio correctly.
Where the unit still appears daily is in network protocols and in the sizes of small resources on the web. A web page's stylesheet, an icon, a certificate, a configuration file, a database index page — all of these are measured in kilooctets, and the standard memory page on most processors is 4 kibioctets, close enough to 4 kilooctets for casual conversation but not for arithmetic.
One kilooctet equals 1,000 octets, 8,000 bits, 8 kilobits, or about 0.9766 kibioctets.