Welcome to MakeMySounds

MakeMySounds is a free collection of 17 audio tools that runs in your browser. It exists because the existing free audio sites all share the same flaw: you upload your file to a server you don’t control, wait for a queue, then download the result. For a podcast intro you’re fine with sharing publicly that’s acceptable. For a rough mix of an unreleased track, an interview recording with a source, or anything you wouldn’t casually email to a stranger, it isn’t.

Most of the tools here run entirely in your browser using the Web Audio API. The file is decoded, processed, and re-encoded inside the tab — nothing crosses a network. The tools that genuinely can’t run in the browser (format conversion to FLAC/M4A/Opus, ffmpeg-based loudness measurement, video demuxing) are clearly labeled as server-side, and we delete the file the moment processing finishes.

What ships in your browser vs. on our server

The split isn’t arbitrary. The browser’s decodeAudioData handles MP3, WAV, AAC, and OGG reliably across Chrome, Firefox, Safari, and Edge. It struggles or outright fails on FLAC (until recent Safari), Opus in OGG containers, M4A with unusual codecs, and anything wrapped in a video container. Anywhere the browser handles the codec, the tool runs locally. Anywhere it doesn’t, the tool calls out to ffmpeg on our server.

Eleven tools run entirely in your browser: cut and trim, merge, fade in/out, peak/RMS normalize, change speed and pitch, reverse, remove silence, record from your mic, edit ID3 tags, detect BPM, and the waveform viewer. These accept MP3 and WAV files up to 100 MB. The cap exists because raw PCM in memory is roughly ten times the size of an MP3 — a five-minute stereo track decodes to about 100 MB of Float32 samples.

Six tools run on our server: bitrate compression, format conversion (MP3/WAV/FLAC/OGG/AAC/M4A/Opus), video-to-audio extraction, EBU R128 LUFS normalization, server-side trimming(for files the browser can’t decode), and bulk MP3 conversion. Each of these pages shows an upload notice before you submit.

How to pick the right tool

A few common situations and where to start:

• Cut a section out of a podcast or song: /audio-cutterif it’s an MP3 or WAV under 100 MB. /audio-trimif it’s FLAC, M4A, Opus, or larger than 100 MB.
• Make an episode loud enough for Apple Podcasts: /loudness-normalizerwith the -16 LUFS preset. Don’t use the simple peak normalizer for this — platforms measure perceived loudness, not peak level.
• Pull the audio from a phone video: /video-to-audio. MP3 at 128 kbps for voice, 256–320 for music.
• Send a 90-second song clip to a friend: cut it, export as MP3 at 192 kbps. File ends up around 2 MB — small enough for any messaging app.
• Convert an album of WAVs to MP3 in one go: /bulk-to-mp3 handles up to 50 files and bundles the results in a ZIP.
• Record a quick voice memo with no software: /audio-recorder. Download as WebM (small) or WAV (universal compatibility).

What “in your browser” actually means

It’s a phrase that gets thrown around loosely. Here’s what it specifically means for the client-side tools: when you drop a file, the browser reads its bytes into memory using the File API. The Web Audio API decodes those bytes into raw Float32 sample arrays inside an AudioBuffer. Processing happens via OfflineAudioContext (or direct array manipulation for things like reverse). Encoding back to WAV is a hand-rolled PCM serializer; encoding to MP3 uses lamejs, a pure-JavaScript port of the LAME encoder. The result is handed to the browser’s download mechanism via a Blob URL. At no point does the audio data leave the tab.

You can verify this. Open the network tab in your browser’s devtools, drop a file into one of the client-side tools, and watch: no upload requests fire. Page assets load when you first visit, and that’s it. The tools work offline once the page has loaded.

What ships when we use the server

The six server-side tools post your file to POST /v1/<endpoint>, ffmpeg processes it, and the result streams back as the response body. The file lives on the server only for the duration of the request — typically a few seconds — and is unlinked from disk before the response finishes. We don’t log file contents, don’t keep copies, and don’t analyze what you upload. The privacy page spells this out per tool.

What this blog covers

Practical posts on audio formats and workflows, each tied to one or more tools on the site. The catalog so far:

• How to cut and trim MP3 files for free — step-by-step walkthrough of the cutter, including how to avoid clicks at cut points.
• MP3 vs WAV vs FLAC: which audio format should you use? — lossy vs lossless, file size math, and when each format actually makes sense.
• How to compress audio files without losing quality — the bitrate ladder explained, plus the re-encoding trap that ruins audio more often than people realize.
• How to extract audio from a video — stream copying vs re-encoding, format choice, and file-size expectations.
• How to normalize audio loudness for podcasts and streaming — LUFS vs peak normalization, with platform-specific targets for Spotify, Apple Podcasts, YouTube, and broadcast.
• Understanding BPM: how audio tempo is detected — what the algorithm actually does, why octave ambiguity happens, and where automatic detection breaks down.
• The best way to record audio from your browser in 2026 — MediaRecorder, WebM vs WAV, mic permissions, and clean-voice recording technique.

Where to start

If you arrived with a specific task, the tool list on the landing pageis the fastest path. If you’re browsing and want a sense of what works well in a browser, the cutteris the most common starting point — drop an MP3, drag the handles, and download the trimmed result in under thirty seconds.