You record a bug repro, a product demo, or a walkthrough for a client. It plays fine on your machine, but the frame also shows things that should not leave it: a customer's name in a sidebar, an internal staging URL, a private Slack channel, a second monitor's worth of desktop clutter. The instinct is to drag a crop box, cut the region out, and send the file. That instinct is right — cropping is the correct fix here, not compression, and not trimming. But a crop box is a fixed rectangle over a moving timeline, and the way you apply it decides whether the sensitive region actually leaves the file. One disclosure up front: I work with VideoBee, whose cropping tool is mentioned as the GUI option below; the ffmpeg approach needs no product at all.
What a crop actually does to the file
Cropping is not metadata. The output frame is literally width × height pixels of the input, and everything outside the rectangle no longer exists in the file — there is no hidden data to recover. That is exactly why crop is the right choice for removing a region you never want seen: unlike a blur, there is nothing left to sharpen or reverse.
Two consequences follow from that:
- The video gets re-encoded. You cannot apply a filter and stream-copy the video at the same time; ffmpeg will refuse with "Filtering and streamcopy cannot be used together." So a crop is a destructive edit — work from a copy and keep the original.
- The audio does not have to be. The audio track is untouched by a spatial filter, so copying it keeps it bit-exact.
Crop, blur, or cover — pick by intent
- Crop when the region should never be seen and the remaining frame still makes sense without it. The output aspect ratio changes, which we deal with below.
- Blur when the layout must stay intact — a fixed-size app window, a form, a design that loses meaning without the region. Blur keeps the pixels present; a weak blur over high-contrast text is sometimes still legible, so check the result at full resolution.
- Cover (a solid rectangle drawn over the region, like a screenshot annotation baked into the video) when you need the layout and a guaranteed opaque block. It is the only option that is visually self-evident to the viewer. Crop is the strongest of the three for privacy because the data is gone. It is also the most constrained, because the rectangle is static.
The failure mode: content that moves, or appears later
A crop rectangle covers one fixed area for the entire duration. The sensitive content usually does not cooperate:
- A tooltip or dropdown appears at second 40, outside your rectangle.
- A notification slides in from a screen edge you cropped away on the other side.
- The cursor moves into the sensitive region halfway through, and now your crop box sits over the wrong area. So define the region across the whole timeline, not from the first frame. Scrub the recording end to end before choosing the rectangle, and note the moments where something sensitive appears outside it. If the sensitive area occupies the center of the screen at some point, a fixed crop cannot save that take — record again, or cut that segment out (trimming) before cropping. Cropping and trimming are different operations: one removes pixels from the frame, the other removes seconds from the timeline, and a privacy fix usually needs the right one or both.
Doing it with ffmpeg
Here is a concrete example. A 1920×1080 recording with an internal sidebar occupying the right 720 pixels. Keep the left 1200×1080:
ffmpeg -i repro.mp4 -vf "crop=1200:1080:0:0" -c:a copy repro-cropped.mp4
The filter syntax is crop=w:h:x:y — output width, height, then the top-left corner of the rectangle. Expressions like iw (input width) and ih (input height) let you compute offsets, e.g. (iw-ow)/2 centers the window horizontally.
Two details that bite:
- Use even dimensions. Common pixel formats like yuv420p store chroma in 2×2 blocks, so encoders expect even width and height. An odd crop size can be rounded by the filter chain or fail at encode depending on your build; picking even numbers deliberately avoids the ambiguity.
- Verify the output, do not trust the command. Check the dimensions actually written to the file: ffprobe -v error -select_streams v:0 \ -show_entries stream=width,height -of csv=p=0 repro-cropped.mp4 Then scrub the cropped file end to end and confirm the region is absent in every frame — that is the check that matters, and it takes a minute. One more thing to expect: 1200×1080 is a 10:9 ratio. Players and platforms handle nonstandard ratios differently — some letterbox, some pad, and a social feed may add its own treatment. If the recipient just needs the repro, that is fine; if the video is going on a feed, decide the final ratio first and crop to it.
If you would rather drag the box
For a one-off edit, a GUI avoids the arithmetic entirely. VideoBee's video cropper runs in the browser: you drag the frame over the area to keep or pick a preset ratio, or type exact pixel dimensions when you need the crop to line up precisely. Per the tool's page, it accepts files up to 5 GB in 30+ formats (MP4, MOV, MKV, WebM, AVI and more), exports MP4, and is free with no sign-up and no watermark; files are processed in the cloud and result files are deleted after processing, typically within 24 hours. Those are the page's claims, not my test results — the same scrub-through check applies regardless of which tool cuts the pixels.
Before you send
- The sensitive region is absent in every frame, including tooltips and notifications near the end.
- The remaining frame still tells its story — you did not crop out the error message the ticket is about.
- Audio is intact and was never the problem.
- The output plays in the destination (the ticket portal, the client's player), not just yours.
- The original recording is still on your machine. Cropping a region out takes one rectangle and one re-encode. The discipline is in choosing the rectangle against the whole timeline, and in checking the output instead of assuming the command did what you meant.

Top comments (0)