Fast trim uses the compatible local path
Fast trim lets the local engine use compatible conversion optimizations. This first writer does not promise keyframe-aligned or lossless trimming; the result is remeasured before it is offered for download.
Local video trimmer
Set a start and end for one local clip. Fast trim uses the compatible local path when possible; Exact trim is for frame-oriented boundaries when local re-encoding is supported.
Your video stays on this device. No upload, account, or server-side processing job.
Browser-local workspace
Choose one local MP4, M4V, MOV, or WebM file. JavaScript activates a browser-native preview and capability check; available conversions depend on the codecs supported by this device.
No upload, account, or server-side media job.
Fast trim lets the local engine use compatible conversion optimizations. This first writer does not promise keyframe-aligned or lossless trimming; the result is remeasured before it is offered for download.
An exact boundary requires a local decode and re-encode of the kept section. The workspace makes that cost visible before starting, especially for high-resolution or long sources.
Private browser processing
Aftermath reads selected video bytes only in the current browser. Unsupported codecs are reported clearly rather than sent to another service. High-resolution conversion can use substantial device battery and processing.
Try a measured example
We requested the first second of this recording using Fast trim. The downloaded result was reopened and measured.
| Before trimming · WebM | Bytes: 32,627 Seconds: 1.804 Pixels: 640 × 360 |
|---|---|
| After trimming · MP4 | Bytes: 17,835 Seconds: 1.012 Pixels: 640 × 360 |
Fast trim can follow encoded packet boundaries. Use Exact when the cut point matters. Fast trimming can also retain the source codec inside an MP4 container.
Tested: · Chromium 149.0.7827.55
These files passed through the actual tool controls. Downloads were reopened to check sizes, duration, dimensions, or page structure. Capture used synthetic streams; hardware permissions were not tested.
These synthetic samples are free to reuse under CC0. No personal files or recordings were used. Your results may differ.
Trim a local MP4, M4V, MOV, or WebM video to one chosen start-to-end range. Fast mode uses a compatible local path when a nearby boundary is acceptable; Exact mode requests frame-oriented re-encoding when supported. The separate result is reopened and measured before download. This browser workflow does not join clips, add effects, or promise a lossless or keyframe-exact cut. One completed output is limited to 500 MB in browser memory.
A 90-second clip should keep only 12.5–38.0 seconds, with exact timing preferred over the compatible fast path.
Observed operation: Set the range, choose the timing mode and create a separate video containing only the selected interval.
Review the result: Check the first and last frames, output duration, audio sync and playback across the entire result.
Boundary: Fast trimming may follow media boundaries, while exact trimming can change encoding quality and unsupported tracks.
Keep one chosen time range from a local video using the compatible fast path or an exact re-encode
The selected video stays in the current browser session and is not sent to an Aftermath processing service. How local processing is verified.
Checks the displayed limits and reports or creates a separately downloaded video containing the selected kept time range from one selected local MP4, M4V, MOV, or WebM file.
Reducing byte size without selecting a time range belongs to /video/compress.