After you crop a video locally in your browser and download the resulting WebM, the items you should review are the output dimensions, the rectangle placement inside the source frame, the presence and quality of audio, the finite duration of the file, the actual byte size on disk, and the playback behavior in the destination player or platform where the video will live. A review is not a single visual glance — it is a small list of concrete checks that confirm the crop was applied to the right pixels, that nothing visible was clipped by accident, that audio survived the browser recorder, that the file will be accepted where you intend to post it, and that you can safely delete the original. Skipping the review is one of the fastest ways to lose work, because some browser crop tools do not preserve subtitles, rotation tags, HDR signaling, or many metadata fields, and the recorded WebM may need a duration patch before it is fully compatible with downstream players. The list below maps each item to a specific check you can run in under a minute on the file you already have on disk.
Why a Post-Crop Review Matters
Cropping is destructive in the sense that the discarded pixels cannot be recovered from the output, and any mistake in X, Y, width, or height will be baked into every frame of the recorded WebM. A browser-based cropper that records the cropped Canvas in real time also introduces three sources of variation you did not have in the source: the chosen codec (VP9, VP8, or generic WebM), the requested bitrate derived from the cropped pixel area, and the Matroska duration patch that turns a streaming recorder output into a finite file. Each of those can change the file you end up reviewing, and only an explicit check confirms they all landed correctly. A review also separates "the crop ran" from "the crop ran correctly" — many crops finish and download a file even when the rectangle was silently clipped, the audio track was dropped, or the duration was not patched for finite playback. The output is re-recorded by the browser encoder, so what you are reviewing is not a lossless cut of the source; it is a fresh WebM with its own codec, bitrate, and container.
The Output Items You Need to Review
These are the concrete items worth a separate look. The exact list depends on what the source had and where the output is going, but a complete pass covers all of them:
- Output dimensions match the requested crop width and height exactly.
- Rectangle placement lines up with the intended X and Y offsets, not shifted, clipped, rounded, or snapped to a default.
- Audio track is present and audible when the source had a capturable track, and absent only when the browser did not expose one.
- Duration is finite and matches the source duration within real-time recording tolerance, not open-ended.
- File opens in the destination player, editor, or platform where you will publish it, not just in the browser tab.
- File size on disk matches what you expect for the cropped area, the chosen bitrate, and the actual duration.
- Subtitles, chapters, rotation tags, HDR signaling, and color metadata are gone — this is expected, so note it before you publish.
Each row on this list maps to a one-line check. The next section walks through them in order.
How to Verify the Cropped WebM Step by Step
- Open the downloaded WebM in a player that shows native dimensions and duration, and confirm the width and height reported by the player match the crop width and height you entered. If the numbers differ by even one pixel, the rectangle was rounded or partially applied and the crop should be re-run.
- Scrub from the first frame to the last frame and look for any black border, soft edge, or static artifact along the rectangle boundary. A correct crop has a sharp boundary on every frame; a clipping or rounding error shows up as a thin static strip on one or more sides.
- Toggle audio on and off in the player, and listen for the original sound at its original loudness. If the source had audio and the output is silent, the browser did not expose a capturable track for that file — note this and decide whether to re-export.
- Check the file properties for a duration value, not an infinity marker or an empty value. A browser MediaRecorder often streams the file out without a finite duration; the cropper patches that in timestamp-scale ticks, and a missing patch will make some editors refuse the file.
- Open the WebM in the destination application — the editor you will cut it into, the social platform you will upload it to, or the device you will play it on. Confirm it imports, plays through, and is not rejected for codec, size, or duration.
- Compare the on-disk byte size to the rough expectation. The output area in pixels at 30 fps, scaled by the chosen bitrate, gives a rough lower bound for a one-minute clip. If the file is dramatically smaller or larger than that band, suspect a different codec or a stale recording.
- Keep the source file on disk until every step above passes. Delete the original only after the destination has accepted the cropped WebM and a backup copy is saved somewhere separate.
Limits That Affect What You Can Review
Some items on the review list are bounded by the cropper's own limits. If any of those limits are exceeded, the crop fails without producing a partial file, and the review list shortens accordingly.
| Limit or rule | Value or constraint | How it shapes the review |
|---|---|---|
| Input file size | Up to 500 MiB | Larger sources cannot be loaded — no review is possible |
| Input duration | Above zero, up to 5 minutes | Sources outside that band never produce an output to review |
| Input resolution | No side above 4096 px; total area up to 3840 × 2160 | Anything larger fails at decode time |
| Output area | No more than 3840 × 2160 pixels | A successful crop is guaranteed to fit that ceiling |
| Crop dimensions | Width and height at least 2 pixels each | Smaller values are rejected before recording |
| Rectangle placement | X + width and Y + height must stay inside the source | A rectangle outside the frame fails without clipping |
| Audio | Included only when the browser exposes a capturable track | An empty audio track in the output may be expected, not a bug |
| Codec | First browser-reported VP9, VP8, or generic WebM | Review must use a player that accepts whichever was chosen |
| Bitrate | 180 kbps to 8 Mbps, derived from cropped area at 30 fps | File size and quality vary with motion and source noise |
| Duration patch | Inserts finite Matroska Duration in timestamp-scale ticks | A missing duration in the player means the patch did not apply |
Each row tells you whether a missing piece in the output is a bug or an expected outcome. Treat the table as a filter: anything outside the limits never makes it to the review step in the first place.
When to Re-Crop or Switch Tools
If any check fails, the cheapest next move is almost always to re-run the crop with corrected inputs rather than to switch tools. A rectangle that is shifted by a few pixels, a width or height that was one pixel short, or an X or Y that overran the frame all become a new run with the same source file. Open the original again, recompute the rectangle from the source dimensions reported by the browser, and re-record. The original is untouched, so nothing is lost in the re-run.
Switch to a different tool when the source has needs the browser cropper does not cover. A single fixed rectangle applied to every frame cannot track a moving subject, change over time, follow a face, or remove an object; if any of those are part of the edit, a tracking cropper or an object-removal tool is required instead. The browser cropper also is not a trim-by-time tool, a resize tool, a compress-only tool, a redaction tool, or a blur tool — those are separate tasks with separate tools. When the destination requires rotation tags, HDR signaling, subtitle tracks, or chapters that the crop strips out, those can be reattached in an editor after the crop, but the cropped WebM itself will not carry them.
For audio that the browser did not expose, a separate pass through an audio-extraction tool can produce the track to mux back in later. For a resize instead of a crop, a resizing tool with bounded output area serves the same source. For a time-range cut without changing the frame, a trim tool produces a shorter WebM from the same source. The crop and the trim stack cleanly: crop first to set the rectangle, then trim the result to set the in and out points.
Make the Review Repeatable
The list of seven items is small enough to copy into a notes file and reuse on the next crop. Treating it as a fixed checklist — same order, same checks — turns "did I remember to verify audio?" into a non-question. For batch work where the same rectangle is applied to many clips at the same coordinates, a repeatable review also catches the case where one source had a capturable audio track and the next one did not, or where one source had rotation tags that the crop stripped out. A consistent review surfaces the differences between sources instead of letting them hide inside the next export.
For readers who want a deeper walk-through of the rectangle math, the source dimensions, and what "stay inside every source frame" means in practice, the Video Cropper page documents the inputs and limits in full. For a side-by-side comparison with other browser-side editing approaches, Compare Video Crop Approaches: Pick the Right Method outlines when a crop is the right primitive and when it is not.
If you're weighing options, When Should You Use Video Crop: Triggers and Limits covers this in detail.