Yes, you can trim a video without uploading a file, because a browser-based trimmer decodes, seeks, captures, and re-encodes the selected range entirely inside the page that is already open on your device. The source video is read from your local disk by the file input, handed to a hidden HTMLMediaElement, and then processed by built-in browser APIs that never make a network request for the media data. Decode, stream capture, recording, and download generation all happen inside the current tab, so the original clip never travels to a server, never enters a cloud queue, and never sits in someone else's storage waiting to be deleted. A local tool built on MediaRecorder produces a new WebM file that you save yourself, and the source stays untouched on your machine for the entire session. This makes it practical to trim private clips, draft work, customer footage, or any material you are not comfortable handing over to a remote service, and it works without installing software, creating an account, or accepting upload terms.
How Local Trimming Works Without an Upload
The phrase "trim without uploading" depends on three browser capabilities working together: local file reading, in-page decoding, and a recording pipeline that can capture decoded playback. When you pick a file through the file picker, the browser exposes the bytes to the page through the File API. The page then creates a URL for that file, assigns it to a video element, and the browser's own media decoders turn the compressed audio and video frames into raw samples. None of those samples ever leave the page; they stay in memory inside the rendering engine that is already running on your computer.
Cutting a bounded section means telling the media element to seek to a start time, then beginning to record while it plays forward to the end time. According to the MDN documentation on Recording a media element, a MediaStream produced from a playing HTMLMediaElement can be fed into a MediaRecorder to produce a new container file on the fly. The same approach is described in the MediaRecorder reference, which explains how the recorder picks a supported codec combination from what the browser can encode and writes it into a media container you can download.
That pipeline is the reason a local trim is possible without a server. The browser is doing what a desktop editor does, but inside the tab instead of inside a separately installed application. The trade-off is real-time re-encoding rather than packet-level stream copying, which is why the output is always WebM and why quality, keyframes, color metadata, and audio layout may differ from the source even when the dimensions stay the same.
Trim a Video Locally in Your Browser
To cut a clip without sending it anywhere, open the Video Trimmer, choose a local file, set the time range, and download the result. The page performs each step in your browser tab.
- Pick one supported local video and wait for its duration to populate in the form. The number you see is the decoded playback length, not the file size.
- Enter the start time and end time in seconds, with optional millisecond precision. Keep the range inside the source duration and make sure the end is later than the start.
- Select Trim video. The page seeks to the start, begins real-time capture through MediaRecorder, and stops at the requested end.
- Review the requested clip duration and the output size the page reports. This is the value written into the WebM Segment Info so compatible players report a finite timeline.
- Save the WebM file through the download link. The source file is not modified, and nothing on the page replaces the original on your disk.
If you cancel mid-trim, the active work stops. Eight independent range fixtures cover zero-based, middle, fractional, tail, and five-minute boundaries, and invalid or reversed ranges fail visibly rather than being silently clamped, which makes it easy to spot a typo before you commit.
Supported Files, Codec Reality, and Hard Limits
A familiar extension is not a guarantee. The container tells the browser the file layout, but playback still depends on the codecs inside. The Video Trimmer accepts MP4, WebM, MOV, M4V, and Ogg containers, and the current browser must be able to decode the actual audio and video codecs those files carry. If a clip fails to load, the most common cause is a codec the browser cannot decode, not a wrong extension.
| Container | Accepted | Notes |
|---|---|---|
| MP4 | Yes | Requires a browser-decodable video and audio track. |
| WebM | Yes | Container and codec are typically browser-native. |
| MOV | Yes | QuickTime container; codec support varies by browser. |
| M4V | Yes | Apple variant of MP4; codec support varies by browser. |
| Ogg | Yes | Usually carries Theora and Vorbis, which most modern browsers decode. |
The hard limits are checked against the decoded media, not the raw file. The file itself may be up to 500 MiB, the decoded playback length must be no longer than five minutes, the frame must not exceed 4096 pixels on either edge, and the total pixel area must stay inside 3840 × 2160. A file that passes the size check can still be rejected if it is too tall, too wide, or too long once the browser starts decoding.
| Limit | Value | Why It Matters |
|---|---|---|
| File size | 500 MiB | Applies to the input on disk before decoding. |
| Decoded duration | 5 minutes | Longer files are rejected after decode. |
| Width or height | 4096 px max | Either edge cannot exceed this. |
| Total pixel area | 3840 × 2160 max | Combined frame area is bounded. |
| Minimum clip length | 0.1 seconds | Shorter ranges are rejected. |
The minimum useful clip is 0.1 seconds, the start must be zero or greater, the end must be later than the start and no later than the decoded duration, and values may include millisecond precision. Because MediaRecorder samples playback time and does not expose frame-accurate editing, the last encoded frame can land a small fraction around the requested boundary, so for exact cut points you should expect a small tolerance rather than a frame-perfect slice.
Privacy: What Never Leaves Your Tab
Because decode, seek, stream capture, recording, and download generation all happen in the current browser tab, the source video never reaches Lizely's servers. There is no upload step, no background sync, and no queue that holds the file until the trim finishes. The page works the same on a laptop on a metered connection as it does on a workstation with no network at all once the page itself has loaded.
The tool does not bypass DRM, does not fetch remote media, does not remove watermarks, and does not preserve every metadata field from the source. It also does not provide frame-accurate cuts, multitrack audio, or MP4 output. For broadcast delivery, exact keyframe cuts, subtitle preservation, multitrack audio, long footage, or a required MP4 codec, you should use a dedicated desktop editor and inspect the exported timeline yourself. The Video Trimmer is built for the common case of pulling a short, finite-duration section out of a local clip you own or have permission to edit, without the round trip through a server.
For readers who want a deeper look at how the same in-browser approach avoids uploading, the walkthrough Cut a Video Clip Without Uploading the Original File covers the same pipeline from a slightly different angle.
When a Desktop Editor Is the Better Choice
A local browser trimmer is the right tool for short, simple cuts where privacy and convenience matter more than frame accuracy. It is not the right tool when you need packet-level cutting on keyframes, when you have to keep an MP4 container because of a downstream requirement, when the source is longer than five minutes, when you need to preserve subtitles, or when you need to mix multiple audio tracks. In those cases, the trimmed WebM is a useful preview, but the final master should come from a desktop editor that can cut at the GOP boundary and write the container the deliverable expects.
The rule of thumb is straightforward. If the task is "pull a section out of a clip and save it as a WebM I can play or share," the browser tool is enough. If the task is "produce a delivery file with exact cuts, original metadata, and the original codec," open a real editor, drop the same file in, and export from there. Knowing which job you are doing keeps the local workflow fast and stops you from blaming a browser recorder for limits it was never designed to remove.
Related reading: How Do I Check the Result After I Trim a Video.