Correct use of a browser video cropper means entering X and Y offsets plus width and height in whole pixels, keeping the resulting rectangle inside every source frame, and verifying the WebM output before deleting the original — three gates the tool will not silently fix for you. When Video Cropper asks for X, Y, width, and height, it is asking for four integers that describe one rectangle drawn from the source frame's top-left corner. The X value moves the rectangle right, the Y value moves it down, the width sets how far the rectangle extends horizontally, and the height sets how far it extends vertically. Getting this right is the difference between a clean export and a wasted minute of real-time processing. A valid crop rectangle must use whole nonnegative pixel counts, must keep width and height at least two pixels each, must remain entirely inside the decoded source dimensions, and must produce an output area of no more than 3840 × 2160 pixels. When any of those gates fails, the tool refuses the crop without shifting, clipping, rounding, or producing a partial file. Treating the rectangle as a precise math problem rather than a visual selection is the first habit that separates correct crops from rework.
What "Using Video Crop Correctly" Actually Means
Using Video Cropper correctly is a four-stage discipline: confirm the source is decodable and within limits, plan a rectangle that meets every input rule, watch real-time processing without closing the tab, and verify the WebM output before deleting the original. Each stage has a small set of failure modes, and skipping any of them is what produces a "wrong" crop result. The tool is intentionally strict — an invalid rectangle fails without trying to recover, and a one-minute source takes about one minute to process because the work happens in real time on the local machine. Correct use, in practice, is the discipline of meeting those strict gates deliberately instead of guessing and hoping the export lands somewhere usable.
Correct use also includes knowing what Video Cropper will not do. It applies one fixed rectangle to every frame — it does not track a moving subject, slide over time, blur, redact, remove an object, or change the rectangle at all. It is not a trim-by-time, resize, or compress-only tool. If the goal is changing duration, dimensions, bitrate, or removing a section of time, the right tool is Video Trimmer or Video Resizer rather than a crop. Calling Video Cropper for a job it cannot do is itself a kind of incorrect use, because the rectangle will come out looking like a crop rather than the change actually needed.
Pre-Crop Checks: Confirm the Source Will Work
Before opening the crop controls, confirm that the source file meets every limit Video Cropper enforces. The file extension alone is not enough — an accepted extension does not guarantee the browser can decode the codec inside. The shared video safety budget also caps the source at:
- 500 MiB or smaller positive file size.
- Decoded duration greater than zero and at most five minutes.
- No source side longer than 4096 pixels.
- No source area larger than 3840 × 2160 pixels.
Wait for the source dimensions to load after choosing the file — those are the decoded values the rectangle math will use, not the values printed in a metadata panel. If the dimensions do not appear, the codec is unsupported in the current browser and the crop will not run. Open the file in Video Cropper, confirm the dimensions, and only then move on to coordinates. Skipping this step is the most common reason a crop appears to fail silently later, with the user assuming the rectangle was wrong when the real problem was upstream.
Entering Coordinates So the Rectangle Is Accepted
The four fields have one job each, and the rules around them are not negotiable. The reference corner is the source frame's top-left, where X = 0 and Y = 0. X moves the crop right, Y moves it down, width is the horizontal extent, and height is the vertical extent. All four must be untrimmed nonnegative whole pixels; width and height must each be at least 2; X plus width must not exceed the decoded source width; Y plus height must not exceed the decoded source height; and the output rectangle (width × height) may not exceed 3840 × 2160.
| Field | Type | Constraint | If broken |
|---|---|---|---|
| X (offset) | Integer pixels | ≥ 0 and X + width ≤ source width | Crop rejected, no partial file |
| Y (offset) | Integer pixels | ≥ 0 and Y + height ≤ source height | Crop rejected, no partial file |
| Width | Integer pixels | ≥ 2 and ≤ source width | Crop rejected, no partial file |
| Height | Integer pixels | ≥ 2 and ≤ source height | Crop rejected, no partial file |
| Output area | Width × Height | ≤ 3840 × 2160 | Crop rejected, no partial file |
A worked example keeps the math honest. Source frame is 1920 × 1080 and the goal is a centered 1080 × 1080 square. X = (1920 − 1080) ÷ 2 = 420. Y = (1080 − 1080) ÷ 2 = 0. X + width = 420 + 1080 = 1500, which is ≤ 1920. Y + height = 0 + 1080 = 1080, which is ≤ 1080. Output area = 1080 × 1080 = 1,166,400 pixels, well under the 3840 × 2160 ceiling. Every gate is satisfied. Defaults in the tool already select the full frame, so leaving width or height empty is not a way to opt out — it is a rejection.
One subtle correctness point: the source numbers must be the values the browser can actually decode. The HTML canvas drawImage specification only operates on whatever the browser has already decoded from the file, which is why a valid extension with an unsupported codec still fails the pre-crop check. Plan the rectangle from those decoded numbers, not from a thumbnail or from a metadata field that the file cannot play back to.
Run the Crop and Watch the Real-Time Processing
Once the rectangle is valid, select Crop video and leave the tab open. Video Cropper plays the source locally, draws only the requested region into an equal-size opaque Canvas at 30 frames per second, requests a bounded bitrate from the cropped pixel area, records the Canvas stream as WebM through the MediaRecorder API, and then patches the recorded blob so it carries a finite Matroska Duration. None of this happens on a server. The reason the tab must stay open is that the recorder is bound to the live page — closing or backgrounding the tab can interrupt the capture stream before the duration patch is written.
A one-minute source takes roughly one minute; a five-minute source takes roughly five minutes. The output WebM is built from the first browser-reported recorder among VP9, VP8, and a generic WebM recorder, so the actual file extension is fixed but the encoder inside is whatever the browser exposes. The bitrate is derived from the cropped pixel area at 30 fps and is bounded between 180 kbps and 8 Mbps — a setting, not a guaranteed size or visual quality. Fast motion, noise, grain, the source codec, and the browser encoder can all change the size and look of the result. Treat the bitrate as a ceiling and plan for the file to land wherever it lands.
If the browser exposes an audio track through media capture, the tool appends it to the Canvas stream. Support varies by browser, and the source may play audibly during real-time processing, so headphones are useful on long clips. The crop does not preserve subtitles, chapters, attachments, rotation tags, HDR signaling, color metadata, or every container feature — verify both picture and sound in the export before treating the file as a replacement for the original.
Verify the Output Before You Delete the Original
Correct use ends with verification, not with the download click. Because Video Cropper does not upload anything and does not give back a guaranteed size, the only way to confirm "correct" is to play the WebM in the destination environment and check four things. Run through this checklist every time:
| Check | How to verify | What a failure tells you |
|---|---|---|
| Duration | Open the WebM in the target player and watch to the end. | Finite Matroska Duration missing; re-run with the tab open the entire time. |
| Crop region | Compare frame edges against the source at the same timestamp. | Coordinates were accepted but visually wrong — re-plan with decoded dimensions. |
| Audio | Listen for the original track; confirm a silent stream was not captured. | Browser does not expose a capturable audio track; document the loss. |
| Compatibility | Play the file in the player where the video will actually ship. | VP8 vs VP9 vs generic WebM matters — keep the original until this passes. |
Keep the original file until the entire output has been reviewed. Because the recorder stream can omit a finite container duration and the duration writer is what makes the file reliable across players, an output that looks fine in one player can still behave oddly in another. If anything in the verification fails, run the crop again with corrected coordinates or a different browser — do not edit the WebM in place. For a deeper walk-through of what the verification stages are actually testing, the accuracy guide for Video Cropper covers how pixels, audio, and duration are checked against the source. If the result still looks wrong after verification, the fix guide for a cropped result that looks wrong walks through the most common recovery steps.
What Video Crop Will Not Do (And Why That Matters for "Correct" Use)
Correct use also means knowing when to reach for a different tool. Video Cropper changes the visible frame region by drawing one fixed rectangle from a Canvas (per the WHATWG HTML canvas specification) and recording that stream; it does not analyze content, follow motion, or alter the timeline. Common tasks it cannot do:
- Track a person or object as it moves — the rectangle is identical on every frame.
- Trim by start and end time — the output keeps the full source duration within the safety budget.
- Resize to a new resolution while keeping the whole frame — that is Video Resizer.
- Reduce file size by re-encoding without changing pixels — that is Video Compressor.
- Remove or blur a specific area — there is no redact pass.
- Preserve subtitles, chapters, rotation tags, HDR signaling, or every container field.
Reaching for Video Cropper when the task is actually trim, resize, compress, or redact is the hidden cause of many "incorrect use" reports: the rectangle is technically valid, the export runs, and the result still does not match the goal. Confirming the job really is a frame-region change before opening Video Cropper is part of using it correctly.