LogoLogoWaveSieve
  • Home
  • Pricing
  • Blog

Convert MP3 to WAV Online Free

Convert your .mp3 files to .wav format. Free, fast, and processed entirely in your browser — your files never leave your device.

Convert MP3 to WAV without re-compression artifacts

We built WaveSieve because converting MP3 files is supposed to be a 30-second job, not a sign-up flow. The MP3-to-WAV path is the one we get asked about most — usually because someone needs to drop an MP3 into a video editor, a DAW, or a transcription pipeline that won't accept compressed audio. Here's what actually happens during the conversion, when it's worth doing, and how to do it in three different tools.

When converting MP3 to WAV is the right call

  • You're importing audio into a DAW (Logic Pro, Pro Tools, Ableton, FL Studio, Reaper, Audacity). Most DAWs accept MP3 but decode it to PCM internally on every playback, which slows down editing on long sessions. Working from WAV avoids that.
  • You're feeding a video editor (Premiere, Final Cut, DaVinci Resolve). Some editors re-encode MP3 at import and add a frame-or-two of silence at the start, which knocks lip-sync out. WAV imports cleanly.
  • You're sending audio to a transcription or analysis tool that lists WAV/PCM as required. Whisper, Otter, descript, and most forensic-audio tools all prefer uncompressed input.
  • You're archiving a recording you can't replace and want a format that won't degrade further if you re-encode it later.
  • You need to burn an audio CD. CD audio is 16-bit / 44.1 kHz PCM, which is exactly what a standard WAV stores.

When converting won't help (and might hurt)

  • You think it'll restore audio quality. It won't. The data MP3 encoding threw away is gone — see the pitfall section below for what's actually happening.
  • You're keeping the file on your phone or sharing it on social media. WAV files are roughly 10× larger than the source MP3, and most consumer apps re-compress on upload anyway.
  • You're playing it through Bluetooth speakers or earbuds. Bluetooth re-encodes the audio in flight (SBC, AAC, or aptX), so the WAV-vs-MP3 difference disappears the moment it leaves your phone.
  • You're streaming over the web. <audio> tags work fine with MP3, and serving WAV bloats your bandwidth bill for no audible upside.

How big the WAV file will be

WAV stores audio uncompressed, so the output is always larger than the source MP3 — usually by 7-10×. Here is what to expect for typical MP3 bitrates converted to standard 16-bit / 44.1 kHz WAV (CD quality, the default we use):

DurationMP3WAVNote
1 minute~0.96 MB (128 kbps)~10.1 MB10.5× larger
10 minutes~9.6 MB (128 kbps)~101 MBA short podcast episode
1 hour~57.6 MB (128 kbps)~605 MBFull DJ set or long interview
1 minute (320 kbps source)~2.4 MB~10.1 MB4.2× larger — higher MP3 bitrate, same WAV size

Source: stereo MP3. Target: 16-bit / 44.1 kHz stereo WAV (~1411 kbps, CD-equivalent). Real numbers vary slightly with the WAV header overhead.

Where WAV works (and where it does not)

Works with

  • Every desktop DAW: Pro Tools, Logic, Ableton, FL Studio, Reaper, Cubase, Audacity
  • Every video editor: Premiere, Final Cut, DaVinci Resolve, iMovie, Shotcut
  • Windows Media Player, macOS QuickTime, VLC
  • Voice transcription tools: Whisper, Otter, Descript, Rev
  • CD burning software (Roxio, ImgBurn, macOS Music)
  • Sample libraries and hardware samplers (MPC, Ableton Push, Maschine)

Does not work with

  • Most websites' <audio> embeds — Safari is fine, but legacy Edge and some Android browsers stutter on big WAVs
  • Spotify, Apple Music, SoundCloud uploads — they accept WAV but re-encode it server-side, so the size advantage is wasted
  • Most Bluetooth speakers and car head units — the file plays, but the wireless link re-compresses it anyway
  • Older portable music players (iPod Classic, Walkman) — limited storage makes WAV impractical
  • Email attachments — typical inbox limits (25 MB) blow out fast on WAV

How to convert MP3 to WAV

Convert with WaveSieve (browser, free, no upload)

This is the fastest path and the one we recommend by default. Conversion runs locally in your browser using FFmpeg.wasm — your file never leaves your device, no account needed.

  1. Drop your MP3 file onto the upload area at the top of this page (or click and pick a file). Up to 100 MB per file.
  2. In the converter that appears, the output is already set to WAV. Leave it as-is.
  3. Click the "Convert to WAV" button. Conversion takes 5-30 seconds depending on file length and your computer.
  4. Click "Download" to save the WAV. The original MP3 is untouched.
Pro tip: Since the conversion is local, there's no upload progress bar — if your file is large (50+ MB) and your laptop is older, give it a moment. We're not stuck, your CPU is just doing the decoding work that a server would normally do.

Convert with Audacity (desktop, free, more control)

Use Audacity when you want to pick a non-default sample rate or bit depth — for example, 24-bit / 48 kHz for video editing.

  1. Open Audacity (free at audacityteam.org). If it's the first time, install the FFmpeg add-on when prompted, otherwise it can't open MP3 files.
  2. File → Open → pick your MP3.
  3. Bottom-left, set the Project Rate to your target sample rate (44100 for music/CD, 48000 for video).
  4. File → Export Audio → choose WAV (Microsoft) signed 16-bit PCM (or 24-bit if you need more headroom).
  5. Pick a destination, click Save. Skip the metadata dialog if you don't need it.
Pro tip: Audacity defaults to 32-bit float internally, which is great for editing but overkill for plain conversion. Stick to 16-bit unless your destination tool specifically asks for 24-bit.

Convert with FFmpeg (command line, scripts, batch jobs)

When you have 50 MP3s to convert at once or you're plumbing this into a build pipeline, FFmpeg is the right tool. It's also what powers WaveSieve under the hood.

  1. Install FFmpeg: brew install ffmpeg (macOS), winget install ffmpeg (Windows), or sudo apt install ffmpeg (Linux).
  2. Open a terminal in the folder with your MP3.
  3. Run: ffmpeg -i input.mp3 -acodec pcm_s16le -ar 44100 output.wav
  4. For a whole folder, run this loop in bash: for f in *.mp3; do ffmpeg -i "$f" -acodec pcm_s16le -ar 44100 "${f%.mp3}.wav"; done
Pro tip: pcm_s16le means 16-bit little-endian PCM — the universal WAV flavor. Use pcm_s24le for 24-bit instead. Don't add -b:a — that's a bitrate flag for lossy codecs and FFmpeg will ignore it for WAV.

Things that surprise people

WAV does not restore quality that MP3 already discarded

This is the single biggest misconception we see. MP3 encoding is lossy — it analyzes the audio, throws away frequencies the human ear is unlikely to notice, and saves the result. Converting back to WAV gives you a bigger file containing exactly the same compromised audio. If you want true quality, you need the original uncompressed source, not a round-trip through WAV.

Don't convert MP3 → WAV → MP3 unless you have to

Every MP3 encode is lossy. If you convert MP3 to WAV, edit, and re-export to MP3, you stack two lossy generations on top of each other and audible artifacts (warbling, smeared transients) start to appear — especially on cymbals and sibilants. If your final destination is MP3 anyway, edit the source MP3 directly in a tool that supports it (we support MP3 export in our cleanup tool), or work from a higher-quality source if you can.

Keep the sample rate consistent

If your MP3 was encoded at 44.1 kHz (the common case for music) and you export WAV at 48 kHz, FFmpeg or your DAW will resample on the fly. That's fine for most uses, but it adds a small amount of processing artifact. Match the source rate (we default to it) unless your destination tool — typically video editors — requires 48 kHz.

Frequently Asked Questions

Can I convert a 2-hour MP3 podcast to WAV in the browser?

Yes, but plan for a 1.2 GB output file and let your laptop work for a minute or two. We've tested up to 100 MB MP3 input which decodes to roughly 1 GB WAV — well within what a modern browser can handle. If your machine struggles, fall back to FFmpeg locally.

Should I pick 16-bit or 24-bit WAV?

Pick 16-bit unless something downstream specifically asks for 24-bit. Source MP3 audio doesn't carry more than 16 bits of usable dynamic range anyway — 24-bit just makes the file 50% bigger without adding anything you can hear. Logic Pro and Pro Tools are happy with either.

What if my MP3 has weird tags or album art?

WAV doesn't have a standard for embedded tags or art, so they're dropped during conversion. The audio is preserved bit-perfectly (within the lossy MP3 source). If you need to keep metadata, use FLAC instead — it's lossless like WAV but supports tags.

Does converting MP3 to WAV remove DRM?

No, and we wouldn't help you do that anyway. Standard MP3s have no DRM and convert cleanly. Files from Apple Music, Audible, or other DRM'd stores can't be opened by any conversion tool — you need to play them back through their official app.

Other MP3 Conversions

MP3 to FLACMP3 to OGGMP3 to AACMP3 to M4AMP3 to Opus

Convert to WAV

FLAC to WAVOGG to WAVAAC to WAVM4A to WAVOpus to WAV
LogoLogoWaveSieve

Free audio converter and AI audio workflows

Convert Audio
  • MP3 to WAV
  • MP3 to FLAC
  • WAV to MP3
  • FLAC to MP3
  • OGG to MP3
  • AAC to MP3
  • M4A to MP3
  • WAV to OGG
Convert to
  • Convert to MP3
  • Convert to WAV
  • Convert to FLAC
  • Convert to OGG
  • Convert to AAC
  • Convert to M4A
AI Tools
  • Audio Cleanup
  • Vocal Remover
  • Speech to Text
  • Audio Converter
Product
  • Pricing
  • FAQ
  • Blog
  • Changelog
  • Roadmap
Company
  • About
  • Contact
  • Waitlist
© 2026 WaveSieve. All Rights Reserved.
Privacy PolicyTerms of ServiceCookie PolicyRefund Policy