The work is executed in the page through browser workers, WebAssembly, Web Audio, or WebGPU as stated.
Audio Converter
One format to another. Convert common audio formats without sending the source to a server.
Original and converted previews appear here.
What does audio converter do?
An audio converter decodes one media format and encodes the same sound into another container or codec. SoundTools uses FFmpeg WebAssembly inside a browser worker to create WAV, MP3, FLAC, or M4A output locally.
A real local processor, not a decorative upload box
FFmpeg WebAssembly runs after you choose a source and explicitly start the operation. The audio samples remain in browser memory; SoundTools does not send the selected media to an application endpoint.
Choose WAV, MP3, FLAC, or M4A, then set an appropriate sample rate and compressed bitrate. Results remain available for preview and download only in the current tab. Closing or refreshing the page releases those temporary objects.
How to use audio converter
- 01
Choose the local source
Open a compatible file in the dedicated workbench at the top of this page. The browser validates and decodes it without an upload step.
- 02
Set the useful controls
Choose WAV, MP3, FLAC, or M4A, then set an appropriate sample rate and compressed bitrate.
- 03
Process, check, and export
Run the local processor, inspect the status and preview, then save WAV · MP3 · FLAC · M4A when the result is ready.
What this tool actually does
Clear limits are part of a useful tool. These values describe the processor currently running in this page.
Runtime and model assets may be downloaded, but the selected file is not attached to those requests.
The dedicated workbench exposes only formats it can actually produce in the current browser.
Useful reasons to open audio converter
- Editor compatibility
Create a WAV or another format accepted by a production tool.
- Smaller handoffs
Encode a compact MP3 or M4A for review and sharing.
- Lossless archive copy
Create FLAC or WAV when a lossless output fits the next step.
Questions about this tool
Answers based on the current browser processor—not promises about a future version.
01Is my audio uploaded for processing?
No. Audio samples stay in browser memory. The page may download a codec or model asset, but it does not send the selected file with that request.
02Why can the first run take longer?
This tool uses FFmpeg WebAssembly. A browser may need to download and initialize that runtime before the first operation; later runs can reuse cached assets.
03Can I preview the result before saving?
Yes. Audio-producing tools expose local result players, while analysis and transcription tools show their detected data before download.
04What happens when the browser is unsupported?
The workbench reports the missing capability instead of uploading the media or pretending that processing is still running.