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

Video Cutter

Cut videos to a Start and End Point

Choose 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)

Transform 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.
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.
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.
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.
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.
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.
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. Video Cutter shares the upload, the caps and the account with the conversions for that reason.
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.
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.
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.

Rate this utility
5.0/5 - 0 votes
ns6.com — Your domain, done right. Free privacy and DNS included.
Or release your files here