How to cut and trim MP3 files for free

You have a recording with ten seconds of dead air at the start. Or a podcast episode where the first three minutes are small talk you want to skip. Or a song you need to shorten for a presentation. The task is always the same: open the file, pick a start and end point, and save just that section.

This guide walks through how to do that with MakeMySounds’s audio cutter, which runs entirely in your browser. Your file never gets uploaded anywhere. We’ll also cover edge cases — what to do with files the browser can’t decode, how export format affects quality, and tips for getting clean cuts.

Why cut audio in the browser?

Desktop audio editors like Audacity work fine for trimming, but they’re overkill if all you need is to remove a few seconds from the beginning or end of a file. You have to install the software, import the file, learn the selection tools, export with the right settings, and hope you didn’t accidentally change the sample rate.

Online tools solve the installation problem, but most of them upload your audio to a server. That means your file sits on someone else’s machine while it gets processed — a real concern if you’re working with unreleased music, voice recordings, interview tapes, or anything you wouldn’t casually email to a stranger.

Browser-based cutting with the Web Audio API avoids both problems. The file loads into your browser’s memory, gets decoded locally, and the trimmed result is encoded on your machine. No upload, no server, no waiting for a download link. The only network traffic is loading the page itself.

Step-by-step: trimming an MP3 or WAV file

Open the audio cutter and follow these steps:

Drop your file. Drag an MP3 or WAV file onto the dropzone, or click it to open a file picker. The tool decodes the audio and renders a waveform so you can see the shape of the sound.
Set the range. Two handles appear on the waveform — one for the start point, one for the end. Drag them to select the section you want to keep. You can also drag the selected region itself to slide it along the timeline without changing its length. The exact start and end times display below the waveform in seconds.
Preview. Hit the play button to hear just the selected section. This is worth doing before you export — it takes a second and saves you from discovering a bad cut after the fact.
Choose your output format. You can export as MP3 or WAV. If you picked MP3, the tool encodes at 128 kbps by default. WAV output is uncompressed, so the file will be larger but lossless.
Download. Click the download button. The trimmed file saves directly to your device.

The whole process takes a few seconds for a typical file. Longer recordings (30+ minutes) may take a moment to decode and encode, but everything still happens locally.

MP3 vs WAV: which output format to pick

If you started with an MP3 and export as MP3, the audio goes through a second round of lossy compression. Each MP3 encode discards some data that the algorithm considers inaudible, and doing it twice compounds the loss. For most practical purposes — trimming a podcast clip for social media, cutting a ringtone, shortening a voice memo — the quality difference from a single re-encode is inaudible. But if you’re doing production work and plan to edit the file again later, export as WAV to keep it lossless until the final encode.

If you started with a WAV and export as WAV, there’s no quality loss at all. The operation is essentially copying a slice of the sample data. Export as MP3 only if you need the smaller file size for sharing or uploading somewhere with size limits.

Getting clean cuts

A cut in the middle of a loud section can produce an audible click or pop. This happens because the waveform jumps abruptly from a non-zero amplitude to silence at the cut point. Here are a few ways to avoid it:

Cut at zero crossings. Zoom into the waveform and place your start and end points where the waveform crosses the center line (zero amplitude). Clicks happen when you cut at a peak.
Cut during silence. If your recording has natural pauses — between sentences, between songs — place the cut there. Cutting silence never produces artifacts.
Add a short fade.If you can’t avoid cutting at a loud point, use the fade toolafterward to apply a quick 50ms fade-in or fade-out at the cut boundary. That’s short enough to be imperceptible as a fade but long enough to eliminate the click.

Handling large files

The audio cutter loads the entire file into your browser’s memory as uncompressed PCM data. A 5-minute stereo MP3 at 44.1 kHz decodes to roughly 100 MB of raw sample data. A 60-minute recording decodes to over a gigabyte. The tool enforces a 100 MB file size limit on the input to prevent your browser tab from running out of memory.

If your file exceeds that limit, you have a few options:

Use the server-side trimmer, which handles files of any size. You enter start and end times in seconds, the server cuts without fully decoding the file, and you download the result. The tradeoff is that your file gets uploaded to the server for processing — but it’s deleted immediately after.
Compress the file first with the audio compressor to bring it under the 100 MB limit, then use the client-side cutter on the compressed version.

When the browser can’t decode your file

The Web Audio API in most browsers can decode MP3, WAV, AAC, OGG Vorbis, and FLAC — but support varies. Safari handles AAC and MP3 well but historically struggles with OGG. Firefox and Chrome cover the broadest range. If you drop a file and the cutter shows a “format not supported” message, the browser simply can’t decode that particular codec.

For files the browser won’t decode — FLAC on older Safari, Opus files, M4A with unusual codecs, or anything exotic — use the server-side trimmer. It wraps ffmpeg, which handles virtually every audio format. You can also convert the file to MP3 or WAV first using the format converter and then cut it client-side.

Common use cases

People trim audio for all kinds of reasons. A few that come up frequently:

Ringtones. Most phones want clips between 20 and 40 seconds. Cut your favorite part of a song, export as MP3, and transfer it to your device.
Podcast clips. Pull a highlight from an episode to share on social media. A 30- to 60-second clip with a strong soundbite works better than a link to the full hour.
Removing intros and outros.Strip the jingle from the beginning of a recording before uploading it somewhere that doesn’t need it.
Voice memo cleanup. Phone recordings often start with a few seconds of fumbling before the actual content. Trim the dead air and save a cleaner file.
Sample chopping. Music producers isolate specific hits, phrases, or textures from longer recordings to use in a DAW. The cutter gives you a quick way to rough-cut a sample before importing it into your project.

What happens under the hood

When you drop a file, the tool creates an AudioContext and calls decodeAudioDataon the file’s raw bytes. This produces an AudioBuffer — an in-memory representation of the audio as arrays of floating-point samples, one array per channel. The waveform visualization is generated by downsampling these arrays into a set of peak values that map to pixels on the canvas.

When you export, the tool creates an OfflineAudioContext — a special audio context that renders as fast as possible instead of in real time. It schedules a buffer source to play only the selected range (using the start(0, startTime, duration)method), renders the output, and then encodes the result as either WAV (a straightforward PCM byte-packing operation) or MP3 (using the lamejs library, which is a pure-JavaScript MP3 encoder). The encoded blob is handed to the browser’s download mechanism, and that’s it — the entire pipeline runs in JavaScript with no server involvement.

Wrapping up

Cutting audio is one of those tasks that should be simple but historically required either installing software or trusting a server with your files. The MakeMySounds cutterhandles it directly in the browser for MP3 and WAV files. For formats the browser can’t decode or files that are too large, the server-side trimmer picks up where the client-side tool leaves off. Between the two, any audio file you have can be trimmed in under a minute.