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 to the duration you drop. The trim is frame-accurate — the kept range is decoded and re-encoded at the visually-lossless default preset, so the clip starts exactly where you say and stays visually true to 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 |
|---|---|---|---|---|
| Default settings | The kept range is decoded and re-encoded at the visually-lossless default preset (CRF 18 H.264 / CRF 17 HEVC) | Proportional to clip length, CPU-bound | Visually indistinguishable from the source | Frame-accurate — cut exactly where you ask |
| Custom settings (codec, CRF, or resolution) | Frames are re-encoded to your settings | Proportional to clip length and codec | Controlled by CRF (18 = visually lossless, 23 = default, 28 = small) | Frame-accurate — cut exactly where you ask |
Every trim re-encodes the kept segment, which is what makes the cut frame-accurate — there is no snapping to the nearest keyframe. Change Video Codec, Constant Quality, or the resize / scale settings only when you also want a different format, quality target, or resolution.
| 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 visibly. The trim re-encodes the kept span at the visually-lossless default preset (CRF 18 for H.264 / CRF 17 for HEVC), so the output is not byte-identical to the source but is visually indistinguishable from it. The upside is precision: the cut starts exactly where you set it instead of snapping to a keyframe. Quality only drops noticeably if you deliberately choose a higher CRF, a lower quality preset, or a smaller resolution.
With XConvert it should be — every trim decodes and re-encodes the kept segment, so the cut starts on the exact frame you request. The snapping you may have seen in other tools comes from stream copying: H.264, H.265, and AV1 are inter-frame codecs where most frames (P- and B-frames) depend on a recent keyframe (I-frame), so a cut made without re-encoding can only start on a keyframe — and cameras space those 2–10 seconds apart. Here the keyframe layout doesn't affect the cut point.
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. Video and audio are re-encoded from the same start point, 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 to a constant frame rate usually fixes that.
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.
Your file is uploaded over an encrypted connection and trimmed on our servers, then offered for download when done; files are deleted automatically after a few hours. You need an active connection while the file uploads and trims; the finished clip downloads when processing completes.
Not reliably. The trim re-encodes to a single video and audio track, and embedded subtitle tracks, chapter markers, and secondary audio tracks are not guaranteed to carry over — lossless audio like FLAC or DTS also comes out as a lossy codec. For multi-track archival edits use a desktop muxer like MKVToolNix and keep the untouched source; use this page when you want a quick, frame-accurate clip. See MKV to MP4 for container conversion specifically.