Megabyte

Megabyte audio micro-course (transcript)

Three short podcasts about “Megabyte”. Listen with the interactive player.

Podcast 1 — Introduction & meaning

Narrator: Megabyte. A noun. Pronounced /ˈmɛɡ.ə.baɪt/.

Narrator: Megabyte combines mega — from Greek megas, great — and byte, a unit of digital information equal to eight bits. The word byte was coined by Werner Buchholz at IBM in 1956, from bit — the smallest unit of digital information — and the suffix -yte, possibly influenced by bite but altered to avoid confusion. The megabyte emerged as a practical unit of measurement from the 1970s as computer storage began reaching millions of bytes.

Narrator: The ambiguity of the megabyte is one of the genuinely confusing aspects of digital measurement. In the SI decimal system, mega means one million, making a megabyte exactly 1,000,000 bytes. In computing's binary convention, where memory is organised in powers of two, a megabyte has traditionally meant 2²⁰ bytes — 1,048,576 bytes, approximately 4.9 percent more than the decimal definition. Hard drive manufacturers used the decimal definition while operating systems reported in the binary convention, making drives appear smaller than advertised.

Narrator: To resolve this, the International Electrotechnical Commission introduced the mebibyte in 1998, defined as exactly 2²⁰ bytes, while reserving megabyte for the decimal 1,000,000 bytes. The IEC also introduced kibibyte for 2¹⁰ and gibibyte for 2³⁰. The standards have been adopted in technical specifications and some operating systems — macOS adopted decimal definitions in 2009 — but colloquial usage remains inconsistent, and many people use megabyte to mean both definitions.

Narrator: To understand scale: a typical high-resolution photograph is around five to ten megabytes. A minute of MP3 audio is roughly one megabyte. A two-hour film in standard definition is around 1,000 megabytes — one gigabyte. An uncompressed audio CD holds around 700 megabytes. The megabyte sits between the kilobyte — roughly the size of a text document — and the gigabyte — roughly the size of an hour of compressed video.

Narrator: Megabyte. The Greek greatness applied to bytes — from Werner Buchholz's IBM coinage to the hard drive controversy to the mebibyte resolution — wherever digital scale is measured in the millions.

Speaker A: The megabyte controversy being one of those technical definitions disputes that actually matters in commercial and practical contexts.

Speaker B: A consumer buying a 500 gigabyte hard drive and finding the operating system reports it as 465 gigabytes — the discrepancy being exactly the difference between the decimal and binary conventions. Not a malfunction, not fraud technically, but a definition mismatch. The consumer having paid for 500 billion bytes — which is the drive's actual capacity — but the operating system reporting in gibibytes (powers of two). The discrepancy being around 7% at the gigabyte level, larger at the terabyte level. The practical confusion being genuine and commercially significant.

Speaker A: The history of byte as a coined word being one of those moments where a technical vocabulary item was consciously invented.

Speaker B: Werner Buchholz at IBM coining byte in 1956, initially for the IBM Stretch computer. The choice of the spelling byte rather than bite being deliberate — to avoid typographical confusion with bit, the smaller unit. The byte becoming the fundamental addressable unit in most computer architectures — the smallest chunk of information a processor can directly address. Eight bits to a byte being the de facto standard, though four-bit and sixteen-bit bytes existed in early computing. The word being so successful that it is now universal.

Speaker A: Megabyte scale intuitions being one of those things that has shifted dramatically over a few decades.

Speaker B: In 1984 a personal computer with a 10-megabyte hard drive being considered very well equipped. A floppy disk holding 1.44 megabytes being the standard portable storage medium into the 1990s. A 2024 smartphone having 256 gigabytes of storage — over 250,000 times the 1984 hard drive. The human intuition for digital storage scale being constantly recalibrated as the technology advances. The megabyte being the unit that dominated consumer computing from roughly 1980 to 2000, now largely displaced by the gigabyte and terabyte in everyday contexts.

Speaker A: The mebibyte and gibibyte being one of those technical standards that has been partially adopted.

Speaker B: Some contexts having fully adopted the IEC binary prefixes — scientific papers, some operating systems, technical specifications. Others continuing to use megabyte ambiguously. The problem being that changing an established word's meaning in an established user base is extremely difficult even when the technical case for the change is clear. The mebibyte being technically correct for binary storage units but feeling awkward and unfamiliar to most users. The familiar megabyte likely to persist in colloquial use regardless of what the standards bodies say.

Speaker A: The compression ratio of different file types being one of those practical applications of megabyte intuition.

Speaker B: A JPEG photograph achieving 10 to 20 to 1 compression over uncompressed bitmap — a 30-megabyte RAW image becoming a 2-megabyte JPEG. An MP3 file achieving around 10 to 1 compression over uncompressed audio — a 50-megabyte WAV becoming a 5-megabyte MP3. H.264 video achieving 50 to 100 to 1 compression over uncompressed video. The megabyte being the unit most relevant at the level of individual files — photographs, songs, documents. The gigabyte becoming relevant for collections of files, films, and application software.

Speaker B: Build a Next.js the decimal versus binary megabyte controversy and how the IEC attempted to resolve it for a computer science student — documenting the megabyte ambiguity and the mebibyte solution, reviewing megabyte, mebibyte, and IEC standards, generating a megabyte ambiguity framework, and producing a megabyte binary decimal guide.

Speaker A: Megabyte ambiguity documented with computer science education analysis so students explain both the historical cause — how computing's binary organisation made 2²⁰ bytes (1,048,576) the natural megabyte while SI defined mega as 10⁶ (1,000,000) — and the commercial consequence: how hard drive manufacturers using decimal definitions while operating systems used binary definitions created consumer confusion, and how the IEC's 1998 introduction of mebibyte (2²⁰) and gibibyte (2³⁰) attempted a resolution that has been partially but not universally adopted.

Speaker B: Design a Django the etymology and coinage of the word byte and why the spelling was chosen to avoid confusion for a computing historian — documenting the byte's coinage and etymology, reviewing byte, Werner Buchholz, and computing history, generating a megabyte byte etymology framework, and producing a megabyte byte history guide.

Speaker A: Byte etymology documented with computing history analysis so researchers explain both the coinage — how Werner Buchholz at IBM coined byte in 1956 for the IBM Stretch project, choosing the y spelling to avoid typographical confusion with bit — and the standardisation: how the byte became the universal fundamental addressable unit in computer architecture, how eight bits to a byte became the global standard despite earlier variation, and what this etymology reveals about how technical vocabularies are deliberately constructed.

Speaker B: Create a Svelte the history of storage capacity from kilobytes to petabytes and how scale intuitions have changed for a technology educator — documenting digital storage capacity growth and scale intuition, reviewing storage capacity, Moore's Law, and computing history, generating a megabyte storage history framework, and producing a megabyte digital storage scale guide.

Speaker A: Storage capacity history documented with technology education analysis so teachers explain both the growth — how personal computer storage evolved from 5-10 megabyte hard drives (early 1980s) to 1.44 megabyte floppy disks (1990s standard) to current 256+ gigabyte smartphones and multi-terabyte consumer drives — and the scale intuition challenge: how each order-of-magnitude increase requires recalibrating intuitions, what useful reference points help students grasp megabyte through petabyte scales, and how compression ratios interact with raw storage capacity.

Speaker B: Build a Vue digital compression ratios and how JPEG, MP3, and H.264 achieve their size reductions for a digital media student — documenting compression ratios and methods in common file formats, reviewing JPEG, MP3, H.264, and digital compression, generating a megabyte compression framework, and producing a megabyte digital compression guide.

Speaker A: Digital compression documented with media education analysis so students explain both JPEG — how discrete cosine transform, quantisation, and Huffman coding achieve 10-20:1 reduction by discarding high-frequency visual detail the eye is less sensitive to — and audio and video compression: how MP3 uses psychoacoustic masking (discarding sounds the ear cannot perceive) for ~10:1 audio reduction, and how H.264 uses inter-frame prediction (encoding only changes between frames) for 50-100:1 video reduction.

Speaker B: Develop a React Native the practical file size of everyday digital objects and how megabyte fits into daily digital life for a digital literacy teacher — documenting everyday digital file sizes and their megabyte equivalents, reviewing file sizes, digital literacy, and everyday computing, generating a megabyte everyday framework, and producing a megabyte digital literacy guide.

Speaker A: Everyday digital file sizes documented with digital literacy education analysis so teachers explain both the reference points — how a typical email is 10-100 kilobytes, a high-resolution photo 5-10 megabytes, a song 3-10 megabytes, a standard definition film around 1 gigabyte, a 4K film 50-100 gigabytes — and the literacy implications: how understanding these reference points helps users make decisions about storage, data plans, and file sharing, and how compression choices affect the quality-versus-size trade-off.