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 WAV file.
WAV 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 WAV Cutter cut the file?
+
Concretely, the cut is sample-exact, so you can place the boundary precisely where you want it rather than on the nearest frame, and the surviving audio is bit-identical to the source. You set the start and end points on the waveform or the timeline and keep what is between them.
Anything specific to WAV when trimming?
+
Yes — WAV is raw PCM, so edits are sample-exact and instant, but the file is about 10 MB per stereo minute and uploads dominate the time. 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.
What can I upload to WAV Cutter?
+
WAV, FLAC and AIFF, at any bit depth and sample rate up to and including 24-bit/192 kHz. Lossy files work in the same batch if you are mixing sources.
Is there a file size limit on WAV Cutter?
+
Yes: free accounts process audio up to 200 MB per file — for uncompressed PCM that is roughly twenty minutes of CD-quality stereo, so it is a real limit here in a way it is not for MP3. If you are over it, converting WAV to FLAC first is the free fix — it is lossless and roughly halves the size.
Will WAV Cutter lower the quality of my WAV audio files?
+
No. Lossless audio is edited sample-exactly, so what comes back decodes bit-identically to what you would get doing the same edit in a desktop editor. You can repeat the cycle as many times as you like without accumulating any loss at all.
Can I run WAV Cutter on several WAV audio files at once?
+
Yes, though lossless files are large, so the batch is bound by upload bandwidth rather than by processing. Settings apply uniformly across the set.
Why does a EPUB site host WAV 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. WAV 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 WAV 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 WAV Cutter means the conversion is made from the version you settled on, not from the one you were still fixing.
Is WAV 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.