Conversion from Yobibits to Megabits

=

Invert

Formula to convert Yobibits (Yibit) to Megabits (Mbit)

More information

Yobibits to Megabits conversion table

Yobibits (Yibit)Megabits (Mbit)
1 Yobibit1.20892581961 × 1018 Mbit
2 Yobibits2.41785163923 × 1018 Mbit
3 Yobibits3.62677745884 × 1018 Mbit
4 Yobibits4.83570327846 × 1018 Mbit
5 Yobibits6.04462909807 × 1018 Mbit
10 Yobibits1.20892581961 × 1019 Mbit
20 Yobibits2.41785163923 × 1019 Mbit
25 Yobibits3.02231454904 × 1019 Mbit
50 Yobibits6.04462909807 × 1019 Mbit
100 Yobibits1.20892581961 × 1020 Mbit

Data reference points

ReferenceYobibits (Yibit)Megabits (Mbit)
A plain text message (160 characters)1.05879 × 10-21 Yibit0.00128 Mbit
A three-minute MP31.98523 × 10-17 Yibit24 Mbit
A smartphone photo2.64698 × 10-17 Yibit32 Mbit
A high-definition film2.64698 × 10-14 Yibit32000 Mbit
A dual-layer Blu-ray disc3.30872 × 10-13 Yibit400000 Mbit

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Yobibit (Yibit)

The yobibit is a unit of digital information equal to two to the eightieth power bits, which is 1,024 zebibits. Its symbol is Yibit. It is the largest of the binary prefixes defined by the International Electrotechnical Commission, and the binary counterpart of the yottabit.

At this step the two conventions differ by 20.9 per cent. That gap is the culmination of the argument for the binary prefixes: a naming habit that was 2.4 per cent wrong at the kibibit is now a fifth wrong, which no engineering document can tolerate. The IEC series stops here because the decimal series stopped at yotta when it was defined in 1998.

When the metric system gained ronna and quetta in 2022, the binary series was not extended to match. There are no accepted names above yobi, so a quantity of two to the ninetieth bits has no short form and must be written out. This is a gap in the system that will presumably be filled when someone needs it, though at present nothing comes close.

A yobibit is 151,115,727,451,828,646,838,272 octets, or 128 zebioctets. The world's entire stock of data is somewhere in the low hundreds of zettaoctets, which is a fraction of a per cent of a yobioctet. Nothing at this scale has been built, is being built, or is presently planned.

The unit is nevertheless properly defined, and that completeness has a purpose. A measurement system whose rules run out at a certain size forces every future user to invent an extension, and competing extensions are how ambiguity begins. Defining the whole ladder in advance costs nothing and prevents that.

For anyone reading technical documents, the practical lesson of the whole binary series is the lowercase i. Kibit, Mibit, Gibit, Tibit, Pibit, Eibit, Zibit and Yibit are binary; kbit, Mbit, Gbit, Tbit, Pbit, Ebit, Zbit and Ybit are decimal; and the difference between them grows from negligible to a fifth as you climb. A writer who omits the i has left the reader to guess.

One yobibit equals 1,024 zebibits, 151,115,727,451,828,646,838,272 octets, or about 1.209 yottabits.


Information about the Megabit (Mbit)

The megabit is a unit of digital information equal to one million bits. Its symbol is Mbit. It is the unit in which the speed of an internet connection is almost always advertised, which makes it one of the few data units that ordinary consumers encounter by name every time they choose a service.

A megabit is one million bits exactly, not 1,048,576. That distinction has practical consequences. A megabit holds 125,000 octets, which is 125 kilooctets, so a connection running at 100 megabits per second transfers about 12.5 megaoctets per second at best. A file listed as 500 megaoctets therefore takes a minimum of forty seconds, not the four the advertised number seems to promise.

That factor of eight is the reason so many people believe their connection is slower than they were sold. Nothing dishonest is happening: the industry quotes throughput in bits per second because that is what the physical layer actually carries, while file managers quote size in octets because that is how storage is organised. Both conventions are correct in their own domain, and the arithmetic between them is a division by eight.

Real throughput is lower still. Protocol headers, error correction and retransmission all consume capacity, and the usable share of a link is typically 90 to 95 per cent of its nominal rate. Wireless links lose more, because the medium is shared and interference forces retries. A connection advertised at 100 megabits per second commonly delivers 90 or so in practice, and less over a busy wireless network.

The numbers that define the eras are worth remembering. Early broadband offered 1 to 8 megabits per second, cable and fibre pushed that to 50 and 100, and gigabit services are now common in cities. High-definition video streaming needs roughly 5 megabits per second, ultra-high-definition roughly 25, and a video call between two 8, so a household's real requirement is usually far below what it buys.

In memory the megabit describes chip capacity. A 512-megabit memory chip holds 64 megaoctets, and several such chips make a module. Manufacturers count in bits because that is what the silicon holds; buyers count in octets because that is what the operating system reports.

One megabit equals 1,000,000 bits, 1,000 kilobits, 125 kilooctets, or about 0.9537 mebibits.