MP3

A perceptual audio codec that discards masked frequencies to reach roughly a tenth of CD size.

Representation

binary

Compression

MPEG-1 Layer III

Lossy

Yes

Typical size

1 MB per minute at 128 kbps

Open specification

Yes

Introduced

1993

Organisation

Fraunhofer IIS / MPEG

1. 1993Standardised in ISO/IEC 11172-3
2. 2017Final Fraunhofer patents expire

• Windowsfull
• macOSfull
• Linuxfull
• Androidfull
• iOSfull

Browsers: Chrome, Firefox, Safari, Edge.

• Plays on everything, including decades-old hardware
• Small files
• ID3 tag ecosystem

• Lossy, with audible artefacts at low bitrates
• Beaten on efficiency by AAC and Opus

• Music libraries
• Podcasts
• Car and legacy players

• Use 192–320 kbps for music, 96–128 kbps for speech

Converting MP3 to FLAC produces a large file that cannot recover the detail MP3 discarded.

• MP3 to WAV
• MP3 to FLAC
• MP3 to AAC
• MP3 to OGG
• MP3 to M4A

Every conclusion below is derived from the structured facts on this page — nothing is written by hand.

• Browser compatibility100/100

  • Because every major browser engine renders it natively.
  • Because at least one shipping browser renders it.

• Operating system compatibility100/100

  • Because Windows, macOS, Linux, Android and iOS all open it without extra software.
  • Because most platforms handle it natively.

• Web suitability100/100

  • Because browsers render it natively, so no conversion step is needed at request time.
  • Because lossy compression keeps transfer sizes and Core Web Vitals in check.
  • Because the specification is open, so tooling and CDNs implement it freely.

• Cloud compatibility100/100

  • Because an open specification means cloud SDKs can implement it without licensing friction.
  • Because it converts into many other formats, which suits automated pipelines.

• Streaming100/100

  • Because lossy compression keeps the bitrate low enough to stream reliably.
  • Because browsers decode it natively, so it plays without a plugin.
  • Because open specifications avoid per-stream licensing complications.

• Everyday consumer usage100/100

  • Because it opens by double-clicking on every mainstream device.
  • Because small files are easy to email, message and upload.
  • Because it is a current format that people and services still expect.

• Open standards100/100

  • Because the specification is published openly.

• Licensing100/100

  • Because an openly specified format can be implemented without a licence negotiation.
  • Because the core patents are old enough to have expired.

• Decode performance100/100

  • Because smaller payloads mean less I/O and faster first paint.
  • Because mature formats benefit from hardware and SIMD-optimised decoders.

• Future-proofing88/100

  • Because it is actively maintained and current.
  • Because open specifications outlive the companies that create them.
  • Because nothing in the graph supersedes it yet.

• Long-term archiving76/100

  • Because the specification is public, so a decoder can always be rebuilt.
  • Because it is a current, actively maintained format.
  • Because it has a decade or more of proven, stable implementations.

• Popularity71/100

  • Because it sits at the centre of the format ecosystem, with many documented relationships.
  • Because every mainstream operating system handles it.
  • Because it is still current rather than being phased out.

• Compression efficiency69/100

  • Because it compresses lossily, which produces much smaller files than lossless coding.
  • Because it defines a documented compression scheme.

• Printing suitability0/100

  • Because lossy artefacts become visible when the image is enlarged for print.
  • Because it does not satisfy: it is a page-description format built around fixed layout.

• Professional editing0/100

  • Because each edit-and-save cycle compounds compression damage.
  • Because it does not satisfy: professional applications read and write it.

• Software compatibility33/100

  • Because only a narrow set of applications handles it.