CapCut's split-and-delete workflow is what most people mean when they ask how to cut video in CapCut, and the same single-cut operation is available in your browser through a local Video Trimmer that decodes the source file, accepts start and end times as decimal seconds, and exports the selected range as a fresh WebM clip. The approach is built for the common case where you have a recording, a screen capture, or a downloaded clip on your computer and just want a straight cut between two timecodes — exactly the job CapCut's split handles when you trim a clip down to a highlight, a teaser, or a shareable snippet. The browser tool re-encodes the chosen range through the MediaRecorder API rather than performing a packet-level cut, so the result is a freshly encoded video file instead of a copied segment of the original. That trade-off is fine for social posts, screen recordings, and previews, and it keeps the source video entirely inside your browser tab. Read on for the exact inputs the tool accepts, the precise steps to perform a CapCut-style trim, and the cases where opening CapCut or a desktop editor is still the smarter move.
What the Video Trimmer Does Inside Your Browser
The Video Trimmer is a single-purpose browser tool that takes one local video, lets you define a start and end time, and produces a new file containing only the selected range. The original video is decoded inside the current tab using the browser's built-in media engine, the page seeks to your chosen start, captures the playback stream, and records until the requested end. The whole process runs on your device: the source file is never uploaded to Lizely, and the resulting WebM clip is offered through a revocable download link rather than stored on any server.
This matches the practical result of CapCut's split-and-delete workflow in a much narrower way. CapCut is a full editor with timeline layers, effects, audio tracks, and keyframes; the Video Trimmer is a single cut operation with no editing on top. If your task is purely "chop this file down to this section and give me the result," the browser tool covers it without an install, an account, or a project file. Anything beyond that — chaining several cuts, adding transitions, mixing audio — still belongs inside CapCut or a comparable editor.
Supported Files, Codec Realities, and Size Limits
Before you pick a file, it helps to know exactly what the tool will and will not accept, because the limits come from three independent places: the file size on disk, what the browser can decode, and how long the decoded video actually is.
| Container | Max source size | Max decoded length | Max pixel width or height | Max total pixel area |
|---|---|---|---|---|
| MP4 | 500 MiB | 5 minutes | 4096 px | 3840 × 2160 |
| WebM | 500 MiB | 5 minutes | 4096 px | 3840 × 2160 |
| MOV | 500 MiB | 5 minutes | 4096 px | 3840 × 2160 |
| M4V | 500 MiB | 5 minutes | 4096 px | 3840 × 2160 |
| Ogg | 500 MiB | 5 minutes | 4096 px | 3840 × 2160 |
A familiar file extension is not enough on its own. The browser must be able to decode the actual audio and video codecs wrapped inside that container, and codec support varies between Chrome, Firefox, Safari, and Edge. A MOV file with a ProRes or HEVC track, for example, may load in one browser and fail in another even though the filename is supported. If the duration never appears after you choose the file, the decoder has not finished with it rather than the tool rejecting it — and that is a useful signal to re-export the source as a more widely supported codec before trimming.
How to Cut Video in CapCut Style Without Installing the App
When you want the same end result as CapCut's split trim but do not want to open CapCut, the Video Trimmer follows the same three-stage pattern: load the file, pick the range, and export. Here is the full sequence.
- Choose one supported local video from your device. Click the file picker and select an MP4, WebM, MOV, M4V, or Ogg file up to 500 MiB. Wait for the duration readout to populate before doing anything else; if the duration is missing, the browser has not finished decoding the file.
- Enter the start time and end time in seconds. You can include a decimal for milliseconds (for example, 12.5 means twelve and a half seconds). The start must be zero or greater, the end must be later than the start, and the end must fall at or before the decoded duration shown above the inputs.
- Confirm the selected range is at least 0.1 seconds. Anything shorter is rejected visibly rather than silently rounded, so you will see an error instead of an empty clip.
- Select Trim video. The tool seeks to the requested start, captures the playback stream, and records in real time until the requested end.
- Review the reported clip duration and output size. The UI shows the requested range and the file size the finished WebM will have once it is saved.
- Download the WebM clip. The file is delivered through a revocable Object URL inside the same tab, and the downloaded clip's Segment Info is patched with the selected duration so compatible players report a finite timeline.
This is the closest browser equivalent to CapCut's split handle on the timeline: pick the in and out points, hit the cut button, and you have a new file containing only that section. If you need more than one cut, repeat the process for each segment or open CapCut to chain them on a single timeline.
How the Cut Actually Happens — A Plain-Language Look
The interesting part for most readers is what the tool is doing during those few seconds between pressing Trim video and the download appearing. It is not splitting the source file at a keyframe; it is replaying the selected portion and re-recording what plays back. Specifically, the page loads the chosen video into a hidden media element, seeks to the start you entered, pipes the playing video through MediaRecorder, and stops the recording when playback crosses the end time. The resulting WebM uses whichever VP9, VP8, or Opus combination the browser considers supported first, and the file's Segment Info is patched with the chosen duration so compatible players report a finite timeline. The MDN recording a media element guide documents exactly this capture-from-media-element pattern.
Two practical consequences flow from that pipeline. First, because recording happens at playback speed, a sixty-second range takes about sixty seconds to produce. Second, because the encoder samples playback time instead of frame numbers, the last encoded frame can land a small fraction around the requested boundary. The tool is built for convenient local trimming, not frame-accurate editing, so do not expect bit-exact alignment to a specific frame. A Cancel control stops active work mid-trim if you change your mind partway through.
Why the Output Is WebM and What That Means for Your Clip
The choice of WebM is deliberate rather than a limitation of the source. The browser tool uses the MediaRecorder API to keep the entire pipeline inside the current tab, and that API exposes WebM containers with VP9, VP8, and optional Opus audio as the most reliably supported combination across modern browsers. Shipping a separate MP4 encoder inside the page would balloon the download size and add a server dependency, which is the opposite of what a no-upload tool is trying to do.
For most social posts and screen captures this is invisible: WebM plays natively in Chrome, Firefox, Edge, and most modern players, and you can upload it directly to many platforms. For destinations that require MP4 specifically, or that demand a particular audio layout, color profile, or subtitle track, run the trimmed WebM through a desktop encoder after the fact rather than expecting the browser tool to match those requirements. The page preserves the dimensions of the source, but quality, keyframes, color metadata, audio layout, and file size will differ from the original because the output is a fresh re-encode rather than a copied segment.
When a Browser Trim Is the Wrong Tool for the Job
The Video Trimmer is the right call when your task is a single bounded cut on a short clip that you own or have permission to edit, and when the destination accepts WebM or can be re-encoded afterward. It is the wrong call in several specific situations, and it helps to recognize them before you start.
- If you need frame-accurate cuts at exact keyframes, broadcast-safe delivery, multitrack audio, subtitle preservation, or clips longer than five minutes, switch to a dedicated desktop editor. The browser tool cannot promise professional frame accuracy and is not designed for long-form footage.
- The tool does not bypass DRM, fetch media from a remote URL, or strip watermarks, so attempts to trim protected content will fail at the decode stage rather than being silently honored.
- A familiar extension is no guarantee of success; the browser must decode the codecs inside the container, and an unsupported codec produces an empty duration readout rather than a working trim.
- For any video you did not create or do not have explicit permission to edit, opening CapCut with a properly licensed source remains the safer route.
For everything else — a short screen recording, a downloaded clip you want to tighten before posting, a stray intro or outro you want to chop off — the browser tool does exactly what CapCut's split handle does, and it does so without an install, an account, or a project file left behind.