Free tool

Trim a video without uploading it

Drag two handles, get the part you wanted. Both ends cut on the exact frame you chose, not on the nearest key frame, and the file never leaves your machine.

Your file never leaves this tab. It is read, edited and written by your own browser, so nothing is uploaded and nothing is stored.

Why this one

What this tool gets right

Frame-exact cuts

Your start point is your start point. Tools that only ever copy frames have to slide the cut back to the previous key frame, which can be a second early.

Millisecond handles

Drag on the filmstrip for the rough cut, then type the timecode for the frame you actually meant. Both ends are editable.

Nothing to upload

A one gigabyte source opens as fast as a one megabyte one, because only the container headers are read until you press export.

Trim, then keep going

Crop, resize, rotate or change the format in the same pass. One decode, one export, instead of four round trips through four tools.

How it works

Three steps, about thirty seconds

01

Drop the file in

Choose a file or drag it onto the page. It opens straight away, because there is nothing to upload.

02

Set it up

Drag the handles or type exact numbers. The preview applies the same operations in the same order the encoder will.

03

Export and download

Your machine does the encoding, with a real progress bar. The file lands in your downloads folder, unmarked.

Why a browser trimmer beats an upload site

Every free trimming site with an upload button is paying for bandwidth, storage and CPU, and it recovers that cost somewhere: a watermark, a queue, a five minute cap, a signup wall, or an ads page you watch while your file sits on someone else's disk. This one has no such cost, because your machine does the work. That changes the shape of the tool as much as the price. There is no upload progress bar, no processing queue and no download step where the site hands your file back to you. There is also nothing to delete afterwards, because no copy was ever made.

Key frames, and why the start of a cut is the expensive end

Video is not stored as a stack of complete pictures. Every few seconds there is a key frame that stands on its own, and everything between is described as the difference from what came before. Cut at the end and the frames you keep still have their key frame, so they can be copied across untouched. Cut at the start and the frames you keep are describing changes to a picture you just deleted. There are only two ways out of that. Move the cut back to the previous key frame, which is fast and up to a couple of seconds off. Or decode and re-encode from your exact point, which is what this tool does, so the cut lands where you put it. The export button says which of the two is about to happen, and the quality setting under Output controls what the re-encode is allowed to spend.

What this tool will not do

  • It will not fetch a video from YouTube, TikTok, Instagram or any other platform. You have to have the file.
  • It will not repair a corrupt or partially downloaded file. If a player cannot open it, neither can this.
  • It will not add anything to the picture: no captions, no logos, no filters. It edits the file you brought.
  • Speed is your hardware. A long 4K clip on a phone will take minutes where a laptop takes seconds.

Questions, answered

It depends which end you move. Cutting only the end copies the existing frames straight across: instant, and pixel for pixel identical. Moving the start re-encodes, because the frames after your cut are described relative to earlier ones that are about to be thrown away. That re-encode is what makes the cut land on the frame you picked instead of sliding back to the previous key frame, which is the compromise most fast trimmers make silently.
Not in one pass. The trim keeps one continuous range. To drop a middle section, export the part before it, then the part after it, and join the two in an editor.
Yes. MP3, WAV, OGG, FLAC and M4A all load, and the same handles apply. There is no filmstrip, but the timecodes work the same way.
No. The file is opened by your browser with the File API and rewritten with WebCodecs, the same video machinery your browser uses to play a video. Nothing is sent to a server, so there is no upload wait, no queue and no copy of your file sitting in someone's storage bucket.
There is no limit we impose. The practical ceiling is your machine: the file is read in small pieces rather than loaded whole, so multi-gigabyte sources open instantly, and if you turn on 'write straight to disk' the result never has to fit in memory either. On a phone, expect long clips to be slow.
None of the three. Because the work happens on your machine, this costs us nothing to run, so there is nothing to gate. You get the file you made, unmarked.
Anything current: Chrome, Edge, Safari 17 and up, and Firefox 130 and up. The tools use WebCodecs, so a very old browser will report that it cannot encode, rather than producing a broken file.

Words are the easy part. Advibly makes the creative.

Advibly turns your brand into finished ads: product-in-hand UGC videos, static image ads, carousels, and explainers. Same thinking as this free tool, pointed at the thing that actually takes time.