Choose a file to convert. It's processed locally — never uploaded. Tip: add several files to convert them all at once.
Settings
Result appears here after you select
{ } How to use
- Choose the video.
- Enter the start and end times, either in seconds or as hh:mm:ss.
- Select Process, then download the clip.
{ } How it works
Trim Video works on the file you upload. Adjust the options, then select Process ▸ and it runs entirely in your browser — nothing is uploaded to a server — then shows the result in the Output panel.
Inputs
- Video file — upload a file (video/*); it is read locally in your browser
- Start (s or hh:mm:ss) — a value (default: "0")
- End (s or hh:mm:ss) — a value (default: "10")
Output
A downloadable MP4 file — use the Download button in the Output panel.
{ } Common uses
- Cut one moment out of a long recording.
- Remove a slow start or a dead ending from a clip.
- Shorten a video to fit a platform’s time limit.
{ } Limitations
- The streams are copied rather than re-encoded, which is what makes this fast and lossless — and it also means the cut can only land on a keyframe. The clip may start a little earlier than the time you asked for, by up to several seconds on footage with widely spaced keyframes.
- The container is read from the file’s own bytes rather than its name, and kept: MP4, MOV and WebM are trimmed as they are. Anything else is re-encoded into MP4, which is slower and costs a generation of quality, but never fails for want of a guess.
- A start time past the end of the clip produces nothing rather than an error, and the tool says so.
{ } FAQ
Is my data uploaded to a server?
No. Everything runs locally in your browser — your files never leave your device.
Can I process more than one file at once?
Yes — add several files and they’re all processed and downloaded together as a ZIP.
Is this tool free?
Yes — it’s completely free and needs no sign-up.
Why does my clip start before the time I entered?
Because trimming copies the video stream instead of re-encoding it, and a copy can only begin at a keyframe. The engine seeks to the nearest keyframe at or before your start time, so you get slightly more than you asked for rather than a broken first second. Footage from phones and screen recorders often has keyframes several seconds apart, which is when this is most obvious.