Audio Trimmer & MP3 Cutter

Yes. No signup, no credit card, no daily quota and no watermark or voice-over on the clip. The cut runs on your own computer, so there is no server bill for us to pass on to you.

No. The file is read straight from your disk and cut by a WebAssembly build of FFmpeg running inside the tab. You can check it yourself: open DevTools, switch to the Network panel and trim something — you will not see your file being sent anywhere.

MP3, WAV, M4A, AAC, OGG, Opus and FLAC, plus the audio track of an MP4 or WebM if your browser can read it. Cutting an MP3 is by far the most common job here, and you can save the result as MP3, WAV or M4A whatever the source was.

Up to 200 MB, which is several hours of a normal podcast. The engine has to hold the file in browser memory, so anything bigger is refused with a clear message instead of freezing the tab. Very long files are still drawn as a waveform, just at a coarser resolution.

Only as much as re-encoding costs. The cut is made from your original file, never from the waveform preview, so nothing is resampled twice. Export to WAV for a lossless copy, or to MP3 at 320 kbps if you want a small file that stays close to the source. Cutting a 128 kbps MP3 and saving it at 320 kbps will not add back detail that was never there.

One file at a time, on purpose. The engine keeps the whole file in memory, and running several 200 MB jobs in parallel would push most tabs over their limit. When a clip is done, click "Trim another" and load the next one.

Yes, in any modern mobile browser. The handles respond to touch, and the numeric time fields are there for when your finger is not precise enough. Keep the selection reasonable — a phone has less memory than a laptop, and a 200 MB source can be too much for older devices.

Select the hook you want and press the Ringtone preset — it caps the selection at 30 seconds and adds a one-second fade-out. On Android, export MP3 and set it from Settings → Sound, or from the Files app. An iPhone needs an .m4r, and that is no barrier here: our ringtone maker writes one directly, because an .m4r is simply the AAC audio an .m4a already holds, under the extension iOS looks for. No renaming step, and nothing to install.