The most reliable video cropper tips and common mistakes share one theme: pixel precision and patience. Crop a video to the wrong rectangle and you either clip your subject, leave a black bar, or waste a real-time pass on a file that needs to be redone. The Lizely Video Cropper avoids the worst of these pitfalls by running entirely in the current tab — no upload, no server round-trip — and by refusing any rectangle that falls outside the decoded source. It draws the fixed region into a Canvas, records it as WebM at roughly real-time speed, and only writes a finite Matroska duration when the output is nonempty and decodes with the requested dimensions. That contract is the foundation for everything below: choose the right source, enter whole-pixel coordinates that fit, keep the tab open, and verify the result before deleting the original. The mistakes that follow come from skipping one of those steps.
What the Video Cropper handles — and what it leaves out
A video cropper removes the outer area of every frame by re-recording only the rectangle you specify. The Video Cropper does this locally in your browser — decoding the source, drawing a fixed region into a Canvas using the method described in the WHATWG HTML canvas specification, and recording that Canvas as WebM. It is not a trimmer, resizer, compressor, blur tool, or object remover, and treating it as one is the first mistake people make.
The cropper also applies one fixed rectangle to every frame. It does not track a moving face, follow a car, or shift the crop window over time. If your subject moves, the rectangle you choose will be applied identically across the entire clip, which usually means you need a different tool or a stabilized source. Knowing the lane the tool actually works in is the first tip that prevents wasted exports, and it sets the expectation that the output is a clean WebM rather than a copy of the original container.
Tips for picking a source that crops cleanly
Pick a browser-decodable format first. The cropper accepts MP4, WebM, MOV, M4V, and Ogg, but an accepted extension does not guarantee the codec inside can actually be decoded — that depends on the browser you are using right now. If the dimensions never load after you choose a file, the container or codec is the first thing to check, not the rectangle.
Wait for the source dimensions to populate before typing numbers. The cropper reads the decoded frame size and uses that as the upper bound for X, Y, width, and height. Entering coordinates before the dimensions appear is a common reason people paste a rectangle that overshoots and gets rejected without a partial output, which then looks like the tool "did nothing."
Respect the shared input budget. Positive files up to 500 MiB are accepted, decoded duration above zero and no more than five minutes, no source side above 4096 pixels, and no source area above 3840 × 2160. A file that fails one of these gates cannot be cropped, no matter how perfect the rectangle would be. When size or length is the blocker, trim first with the Video Trimmer or shrink the file with the Video Compressor before sending the result back into the cropper. Cropping is the wrong tool for shortening a recording or hitting a target file size.
How to crop a video with exact pixel coordinates
- Choose a browser-decodable video file and wait until the source dimensions appear on screen — the rectangle fields depend on those numbers.
- Enter the X and Y offsets plus crop width and height in whole source pixels. X moves the crop right from the top-left corner, Y moves it down, width controls horizontal extent, and height controls vertical extent.
- Confirm that width and height are each at least two pixels. Anything smaller fails validation.
- Confirm that X plus width and Y plus height stay inside the decoded source. The cropper rejects rectangles that overflow any frame.
- Confirm the output area — width times height — does not exceed 3840 × 2160 pixels. Anything larger is refused.
- Select Crop video and keep the tab open. Processing runs in real time, so a one-minute source takes roughly one minute while you wait.
- Download the resulting WebM when the recorder finishes, then play the file end-to-end in the destination player before deleting the original.
Mistakes that wreck your cropped video
Most failed exports come from a handful of repeat errors. Skim this list before each crop so you do not have to redo a minute of recording.
- Entering coordinates before the source dimensions load, which usually produces an invalid rectangle and no output.
- Typing decimals like 320.5 instead of whole pixels — the cropper parses untrimmed integer values only.
- Forgetting that X and Y start at the top-left corner, so a value of 0,0 means the crop begins at the very top-left of the source frame.
- Letting X plus width exceed the source width, or Y plus height exceed the source height. The cropper rejects overshoots instead of clipping.
- Setting width or height to 0 or 1. Both dimensions need to be at least two pixels.
- Closing or refreshing the tab during the real-time pass. The MediaRecorder runs in the current page, and the output will be truncated or lost.
- Treating the output bitrate range of 180 kbps to 8 Mbps as a guarantee of file size or visual quality — fast motion, noise, source codec, and browser encoder all change the result, and the contract explicitly does not promise a target size.
- Deleting the original before the entire WebM has been reviewed. Keep the source until you have confirmed crop, duration, audio, and compatibility.
- Assuming subtitles, chapters, rotation tags, HDR signaling, and color metadata are preserved — they are not, so do not rely on them after cropping.
- Expecting the rectangle to follow a moving subject. The cropper applies one fixed region to every frame and does not track motion.
Where the Video Cropper fits among local video tools
Many "common mistakes" are actually category mismatches: people reach for a cropper when they need a trimmer, resizer, compressor, frame extractor, or audio ripper. The table below maps the most frequent task descriptions to the right Lizely tool so you can pick the correct local workflow before you start.
| Task you describe | Video Cropper | Better local alternative |
|---|---|---|
| Cut the same edges off every frame | Yes — fixed rectangle per frame | — |
| Shrink the frame to a smaller resolution | No | Video Resizer |
| Cut a section by start and end time | No | Video Trimmer |
| Reduce file size without changing content | No | Video Compressor |
| Save only the audio track | Audio only when the browser exposes a capturable track | Video to Audio Converter |
| Grab a single frame as a PNG | No | Video Frame Extractor |
| Follow a moving subject with the crop | No — one rectangle for the whole clip | Desktop NLE with motion tracking |
For deeper coverage of pixel accuracy, audio handling, and duration, see Video Cropper Accuracy: Pixels, Audio, Duration. For background on how the finite-duration WebM is written, the relevant container rules are documented in the IETF Matroska Media Container Format draft.
After-crop verification checklist
Verification is the step that turns a "looks fine" export into one you can actually delete the original for. Play the file in the destination player — not just the browser tab — and confirm each of the following.
- Duration is finite and matches the source. The cropper patches a Matroska Duration value into the WebM so the file reports a known length; if the player shows 0:00 or an open-ended clip, re-run the crop without closing the tab.
- Crop placement matches the intended rectangle on multiple timestamps, not just the first frame.
- Audio plays correctly when present. Audio is only included when the browser exposes a capturable track, so a silent output may simply mean the source had no capturable audio.
- Subtitles, captions, chapters, HDR signaling, and rotation are absent. This is expected behavior for the cropper, so plan to re-add anything you need downstream.
- The file opens in the player or editor you actually plan to use. VP9, VP8, and generic WebM are tried in that order, and the first one the browser reports is the one you receive.
Only after the entire output has been reviewed — every timestamp, the audio track, and the destination player — should the original be removed. That single habit prevents the most expensive mistake on this list: deleting a source you cannot recreate.
If you're weighing options, Video Compressor Tips and Common Mistakes to Skip covers this in detail.