A video cutter is a tool that removes unwanted portions from a video file or extracts a chosen segment as a standalone clip. The quickest way to do this without uploading anything is to use a browser-based tool such as Video Trimmer, which decodes your local file, accepts start and end times in seconds, and re-encodes the selected range into a new WebM file you can download right away. Every step happens inside your current tab, so the source video stays on your device and is never transmitted to a remote server. For most everyday clip-cutting tasks — pulling a highlight from a longer recording, trimming dead air off the beginning or end, or slicing out a single scene — this local approach is faster and more private than installing desktop software or handing your footage to an upload-based service. The trade-off is real: browser-based cutters trade a narrower format list and an approximate cut for a workflow that takes seconds to start and leaves your footage untouched on disk.
What a Video Cutter Does to a Local File
At its core, a video cutter performs three jobs: it reads the source file, decides which portion of the timeline to keep, and writes that portion to a new file. The interesting differences between tools come from how each step is implemented. Some cutters work entirely on your device using the operating system's media frameworks. Others upload the file to a remote server, run a server-side encoding command, and return the trimmed clip as a download. A third category — and the one this article focuses on — uses the browser's built-in media APIs to decode and re-encode the source without ever leaving your tab.
Video Trimmer belongs to that third category. According to its verified behavior, the tool accepts a local file, parses its decoded metadata, seeks to the requested start time, captures the browser-exposed media stream, and records until the requested end. Because the recording happens while the media element plays back, the cut is a real-time re-encode, not a packet-level lossless slice.
How a Local Browser Cutter Compares to Upload-Based Tools
Upload-based cutters tend to advertise longer format support, frame-accurate cuts, and MP4 output. They earn that flexibility at a cost: your source file is transferred to someone else's infrastructure, stored for some window of time, and processed by software you don't control. For personal clips, internal recordings, or anything under NDA, that trade-off is often unacceptable.
A local browser cutter like Video Trimmer inverts the trade-off. Privacy and speed come first; the format menu is narrower and the cut is approximate. If you want a deeper comparison of how a no-upload workflow feels in practice, the guide on cutting a clip without uploading the original file walks through the same task with a slightly different lens.
What Video Trimmer Accepts and What It Outputs
Before you cut anything, it helps to know exactly what the tool will and won't swallow. The verified limits are tight and worth memorizing:
| Attribute | Limit or behavior |
|---|---|
| Input containers | MP4, WebM, MOV, M4V, Ogg |
| Input file size | Up to 500 MiB |
| Decoded duration | No longer than five minutes |
| Decoded width or height | No wider or taller than 4096 px |
| Decoded total area | No greater than 3840 × 2160 px |
| Output container | WebM |
| Output codecs | VP9, VP8, or optional Opus combination chosen by the browser |
| Output dimensions | Preserved from source |
| Minimum clip length | 0.1 seconds |
A familiar extension is not a guarantee of success. The current browser must decode the actual codecs inside the container, not merely recognize the filename. If a player can't decode the codecs in your MP4, Video Trimmer won't be able to either.
Cut a Video Clip with Video Trimmer
The cut itself takes three deliberate steps. Each one depends on the previous step completing cleanly, so don't rush past the duration readout.
- Choose one supported local video and wait for its duration to populate. The decoded metadata drives every later input.
- Enter start and end times as decimal seconds, keeping the range inside the source duration. The start must be zero or greater, the end must be later than the start and no later than the decoded duration, and the selected clip must be at least 0.1 seconds. Milliseconds are accepted.
- Select Trim video, review the reported clip duration and output size, and download the resulting WebM file. Invalid or reversed ranges fail visibly instead of being guessed or clamped.
For an accuracy-first read on what each step actually does under the hood, the guide on trim accuracy in local browser tools fills in the details.
Limits That Decide Whether the Cut Will Work
Most failed cuts come from one of four causes, all of which are visible before recording starts. A file over 500 MiB is outside the accepted size limit. A clip whose decoded duration runs past five minutes is rejected when the metadata is parsed. A file whose width or height exceeds 4096 pixels — common with high-resolution phone captures — fails the same way. And a file whose internal codecs the browser can't decode will fail to trim.
Two related limits are easy to miss. First, the start and end values are decimal seconds, not frames or timecodes; converting a frame number back to seconds requires knowing the source frame rate. Second, because the cut is a real-time re-encode, the last encoded frame can land a small fraction around the requested boundary. MDN's MediaRecorder documentation explains why playback-time sampling doesn't expose frame-accurate editing.
Why the Output Is Always WebM, Not MP4
Every cut from Video Trimmer comes out as a WebM file. That's not an arbitrary choice; it's a consequence of using the browser's built-in MediaRecorder. The recorder selects the first supported configuration from the browser's available VP9, VP8, and optional Opus combinations. To use a different container you'd need to ship a large media-processing dependency or perform the encode on a server — both of which would change the privacy story entirely.
The WebM file you download carries the selected duration in its Segment Info so compatible players report a finite timeline. Dimensions are preserved, but quality, keyframes, color metadata, audio layout, and file size may differ from the source. If you need an MP4 for delivery, plan to convert the WebM afterwards with a dedicated tool.
When a Desktop Editor Still Wins
A browser video cutter is the right tool for the tasks it handles: short clips, quick highlights, and any work where keeping the file local matters more than frame precision. It is not the right tool for broadcast delivery, exact keyframe-aligned cuts, subtitle preservation, multitrack audio, footage longer than five minutes, or any workflow that requires an MP4 codec on the first pass. For those jobs, install a dedicated desktop editor and inspect the exported timeline before you commit. Use only video you own or have permission to edit, regardless of which tool you choose.
Browser Cutter vs. Desktop Editor at a Glance
The trade-offs above become easier to compare side by side. The following table pairs common tasks with the tool that fits each one, based on what the browser cutter is verified to do and what it explicitly hands off to a desktop editor.
| Task or requirement | Browser video cutter (Video Trimmer) | Desktop editor |
|---|---|---|
| Cut a clip up to five minutes from a local file | Yes | Yes |
| Cut a clip longer than five minutes | No — exceeds the decoded duration limit | Yes |
| Frame-accurate or keyframe-aligned boundary | No — real-time re-encode, approximate boundary | Yes |
| Output as MP4 directly | No — WebM only | Yes |
| Preserve every metadata field from the source | No — only dimensions are preserved exactly | Yes |
| Multitrack audio or subtitle pipeline | No — single-track capture without subtitle handling | Yes |
| Keep the source off remote servers | Yes — runs entirely in the current browser tab | Yes (local install) |
Use the table as a quick triage step before you open a tab or an installer. If every row points to the browser side, the cut will land inside its verified limits and you can proceed with Video Trimmer. If even one row demands the desktop column — long footage, exact keyframes, MP4 output, full metadata, or multitrack audio — skip the browser step and go straight to a dedicated editor.