Choose the input
Choose an audio file that the current browser can decode.
Open a browser-supported audio file, choose MP3 bitrate and channel layout, then encode and download a real MP3 without sending the recording to a server. No account or software installation is required.
Your file stays on this device while you edit it. This tool does not upload your audio.
Choose an audio file that the current browser can decode.
Select an MP3 bitrate and retain stereo or intentionally mix to mono.
Create the MP3 locally, download it and play the saved result to verify it.
An audio-to-MP3 converter decodes a supported source into samples and encodes those samples with the MP3 codec. The page fixes MP3 as the output while accepting the formats the current browser can decode, making it more focused than a converter with several destinations.
This page gives you a dedicated workspace for audio to mp3 converter, followed by practical guidance for checking and using the result. If you need a different workflow, the related tools below make it easy to continue without starting over.
Web Audio decodes the complete source into floating-point PCM. The exporter optionally preserves, mixes or expands channels, resamples when the encoder requires a supported rate and passes 16-bit sample values to the bundled LAME-based encoder at 128, 192, 256 or 320 kbps.
Music Tools Lab validates the expected input, then asks the current browser to decode the complete file into PCM. Any input must first pass the browser’s codec support. MP3 output uses a bundled LAME-based encoder at the selected bitrate; WAV output writes a new 16-bit PCM RIFF/WAVE file. The source stays in browser memory and is never uploaded.
The page creates a new file in browser memory and leaves the source unchanged. Decode and encode support depends on the current browser, so preview the processed version and verify the saved download before using it in another workflow.
MP3 remains broadly compatible and much smaller than uncompressed PCM, which makes it practical for reference files, spoken recordings and sharing with systems that reject a less common source format. The locked output removes ambiguity while keeping bitrate control visible.
Create the fixed destination requested by a device, editor or delivery workflow.
Use PCM WAV when a simple editor handles uncompressed input more predictably.
Choose MP3 and an appropriate bitrate when compact playback matters more than archival preservation.
Keep the decoded source, intentionally mix speech to mono or create a two-channel output.
Choose bitrate according to the destination and listen to a representative difficult passage. The MP3 is a derivative, not a new master; retain the source whenever future editing or re-encoding is possible.
Begin with a short, known source when testing the workflow: Choose an audio file that the current browser can decode. Preserve the original, use a new output name and audition the downloaded file in a separate player before replacing any production asset.
A new container or codec can solve compatibility and size problems, but it cannot recreate information missing from the source. Lossy MP3 output removes information by design. PCM WAV avoids an additional lossy encode yet remains limited by whatever survived in the decoded input.
Preview the boundary or processed version with a little context before and after the important sound. Headphones make clicks, clipped syllables, over-reduced center material and abrupt fades easier to notice. Keep the source file unchanged and choose a short test export first when you are working on a long recording or a phone with limited memory.
After export, open the downloaded file in a separate player and confirm its beginning, ending, channel balance, duration and format. Re-encoding can change file size and sound even when the timing is correct. That final playback check is especially useful before replacing a production asset, sending a clip to someone else or deleting any earlier version.
A browser-supported WAV, FLAC, OGG or unprotected M4A can be converted to a 192 kbps MP3 for convenient listening. Choose mono for speech when stereo information is unnecessary, or retain stereo for a music mix.
Input support depends on the codecs in the browser and operating system. MP3 is lossy, so a new encode can remove information and cannot improve an already compressed source. Tags, artwork and embedded metadata are not copied, and the 50 MB/20 minute limits keep local memory use manageable.
Check the saved file from beginning to end, confirm its format and channel layout, and return to the unchanged source if a boundary, codec choice or processing artifact needs correction.
These technical references provide extra background on the browser features, audio formats or music concepts used on this page.
Read the original reference for more detail.
View reference ↗REFERENCERead the original reference for more detail.
View reference ↗REFERENCERead the original reference for more detail.
View reference ↗Selected files are processed in your browser and are not uploaded to Music Tools Lab. Keep this tab open while the tool is working. Read about privacy & accuracy.
MP3 and WAV are the safest inputs. FLAC, OGG and M4A work only when the current browser and operating system include the required decoder.
192 kbps is a practical general setting. Speech can often use less, while complex music may benefit from 256 or 320 kbps. Higher bitrate creates a larger file.
No. MP3 encoding is lossy. A higher bitrate can reduce audible artifacts but does not make the process lossless.
No. Decoding and encoding occur in browser memory on your device, and the page creates a local download.
No. The current exporter writes a new audio stream without copying artwork or source metadata.