2Drag the start and end handles on the waveform or the timeline, or type exact timecodes if you already know them.
3Preview the selection and run the cut — the part you keep is copied through untouched wherever the format allows it.
4Download the trimmed Audio file.
Audio Cutter FAQ
Does the format limit where I can cut?
+
It does. this format is read and written by the same streaming pipeline as everything else we support. That is precisely what decides whether a cut can be placed arbitrarily or has to land on a structural boundary.
Anything specific to Audio when trimming?
+
Yes — the codec is detected from the stream, so a mislabelled extension does not derail the job. It explains most of the "the cut is a fraction of a second off" surprises.
How does Audio Cutter cut the file?
+
Concretely, the cut is stream-copied where the codec allows it and sample-exact where the source is lossless, so you get the cheapest correct path for the file you actually uploaded. You set the start and end points on the waveform or the timeline and keep what is between them.
How precisely can I place the start and end points?
+
You can type exact timecodes rather than only dragging, and the preview scrubs to the position as you move it. How exact the result can be depends on the format: some allow a cut anywhere, others snap to the nearest frame or keyframe.
Do tags and cover art survive?
+
Yes — ID3, Vorbis comments and MP4 atoms are carried across along with embedded artwork, so processed files still sort correctly in a music library.
Which audio formats does Audio Cutter accept?
+
MP3, WAV, AAC, M4A, FLAC, OGG, Opus, WMA and AIFF. Codecs are detected from the stream rather than the extension, so a mislabelled file still works and a mixed batch is handled per file.
Is there a file size limit on Audio Cutter?
+
Yes: free accounts process audio up to 200 MB per file whichever codec you brought; ffmpeg handles the decode and encode. In practice that limit only bites on uncompressed WAV; a compressed file of the same length is nowhere near it.
Will Audio Cutter lower the quality of my audio files?
+
It depends on the source. Lossless input (WAV, FLAC, AIFF) is edited sample-exactly and loses nothing. Lossy input has already discarded detail once, so where the job can be done by copying the encoded stream rather than re-encoding it, that is the path taken.
Why would a modern-format site run Audio Cutter?
+
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Audio Cutter is on the same upload and the same account so those questions get answered in one place.
Once Audio Cutter has run, what is worth doing next?
+
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
Do the sibling sites run something different?
+
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
What happens to my file, and is an account required?
+
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.
