Audio Trimmer and Clip Cutter failed, stalled, or looks wrong? Troubleshooting
Troubleshoot Audio Trimmer and Clip Cutter by codec, container, parameters, memory, and browser while respecting quality and device boundaries.
Do not rename an extension to fake a format
An extension names a container, not a guaranteed video/audio codec. Keep the source and record size, duration, codec, dimensions, browser, and exact error. Never overwrite the only original repeatedly.
The easy-to-miss issue for this tool
For 02:15–03:00 of a podcast, current output is MP3 only with no WAV or fade control. Adjust boundaries if an edge clicks.
Recommended troubleshooting order
- Load a very short, low-resolution known-good sample to confirm the tool starts.
- Check whether duration, video, audio, and dimensions are detected; missing metadata often means damage or an unsupported codec.
- Reduce duration, resolution, frame rate, or simultaneous file count.
- Close heavy tabs, retry in current desktop Chrome/Edge, and keep the page active.
- Reapply the workflow:
- Choose audio and wait for its complete duration.
- Enter start and end times.
- Set MP3 audio bitrate and start trimming.
- Check edges, clicks, and actual duration before download.
- If it still fails, use desktop FFmpeg or the producing application; do not claim browser support for that codec.
Parameter checks
- Start time
- End time
- MP3 output; WAV and fade controls are not currently available
Common errors
Why is there a click at the edge?
A non-zero-crossing cut can jump. The current page has no fade control, so adjust the start/end position.
Can MP3 be cut losslessly?
Some frame-aligned copies are possible, but this workflow may re-encode for timing and compatibility.
Is audio uploaded?
Media is read and transcoded in this browser tab and is not uploaded to FreeTool to perform the task.
Boundaries that cannot be bypassed
- Current output is MP3 only, not WAV
- Compressed-frame boundaries can differ by milliseconds
- No fades, noise reduction, or multitrack editing
Browser WASM lacks the full performance and codec set of native apps, and long video can take substantial time. A paused progress display does not mean server upload; processing is in the tab, but the browser can terminate it under memory pressure.
Privacy, rights, and open-source licenses
Media is read and transcoded in this browser tab and is not uploaded to FreeTool to perform the task. Troubleshooting images and outputs can still contain private, copyrighted, or hidden metadata. The ffmpeg.wasm wrapper is MIT and this release's FFmpeg core is GPL-2.0-or-later; source access and license notices must not be removed.