| Megaoctets (Mo) | Petaoctets (Po) |
|---|---|
| 1 Megaoctet | 0.000000001 Po |
| 2 Megaoctets | 0.000000002 Po |
| 3 Megaoctets | 0.000000003 Po |
| 4 Megaoctets | 0.000000004 Po |
| 5 Megaoctets | 0.000000005 Po |
| 10 Megaoctets | 0.00000001 Po |
| 20 Megaoctets | 0.00000002 Po |
| 25 Megaoctets | 0.000000025 Po |
| 50 Megaoctets | 0.00000005 Po |
| 100 Megaoctets | 0.0000001 Po |
| Reference | Megaoctets (Mo) | Petaoctets (Po) |
|---|---|---|
| A plain text message (160 characters) | 0.00016 Mo | 1.6 × 10-13 Po |
| A three-minute MP3 | 3 Mo | 0.000000003 Po |
| A smartphone photo | 4 Mo | 0.000000004 Po |
| A high-definition film | 4000 Mo | 0.000004 Po |
| A dual-layer Blu-ray disc | 50000 Mo | 0.00005 Po |
The megaoctet is a unit of digital information equal to one million octets, or eight million bits. Its symbol is Mo. It is the unit of the individual file: a photograph, a song, a document, an application download are all sized in megaoctets, which makes it the most frequently read data unit in daily life.
The typical figures are worth carrying in the head. A photograph from a phone is 2 to 5 megaoctets, a raw photograph from a system camera 25 to 50. A compressed song is 3 to 10. A minute of high-definition video is around 100. A long text document is under one. An operating system update is several thousand, which is why it is quoted in gigaoctets instead.
The megaoctet also carries the most notorious unit error in computing history. The 1.44 MB floppy disc holds neither 1.44 million octets nor 1.44 times 1,048,576. Its capacity is 1,440 kibioctets, which is 1,474,560 octets — the manufacturers multiplied a binary kilo by a decimal thousand and produced a figure that is correct in no system at all. It remains the standard illustration of why the IEC prefixes were needed.
Compact discs are cleaner: a standard disc holds about 700 megaoctets of data, or 74 to 80 minutes of audio, and that capacity was the practical limit for distributing software for a decade. Before them, distributing a program meant a box of floppies, and after them a DVD held about 4.7 gigaoctets, nearly seven times as much.
Memory sizes reached megaoctets in the early 1990s and stayed there for a decade. Four megaoctets was a comfortable amount in 1993 and inadequate by 1998, which tracks the arrival of graphical interfaces and the web. Today a single browser tab routinely holds more memory than an entire computer of that era.
The decimal-binary gap matters at this scale. A megaoctet is a million octets, but a mebioctet is 1,048,576, and a file reported as 100 MB by one program may appear as 95.4 MB in another. The difference is 4.9 per cent, small enough to overlook and large enough to cause arguments about whether a download completed correctly.
One megaoctet equals 1,000,000 octets, 1,000 kilooctets, 8 megabits, or about 0.9537 mebioctets.
The petaoctet is a unit of digital information equal to a thousand teraoctets, or a million gigaoctets. Its symbol is Po. It is the unit of institutional storage: the scale at which data belongs to an organisation rather than to a person, and at which keeping it becomes a budget line rather than an afterthought.
A petaoctet is roughly the storage of a thousand large consumer hard drives, or the text of every book ever published several times over. In video terms it is about twenty thousand hours in ultra-high definition, or two and a half years of continuous viewing. The entire catalogue of a large streaming service, held once at each quality level, comes to a few petaoctets.
Science reached this scale first. The Large Hadron Collider at CERN records tens of petaoctets a year after its trigger systems have already discarded more than 99.99 per cent of what the detectors see, and the full archive runs to several hundred petaoctets. Astronomy, genomics and climate modelling all keep archives of comparable size, and the discipline of managing them became a research field of its own.
Commercially the petaoctet describes a single data centre's storage rather than a company's total. A large organisation holds tens or hundreds of petaoctets across many sites, and the largest cloud providers hold exaoctets. At this size the practical problems are not capacity but the electricity to keep the drives spinning, the cooling, and the certainty that a fraction of the hardware is failing at any moment.
That last point drives the design. In a petaoctet array, drive failures are not exceptional events but a continuous background rate, so the system is built to lose devices constantly and rebuild without interruption. Data is stored with erasure coding across many machines, and no single copy of anything is trusted.
Reading a petaoctet is itself a problem. Even at ten gigaoctets per second, a rate few systems sustain, a full pass takes more than a day. This is why analysis at this scale is designed to move the computation to the data rather than the data to the computation, an inversion that shaped the whole field of distributed processing.
One petaoctet equals 1,000 teraoctets, 1,000,000 gigaoctets, 8 petabits, or about 0.8882 pebioctets.