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.
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 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.
Does M4A Cutter cost anything?
+
No. M4A Cutter is free without an account and adds no audio watermark or spoken tag to the output. Your upload is deleted from the workers shortly after the job completes.
Is there a file size limit on M4A Cutter?
+
Yes: free accounts process audio up to 200 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.
Why does a PNG site host M4A 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 M4A 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 M4A 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 M4A Cutter rather than before it means the conversion works from the file you finally settled on.
Is M4A 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.
