A video cropper removes the outer area of a video by keeping only a rectangular region you choose, measured in exact pixel coordinates from the top-left corner of each frame. For beginners, the concept is simple: every frame of a video is a grid of pixels, and a crop is just a window onto that grid — you pick where the window starts (X, Y) and how wide and tall it is (width, height). The chosen rectangle is then re-recorded into a new file, leaving the unwanted edges behind. Browser-based tools like the Video Cropper do this locally in your current tab without uploading the original anywhere, which keeps private clips private and avoids waiting on a remote server. The output is a WebM file with a finite duration you can play in any modern browser or video player. This beginner's guide walks through what a crop actually is, which inputs the tool accepts, how to read the four coordinate boxes, and what does and does not survive the trip into the cropped file.
What "Cropping" Actually Means in Pixel Terms
A video is a stack of still images shown one after another. Each still image, called a frame, has a fixed pixel size — for example, 1920 pixels wide and 1080 pixels tall. Cropping means choosing a smaller rectangle inside every frame and re-recording only that rectangle. The unwanted outer pixels are simply dropped.
Nothing about the surviving pixels changes: their colors, brightness, and timing all stay the same. The crop only affects the visible area, not the encoding or the playback speed. If you crop a 1920×1080 clip down to a centered 1280×720 rectangle, the surviving 1280×720 pixels keep their original sharpness and timestamps; the picture just looks like a zoomed-in version of the original.
Because cropping is measured in source pixels, the tool needs the decoded dimensions of your video before it can accept rectangle values. That is why the very first step of any browser-based cropper is to load the file and wait for its true width and height to appear. Without those numbers, there is no reliable way to keep the rectangle inside the frame on every single frame.
Browser-Based vs Desktop Cropping
Desktop editors can crop, but they often come with a learning curve: timelines, preview windows, project files, and rendering queues. A beginner who only wants to chop the edges off a short clip rarely needs all of that. Browser-based cropping collapses the task into three actions — pick a file, type four numbers, press one button — and produces a single WebM file at the end.
The trade-off is that browser cropping records the result in real time while the source plays. A one-minute source takes about one minute to process, because the canvas is drawn at a fixed 30 fps. For a short clip this delay is invisible; for very long projects it is worth knowing the constraint exists up front.
Another trade-off is codec coverage. The browser can only decode what its current media engine supports. MP4, WebM, MOV, M4V, and Ogg files are common targets, but having an accepted file extension does not guarantee the decoder can read it. If your file fails to load, the cause is almost always a codec mismatch inside the container, not the container itself.
Inputs, Limits, and Output Format at a Glance
| Setting | Allowed value |
|---|---|
| File container | MP4, WebM, MOV, M4V, or Ogg (codec support depends on the browser) |
| Maximum file size | 500 MiB |
| Maximum decoded duration | Five minutes (above zero) |
| Maximum source side | 4,096 pixels on either width or height |
| Maximum source area | 3,840 × 2,160 pixels |
| Crop X, Y | Nonnegative whole pixels; X moves right, Y moves down |
| Crop width, height | Whole pixels, each at least 2 |
| Rectangle must fit | X + width ≤ source width, Y + height ≤ source height |
| Maximum output area | 3,840 × 2,160 pixels |
| Output container | WebM with finite Matroska duration |
| Output bitrate range | 180 kbps through 8 Mbps, scaled from cropped area at 30 fps |
If a value falls outside these limits, the tool refuses the rectangle without rounding, clipping, or producing a partial file. That refusal is the safety net that protects beginners from accidentally asking for an impossible output.
How to Crop a Video in Three Steps
- Open the Video Cropper and choose a browser-decodable video file (MP4, WebM, MOV, M4V, or Ogg). Wait until the source dimensions appear — the tool cannot validate a rectangle until it knows the true pixel size of the decoded frames.
- Enter whole-pixel values for X, Y, width, and height. Start at zero to keep the original top-left, move the numbers larger to slide the rectangle right (X) or down (Y), and pick width and height that match how much of the frame you want to keep. Make sure X + width and Y + height stay inside the source dimensions shown above the inputs.
- Select Crop video, keep the tab open while the source plays in real time, and download the WebM when it appears. Play the result in your usual player before deleting the original — confirm the crop region, the duration, and the audio if you expected sound.
Reading X, Y, Width, and Height Without Math Anxiety
The four boxes can look intimidating, but each one answers a single question.
- X: how many pixels in from the left edge does the crop window start?
- Y: how many pixels down from the top edge does the crop window start?
- Width: how many pixels wide is the crop window?
- Height: how many pixels tall is the crop window?
Coordinates start at the source frame's top-left corner, which is the (0, 0) point. X moves the window to the right and Y moves it down; there is no negative direction in this tool. The defaults select the full frame, which is a safe starting point if you want to see the original dimensions before trimming the edges.
Worked example: a 1920×1080 source has a thin black bar at the top and bottom that you want to remove. Set Y = 80 and height = 920 so the window starts 80 pixels down and ends 80 pixels before the bottom edge. Keep X = 0 and width = 1920 to retain the full horizontal extent.
- Check horizontal: X + width = 0 + 1920 = 1920, which is exactly the source width, so the rectangle fits.
- Check vertical: Y + height = 80 + 920 = 1000, which is below the source height of 1080, so the rectangle fits.
- Output area: 1920 × 920 = 1,766,400 pixels, well below the 3,840 × 2,160 cap of 8,294,400 pixels, so the output is within limits.
That single subtraction (Y + height ≤ source height) is the arithmetic the tool enforces. If you can confirm both edges fit, the rectangle is valid. The same logic follows the WHATWG canvas drawing model: the source region is drawn into an equal-size canvas at fixed offsets, frame after frame.
What the Output Keeps and What It Drops
| Property | Survives the crop? |
|---|---|
| Visible pixel region | Yes — exactly the rectangle you requested |
| Playback timing of frames | Yes — the canvas is drawn at 30 fps from the source |
| Audio track | Only if a capturable track is exposed by the browser |
| Subtitles and chapters | No — these are container features, not pixels |
| Rotation tags | No — orientation is not rewritten |
| HDR signaling and color metadata | No — output is standard WebM video |
| Attachments and other metadata | No — most metadata fields are not preserved |
| File duration | Yes — a finite Matroska duration is written into the WebM |
The crop is also not a trim-by-time tool: the output spans the entire source duration, not a chosen start and end. It is not a resize tool (the surviving pixels keep their original size) and it is not a redaction or blur tool (no area is hidden). For a step-by-step look at pixel-accurate cropping aimed at a vertical aspect ratio, the Crop a Video to 9:16 With Exact Pixel Coordinates guide shows the same input boxes used to reach a 9:16 rectangle.
First-Time User Pitfalls and Easy Fixes
Beginners usually hit one of three snags on the first try.
- The file fails to load. The container extension is fine, but the codec inside is not what the current browser can decode. Re-export the source from your phone or editor as a standard H.264 MP4 or VP9 WebM, then load it again.
- The Crop action fails without producing a file. This is almost always a rectangle that drifts outside the frame. Re-read the source dimensions at the top of the page, then recompute X + width and Y + height so both stay inside the source. Width and height must also be at least 2 each.
- The output has no sound. The browser may not be exposing a capturable audio track for the source. Try a different source file or open the original in a player to confirm it has audio at all; if it does, a current Chromium-based browser is most likely to pass audio through the canvas stream.
A few smaller reminders keep the first session from going off the rails. The bitrate is bounded between 180 kbps and 8 Mbps based on the cropped area at 30 fps, so very small crops get very modest bitrates and very large crops approach the cap. Fast motion, grain, and the browser's encoder all change the final file size, so the value is a disclosed setting, not a guaranteed target. Do not delete the original until you have played the entire WebM and confirmed the picture, sound, and duration.
When a Fixed Rectangle Is Not Enough
A single rectangle applied to every frame is the right tool when the unwanted edges are static throughout the clip — letterbox bars, watermarks in a fixed corner, a tripod leg in the same spot. It is the wrong tool when the unwanted element moves, because the rectangle does not track.
If your goal is to follow a person, blur a face, or hide a license plate that changes position, you need a tracker, a mask, or frame-by-frame keyframes — none of which a fixed-crop tool provides. Use the cropper to set the canvas, then move to a mask-based editor for the moving region.
The cropper is also not the right tool for trimming a clip in time or for shrinking the dimensions of an output. Trim-by-time cuts from the same source are a different task, and so is downscaling the pixel size of an output without changing the visible region. Picking the right tool is part of the beginner skill set, and starting with the cropper's three-step flow keeps the first crop predictable and reversible.