Guides · updated October 22, 2026

Convert WAV to MP3 on a Mac

Browser, Music app, Audacity and Terminal ffmpeg. What each one does with a WAV, which one writes MP3, and how to avoid an unnecessary upload.

Tested: 22 October 2026 · macOS · Safari/WebKit 27.2, Chrome 156, ffmpeg 8.0.1

Short answer

The browser converter is the shortest route: open it in Safari 26+ or Chrome, drop the WAV, pick a bitrate and convert. The Music app can create MP3 versions of imported audio, Audacity adds editing and batch macros, and ffmpeg in Terminal is the scriptable route. None of them needs an upload.

Route 1: the browser

  1. Open the converter in Safari 26+ or Chrome.
  2. Drop the WAV, or click and choose it.
  3. Pick 192 or 320 kbps.
  4. Convert and download.

This is the shortest route for one file. It also shows the source sample rate and channels before conversion, which is useful when a WAV is 24-bit/96 kHz and the destination expects 44.1 kHz.

Route 2: the Music app

The Music app can encode MP3, but it is built around a library:

  1. Music → Settings → Files → Import Settings.
  2. Set Import Using to MP3 Encoder and choose a quality.
  3. Add the WAV to the library.
  4. Select the track, then File → Convert → Create MP3 Version.

The original WAV stays in the library; the MP3 appears next to it. This is a good route if the audio is already in Music. It is a clumsy route for a single file that lives in Downloads, because you have to import it first.

Route 3: Audacity

Audacity is the route when the WAV needs editing or a repeatable batch:

  1. Open the WAV.
  2. Edit, normalize or apply effects if needed.
  3. File → Export → Export as MP3.
  4. Choose CBR, average or variable bitrate.
  5. Export.

For a folder, create a Macro with Export as MP3 and apply it to the files. Audacity is local; it does not upload the audio.

Route 4: Terminal ffmpeg

ffmpeg -i input.wav -c:a libmp3lame -b:a 192k -ar 44100 output.mp3

For a folder:

for f in *.wav; do
  ffmpeg -i "$f" -c:a libmp3lame -b:a 192k "${f%.wav}.mp3"
done

Install ffmpeg with brew install ffmpeg. Use this route when you need VBR, a specific sample rate, or an unattended batch. It is local and scriptable.

Which route fits

Job Route
One WAV, no install Browser
Audio already in Music Music app
Editing, effects, batch macro Audacity
Scripted batch, VBR, precise flags ffmpeg
A machine where you cannot install anything Browser

The Mac-specific traps

The common mistake

Renaming file.wav to file.mp3 does not convert anything. The bytes are still PCM; players that check the contents will reject or misread the file. Always encode.

FAQ

Does macOS have a built-in WAV to MP3 converter?

The Music app can create an MP3 version of audio in its library: Music → Settings → Files → Import Settings → Import Using MP3 Encoder, then File → Convert → Create MP3 Version. It is designed for music library tracks, not for a one-off file outside the library. QuickTime Player does not export MP3.

Is the browser faster than the Music app?

For one file, the browser is usually faster to start: no import, no library, no conversion menu. The Music app may be faster to encode because it uses a native encoder. For a single WAV, convenience wins.

Can I use afconvert?

afconvert is Apple's command-line audio converter, but its MP3 encoding support is not something to rely on across macOS versions. For a guaranteed MP3, use ffmpeg, Audacity or the browser.

Does the browser upload the WAV?

No. The file is read through the File API and processed in the tab. There is no upload endpoint.

Which bitrate should I use on a Mac?

192 kbps for mixed speech and music, 320 kbps for music from a good master, 96–128 kbps mono for speech. The source WAV is lossless, so the MP3 bitrate is the only lossy step.

Compare upload-based alternatives

Convert a WAV file