Loading video tools…
Loading video tools…
Cut your video to a precise start and end time in your browser.
Your video never leaves your browser. All processing runs locally using Canvas and MediaRecorder.
Drop a video to trim
or click to browse — max 500 MB · MP4, WebM, MOV, AVI
Your video files never leave your device
All processing runs directly in your browser using built-in Web APIs — the Canvas API, Web Audio API, and WebAssembly. Nothing is uploaded to any server. There is no account, no email, and no data retention. You can verify this yourself: open your browser's DevTools Network tab and watch zero outbound file requests while the tool processes your video files.
GDPR-friendly · Works offline after page load · No file size limits beyond your device memory
Upload your video
Drag and drop or click to select your video file.
Set start and end
Drag the sliders or type exact times to mark the clip you want.
Click Trim Video
The selected range is recorded instantly in your browser.
Download the result
Save your trimmed clip.
Each social platform has specific duration, file size, and format requirements. Use this table to trim your videos to the exact specs each platform expects:
| Platform | Max Duration | Max File Size | Format | Recommended Resolution |
|---|---|---|---|---|
| Instagram Feed | 60 seconds | 650 MB | MP4 (H.264) | 1080×1080 (square) or 1080×1350 (portrait) |
| Instagram Reels | 90 seconds | 650 MB | MP4 (H.264) | 1080×1920 (9:16 vertical) |
| Instagram Stories | 60 seconds | 650 MB | MP4 (H.264) | 1080×1920 (9:16 vertical) |
| TikTok | 10 minutes | 287.6 MB | MP4 or MOV | 1080×1920 (9:16 vertical) |
| YouTube Shorts | 60 seconds | 256 MB | MP4 | 1080×1920 (9:16 vertical) |
| YouTube Standard | 12 hours | 256 GB | MP4, MOV, AVI, WMV, FLV | 1920×1080 (16:9) or higher |
| Twitter/X | 2 min 20 sec | 512 MB | MP4 (H.264) | Up to 1920×1200, min 32×32 |
| 10 minutes | 5 GB | MP4 | 256×144 to 4096×2304 | |
| Facebook Feed | 240 minutes | 10 GB | MP4 or MOV | 1280×720 minimum |
| Facebook Stories | 20 seconds | 4 GB | MP4 or MOV | 1080×1920 (9:16 vertical) |
Trim to 60–90 seconds max. Use 1080×1920 resolution. File size rarely an issue for short clips.
YouTube allows up to 12 hours. LinkedIn caps at 10 minutes. Use 1920×1080 or higher.
Twitter: 2:20 max. Instagram Feed: 60 seconds. Keep file under 512 MB for best compatibility.
You need to trim a video when the full recording is longer than what you actually want to share or when a platform has a duration limit. Here are the most common scenarios:
Video trimming precision depends on how video files are structured. Unlike images, where every pixel is independent, video frames are interdependent — most frames store only the changes since the last full frame, not the complete picture. This compression scheme, used by nearly all modern codecs (H.264, H.265, VP9, AV1), means you can't always cut a video at an arbitrary millisecond with perfect accuracy unless you re-encode it.
A typical video has three types of frames: I-frames (intra-coded, full frames that can be decoded independently), P-frames (predicted frames that reference the previous frame), and B-frames (bidirectional frames that reference both previous and future frames). I-frames, also called keyframes, appear every 1–2 seconds in typical footage — more frequently in high-action scenes, less so in static shots. When you trim a video, the ideal start point is an I-frame, because the decoder can begin playback immediately without needing prior context.
If you trim at a non-keyframe position — say, 5.3 seconds into a video where the nearest I-frame is at 5.0 seconds — one of two things happens. Either the tool re-encodes the output so the new start point becomes an I-frame (what this tool does, via the browser's MediaRecorder API), or it performs a "lossless cut" by keeping the original codec data and starting at the nearest I-frame before your chosen point, then skipping forward internally to your exact timestamp. The former preserves your exact cut point but re-compresses the video slightly; the latter avoids quality loss but may shift your cut by up to a second or two.
For most use cases — social media clips, removing intros, extracting highlights — frame-accurate trimming to the exact millisecond isn't necessary. A half-second margin is imperceptible. But for professional editing, sync-critical work, or splicing footage that will be further processed, understanding the keyframe structure matters. Desktop tools like FFmpeg offer both modes: re-encode for exact cuts with slight quality loss, or stream-copy for lossless cuts with keyframe-aligned boundaries. Browser-based tools like this one default to re-encoding because it's simpler and guarantees the output plays smoothly on all devices.
The fundamental tradeoff in video trimming is between convenience and quality preservation. Re-encoding — what this tool does — decodes the selected portion of your video back into raw frames, then re-compresses them with the browser's chosen codec and bitrate. This guarantees the output starts and ends exactly where you specify, with no playback glitches, at the cost of a small quality hit from the second round of compression. Lossless cutting, by contrast, copies the exact codec data from the input to the output without recompression, preserving every bit of the original quality, but requires the cut points to align with keyframes and may not work if the output format differs from the input.
For short social media clips trimmed once from a high-quality source, re-encoding quality loss is negligible. A 1080p30 video re-encoded at 5–10 Mbps (typical for browser MediaRecorder output) looks nearly identical to the source unless you zoom in frame-by-frame. The real danger is repeated re-encoding — trimming a clip, then trimming the trimmed clip, then exporting that again. Each generation compounds compression artifacts: softening, blockiness, color banding. Professional editors avoid this by working with "proxies" (lower-quality preview files) for editing, then rendering the final output from the original high-res sources in a single encode pass.
Browser-based trimming tools inherently re-encode because the MediaRecorder API doesn't expose low-level codec stream manipulation — it's designed for simplicity, not professional-grade lossless workflows. If you need a truly lossless trim, use a desktop tool like FFmpeg with the -c copyflag, or a GUI editor like LosslessCut that wraps FFmpeg. These tools can extract a segment by copying the codec bitstream directly, but you'll sacrifice millisecond precision (cuts snap to the nearest keyframe) and may encounter sync issues if your source video has variable frame rate or non-standard codec parameters.
The right choice depends on your end goal. Publishing a 60-second Instagram Reel from a 5-minute raw recording? Re-encoding is fine — Instagram will re-encode it again on upload anyway. Preparing archival footage or trimming 4K 60fps gameplay for a YouTube montage where every frame counts? Lossless cutting preserves maximum quality, accepting keyframe-aligned boundaries. For browser convenience without software installation, this tool prioritizes ease of use and universal compatibility over the edge-case benefits of lossless stream copying.
Trimming effectively isn't just about setting a start and end time — it's about understanding what you're cutting and why. Here are the most common trimming techniques and when to use each.
The most common trim: cutting dead air or setup time from the beginning and end of a recording. Phone videos often start with a few seconds of aiming the camera or starting the recording app, and end with fumbling to stop it. Trimming 3–5 seconds off each end is standard practice before sharing. For screencasts or tutorials, trim the desktop setup phase at the start and the "okay, that's it" sign-off at the end, leaving only the core content.
You recorded a 20-minute live stream or lecture, but only 90 seconds in the middle is worth sharing as a standalone clip. Set the start time to just before the key moment begins, and the end time just after it concludes, leaving a small buffer (1–2 seconds) on each side so the clip doesn't feel abruptly cut-in or cut-out. This buffer is especially important if the audio has speaking — cutting mid-word or mid-syllable is jarring, while a breath or pause feels natural.
Your video is 95 seconds, but Instagram Reels caps at 90. Rather than arbitrarily trimming 5 seconds off the end, watch through and identify the least essential 5 seconds — often mid-content padding, a repetitive section, or an extended pause. Trim those specifically, or speed up the entire video slightly using a speed changer tool (1.05× speed is imperceptible but saves 5% duration) before trimming to length.
If you recorded a video in one take and made a mistake halfway through, trim the mistake out by extracting the good footage before and after it, then merging them. This tool handles one trim at a time, so you'd trim 0:00–5:30 (everything before the mistake) and save it, then trim 6:00–10:00 (everything after the mistake) and save that, then use a video joiner to concatenate the two clips seamlessly. Alternatively, re-record the whole section if the mistake is extensive — sometimes a clean retake is faster than multi-segment splicing.
If you have 20 videos that all need the first 10 seconds removed, this tool processes them one at a time, which is tedious but straightforward. For true batch operations, desktop tools or scripts (like FFmpeg with a loop) are more efficient. This tool excels at single-video trimming where you need to visually confirm the exact cut points before committing.
Start with the highest quality source you have. Trimming a 1080p video down to a 60-second clip produces better output than trimming a pre-compressed 720p version of the same footage. Avoid trimming an already-trimmed file. If you trim a video, review it, decide you want a different section, go back to the original recording and trim again from that, rather than trimming your previous output. Export once. If you need to both trim and apply other edits (like adding text or a watermark), do them all in one tool session or workflow rather than trimming, exporting, re-importing, editing, and exporting again — each export compounds quality loss.
Unlike most online tools, Toolivon processes everything directly in your browser using the Web APIs built into Chrome, Firefox, Safari, and Edge.
Last updated: