The reliable substitute for an in-app crop tool that will not load your file is a local browser-based cropper such as Video Cropper, which takes four whole-pixel values — X offset, Y offset, width, and height — from the source frame's top-left corner and re-records the chosen region as a downloadable WebM. That approach works because no upload is required, decoding happens inside the current tab using whichever codec the browser supports, and the crop is defined by four whole numbers rather than a drag rectangle that drifts between frames. The default values already select the full frame, so nothing changes until new numbers are typed, and the output is a WebM file you can save, play, and verify before deleting anything from the original source. This article walks through the situations where an in-app cropper fails, the exact limits that govern the local replacement, the step-by-step procedure, and the verification checks that should run before the source clip is removed.
為何應用程式內建的影片裁切工具會失效
Built-in crop controls break down in a handful of predictable ways. The most common reason a crop button does nothing is that the file exceeds the editor's size cap: many mobile apps refuse files larger than a few hundred megabytes, and several web editors reject anything past a one-gigabyte ceiling. A second cause is codec mismatch. The file opens as a thumbnail and then stalls, or the timeline loads but the preview stays black, because the editor's decoder cannot read the container or the underlying H.264, HEVC, VP9, or AV1 stream. A third failure is upload itself. Some editors route every clip through a server, and when that upload times out, gets blocked by a corporate network, or fails silently on a slow connection, the crop controls never appear at all. A fourth scenario is older software that simply has no crop feature: Windows Media Player, for example, plays files but cannot edit them, so its crop button does not exist rather than malfunctioning. A fifth case is a bug where the crop rectangle saves correctly inside the editor but the export step drops it, producing an output that matches the source. Each of these situations leaves the user with a clear goal — remove the outer area of one video — and no working control inside the app they opened.
改用在本機執行的瀏覽器式裁切工具
A browser-based cropper bypasses every reason above because it runs entirely on the user's machine, decoding the file with the browser's built-in media stack rather than an app-specific decoder. Video Cropper accepts an MP4, WebM, MOV, M4V, or Ogg file, waits for the decoded dimensions to appear in the page, and then accepts four whole-pixel numbers — X offset, Y offset, crop width, and crop height — measured from the top-left corner of the source frame. The default values already select the full frame, so opening the tool does nothing destructive. Once coordinates are typed and the crop is triggered, the page plays the source locally, draws only the requested rectangle into an opaque Canvas at 30 frames per second using the standard drawImage method described in the WHATWG HTML Canvas specification, records that Canvas stream as a WebM, and offers the resulting file for download. Nothing is uploaded, nothing is stored on a remote server, and the original file stays on disk the whole time. For readers who want a deeper look at why this works without sending the file anywhere, the guide Can I Use a Video Cropper Without Uploading a File? covers the same point with extra detail.
當其他工具無法運作時，如何在本機裁切影片
The procedure is short because most of the work happens inside the browser tab. The following steps cover a typical run on a desktop browser such as Chrome, Edge, or Firefox.
- Open Video Cropper in the current tab and choose a browser-decodable video file. The page reads the source locally and reports the decoded width and height once they have loaded. Wait for those dimensions to appear before continuing, because typing coordinates before the dimensions load almost always produces a rejected rectangle.
- Enter whole-pixel values for X, Y, width, and height in the input fields. X and Y are offsets from the top-left corner; width controls the horizontal extent; height controls the vertical extent. Every value must be a nonnegative whole pixel count, width and height must each be at least two pixels, and X plus width and Y plus height must both remain inside the decoded source.
- Select the Crop video action. The page begins real-time processing: it plays the source locally, draws the chosen rectangle into a Canvas frame by frame, and records the Canvas stream as a WebM in the current tab. Keep the tab open and the page in the foreground. A one-minute source takes roughly one minute; a five-minute source takes roughly five minutes.
- When the recording finishes, the page offers the WebM for download. Save it to a known folder, then play it end to end in a media player or the destination platform to confirm that the crop edges look right, the audio still plays when present, and the container reports a finite duration.
Source and Output Limits to Check Before Cropping
Before typing coordinates, confirm that the source fits within the tool's safety budget and that the planned rectangle is geometrically valid. The table below summarizes the rules that determine whether the crop can start at all.
| Property | Source requirement | Output constraint |
|---|---|---|
| Container | MP4, WebM, MOV, M4V, or Ogg | WebM (VP9, VP8, or generic) |
| File size | Up to 500 MiB | Derived from the cropped area and chosen bitrate |
| Decoded duration | Above zero and at most five minutes | Same as source |
| Largest source side | No side above 4096 pixels | N/A |
| Decoded frame area | No source area above 3840 × 2160 | Output area no larger than 3840 × 2160 |
| Rectangle edges | X plus width ≤ source width, Y plus height ≤ source height | Width and height each at least 2 pixels |
| Capture rate | N/A | 30 frames per second |
An accepted extension does not guarantee that decoding will succeed, because support depends on the current browser's media stack. If the dimensions never appear after the file is chosen, the codec is not decodable in that browser and the crop cannot begin — switch to a different source file or a different browser before changing any other setting.
Coordinate Validation Walkthrough
Take a source clip decoded at 1920 × 1080 and plan a crop rectangle starting 100 pixels right of the left edge and 50 pixels below the top edge, sized at 800 pixels wide by 600 pixels tall. The four values 100, 50, 800, and 600 are all nonnegative whole numbers, and width and height are both at least two. The right edge sits at X + width = 100 + 800 = 900, which is less than the source width 1920. The bottom edge sits at Y + height = 50 + 600 = 650, which is less than the source height 1080. The output area is 800 × 600 = 480,000 pixels, which is well below the 3840 × 2160 cap. Every check passes, so the crop can start. If any one of those checks fails — for example Y + height = 1081 when the source is 1080 — the tool rejects the rectangle without shifting, clipping, rounding, or producing a partial file.
What the Cropped WebM Keeps and Drops
The crop changes the visible frame region only; it is not a trim-by-time, resize, compress-only, redact, blur, or object-removal tool. The same single rectangle is applied to every frame, so the tool does not track a moving subject and cannot follow a face or object across the timeline. When the browser exposes an audio track through media capture, the tool appends that audio to the Canvas stream and the resulting WebM plays with sound. If the source plays audibly during real-time processing, that is a side effect of the recording setup rather than a failure — it does not mean the audio is missing from the output. Support for audio capture varies, so always listen to the downloaded file before assuming the track survived. What the crop does not preserve is the broader metadata: subtitles, chapters, attachments, rotation tags, HDR signaling, and many container-level fields are dropped, and the output WebM may report a different feature set than the original. Treat the WebM as a freshly recorded file with the cropped rectangle, not as a faithful copy of the source.
Verify the Result Before Deleting the Source
Browser MediaRecorder output occasionally omits a finite container duration, so the tool uses an already standards-tested WebM duration writer shared with Video Compressor: it parses Segment Info and TimestampScale and inserts a big-endian Matroska Duration value in timestamp-scale ticks, as documented in the IETF Matroska Media Container Format specification. The result must remain nonempty and decode with the requested dimensions, but the safest confirmation is a manual playthrough. Run through this short checklist before removing the original clip from disk:
- Play the downloaded WebM end to end in the player where the cropped clip will actually be used, and confirm the duration is reported as a positive number rather than zero or unknown.
- Scrub to the very first and very last frame and confirm the cropped edges are stable across the entire clip, with no flicker or reframe drift.
- Listen for audio. If the source had a soundtrack and the output is silent, the browser did not expose a capturable audio track and the file should be treated as picture-only.
- Open the file in the destination platform — a social upload queue, a presentation slide, an editing timeline — and confirm it imports without complaint.
Only when all four points check out should the original source file be deleted.
If you're weighing options, What to Verify Before You Use a Video Crop Tool covers this in detail.