| Gibioctets (Gio) | Kibioctets (Kio) |
|---|---|
| 1 Gibioctet | 1048576 Kio |
| 2 Gibioctets | 2097152 Kio |
| 3 Gibioctets | 3145728 Kio |
| 4 Gibioctets | 4194304 Kio |
| 5 Gibioctets | 5242880 Kio |
| 10 Gibioctets | 10485760 Kio |
| 20 Gibioctets | 20971520 Kio |
| 25 Gibioctets | 26214400 Kio |
| 50 Gibioctets | 52428800 Kio |
| 100 Gibioctets | 104857600 Kio |
| Reference | Gibioctets (Gio) | Kibioctets (Kio) |
|---|---|---|
| A plain text message (160 characters) | 0.000000149012 Gio | 0.15625 Kio |
| A three-minute MP3 | 0.00279397 Gio | 2929.69 Kio |
| A smartphone photo | 0.00372529 Gio | 3906.25 Kio |
| A high-definition film | 3.72529 Gio | 3906250 Kio |
| A dual-layer Blu-ray disc | 46.5661 Gio | 48828125 Kio |
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 kibioctet is a unit of digital information equal to 1,024 octets, and therefore to 8,192 bits. Its symbol is Kio. It is the binary counterpart of the kilooctet, and although the two differ by only 2.4 per cent, this is the unit in which a great deal of a computer's internal organisation is actually measured.
The most important example is the memory page. Processors do not manage memory octet by octet but in fixed-size blocks, and on almost every architecture in common use that block is 4 kibioctets. Every allocation a program makes is rounded up to a multiple of that, every entry in the page tables describes one of them, and the performance of a program often depends on how well its access pattern fits that four-kibioctet grid.
Disc sectors tell a similar story. Hard drives used 512-octet sectors for decades, and modern drives use 4 kibioctets, matching the memory page so that a page can be read or written in a single operation. Filesystems then allocate space in blocks that are themselves powers of two, usually 4 kibioctets, which is why a one-octet file consumes four kibioctets of disc.
Network protocols use the unit too. Buffer sizes, window sizes and the maximum size of many protocol structures are powers of two, and the 64-kibioctet limit appears repeatedly: it is the largest value a 16-bit length field can express, and it therefore caps the size of a UDP datagram, an IP packet and several older file formats.
That is the general pattern: wherever a limit comes from the width of a binary field, the limit is a power of two, and the honest way to write it is with a binary prefix. Writing 64 KB for the datagram limit is not wrong by much, but writing 64 KiB is exactly right and says where the number came from.
In everyday use the difference is invisible. A 200-kilooctet file and a 200-kibioctet file are 4.8 kibioctets apart, which nobody notices. The value of the distinction is that it makes the arithmetic behind a figure legible, which matters far more as the numbers grow.
One kibioctet equals 1,024 octets, 8,192 bits, 8 kibibits, or 1.024 kilooctets.