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 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.
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.
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.
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.
Why does a EPUB site host Audio Cutter?
+
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Audio Cutter runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once Audio Cutter is finished?
+
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Audio Cutter means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Audio Cutter here the same tool the sibling sites run?
+
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
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, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.
