How to Trim a Video Online

You recorded a 10-minute video but only need the middle 45 seconds. Or a meeting recording has 5 minutes of dead air at the start. Trimming cuts a video down to exactly what you need, no complicated editing software required. A browser-based trimmer handles the entire job locally using WebAssembly, with no server upload of your potentially-sensitive video.

How to trim a video online

1. Upload your video: select the file you want to trim. The tool accepts MP4, WebM, MOV, AVI, and other common formats.
2. Set start and end times: drag the timeline handles or enter exact times. The video player previews your selection in real time.
3. Download the trimmed clip: choose your trimming mode and download the result.

Fast mode vs. precise mode

Fast mode (stream copy):

• Instant processing, no re-encoding
• Original quality preserved exactly
• Cut points may be off by 1-2 seconds (lands on nearest keyframe)
• Best for: removing large sections, rough cuts, quick extractions

Precise mode (re-encode):

• Takes longer (depends on video length and your device)
• Frame-accurate cut points, exactly where you set them
• Minimal quality difference at default settings
• Best for: clean cuts, clips for presentations, content that will be published

For most uses, fast mode is the right choice. Use precise mode only when the exact start and end frames matter.

Why fast mode is fast: keyframes explained

Modern video codecs (H.264, H.265, AV1, VP9) use inter-frame compression: most frames are stored only as the difference from a nearby reference frame, not as a full picture. The reference frames are called keyframes (or I-frames in MPEG terminology). They appear every 1-10 seconds depending on the encoder settings.

Fast trimming works by removing data outside your cut points without decoding anything. The output starts at the nearest keyframe before your cut and ends at the nearest keyframe after. No re-encoding means no quality loss but also limited precision.

Precise trimming decodes every frame back to raw pixels, applies your cut at the exact frame, then re-encodes from there. This takes more CPU and slightly degrades quality (re-encoding is lossy), but lets you cut on any frame.

Most browsers can trim a 10-minute 1080p MP4 in fast mode in under 5 seconds (it is essentially file I/O). Precise mode on the same clip might take 30-60 seconds depending on your CPU.

A brief history of digital video editing

Early digital video editing (1990s) required expensive hardware: Avid Media Composer cost $50,000+ for a complete edit suite. Trimming a clip meant capturing it to disk, importing into the timeline, dragging in/out points, and rendering the output. The whole flow took hours for any meaningful change.

Consumer-grade non-linear editors (Final Cut Pro 1999, Adobe Premiere Elements 2003, iMovie 1999, Windows Movie Maker 2000) made trimming accessible to home users. By 2010, every phone could trim its own video clips directly without exporting to a desktop.

WebAssembly (2017) made high-performance video editing possible in the browser. FFmpeg compiled to WebAssembly (ffmpeg.wasm, released 2020) brought the same trimming, transcoding, and effect capabilities as desktop FFmpeg, running entirely client-side. A browser-based trimmer today can match the functionality of Premiere Elements from 10 years ago, with zero installation and complete privacy.

Common trimming tasks

• Remove intro/outro: cut dead air, countdown screens, or branding from the start or end
• Extract a highlight: pull out the best moment from a longer recording
• Meet file size limits: a shorter video is smaller, helping you fit under upload limits
• Clean up recordings: remove mistakes, pauses, or irrelevant sections
• Make a teaser: pull a 15-30 second snippet from a longer video for social promotion
• Create chapters: trim a long video into multiple shorter clips for separate uploads
• Bug reports: trim a long screen recording down to the moment a bug occurred
• Educational content: extract a specific lecture moment for a study aid

Platform upload size limits

Trimming to fit a platform's limit is one of the most common reasons:

Choosing the right output format

After trimming, the format matters:

• MP4 (H.264): universal compatibility, plays everywhere, ~80% the size of original recordings.
• WebM (VP9 / AV1): ~30% smaller than MP4 at similar quality. Native in Chrome/Firefox, not in older iOS.
• MOV (H.264 in QuickTime container): same compression as MP4 but with Apple-friendly metadata. Mostly indistinguishable from MP4 in 2026.
• GIF: bigger than MP4 for the same content, no audio, but plays inline in places MP4 cannot.

If you do not know the destination, use MP4. If you control where it plays and want small files, use WebM.

Common pitfalls

• Cut points drift with fast mode: a 1-2 second offset can crop important content. If precision matters, use precise mode.
• Audio is offset from video: precise-mode trimming on some codecs (AAC audio in particular) can produce a slight audio-video desync. Modern tools handle this, but verify before publishing.
• HDR videos lose tone-mapping: trimming an HDR video can produce flat-looking output if the destination does not support HDR. Convert to SDR after trimming if needed.
• VFR (variable frame rate) issues: screen recordings often use variable frame rate, which confuses some trimmers and produces a "frozen" first second. Re-encode with constant frame rate before trimming if you hit this.
• Audio-only segments lose video: if your trim covers an audio-only section (e.g. a pause where the camera was off), some trimmers will silently drop the entire trim. Verify the duration of the output matches your selection.
• Subtitles lost on trim: external subtitle tracks (SRT, VTT) are not automatically trimmed in sync. You will need to manually adjust subtitle timestamps.
• Large files crash the browser: clips over ~2 GB may run out of browser memory. Trim in batches or use a desktop tool for very large source files.

Tips

• Preview before processing: use the "Set to current" buttons to mark trim points while watching the video. This is faster than typing timecodes manually.
• Trim before compressing: if you need both a shorter and smaller file, trim first, then compress. Compressing a shorter clip is faster and gives better results.
• Use fast mode by default: unless you specifically need frame-perfect cuts, fast mode saves significant processing time with no visible difference.
• Keep the original: trimming creates a new file, so your original video is safe. But it is good practice to verify the trimmed result before deleting the source.
• Add a small buffer: when trimming for content (vs file size), add 0.5 seconds before and after your target. Hard cuts on the first/last frame of dialogue feel abrupt.
• Trim then crop: if you also need to crop the video (change aspect ratio), trim first to minimize re-encoding work.

Privacy and sensitive video

The video trimmer runs entirely in your browser using WebAssembly. The source video you upload, the intermediate processing data, and the trimmed output all stay on your device. Nothing is uploaded to a server.

This matters because videos often contain very sensitive content: personal recordings, family moments, customer screen recordings, internal company demos, security footage, medical-grade video. Cloud trimmers necessarily upload your video to their servers, where it may be retained for "service improvement" or accessible to employees. A browser-based trimmer has zero exposure: the video never leaves your machine.

Browser-based trimming also works offline once the page is loaded, useful for editing on flights or in low-connectivity environments. The only network call is the initial page load.