MP3 Cutter

MP3 cutter is one of the highest-volume audio tool searches on Google — 10,000 monthly searches in the US alone, more globally. The reason is mostly ringtones. The MP3 era from roughly 2003 to 2015 trained a generation of users to think of MP3 as the universal audio format, and ringtone-making is the headline use case where you start with a song you already own as MP3 and end with a short clip on your phone. Even though modern formats like AAC are technically more efficient, the install base of MP3 files (legacy music libraries, podcast feeds, audiobook downloads) keeps the format dominant for end users. If you have an MP3 and want a piece of it, you want an MP3 cutter.

MP3 is a lossy format, and any cut requires a re-encode (so the cut can land at any sample, not just at frame boundaries). The re-encode happens at the source bitrate by default — a 320 kbps source comes out as a 320 kbps cut, a 128 kbps source comes out as a 128 kbps cut. This single transcoding pass introduces a small amount of additional loss that is essentially inaudible on typical playback gear above 192 kbps and noticeable only on critical listening below 128 kbps. If you have the original lossless master (WAV or FLAC), you will get cleaner output by cutting that file and converting to MP3 afterward. For everyday cutting (ringtones, podcast clips, voice memos), the transcoding loss is invisible.

If quality is critical — mastering source, archival recording, court audio, anything that might be analyzed — convert the MP3 to WAV first using the /mp3-to-wav tool, do your cut on the WAV, and convert back to MP3 (or keep the WAV as the master). This avoids stacking transcoding passes. The trade-off is file size: a 60-minute MP3 at 192 kbps is about 80 MB, the same content as WAV is about 600 MB. For one-off cuts where the result will be played on phones or laptops, skip the conversion and cut the MP3 directly — the audible difference is well below the noise floor of typical playback gear.

Desktop MP3 editors like Audacity, mp3DirectCut, and MP3 Cutter Joiner have one trick this tool deliberately does not — frame-level cutting without any re-encode. mp3DirectCut in particular is the gold standard if you want zero quality loss when cutting MP3, but it forces you to round cuts to the nearest MP3 frame (about 26ms at 44.1 kHz), it only runs on Windows, and it requires an install. For sample-accurate cuts at any timestamp, plus zero install, plus universal OS support, plus no upload — browser-based wins. For producers who care about every dB of preserved bitrate across hundreds of cuts, desktop wins. Pick based on your scale.

Most browser-based MP3 cutters upload your file to a server, cut it there, and stream the result back. That is convenient for them (server CPU is cheap and reliable) but unnecessary and intrusive. We compile FFmpeg to WebAssembly and run the cut entirely in your browser. The MP3 never crosses the network. We have no logs of what you cut, no temporary copies of your file, and no way to recover it after the page closes. This matters for leaked tracks, demo recordings, NDA-covered material, voice memos with personal details, and any other audio you would rather not hand to a third-party server.