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 M4A file.
M4A Cutter FAQ
Does the format limit where I can cut?
+
It does. M4A is an MP4 container holding AAC or ALAC audio — the default for iTunes and Apple Music files. That is precisely what decides whether a cut can be placed arbitrarily or has to land on a structural boundary.
Anything specific to M4A when trimming?
+
Yes — an .m4a can hold either AAC or ALAC, so lossy and lossless files share one extension and have to be told apart by inspection. 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.
How does M4A Cutter cut the file?
+
Concretely, the cut is made on frame boundaries and the surviving frames are copied through without re-encoding, so the audio you keep is bit-identical to the original — no second generation, and the job finishes in about the time it takes to upload. You set the start and end points on the waveform or the timeline and keep what is between them.
Can I run M4A Cutter on several M4A audio files at once?
+
Yes. Upload the set and they process in parallel with the same settings, which is the practical way to handle a podcast series or an album rather than repeating the job by hand.
Do tags and cover art survive?
+
Yes. ID3, Vorbis comments and MP4 metadata atoms are carried across, cover art included, so a processed file still sorts correctly in a music library. ReplayGain values are recalculated rather than copied, because a stale one is worse than none.
Is there a file size limit on M4A Cutter?
+
Yes: free accounts process audio up to 15 MB per file, which at typical bitrates is several hours of material; ffmpeg does the decoding and encoding, exactly as it would on a desktop. That is the most generous cap on the site after video, and audio work rarely runs into it.
Will M4A Cutter lower the quality of my M4A audio files?
+
A lossy file has already discarded detail once, and re-encoding discards more — that is generation loss and it does not undo. Wherever the job can be completed by copying the encoded stream rather than re-encoding it, that is what happens, and the audio comes back bit-identical.
Why does a Word site host M4A Cutter?
+
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. M4A Cutter shares the upload, the caps and the account with the conversions for that reason.
What should I do with the result once M4A Cutter is finished?
+
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
Is M4A Cutter here the same tool the sibling sites run?
+
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
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.
