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.
Can I remove a section from the middle instead of keeping one?
+
Yes — cut the piece before it and the piece after it, then merge the two results. That is deliberately two steps because it keeps both halves on the fast, lossless path instead of forcing a full re-encode.
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.
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.
Is there a file size limit on Audio Cutter?
+
Yes: free accounts process audio up to 15 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.
Why does a PNG site host Audio Cutter?
+
PNG.to is built around the format you use when you cannot afford to lose a pixel: lossless, alpha-capable, and the correct answer for screenshots, logos, line art and anything with hard edges. Image work is rarely one step: people arrive to change a format and leave needing the picture a different size, a different weight or a different shape. Running Audio Cutter on the same upload pipeline, the same size caps and the same account is the whole reason it is here rather than on a fourth tab.
What should I do with the result once Audio Cutter is finished?
+
The converter on this site moves images to and from PNG, JPG, WebP, GIF and SVG — which is the step where the decision about transparency actually gets made. That is the step most people actually came for, and doing it after Audio Cutter rather than before it means the conversion works from the file you finally settled on.
Is Audio Cutter here the same tool the sibling sites run?
+
The engines are shared — the same libraries, the same workers, the same limits. What differs is the advice, and the advice here starts from one fact about the format this site is named after: there is no quality slider to get wrong — a PNG round-trips bit-exactly, so the only thing edits cost you is file size. A PNG site is opinionated about where PNG is the right destination and where it is not, and that judgement is worth more than the button.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, and nothing you process is indexed, listed or used for anything else. Free accounts exist for history and batch size, not for access.
