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 MPG file.
MPG 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 precisely can I place the start and end points?
+
You can type exact timecodes rather than only dragging, and the preview scrubs to the position as you move it. How exact the result can be depends on the format: some allow a cut anywhere, others snap to the nearest frame or keyframe.
Does the format limit where I can cut?
+
It does. MPG is the same MPEG-1/2 program stream under the shorter extension, still the format of DVD-era captures. That is precisely what decides whether a cut can be placed arbitrarily or has to land on a structural boundary.
Anything specific to MPG when trimming?
+
Yes — a .mpg is the same program stream as .mpeg, and both come out of DVD-era capture hardware with interlacing still baked in. It explains most of the "the cut is a fraction of a second off" surprises.
Will MPG Cutter lower the quality of my MPG videos?
+
It depends on whether the job needs a re-encode. Operations that only touch the container or the timeline are done as a stream copy and the picture is bit-identical to the source. Anything that has to redraw frames goes through x264/x265 at a quality level you set, where CRF 23 is visually transparent on most footage.
Can I run MPG Cutter on several MPG videos at once?
+
Yes. Uploads queue in parallel, which matters more here than anywhere else because video jobs are minutes rather than seconds. Free accounts run one file at a time; a pass lifts that.
What happens to audio, subtitle and chapter tracks?
+
They are carried across. Multi-track audio, embedded subtitle tracks and chapter markers survive wherever the target container can represent them — that is the main thing that separates a proper job from a naive re-encode that silently keeps only track one.
Does MPG Cutter cost anything?
+
No. MPG Cutter is free without an account, and the output carries no watermark, no corner logo and no intro card. Uploaded video is deleted from the workers shortly after the job completes.
Why does a WebM site host MPG Cutter?
+
WEBM.to is built around the container the open web actually chose — VP9 or AV1 with Opus audio, decoded natively by every modern browser and needing no plugin, licence or player. Video is the case where extra round trips hurt most — the files are large and every upload costs real minutes. Running MPG Cutter on the same pipeline as the conversions means one upload covers the whole job instead of one upload per tool.
What should I do with the result once MPG Cutter is finished?
+
The converter on this site moves video between WebM, MP4, MKV, MOV and the rest, or pulls the soundtrack out entirely, without another upload. Sequencing it that way matters more for video than anywhere else: each re-encode is another generation, so the fewer of them stand between the source and the file you publish, the better it looks.
Is MPG Cutter here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build with x264, x265 and libvpx, the same workers, the same limits. What a WebM site adds is a view on containers and codecs: which combinations play everywhere, which need a re-encode and which can simply be copied across. It also starts from one fact about the format this site is named after: WebM is VP9 or AV1 with Opus audio, which browsers decode natively but which most desktop editors still transcode on import.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploaded video is deleted from the workers shortly after the job finishes, nothing is watched and nothing is indexed. Free accounts exist for history and batch size, not for access.
