A video crop tool should be compared on five things before you open a file: where the decode and write happen, how the bounding box is specified, what container and codec the output uses, which input formats the current browser actually decodes, and what numeric limits apply to source size, source duration, source dimensions, and output area. Each checkpoint decides whether the resulting clip lands in the destination player intact, on time, at the right pixel rectangle, and with audio intact. Skipping the comparison step is how people end up with clipped edges, missing sound, infinite-duration WebM files that will not seek, or worse, a private clip uploaded somewhere they did not expect. The Video Cropper at /video/video-cropper/ satisfies every checkpoint on that short list by re-recording the chosen rectangle locally inside the browser, accepting whole-pixel X, Y, width, and height values, writing a finite-duration WebM, and refusing to touch the source beyond the open tab. The rest of this article walks through each comparison point, shows the exact workflow that turns the comparison into a finished clip, and explains how to verify the output before deleting anything.
What to compare in any video crop tool before you commit
A short, structured comparison takes less time than re-doing a failed crop, so work through five checkpoints before opening a file.
- Processing location. Does the tool decode, crop, and write entirely on the device, or does it upload the source to a remote server first? The answer controls who can see the file.
- Coordinate system. Does the bounding box come from a drag-and-drop preview, whole-pixel numeric inputs, or a percentage of the frame? Numeric whole-pixel inputs are the only way to match a target platform's exact rectangle.
- Output container and codec. WebM (VP9 or VP8), MP4 (H.264 or H.265), MOV, or GIF, and whether the resulting file plays in the destination player without conversion.
- Supported source formats. Whether the tool accepts MP4, WebM, MOV, M4V, and Ogg, and how it behaves when the chosen extension is not actually decodable by the current browser.
- Numeric limits. The maximum source size in bytes, maximum decoded duration, maximum source dimensions per side, and maximum output area in pixels.
If a tool cannot answer each of these five questions with concrete values, treat it as a black box and move on.
Privacy and processing location
Privacy is the first checkpoint because it is the hardest to reverse. A tool that uploads the source to a server exposes the file to network intermediaries, server logs, and the vendor's retention policy, even when the upload itself is encrypted in transit. A tool that keeps the file inside the browser tab leaves the file on the device and removes a layer of trust from the workflow. Video Cropper belongs to the second group: decoding, canvas drawing, MediaRecorder capture, and WebM writing all happen in the current tab, and no source or output leaves the browser. That is the right baseline for a personal clip, a draft cut that is not ready to publish, or any file under NDA. The same comparison also exposes a related trap: tools that look local but actually call a hosted encoder for the final write step still move the bytes off-device, even when the preview was drawn locally.
Coordinate system, output limits, and what "exact" really means
Pixel-exact cropping depends on a coordinate system the tool actually documents. Video Cropper measures from the source frame's top-left corner: X moves the crop right, Y moves it down, width sets the horizontal extent, and height sets the vertical extent. Every value is an untrimmed nonnegative whole pixel count, and width and height must each be at least two pixels. X plus width and Y plus height must remain inside the decoded source on every frame. Anything that rounds, shifts, or clips silently breaks a platform's exact size, so the comparison here is between tools that publish the rules and tools that only show a preview.
Output dimensions matter just as much. The output area cannot exceed 3840 × 2160 pixels, and the source itself is bounded by the same explicit video safety budget that other local tools share: positive files up to 500 MiB, decoded duration above zero and no more than five minutes, no source side above 4096 pixels, and no source area above 3840 × 2160. The table below sets the limits in one place.
| Limit | Allowed range |
|---|---|
| Source file size | Positive, up to 500 MiB |
| Decoded duration | Above 0 seconds, up to 5 minutes |
| Source width or height | Up to 4096 pixels per side |
| Source area | Up to 3840 × 2160 pixels |
| Cropped output area | Up to 3840 × 2160 pixels |
| Crop width and height | Each at least 2 pixels |
| Bitrate band | 180 kbps through 8 Mbps, derived from cropped pixel area at 30 fps |
Invalid rectangles fail without shifting, clipping, rounding, or producing a partial file, which is the right behaviour for a comparison shopper who needs to know the tool rejected a bad input rather than quietly returned something wrong.
How to run Video Cropper once the comparison checks out
Once the tool passes the five checkpoints, the workflow is short and the result is deterministic for the same source plus the same coordinates.
- Choose a browser-decodable video (MP4, WebM, MOV, M4V, or Ogg) and wait for the decoded source dimensions to load. An accepted extension does not guarantee codec support, because decoding depends on the current browser.
- Enter X, Y, width, and height as whole pixels. The defaults select the full frame, which is the safe starting point for a first run.
- Confirm the rectangle sits inside the source on every side, and confirm the cropped area does not exceed 3840 × 2160 pixels.
- Select Crop video and keep the tab open. Processing happens in real time, so a one-minute source takes about one minute.
- Download the WebM and the surrounding browser-recorded audio track when the recorder exposes one.
- Fully review the file in the destination player for duration, crop placement, audio, and compatibility.
Keep the original source until the entire output has been reviewed, because real-time MediaRecorder output can omit a finite container duration and the final step that patches the Matroska Duration only runs on the file that was actually written.
Verifying the WebM before you delete the source
Verification closes the loop on the comparison. The WebM that comes out of Video Cropper is recorded through the first browser-reported WebM recorder among VP9, VP8, and generic WebM, and a finite Matroska Duration is inserted in timestamp-scale ticks using the same standards-tested writer that Video Compressor reuses. The output must remain nonempty and decode at the requested dimensions. That last clause is what makes the comparison honest: a tool that writes a valid container but with the wrong frame size has still failed the user's spec. Confirm duration, the cropped rectangle, audio presence, and playback in the destination player before deleting anything. The audio track is only attached when the browser exposes one through media capture, so silence in the result is not always a bug, but it is always worth checking. Captured audio may also play audibly through the source during real-time processing, so use headphones for any sensitive material.
When a different approach makes more sense
Cropping is one specific operation: change the visible frame region by re-recording a fixed rectangle. It is not the right tool for trimming a clip by start and end time, resizing without cropping, compressing without changing the rectangle, redacting faces or plates, blurring an object, or removing a watermark. It also does not preserve subtitles, chapters, attachments, rotation tags, HDR signaling, or color metadata, because the tool re-records the visible pixels rather than copying the container. The crop applies one rectangle to every frame, so a moving subject that drifts across the frame will not be tracked. For those tasks, a trim-by-time tool, a resize tool, a compress-only tool, or a dedicated redaction workflow is the right call. The companion guide Compare Video Crop Approaches: Pick the Right Method walks through how each approach fits a different editing goal, which makes it a useful next read when the answer to "what should I compare" turns out to be "a different tool entirely."
If you're weighing options, What to Compare Before You Use Video Compression covers this in detail.