Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Video Cutter

Free Online Video Cutter and Trimmer

Go with your files

*Files deleted after 24 hours

Specify the start and end time for the portion you want to keep.

Format: HH:MM:SS (e.g., 00:01:30 for 1 minute 30 seconds)

Optimize up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Cut and Trim Video

1 Upload the videos you want to cut.
2 Drag the start and end handles on the waveform or the timeline, or type exact timecodes if you already know them.
3 Preview the selection and run the cut — the part you keep is copied through untouched wherever the format allows it.
4 Download the trimmed Video file.

Video Cutter FAQ

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.
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.
Concretely, the cut is stream-copied at a keyframe boundary wherever possible, so most clips trim in seconds regardless of how long the source was. You set the start and end points on the waveform or the timeline and keep what is between them.
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.
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.
MP4, MOV, MKV, WebM, AVI, WMV, FLV, 3GP, M4V, MPEG and MPG. Each file is probed for its real container and codec before anything runs, so a mixed batch is handled correctly file by file.
Yes: free accounts process video up to 1 GiB per file whichever container you brought; ffmpeg with x264, x265 and libvpx does the encoding. It is high enough that upload speed is usually the binding constraint rather than the cap itself.
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.
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Video Cutter is on the same upload and the same account so those questions get answered in one place.
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.

Rate this optimizer
5.0/5 - 0 votes
ns6.com — Buy your domain in minutes. Search, register, launch.
Or position your files here