Choosing the MP3 Extension: Making Compressed Audio Recognizable as a File

At 12:29 on 14 July 1995, an internal email at Fraunhofer’s Institute for Integrated Circuits announced the extension survey’s result: ISO MPEG Audio Layer 3 files would use .mp3. Its preserved English translation instructs future pages, shareware and demonstrations to stop using .bit. The audio team in Erlangen, Germany, was addressing how its research would be identified and distributed.

The wording already addressed World Wide Web pages and software available for trial. A consistent suffix gave users a common label in directories, download links and documentation. Renaming alone did not compress an ordinary audio file or make non-compliant data playable as MP3.

References: [1]

In his 1999 technical paper, Karlheinz Brandenburg dates the definition of Layer 3 to 1991 and adoption of the first-phase MPEG standard to late 1992. RFC 2250 of 1998 cites the formal ISO/IEC 11172 standard publication as 1993. Technical development, publication of the standard and the 1995 naming decision were adjacent but different steps.

MPEG-1 divides audio coding into three layers. Layer 3 is the more complex approach aimed at audio quality at lower bitrates. The three in MP3 denotes that layer, rather than a third MPEG generation. Interchange required different implementations to follow shared data formats and decoding rules.

References: [2] [3]

Perceptual audio coding uses auditory masking to allocate errors that are less likely to be heard. The encoder analyzes frequency components, assigns quantization precision through an auditory model and organizes a compressed bitstream. It aims to reduce storage and transmission requirements while preserving perceived sound rather than restoring every bit of the source recording.

Files sharing the .mp3 extension can therefore differ in quality. Bitrate, content and encoder decisions affect results. Excessive compression may remove high-frequency detail or introduce noise before transients. The common standard provides a method for interpreting the data without ensuring equally good choices from every encoder.

References: [2]

A shared extension helped distribute files; real-time network playback required additional arrangements. RFC 2250, published in January 1998, specifies encapsulation of MPEG audio and video in RTP. Its audio section permits multiple complete audio frames in one packet or fragmentation of an oversized frame across packets, with offsets to locate fragments. Timestamps mark playback timing.

The later document separates compressed data formats from network transport. File storage, packet division and receiver playback need coordinated conventions. The 1995 email standardized the user-facing name, while later protocols and consumer devices belonged to subsequent development.

References: [1] [3]