Convertio for Audio Editors: When to Convert MP3, WAV, and M4A

Convertio is a browser-based file converter that has been running since 2014. Nothing installs locally: you drop a file on the page, pick an output format, and download the result. Files can come from a computer, Google Drive, Dropbox, or a direct URL, and several files can be queued in one batch.

Convertio reports coverage of more than 300 formats across over 25,600 conversion routes, with more than a million files processed daily. For an editor, the useful part is narrower: the audio routes expose real encoding controls rather than a single fixed preset, so the output matches the project instead of a generic default.

Two practical habits come out of that. Batches move as one job, so an entire folder of location recordings converts in a single pass instead of file by file. Sources can be pulled straight from Google Drive, Dropbox, or a URL, which keeps a shared production folder as the single source of truth and skips the download and re-upload round trip.

Because the processing happens server side, an aging laptop finishes a batch as fast as a workstation does, and the same workflow runs on Windows, macOS, Linux, or a phone between shoots.

Three formats cover most of what arrives in a typical project folder, and they solve three different problems.

WAV stores audio as linear PCM with the sample rate, bit depth, and channel count described in the header, which is why it opens identically in Audacity, Audition, Logic, Resolve, and Premiere. MP3 reaches roughly a tenth of that size by discarding material a perceptual model predicts you will not notice.

Preservation practice points the same way for masters. The Library of Congress recommended formats statement places uncompressed files above compressed ones, and lossless compression above lossy compression, for audio works intended to last.

Converting to WAV is about the working file, not about quality recovery. It earns its place in three situations.

• Your editor or DAW behaves better with PCM. Time stretching, spectral repair, and loudness analysis all run on decoded samples. Starting from an uncompressed file removes one decode step and one source of inconsistency between applications.
• You are going to process the clip repeatedly. Every export back to a lossy format re-encodes what is already encoded, and small artifacts compound. A WAV intermediate breaks that chain.
• You need control over sample rate and channels. The conversion settings let you force a sample rate or downmix to stereo before the file ever reaches the timeline, which prevents silent resampling inside the project.

⚠️ WAV does not undo MP3 compression. The conversion unpacks the audio into an uncompressed container, so the file becomes easier to work with and stops degrading further. The detail removed during the original MP3 encode is gone and cannot be rebuilt. Expect a file roughly ten times larger, not a better sounding one.

The practical rule: convert to WAV when the file is going to be worked on, and keep the original MP3 as a reference copy in case someone later asks for exactly what was sent.

Most conversion regret comes from accepting defaults. Five controls do nearly all the work.

• Bitrate. For MP3 delivery, 192 kbps is a reasonable floor for music and dense mixes, and 320 kbps is the safe choice when the file has already been through one lossy encoder. Spoken word tolerates less.
• CBR versus VBR. Variable bitrate spends data where the audio is complex and usually sounds better per megabyte. Constant bitrate is the safer pick for legacy players, some of which report the wrong duration on VBR files, which matters when someone is giving you timecoded notes.
• Sample rate. Match the project. Resampling 48 kHz production audio to 44.1 kHz for a web deliverable is normal, but doing it twice, or letting the NLE do it silently, is how sync drift and dull high end creep in.
• Bit depth. Work at 24 bit where the format allows it. The extra headroom matters while you are still adjusting levels, not after the mix is locked.
• Channels. Downmix to mono deliberately when the source is a single voice, and check the result. An automatic downmix of material with phase differences can thin out or partially cancel content.

Each of these controls sits on the conversion page itself, including PCM bit depth for WAV output, sample rate, bitrate range for MP3, and mono or stereo handling, so a file can be prepared correctly before it reaches the timeline rather than fixed afterwards.

These choices only pay off if the mix underneath them is solid. Our guide to mixing dialogue, music, and sound effects in Premiere Pro covers the balancing work that happens before any export dialog opens.

Client audio is rarely public material, so it is worth knowing how a converter treats it. Convertio deletes input files and temporary files immediately after conversion, removes output files automatically after 24 hours, and lets you delete an output manually at any point from the My Files panel. Transfers between the browser and the conversion hosts run over TLS with HSTS enabled, the data centers hold ISO 27001 certification, and files are kept inside the European Union.

That level of detail is more than most converters publish, and it lines up with how a professional pipeline is supposed to work: files that exist only as long as the job needs them, on infrastructure with a recognized security standard behind it.

📋 Convert the whole folder in one pass. Queue every take at once, pull the sources directly from Google Drive or Dropbox, and set bitrate, sample rate, and channels once for the batch. A day of location audio reaches the timeline in a consistent format without a single manual export.

Run through this before converting anything that matters.

1. Identify the stage. Working file or deliverable? That single answer usually decides between WAV and MP3.
2. Check what is inside the container. Especially with M4A, know whether you are starting from AAC or ALAC.
3. Set bitrate, sample rate, and channels deliberately. Auto is a fallback, not a decision.
4. Convert once. Go from the best available source to the target format instead of chaining conversions.
5. Verify the output. Confirm duration, channel count, and level, and listen to at least one loud passage.
6. Keep the original. Archive the source file before replacing anything in the project folder.
7. Fill gaps with licensed audio rather than reprocessing. When a converted file simply lacks quality, a clean replacement from a royalty-free sound effects library is a faster fix than any amount of repair work.

Format choice follows the stage of the work rather than a ranking of best to worst. WAV is the format you work in, because uncompressed audio survives repeated processing and behaves predictably across applications. MP3 is the format you hand over, because it plays everywhere. M4A sits between them, efficient and common, as long as you know which codec is inside.

A converter is worth using when it gives you those controls and gets out of the way. Decide what the file is for, set the output deliberately, convert once, and keep the master.