How to Use Video Trim: A Complete Guide
Video Trim reads and processes the selected file inside the browser. This guide describes the current interface and the exact trade-off between its two export modes; it does not assume that every codec inside a recognised container will work.
1. Choose a file
Open the video trimmer and select the upload area, or drag a file onto it. The initial file check recognises MP4, M4V, MOV, WebM, MKV, OGG and AVI container signatures. That check prevents an unrelated file renamed to .mp4 from reaching the processing engine.
A container is only the outer wrapper. Browser preview and export also depend on the video and audio codecs inside, so recognition is not a universal compatibility promise. Check the current compatibility notes if a file is important or unusual.
2. Set the clip boundaries
After the browser loads the metadata, the timeline covers the full duration. Drag the cyan start and end handles, use the keyboard arrow keys while a handle is focused, or enter decimal seconds in the labelled Start and End fields.
Use the white playhead to inspect the selected range. Playback stops at the end boundary and returns to the start, which makes it easier to check a short loop without repeatedly seeking.
3. Pick the correct trim mode
Lossless uses FFmpeg stream copy. The encoded video and audio are copied instead of recompressed, so this is normally the fastest mode and does not add another generation of picture loss. The limitation is structural: a stream-copy cut starts on a nearby keyframe, and the original streams must be valid inside the MP4 output container.
Accurate re-encodes the video as H.264 with CRF 20 and the veryfast preset, and converts audio to AAC at 192 kbps. Re-encoding lets the cut land on the selected frame and makes the MP4 streams more broadly compatible, but it takes longer and changes the compressed picture and sound.
For removing silence or shortening a recording, try Lossless first. Use Accurate when the exact opening frame matters more than avoiding recompression. The guide to keyframes and lossless trimming explains why the two results can start at slightly different moments.
4. Export and download
Select Trim Video. The first export also loads the local WebAssembly processing engine, so it can take longer than a later export in the same browser session. The progress indicator measures the processing stage; there is no video-upload stage.
When processing finishes, select Download to save trimmed_video.mp4. If the export fails, keep the error message and the source container and codec details. Do not email private footage; the contact page explains what diagnostic information is useful.
Practical limits
There is no account-level file-size cap, but the browser still needs memory for the input, processing engine and output. Phones usually reach that ceiling sooner than laptops. If a large export stops, try a shorter source file, close memory-heavy tabs, or use a desktop browser.
The engine loader requires JavaScript, WebAssembly and DecompressionStream. The implementation targets Chrome 80+, Firefox 113+ and Safari 16.4+ for that decompression step. Actual media preview support can be narrower because it depends on the codecs your browser and operating system expose.
Verify the local-processing claim
Open the browser developer tools, select the Network panel, clear it, and then trim a non-sensitive test file. Requests may appear for the site assets and FFmpeg engine, but the selected media file is represented by a local blob: URL and is not posted to an application server. Once the engine has loaded, you can also disconnect the network and repeat the trim.
Technical references
- FFmpeg: stream copy — Why copied streams avoid recompression.
- MDN: DecompressionStream — The browser API used to load the compressed engine.