Trimming a video means selecting a bounded segment between a chosen start and end timestamp, then exporting just that portion as a new file. To get started, you open the Video Trimmer tool in your browser, choose a supported local video, type two timestamps, and download the resulting WebM clip without ever uploading the source. The whole process runs in the current browser tab, so the only prerequisites are the file sitting on disk, a current browser, and a rough idea of the section you want to keep. If you have never trimmed a video before, the path from an untouched recording to a finished short clip is just four actions, and the rest of this guide walks through each one in plain language. You will also learn what the tool does not do, because trimming in a browser has real limits around codecs, duration, and output format, and ignoring those limits is the fastest way to get a file that does not play back the way you expected.
Trimming vs Cutting: The One Thing This Tool Does
Trimming is the narrowest possible edit: keep a continuous range and throw away the rest. There are no cuts in the middle, no fades, no transitions, and no re-timing. The Video Trimmer does exactly that one operation, then exports the result. Because the tool runs inside a browser tab using the built-in media decoder and MediaRecorder API (documented on the MDN Web Docs MediaRecorder reference), the source file is never sent to a server. Decode, stream capture, re-encoding, and the final download all happen on your own machine.
This matters because "trim" is often confused with three other jobs: cutting (which can mean removing a section in the middle), cropping (which shrinks the visible frame), and resizing (which changes the frame dimensions). The Video Trimmer only does the first job. It will not split a video into pieces, shrink a frame, or strip audio. If your goal is to remove a middle section, you have to trim twice: once for the front half, once for the back half, and then line the two WebM clips up downstream.
What You Need Before You Open the Tool
Before you start, the file on disk has to clear four hard limits, all of which are checked when the tool reads the duration:
| Property | Accepted value |
|---|---|
| Container | MP4, WebM, MOV, M4V, or Ogg |
| File size | Up to 500 MiB |
| Decoded duration | No longer than five minutes |
| Frame dimensions | No wider or taller than 4096 px; total area no greater than 3840 × 2160 px |
Two extra notes deserve attention. First, a familiar file extension is not a guarantee — the browser must also be able to decode the actual audio and video codecs inside the container. An MP4 with a codec the browser does not support will fail at the duration step, even though the filename is on the menu. Second, "five minutes" refers to the duration the browser can decode, which is usually the same as the source duration but can be shorter if the source uses tricks the browser cannot play back locally.
For a first session, pick a short clip you already trust — something under two minutes that you have played locally without trouble. That removes every variable except the ones you actually want to learn: how the inputs behave, what the output looks like, and how long a real trim takes to render.
Trim a Video From Scratch
Once your file passes the checks above, the trim itself takes four concrete actions. Work through them in this order.
- Choose one supported local video. Use the file picker to select a single MP4, WebM, MOV, M4V, or Ogg from your computer. Do not pick multiple files at once and do not point the tool at a URL — the tool only reads local files in the current browser tab.
- Wait for the duration to populate. After the file is selected, the tool reads the container and reports the total decoded duration. Until that number appears, the start and end inputs are not yet ready to accept values, because the end has to be checked against a real upper bound.
- Enter start and end times in seconds. Type two decimal numbers, for example 15.5 and 47.25. The start must be zero or greater, the end must be later than the start and no later than the decoded duration, and the resulting clip must be at least 0.1 seconds long. Milliseconds are allowed in both fields. If the range is reversed or too short, the tool reports a visible error rather than guessing or clamping the values for you.
- Select Trim video, review the reported clip duration, and download the WebM file. After trimming, the UI shows the requested duration and the output size. If those numbers match your plan, click download to save the WebM clip. Use Cancel if you need to stop an in-progress encode.
Worked example for the third step: a 120-second source clip where you want the middle section, from 15.5 s to 47.25 s. The output duration is 47.25 − 15.5 = 31.75 seconds, which is well above the 0.1-second minimum. Enter those two numbers, trim, and the downloaded WebM is a 31.75-second clip.
To make the boundaries easier to set, it helps to know what kinds of ranges the tool is designed to accept:
| Range shape | Start | End | Meaning |
|---|---|---|---|
| Zero-based | 0 | any positive value | Keep from the very first frame |
| Middle | greater than 0 | less than duration | Keep a section from inside the source |
| Fractional | any decimal | any decimal | Keep a partial second at either boundary |
| Tail | any value | equal to decoded duration | Keep right up to the last frame |
| Five-minute boundary | any value | equal to 300 | Keep up to the longest allowed source |
What You Get Back: The WebM Clip Explained
The download is a fresh WebM file, not a slice of the original. The width and height of the frame are preserved, but the clip is re-encoded in real time during playback using the browser's MediaRecorder, picking the first supported configuration from the VP9, VP8, and optional Opus combinations the browser exposes. That means a few properties are guaranteed to change even when the visible content looks the same:
- Codec and container: always WebM with a VP8 or VP9 video track.
- Quality and bitrate: set by the recorder, not inherited from the source.
- Keyframe placement: regenerated by the encoder.
- Audio layout: may be re-mixed or dropped if the recorder does not advertise the same channel count.
- Color metadata, timecodes, subtitles, and side data: not preserved.
One detail worth noting: the generated WebM is patched so its Segment Info records the chosen duration, which is why compatible players show a finite timeline instead of an open-ended stream. That patch is what lets the file behave like a normal clip in chat apps and social uploaders that read the container first.
First-Time Errors and Why They Happen
Most first-time failures cluster around four causes. Knowing them up front saves a lot of guessing.
The duration field never fills in. The container parsed, but the codecs inside cannot be decoded by this browser. Try a different file or open the same clip in the browser directly — if it does not play there, no browser-side tool will trim it.
The tool rejects the range with a visible error. The end is not later than the start, the clip is shorter than 0.1 seconds, or the end is past the decoded duration. The tool does not silently clamp, so the message tells you exactly which rule was broken.
The downloaded WebM is much smaller than the source. That is expected. The recorder re-encodes with its own quality settings, so a 200 MiB MP4 can become a 30 MiB WebM without any data loss in the visible content — just a different codec decision. If the file is dramatically too small, the recorder fell back to a low-bitrate configuration and you should consider a desktop editor with explicit rate control.
The last frame lands a fraction of a second off the requested boundary. This is the documented limit of real-time browser capture. MediaRecorder samples playback time and does not expose frame-accurate editing, so the encoded end can land a small fraction before or after the requested timestamp. For social clips this is invisible; for broadcast delivery or exact cuts on a known keyframe, use a desktop editor.
When a Browser Trim Is Not Enough
A browser trim covers a large share of everyday tasks — shortening a recording for a message, cutting a tutorial intro, clipping a moment for a tweet. It is not the right tool when any of the following apply:
- The source is longer than the five-minute decoded limit.
- The output must be MP4 with a specific codec for a downstream pipeline.
- The cut must land exactly on a known keyframe.
- Subtitles, multiple audio tracks, or surround sound have to be preserved.
- The source is protected by DRM, which the tool explicitly does not bypass.
For those jobs, move to a dedicated desktop editor and inspect the exported timeline yourself. For everything inside the limits, the browser-based Video Trimmer is the fastest way to get from a long source file to a short clip without installing anything or uploading a single byte. If you would rather start by thinking about whether trimming is the right move at all, the guide how to decide if you actually need to trim a video walks through that question first.
Related reading: How Do I Plan the Steps Needed to Trim Video.