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 Video file.
Video 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. this format is read and written by the same streaming pipeline as everything else we support. That is precisely what decides whether a cut can be placed arbitrarily or has to land on a structural boundary.
Anything specific to Video when trimming?
+
Yes — the container and codec are probed before anything runs, so mixed uploads in one batch are handled per file. It explains most of the "the cut is a fraction of a second off" surprises.
Will Video Cutter lower the quality of my videos?
+
Only if the operation requires re-drawing frames. Container-level and timeline-level work is done as a stream copy, which is bit-identical to the source and finishes in seconds. Anything that must re-encode does so at a quality level you choose.
Can I run Video Cutter on several videos at once?
+
Yes, and it matters here more than anywhere else — video jobs run in minutes, so queueing the batch in parallel is the difference between one wait and several.
What happens to audio, subtitle and chapter tracks?
+
They are carried across wherever the target container can hold them, including multiple audio languages, embedded subtitles and chapter markers, rather than silently keeping only the first track of each.
Does Video Cutter cost anything?
+
No. Video Cutter is free without an account, and the output has no watermark, corner logo or intro card. Uploaded video is deleted from the workers shortly after the job completes.
Why does a WebM site host Video 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 Video 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 Video 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 Video 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.
