Mono matters more than most people expect. Phone calls, voicemail systems, many podcast platforms, most speech recognition pipelines and a lot of embedded audio hardware all work in a single channel, and feeding them a stereo file either forces a lossy automatic downmix on their end or, worse, only plays back whichever channel that system happens to read. Converting to mono yourself, with control over exactly how the mix happens, removes that guesswork.
Everything runs locally. The Web Audio API decodes the file, a short averaging routine mixes the channels in your browser tab, and a hand written WAV writer encodes the mono result, so a private recording never has to leave your device to be downmixed.
Your podcast host rejects stereo, but the interview was recorded in it
Voice recordings are the most common case. A phone call, an interview or a voice memo recorded in stereo usually carries the same signal on both channels anyway, captured from a single microphone, so converting it to mono halves the file size for no audible loss at all. True stereo material, such as music with instruments panned across the stereo field, changes more noticeably when mixed down, since content that only existed on one side now sits at half its original level in the combined channel.
Podcast hosting platforms, IVR and telephony systems, many transcription services and a good deal of embedded or industrial audio hardware either expect mono input or handle it more predictably than stereo. Converting before you upload or import avoids an automatic downmix performed by software you cannot inspect or control.
- Convert to mono before uploading a voice recording to a podcast host or transcription service that expects a single channel.
- Use an audio mono converter to halve file size on spoken word content where the channels are already near identical.
- Mix music or dual channel recordings down when a destination system only reads a single channel reliably.
- Skip the conversion when true stereo separation, such as panned instruments, is part of what you need to preserve.
How this stereo to mono converter mixes the channels
The conversion reads every channel of the decoded AudioBuffer sample by sample and writes the average of all of them into a single new channel. For a typical stereo file that means the left and right samples are added together and divided by two at every position in the file, so a signal that appears identically on both channels keeps its original loudness in the output, while a signal that only existed on one channel drops to half its amplitude in the mix.
This averaging approach is deliberately simple and completely predictable. Some downmix algorithms apply extra gain compensation or phase correction to avoid that half level effect on hard panned content, but those choices assume things about the source material that are not always true, and a hidden gain boost can just as easily clip a signal that was already close to full scale. Straightforward averaging keeps the relationship between the original and the mixed result easy to reason about.
What changes and what does not when you convert stereo to mono
Sample rate, bit depth handling and duration are all unaffected. Only the channel count changes, from however many channels the source had down to exactly one. If your source file was already mono, running it through this tool is a harmless no op that simply re encodes it as WAV.
Because every channel contributes to the same averaged output, any content that was out of phase between channels, a deliberate stereo widening effect or certain kinds of noise reduction artifacts, can partially or fully cancel out in the mix. This is a physical consequence of averaging, not a bug, and it is worth previewing important recordings after conversion to confirm nothing important depended on that phase relationship.
File size and compatibility after mixing to mono
A mono WAV file is roughly half the size of the same duration stereo WAV at the same sample rate and bit depth, since there is exactly one sample stream to store instead of two or more interleaved ones. For an hour long stereo recording that routinely means the difference between a file that comfortably attaches to an email and one that does not.
The WAV output uses standard 16 bit PCM in a single channel, which every audio editor, transcription tool and telephony system can read without special handling, since mono PCM is the simplest and most universally supported audio layout there is.
The audio mono converter math: decodeAudioData, then average every channel
Decoding uses the Web Audio API's decodeAudioData method, which turns the compressed file into an AudioBuffer holding one Float32Array of raw samples per channel. The mixdown step reads every channel array at each sample index, averages the values and writes the result into a new single channel AudioBuffer created with the same sample rate and length as the source.
That new mono buffer is then handed to a hand written WAV encoder that writes the standard 44 byte RIFF header followed by the mixed samples converted to signed 16 bit integers. Because the averaging math runs on the AudioBuffer that already lives in the tab's own memory, there is no point in this pipeline where the file would need to travel anywhere else to be mixed down.
How to convert audio to mono
- 1
Add your audio file
Drag a stereo or multi channel audio file onto the drop area, or click it to browse. MP3, OGG, FLAC, M4A, AAC and WAV are all accepted.
- 2
Review the channel count
The detected channel count and duration are shown once the file is decoded, so you can confirm it is not already mono.
- 3
Mix to mono
Press convert. Every channel is averaged together sample by sample into a single mono channel.
- 4
Download the mono WAV
Download the resulting file. It plays back identically through both speakers, since there is now only one channel to send.
Related tools worth bookmarking
Sources and further reading
Frequently asked questions
Common questions about the audio mono converter.
No. Deleting a channel throws away half the signal and can lose content that only existed on the discarded side. This tool averages every channel together sample by sample instead, so content from every channel contributes to the mono result rather than being silently discarded.
Content that was identical on every channel keeps roughly the same loudness after averaging. Content that only existed on one channel, such as a hard panned instrument, drops to about half its original amplitude in the mix, since it is now being averaged against silence on the other channel.
Yes. A mono WAV file stores one sample stream instead of two or more, so it is roughly half the size of an equivalent stereo WAV at the same sample rate and bit depth. Converting a compressed stereo source to a mono WAV can still be larger than the original if the source was heavily compressed, since WAV itself is uncompressed.
Yes. Running a mono file through this tool has no meaningful effect on the audio, since there is only one channel to average with itself. It simply decodes and re encodes the file as a 16 bit PCM WAV.
Not with this tool, since it always averages every channel together to produce the mono result. If you specifically want one original channel isolated rather than blended, use an audio channel splitter first to pull the left and right channels apart, then keep only the one you need.
Many destinations, including phone systems, some podcast hosts and most speech recognition tools, either expect a single channel or handle it more predictably than stereo. Mixing to mono yourself also halves file size for spoken word content where the channels usually carry near identical audio anyway.