Trim MP4, MOV, AVI, MKV, WebM and any video format. No re-encoding, no quality loss. Set exact timestamps. Free, no watermarks.
Process files in seconds with our optimized servers
Set exact start and end points with frame accuracy
Maintain original quality with smart re-encoding
HH:MM:SS.sss format for millisecond precision (e.g., 00:01:23.500). Scrub the preview to find exact cut points, or type the values directly. Set multiple in/out pairs to keep several segments from one source.Trimming is the single highest-leverage edit you can make to a video: it cuts the parts viewers skip (intros, dead air, mistakes), brings the file under platform length limits, and shrinks file size proportionally without touching quality. Done right, trimming is a stream copy — the original H.264 / H.265 / AV1 video and AAC / Opus audio streams are written straight into the new container with no decode-encode cycle, so the output is bit-for-bit identical to the kept frames of the source. Common scenarios:
Need to compress after trimming, or convert containers first? See Video Compressor, MOV to MP4, and the per-format trimmers below: Trim MP4, Trim MOV, Trim MKV, Trim WebM.
| Setting | What happens | Speed | Quality | Cut precision |
|---|---|---|---|---|
| Stream copy (default when keeping codec) | Container is rewritten; video / audio streams copied byte-for-byte | Seconds even for hour-long files | 100% identical to source | Limited to nearest keyframe (~every 2–10 seconds for typical H.264 / H.265) |
| Re-encode (triggered by changing codec, CRF, or resolution) | Frames are decoded and re-encoded to your settings | Roughly real-time per source minute, CPU-bound | Slight loss — controlled by CRF (18 = visually lossless, 23 = default, 28 = small) | Frame-accurate — cut exactly where you ask |
If you change Video Codec, Constant Quality, or anything in the resize / scale section, the tool re-encodes (and the cut becomes frame-accurate). Leave all of those at default and the trim is lossless and finishes in seconds.
| Platform | In-app recording max | Uploaded video max | Notes |
|---|---|---|---|
| Instagram Reels | 90 seconds | 20 minutes (since late 2025) | Algorithm still favors <90 s for discovery |
| TikTok | 10 minutes | 60 minutes (gradual rollout) | Most engagement still on 15–60 s clips |
| YouTube Shorts | 60 seconds in-app | 3 minutes (raised October 2024) | Vertical or square only; licensed music still 60 s |
| X / Twitter (free) | n/a | 2 min 20 s (140 s), 512 MB | Premium: up to 4 hours on web / iOS |
| n/a | 10 minutes | Native uploads only | |
| WhatsApp Status | 60 seconds (raised from 30 s in 2023) | 60 seconds | Auto-deletes after 24 h |
| Discord (free) | n/a | 10 MB per file (lowered Sept 2024) | Nitro Basic: 50 MB; Nitro: 500 MB |
MP4, MOV, MKV, WebM, AVI, WMV, FLV, MTS / M2TS, MPEG / MPEG-2, MPG, M4V, 3GP / 3G2, TS, VOB, OGV, MXF, ASF, F4V, RM / RMVB, AVCHD, DivX, Xvid, and pure HEVC / AV1 streams — over 30 formats. The output uses the same container as the input by default; switch containers under the optional codec settings if you need a different one.
Not when the default stream-copy path is used. The kept frames are written to the new container without re-decoding, so the output is byte-for-byte identical to that span of the source — same bitrate, same codec, same chroma, same color profile. Quality only changes if you opt into re-encoding by changing the codec, CRF, or resolution.
H.264, H.265, and AV1 are inter-frame codecs: most frames (P- and B-frames) depend on a recent keyframe (I-frame), so a clean lossless cut can only start on a keyframe. Most cameras and screen recorders space keyframes 2–10 seconds apart, so a lossless trim snaps to the nearest one. For frame-accurate cuts, re-enable encoding by setting a target codec or CRF — the tool will decode and re-encode the boundary segment and the rest is frame-precise.
Yes — add multiple start / end pairs in the trim panel and each kept segment is written to its own output file. To stitch them back into a single video without gaps, run them through Video Cutter or merge the outputs.
Yes. Stream-copy trims keep the original audio timestamps relative to the kept video frames, so lip-sync is preserved. If a clip drifts after trim, it almost always means the source itself had A/V drift (common on long screen recordings or some webcam captures). Re-encoding with default settings rebuilds timestamps and usually fixes the drift.
There is no fixed cap published — the server-side processing is bounded by upload size and connection speed and disk. In practice, files up to a few GB work on a current laptop without issue; very large 4K source files (20+ GB) may be slow on low-RAM devices. If a file is too large, compress first with Video Compressor and then trim.
Yes. The trimmer runs in any modern mobile browser (Safari 14.1+, Chrome, Firefox, Edge). On iOS, files import from Photos via the standard file picker; on Android, files come from local storage or Drive via the file picker. No app install, no account.
The initial page load needs internet, but once loaded the trim itself happens in your browser — your file isn't uploaded to a server for processing in the lossless stream-copy path. You can disconnect after the page loads and the trim still completes (the result is downloaded locally when done).
When the output container stays the same (MKV → MKV, MP4 → MP4), embedded subtitle tracks, chapter markers, and multiple audio tracks are preserved through the stream copy. Switching containers — for example MKV to MP4 — keeps only what the target container supports (MP4 typically keeps the first audio track and mov_text subtitle streams; chapter markers may be lost). See MKV to MP4 for that conversion specifically.