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

Video Cutter

Cut videos to a Start and End Point

Settle on 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)

Convert 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

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.
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 — 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.
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.
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.
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Video Cutter runs on the same upload and the same account as the conversions because that is where it is needed.
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Video Cutter means the conversion is made from the version you settled on, not from the one you were still fixing.
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
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 converter

5.0/5 - 0 votes
ns6.com — Free WHOIS privacy, DNS and SSL on every domain.
Or leave your files here