Why this is the fastest online video cropper
Browser ffmpeg.wasm croppers are single-threaded, cap out around a 2 GB tab memory, and crash on phone clips above ~200 MB. Most server-side competitors upload to one US region and stream the result back through one origin. We rebuilt the pipeline: presigned upload direct to the nearest Backblaze B2 storage POP, native ffmpeg crop on our server tuned for H.264 output, finished file delivered through Bunny CDN's edge. A 30-second 1080p crop usually clears in 5–10 seconds end-to-end.
Crop, don't resize, when content matters
Resizing is what you do when you need a specific aspect ratio and don't care which pixels survive. Cropping is what you do when specific pixels matter. If there's a webcam overlay in the corner of your screen recording, resizing won't remove it — it'll just shrink it. A crop cuts it out entirely. Same for a sidebar UI you don't want shipped, browser chrome at the top of a tab recording, or a logo watermark another tool baked in.
Sister tools
Cropped output is often the input for the next step. If the new framing should be silent for a Twitter / LinkedIn autoplay-muted embed, mute video strips the audio in a stream-copy. If you need the clip a fixed aspect ratio after the crop, resize video handles the scaling. Stitching multiple cropped takes together? Merge videos concatenates them into one MP4. Need to slow down or speed up after cropping? Video speed controller does that as a single ffmpeg pass.