A video crop in a browser fails for one of four predictable reasons: the input file cannot be decoded, the rectangle math is wrong, the recording is interrupted, or the WebM output does not behave the way you expected. Treating those four surfaces as a checklist turns a stuck export into a five-minute fix, because Video Cropper exposes every gate to the user rather than hiding them behind a black box. The tool also runs entirely in the current tab, so no upload is happening and no remote server is rejecting the file; every rejection or output you see is decided locally. Once you identify which surface is failing, the specific remedy usually follows from the contract of the tool: file size, decoded duration, pixel dimensions, rectangle bounds, the open tab, and the resulting WebM. Working through the surfaces in order, input, coordinates, processing, output, covers roughly every reported issue and stops you from re-running the same broken crop.
Where Video Crop Problems Typically Start
The fastest way to find a crop bug is to start at the source and work outward. Input failures appear before the coordinates are accepted, coordinate failures appear as a disabled crop button or a clipped rectangle, processing failures appear as a missing or truncated download, and output failures appear only when you play the WebM back. Because Video Cropper refuses invalid inputs without shifting, clipping, rounding, or producing a partial file, a successful download is itself a confirmation that the rectangle the tool accepted was inside the source and within the output area cap. Use that fact to your advantage: if a download arrives, the rectangle was valid; if a download does not arrive, the rectangle or the input was not.
Diagnose Input Problems First
Most crop failures start with the source file. Video Cropper accepts MP4, WebM, MOV, M4V, or Ogg files, but the extension alone does not guarantee decoding; the current browser must also be able to decode the codec inside the container. If the file picker accepts the file and the decoded dimensions never appear, the codec is almost always the reason. A short re-encode in a different browser or with a more common codec usually resolves it.
The input budget is explicit and applies to every load:
- File size: positive files up to 500 MiB
- Decoded duration: above zero and at most five minutes
- Source dimensions: no side above 4096 pixels
- Source area: at most 3840 × 2160 pixels
If any of these limits is exceeded, the tool rejects the file before you can enter coordinates. A file that is "almost" within the limits, 4097 pixels on one side, 5 minutes and one second, exactly 500.1 MiB, fails with the same message as a corrupt file, so read the decoded values the moment they load. If the file is too long, split it first and crop the resulting segments instead of fighting the budget. A loaded file that displays the wrong resolution usually means the decoder picked a fallback stream or the source uses non-square pixels that the browser did not normalize. Either way, the coordinates you enter are measured against the decoded dimensions the tool reports, not the dimensions you remember or saw in another editor.
Fix Coordinate and Rectangle Errors
Every crop coordinate is a whole pixel count taken from the source frame's top-left corner. X moves the crop right, Y moves it down, width stretches horizontally, and height stretches vertically. The tool rejects the action, without shifting, clipping, or rounding, when any of these conditions fail:
- X or Y is negative or contains a decimal
- width or height is below two pixels
- X + width extends past the source width
- Y + height extends past the source height
- the resulting output area exceeds 3840 × 2160 pixels
A worked example: a 1920 × 1080 source with X = 100, Y = 50, width = 800, height = 600. The formula X + width gives 100 + 800 = 900, which is within the source width of 1920. The formula Y + height gives 50 + 600 = 650, which is within the source height of 1080. The crop area is 800 × 600, well under the 3840 × 2160 area cap, so the tool accepts the rectangle. Move X to 1500 with the same width of 800 and X + width becomes 2300, past the 1920 boundary. The tool refuses, no partial file is produced, and the original is untouched. The math is the same in every case: add the offset to the size and compare against the source dimension.
A common pitfall is mixing width and height with X and Y. Width and height are sizes, not positions; X and Y are offsets. Entering 100 into the width field when you meant to set X to 100 produces a rectangle that starts at zero and runs off the right edge. If the rectangle is mathematically valid but ends up in the wrong place, treat that as a coordinate mistake, not a tool bug. If you see a black border on one edge of the output, the rectangle reached the frame edge but the source had no pixels there. Recompute against the decoded dimensions, not against remembered values, because the decoded dimensions are the only contract the tool honors.
Resolve Processing Failures During Real-Time Recording
Once you select Crop video, the tool plays the source locally, draws only the requested region into a Canvas, and records that Canvas as WebM. Processing happens in real time, which means a one-minute source takes about one minute while the tab stays open. Closing the tab, navigating away, or letting the device sleep aborts the recording and produces no file.
If the WebM download never appears, the most likely cause is the tab losing focus on a mobile browser that suspends background tabs. Keep the tab in the foreground on a phone, and keep the laptop awake while recording. On phones, also disable low-power mode so the encoder stays at full speed. If the download still does not appear, the source duration likely exceeded five minutes once decoding stripped the container overhead; trim it first and retry.
The output codec is the first browser-reported WebM recorder among VP9, VP8, and generic WebM. If a downstream tool rejects the file because it expects a specific codec, re-record in a different browser to switch encoders. The bitrate is derived from the cropped pixel area at 30 fps and is bounded between 180 kbps and 8 Mbps, so a small crop receives a small bitrate. This is a disclosed single-pass setting, not a guaranteed file size or visual quality. Fast motion, grain, source codec, and the browser encoder can change the actual bytes, so do not treat the estimate as a contract.
When the browser exposes a capturable audio track, the tool appends it to the Canvas stream. Support varies, and the source may play audibly during real-time processing. If the output is silent, test in another browser before assuming the source has no audio. Subtitle tracks, chapter markers, attachments, rotation tags, HDR signaling, and most color metadata do not survive the crop, so plan to re-add them afterward or pick a workflow that does not require them.
The output container is patched with a finite Matroska Duration in timestamp-scale ticks so players do not loop the file forever, per the Matroska Media Container Format specification. If a player still reports an infinite duration, the file likely came from a tool that did not run the same patch. Re-export from Video Cropper and confirm the new file decodes at the requested dimensions before reusing it.
Crop a Video With Video Cropper in Your Browser
The fastest path through a problematic crop is to start over with verified inputs and exact coordinates. Video Cropper exposes three stages; running them in order prevents most issues.
- Choose a browser-decodable video file (MP4, WebM, MOV, M4V, or Ogg) and wait for the decoded source dimensions to load in the interface.
- Enter whole-pixel X, Y, width, and height values that stay inside every source frame; keep the output area at or below 3840 × 2160.
- Select Crop video, keep the tab open during real-time processing, then download and fully review the resulting WebM before deleting the source.
Repeat the same three steps with identical numbers to reproduce the same crop, useful when a downstream check fails and you need to confirm whether the issue is the source or the rectangle. If you want to understand whether a moving subject or a fixed frame is the right approach, see Can the Crop Move During the Video in a Video Cropper? before deciding.
Verify the Output Before Deleting the Source
A crop is not finished when the WebM downloads. Open it in the destination player and confirm four things: the duration is finite and matches what you recorded, the visible region matches the coordinates you entered, the audio plays when the source had a capturable track, and the file opens cleanly in the platform where it will be published. A clip that looks right in one player but loops in another usually means the duration patch did not apply; re-export and test again in a second player.
If the output appears shifted or scaled relative to your expectations, the rectangle was inside the source but not where you thought. The tool does not shift, clip, round, or produce a partial file on rejection, so anything you downloaded was produced from a rectangle the tool accepted. Treat the resulting region as ground truth and recompute from there, then re-export. If you need to shrink the file further without changing the crop, re-encode the resulting WebM with bounded presets in a second pass; do not change the crop and the size in the same step, because the two interactions are easier to debug separately.
Limits and Settings That Affect the Result
A short reference table can save a troubleshooting cycle. The values below are taken directly from the verified Video Cropper contract, so they will not drift between releases.
| Problem | Likely Cause | Fix |
|---|---|---|
| Crop button stays disabled | Invalid rectangle | Verify X, Y, width, height are whole pixels, at least 2, and inside the source |
| Decoded dimensions never appear | Codec not supported by browser | Re-encode to a common codec or try a different browser |
| No WebM download | Tab lost focus during real-time recording | Keep the tab foregrounded and disable low-power mode on mobile |
| Output has black edges | Rectangle reached a frame edge | Recompute against decoded dimensions, not remembered values |
| Output is silent | Browser did not expose a capturable track | Re-test in a different browser before assuming no audio |
| Output loops in some players | Player does not honor the duration patch | Re-export and confirm in a second player |
| Limit | Value |
|---|---|
| Accepted file types | MP4, WebM, MOV, M4V, Ogg |
| Maximum file size | 500 MiB |
| Maximum decoded duration | 5 minutes |
| Maximum source side | 4096 pixels |
| Maximum source area | 3840 × 2160 pixels |
| Maximum output area | 3840 × 2160 pixels |
| Minimum width and height | 2 pixels each |
| Bitrate range | 180 kbps to 8 Mbps |
| Output codecs | VP9, VP8, or generic WebM |
When a problem persists after every check above, return to the Video Cropper tool with a fresh file and confirm whether the issue follows the source. If it does, the source needs repair before any further cropping; if it does not, the rectangle math is the next place to look.
Related reading: Common Mistakes When You Use a Video Crop Tool.