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
Is the part I keep re-encoded?
+
Not if the format allows a stream copy — the data you keep is bit-identical to the source and the job finishes in about the time the upload took. Only a frame-exact cut on a format that cannot do it cheaply needs a re-encode.
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.
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.
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.
Can I run Audio Cutter on several audio files at once?
+
Yes. The set queues in parallel with identical settings, which is how you process an album or a podcast back catalogue without repeating yourself.
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.
Does Audio Cutter cost anything?
+
No. Audio Cutter is free with no account, and nothing is added to the audio. Uploads are deleted from the workers shortly after the job completes.
Why does a WebM site host Audio Cutter?
+
WEBM.to is built around the container the open web actually chose — VP9 or AV1 with Opus audio, decoded natively by every modern browser and needing no plugin, licence or player. Video is the case where extra round trips hurt most — the files are large and every upload costs real minutes. Running Audio Cutter on the same pipeline as the conversions means one upload covers the whole job instead of one upload per tool.
What should I do with the result once Audio Cutter is finished?
+
The converter on this site moves video between WebM, MP4, MKV, MOV and the rest, or pulls the soundtrack out entirely, without another upload. Sequencing it that way matters more for video than anywhere else: each re-encode is another generation, so the fewer of them stand between the source and the file you publish, the better it looks.
Is Audio Cutter here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build with x264, x265 and libvpx, the same workers, the same limits. What a WebM site adds is a view on containers and codecs: which combinations play everywhere, which need a re-encode and which can simply be copied across. It also starts from one fact about the format this site is named after: WebM is VP9 or AV1 with Opus audio, which browsers decode natively but which most desktop editors still transcode on import.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploaded video is deleted from the workers shortly after the job finishes, nothing is watched and nothing is indexed. Free accounts exist for history and batch size, not for access.
