A video cropper on Windows can run entirely inside Chrome, Edge, or Firefox without installing a desktop editor: open the browser tool, enter exact pixel coordinates, and download a WebM of just the region you want. The whole pipeline — decoding the source, drawing the rectangle on a Canvas, recording that Canvas as WebM, and patching in a finite Matroska Duration — happens in the current tab, so nothing is uploaded to a remote server. For Windows users who do not want to install DaVinci Resolve, Clipchamp, or another full editor, this is a focused way to remove black bars, watermarks in a fixed corner, or static edges from a single clip. The crop is defined by four whole-pixel values — X, Y, width, and height — that must stay inside the decoded source frame on every frame, and a single rectangle is applied to the whole clip rather than tracked over time.
Why Windows Users Look for a Browser-Based Cropper
Windows 10 and Windows 11 ship with a few video tools, but they are not all built for pixel-accurate cropping. Clipchamp covers simple framing, DaVinci Resolve is a full editor that takes time to learn, and many free apps install background services or ask for an account. A browser-based cropper skips both the install and the sign-in: you point a browser tab at the file on disk, the page reads the dimensions, you type four numbers, and the result lands as a downloadable WebM. For a Windows user with one clip and fixed unwanted edges, that is the right size of tool.
Browser tools also keep the source local. The file you select is read by the browser's media decoder, the rectangle is drawn into a Canvas element, and that Canvas stream is recorded as WebM. None of those steps require sending the clip to a remote server, which matters on a work laptop or a shared family PC where uploads are restricted.
Supported Inputs, Outputs, and Browser Limits
On Windows, the Video Cropper accepts files with the extensions MP4, WebM, MOV, M4V, and Ogg. Having the right extension does not guarantee the codec will decode — that depends on what the current browser supports. Chrome and Edge on Windows ship with broad codec coverage, while Firefox is more limited for some MP4 and MOV variants. The safest path is to try the file and, if decoding fails, re-wrap or transcode it first with Video Compressor before cropping.
The output is always a WebM file recorded with the first browser-reported recorder among VP9, VP8, and generic WebM. Audio is appended only when the browser exposes a capturable track through media capture; in practice this usually means there is a sound, but support varies, and the source may play audibly while the tool records in real time.
| Limit | Value |
|---|---|
| Positive file size | up to 500 MiB |
| Decoded duration | greater than 0, no more than 5 minutes |
| Source side (width or height) | no more than 4096 pixels |
| Source area | no more than 3840 × 2160 pixels |
| Output area | no more than 3840 × 2160 pixels |
| Crop width, crop height | at least 2 pixels each |
| Output frame rate | 30 fps |
| Bitrate range | 180 kbps through 8 Mbps |
| Recording pass | single-pass, real time, in-tab |
The whole pipeline follows the W3C MediaStream Recording and Media Capture from DOM Elements specifications for the recorder, the WHATWG HTML Canvas drawImage call for the region, and the IETF Matroska container format for the WebM container with its finite Duration field.
How to Crop a Video on Windows in Your Browser
The crop is defined by four whole-pixel values, so the task is mainly about measuring the source frame and entering those numbers carefully.
- Open the Video Cropper in Chrome, Edge, or Firefox on Windows 10 or Windows 11.
- Choose a file from disk. The tool accepts MP4, WebM, MOV, M4V, and Ogg files up to 500 MiB, with decoded duration between zero and five minutes, no side over 4096 pixels, and no source area above 3840 × 2160.
- Wait for the source dimensions to appear. The defaults select the full frame, which is a useful sanity check before you start trimming.
- Enter X and Y offsets as nonnegative whole pixels, measured from the top-left corner of the source frame. X moves the crop right, Y moves it down.
- Enter width and height as whole pixels. Each must be at least two, and X + width and Y + height must both stay inside the decoded source on every frame.
- Select Crop video. Keep the tab open and in the foreground — the tool records in real time, so a one-minute source takes about a minute to process.
- Download the WebM when the recorder finishes, then play it back in full in the player you actually plan to use, checking duration, crop position, picture, and audio.
A concrete worked check: if the source decodes at 1920 × 1080 and the goal is a centered 1280 × 720 region, X = 320 and Y = 180 satisfy X + width = 1600 ≤ 1920 and Y + height = 900 ≤ 1080, and the output area of 921,600 pixels sits comfortably under the 3840 × 2160 ceiling.
Pixel Rules and Limits Worth Knowing
Every value is an untrimmed, nonnegative whole pixel count, and the tool will not round, clip, or silently shift an invalid rectangle. If the rectangle is illegal — X or Y negative, a dimension below two, X + width past the right edge, or Y + height past the bottom edge — the crop fails without producing a file. That is a feature: a failed crop is better than a WebM that looks right at the start and cuts off the last second.
Coordinates are read from the source frame's top-left corner, not from the center and not from a preview overlay, so it is worth previewing the original dimensions before typing. For a Windows user recording gameplay or a screen capture, the source is usually a clean full frame and the unwanted area is in the corners; measuring in the original viewer is the most reliable way to pick the right offsets.
What the Cropped WebM Does and Does Not Keep
The crop changes the visible frame region. It does not preserve subtitles, chapters, attachments, rotation tags, HDR signaling, color metadata, or every container feature, and it is not a trim-by-time, resize, compress-only, redact, blur, or object-removal tool. The result is a WebM that re-encodes the picture through the browser's VP9, VP8, or generic WebM recorder at 30 fps, with a bitrate that scales with cropped pixel area and is bounded between 180 kbps and 8 Mbps.
Size and visual quality are best-effort. Fast motion, noise, grain, the source codec, and the browser's encoder all shift the result, so a noisy or high-motion clip will land larger and look softer than a clean static clip at the same coordinates. Keep the original until the cropped WebM has been reviewed in full.
One detail worth knowing: a streaming MediaRecorder output can omit a finite container duration, which is why the tool inserts a big-endian Matroska Duration value in timestamp-scale ticks after recording, using the same standards-tested WebM duration writer that Video Compressor uses on Lizely.
Verifying the Output Before You Delete the Source
Open the downloaded WebM in the player you actually plan to use — VLC, Movies & TV on Windows, or the browser itself — and watch the entire clip. Confirm the duration matches the source, the crop sits where you typed, no static edges are still showing, and the audio matches the picture. If the source played audibly during recording, that is expected; the resulting WebM should have its own track if the browser exposed one.
For a Windows workflow that also needs a different length, see Crop a Video on a Laptop With Exact Pixel Coordinates for the broader laptop context, and use Video Trimmer to cut the clip in time rather than in frame. A practical order on Windows is: trim, then crop, then resize or compress — each step on its own page, each output reviewed before moving on.