| Gigaoctets (Go) | Kibibits (Kibit) |
|---|---|
| 1 Gigaoctet | 7812500 Kibit |
| 2 Gigaoctets | 15625000 Kibit |
| 3 Gigaoctets | 23437500 Kibit |
| 4 Gigaoctets | 31250000 Kibit |
| 5 Gigaoctets | 39062500 Kibit |
| 10 Gigaoctets | 78125000 Kibit |
| 20 Gigaoctets | 156250000 Kibit |
| 25 Gigaoctets | 195312500 Kibit |
| 50 Gigaoctets | 390625000 Kibit |
| 100 Gigaoctets | 781250000 Kibit |
| Reference | Gigaoctets (Go) | Kibibits (Kibit) |
|---|---|---|
| A plain text message (160 characters) | 0.00000016 Go | 1.25 Kibit |
| A three-minute MP3 | 0.003 Go | 23437.5 Kibit |
| A smartphone photo | 0.004 Go | 31250 Kibit |
| A high-definition film | 4 Go | 31250000 Kibit |
| A dual-layer Blu-ray disc | 50 Go | 390625000 Kibit |
The gigaoctet is a unit of digital information equal to one thousand million octets, or eight gigabits. Its symbol is Go. It is the unit in which most things people actually buy are sized: the memory in a computer, the storage in a phone, the monthly allowance on a mobile contract.
The reference points are familiar. A DVD holds 4.7 gigaoctets and a dual-layer disc 8.5. A Blu-ray holds 25 or 50. A feature film in high definition is 4 to 15 gigaoctets depending on compression, and in ultra-high definition 40 or more. A phone with 128 gigaoctets of storage holds roughly thirty thousand photographs, or a few hundred hours of music.
Memory sizes now sit in this range and are stated in gibioctets even when written as gigaoctets. A module labelled 8 GB holds 8 gibioctets, which is 8.59 gigaoctets, because memory addressing is binary and always has been. The same is true of processor caches and of the page tables that map memory, so anything on the memory side of a computer is binary while anything on the storage side is decimal.
That split is the source of the most familiar consumer complaint about units. A hard drive sold as one teraoctet holds a million million octets, which the operating system divides by 1,024 three times and reports as 931 gigaoctets. Nothing has been lost; the drive holds exactly what the box says, but the two are counting in different bases. Lawsuits over this were settled in the manufacturers' favour, since the decimal usage matches the metric system.
Mobile data allowances made the gigaoctet a household figure. A few gigaoctets a month was generous around 2012 and is now minimal, because video dominates: an hour of standard-definition streaming is about 0.7 gigaoctets, an hour in high definition around 3, and an hour in ultra-high definition 7 or more.
For scale in text, a gigaoctet holds around a thousand full-length books as plain text, or the complete works of most authors many times over. Digital storage stopped being a constraint on text decades ago, and every capacity discussion since has really been about images, sound and video.
One gigaoctet equals 1,000,000,000 octets, 1,000 megaoctets, 8 gigabits, or about 0.9313 gibioctets.
The kibibit is a unit of digital information equal to 1,024 bits. Its symbol is Kibit. It is the first of the binary prefixes, a set of units defined by the International Electrotechnical Commission in 1998 to end a confusion that had run through computing since the 1960s.
The problem was straightforward. Computers address memory in powers of two, so memory came in chunks of 1,024 rather than 1,000. Engineers borrowed the metric prefix kilo for that quantity because 1,024 is close to 1,000, and for small numbers the approximation was harmless. But storage and transmission counted in true thousands, so the same prefix meant two different things depending on which part of the machine was being described.
The IEC's solution was to coin new names. Kibi is a contraction of kilo binary, and the pattern continues with mebi, gibi, tebi, pebi, exbi, zebi and yobi. Each is 1,024 times the one below, and each symbol takes the form of a capital letter followed by a lowercase i: Ki, Mi, Gi, Ti and so on. The kilobit then means one thousand bits and nothing else.
A kibibit is 128 octets, and the gap from a kilobit is 2.4 per cent. That small difference is why the two were confused for so long: at this scale nobody notices. The error compounds by 2.4 per cent at every step, reaching 5 per cent at the mebibit, 7 per cent at the gibibit and 21 per cent by the yobibit, which is where the ambiguity became genuinely expensive.
Adoption has been partial and uneven. Standards bodies, the Linux kernel and most technical documentation use the IEC prefixes correctly. Consumer software largely does not, and many programs still write KB while dividing by 1,024. The result is that a reader must often infer from context which convention a number follows, which is exactly what the standard was written to prevent.
In practice the kibibit itself appears mainly in the specifications of small memory chips, in serial memory used by embedded systems, and in protocol documents where an exact power of two matters. Anywhere the number 1,024 is meant rather than 1,000, this is the correct unit.
One kibibit equals 1,024 bits, 128 octets, or 1.024 kilobits.