MP3, AAC, Ogg or Opus: Which Audio Format Should You Use on the Web?
Choosing an audio format affects how fast your pages load, how good your tracks sound and whether every visitor can play them. Here is a short, practical comparison.
Quick comparison
| Format | Browser support | Typical use |
|---|---|---|
| MP3 | All modern browsers | Safe default for music and podcasts |
| AAC (.m4a) | All modern browsers | Slightly better quality than MP3 at the same bitrate |
| Ogg Vorbis | Most browsers; older Safari versions lack support | Open-format fallback |
| Opus | All current major browsers | Excellent quality at low bitrates, great for speech |
| WAV | All modern browsers | Uncompressed; usually too large for streaming |
MP3: the safe default
MP3 is supported everywhere, and every editing tool can export it. At 128–192 kbps it sounds good enough for most music on a website. If you only want to produce one file per track, choose MP3.
AAC: same reach, a bit more efficient
AAC usually sounds better than MP3 at the same file size. It is a good choice if your audio already comes from a tool or platform that exports AAC.
Opus: the most efficient option
Opus delivers very good quality at low bitrates. Spoken-word content can sound clear at 32–48 kbps, which is a fraction of the size of a typical MP3. Offer Opus as the first <source> with MP3 as a fallback if you want the smallest files without losing compatibility.
Ogg Vorbis: mostly a legacy fallback
Ogg Vorbis was a popular open alternative to MP3. Today Opus has largely replaced it for new projects, but you may still see it in older players and tutorials.
WAV: keep it for editing
WAV files are uncompressed and can be ten times larger than an MP3. Keep them as your master copies, then export compressed versions for the website.
Recommended setup
- Music: MP3 at 160–192 kbps, optionally Opus at around 96–128 kbps first.
- Podcasts and speech: MP3 at 64–96 kbps mono, or Opus at 32–48 kbps.
- Short sound effects: small MP3 or Opus files; avoid WAV.