Audio converter for local MP3 and WAV output

An audio converter with a small, explicit format matrix

A format menu is useful only when every visible choice represents a path the current browser can complete. This page is deliberately narrower than an all-formats promise. Tested audio-only WAV, FLAC, Ogg, and raw AAC sources can target a new MP3 at a bitrate you pick when the current browser exposes the required decoder. MP3 can target a 16-bit WAV. Chrome decodes FLAC; Safari does not, so FLAC is never offered from signature bytes alone. A mode is enabled from real engine capability and container inspection, not from a long list of extensions printed for search engines. Converting also cannot repair what was never captured properly — a take recorded too quietly or clipped into distortion arrives in the new format with the same faults. When the source is your own voice, a microphone test settles that before the file exists.

The four most common directional jobs have their own focused pages: MP4 to MP3, M4A to MP3, WAV to MP3, and MP3 to WAV. This workbench collects smaller audio inputs without manufacturing a landing page for every permutation. It does not replace those canonical routes or turn a low-demand format into thin duplicated copy.

A WAV nevertheless converts here as well, and that is a correction rather than a duplication. Until recently this page refused one, on the reasoning that the direction already had an address of its own. But the refusal fell on the reader who arrived with the broadest possible intention — any audio file — and the file picker did not even list the extension, so only a dropped file ever reached the explanation. Both pages now produce the same MP3, because they are one converter behind two doors, and the dedicated route is named beside the conversion instead of in place of it. An audio-only M4A converts here too. A file with a video track is still handed over to MP4 to MP3, because taking the soundtrack out of a video is a different question with a page that can answer it.

Browser support is measured instead of assumed

Signature bytes can identify a FLAC stream, an Ogg container, an AIFF family file, an AAC header, or an MP3. Recognition is only the first gate. A container can carry a codec that the local operating system does not expose, and browser builds do not all ship the same decoders. The tool opens the actual track and decodes a sample of it before it offers a conversion, so what it offers is what this browser can finish.

Unsupported does not mean “upload it somewhere else.” The page names the format or codec boundary and leaves the source on the device. It never renames bytes, substitutes a different destination, or presents a disabled path as a successful conversion. A known extension with malformed content also fails separately from a healthy format whose decoder is unavailable. AIFF can be chosen, and is checked, but the parser in this page cannot read it yet. The message says so by name and suggests exporting a WAV copy from the app that made the file.

MP3 output and WAV output make different promises

MP3 output creates a lossy delivery file, 128 kbps unless you pick another rate. FLAC masters can become much smaller, but the MP3 does not retain every sample. Ogg or AAC sources may undergo one lossy decode-and-encode generation after another. The output is suitable when compatibility or size is the requirement; the original remains the better archive.

The bitrate is a visible choice, and the finished file is read back so the result shows the rate it really carries. This page will not re-encode an MP3 into another MP3 at all: a converter that changes format should not also quietly be a size tool. When making the file smaller is the actual goal — including MP3 straight back to MP3 at a lower rate — the audio compressor owns that job, with the bitrate, channel and sample-rate choices in the open and the measured bytes on both sides.

WAV output is available for MP3 input and writes signed PCM16 at the decoded source sample rate. That avoids another perceptual encode, yet it cannot reconstruct detail previously removed from the MP3. The WAV will usually be dramatically larger. Neither mode transfers tags, embedded artwork, comments, chapters, or private metadata fields.

Channel layout is preserved or rejected, never guessed

Mono remains one channel and stereo remains two. More channels do not collapse into a hidden mix. A surround conversion needs explicit coefficients, clipping policy, and review material; those decisions are outside this compact utility. The error explains the boundary before an encoder asset is loaded.

For a supported job, the worker processes audio away from the interface thread and reports progress from completed sample work. Cancel stops the current result, and changing the source file invalidates any older blob. Once complete, the browser reopens the new file and the receipt records measured codec or PCM type, duration, rate, channels, and bytes.

Audio-only means this page does not extract video soundtracks

MP4 and M4A share a container family, but their user jobs diverge when a picture track is present. This generic converter rejects video-bearing material. Use MP4 to MP3 when the goal is its primary soundtrack, or the video trimmer when picture and audio must stay synchronized. Creating a second route called “audio extractor” would duplicate the same video-to-audio result without clarifying the destination.

Conversion also leaves timing untouched. To keep or remove a selected interval, go to the audio trimmer. To generate a still visual asset from amplitude, use the audio waveform generator. Those tools answer editing and artwork requests rather than hiding unrelated operations in another format mode.

Files enter from disk and leave through a local download

Drop an audio file or choose one with the picker. The source is decoded locally, passed to a worker, and returned through a temporary object URL. There is no account, server upload, remote-media field, analytics payload containing the file, or cloud fallback after a codec error. Long audio still consumes real memory, so the interface shows the expected decoded or PCM cost and reports resource exhaustion as such. Local processing removes a service quota; it does not make device capacity infinite.