Why is the output WebM and not MP4?

Browser MediaRecorder produces WebM — it's the only video format the API can write reliably across browsers. WebM plays everywhere modern (Discord, Slack, YouTube uploads, GitHub, Notion). For MP4, convert the result with ffmpeg locally: `ffmpeg -i trimmed.webm -c:v libx264 trimmed.mp4`.

Why does processing take as long as the trimmed clip?

MediaRecorder records in real time. There's no faster path in the browser API — a 60-second trim takes 60 seconds. For instant trim with no re-encoding, use desktop ffmpeg with `-c copy`, which only rewrites the container and is essentially instant.

Will I lose video quality?

Slightly — the source is decoded and re-encoded at VP8/VP9, so it's a generation-loss step. Typical loss is small (you wouldn't notice in a chat preview), but for archival quality use ffmpeg with `-c copy` to trim without re-encoding.

Can I do frame-precise trims?

Roughly — the trim handles snap to ~30ms keyframe boundaries, and the actual cut point may be the nearest seekable frame in the source video. For frame-perfect editing, use a video editor with native timeline tools.

Does it preserve audio?

Yes. If the source has audio, the trimmed output keeps it (encoded as Opus in the WebM container). To trim WITHOUT audio, use the video-mute tool first, then trim — or trim first and then mute.

Is the video uploaded anywhere?

No. The file is decoded by the browser, played into a hidden video element, captured by MediaRecorder, all in browser memory. Open DevTools → Network during use and you'll see zero outbound requests. Your video stays on your device.

Audio, Video & Voice · Free tool

Video Trimmer

Cut MP4 and WebM videos directly in your browser. Set start and end points, preview, and save the clip with no watermark or uploads—free and instant.

Updated June 2026

Found this useful?Email Buy Me a Coffee

What it does

Drop a video (MP4, MOV, WebM, or any format your browser plays), drag the trim handles to mark a start and end point, and export just that section. The whole pipeline stays in your browser — there's no upload to a third-party server, no waiting in a queue, no watermark, and no time limit beyond your browser's memory. Works on phones (Chrome Android and Safari iOS both support it) for trimming clips on the go.

The most common reasons people trim videos: cutting a 30-second highlight out of a long clip to share on social, removing the dead time at the start or end of a screen recording before posting, extracting a single answer from a longer interview or panel discussion, or just chopping down a phone clip to fit a 60- second platform limit.

Output is a WebM file (VP8/VP9 video, Opus audio if your source had audio). WebM is the format browser MediaRecorder can write — it plays in every modern app including Discord, Slack, Notion, GitHub, YouTube uploads, and most messaging clients. If you specifically need MP4, run the WebM through ffmpeg or any free converter afterward.

Embed this tool on your siteShow snippet

Paste this snippet into any page. Loads on-demand (lazy), no tracking scripts, and sized to most dashboards. Replace the height to fit your layout.

<iframe src="https://freetoolarena.com/embed/video-trimmer" width="100%" height="720" frameborder="0" loading="lazy" title="Video Trimmer" style="border:1px solid #e2e8f0;border-radius:12px;max-width:720px;"></iframe>

Embed docs →

How to use it

Drop your video into the upload area or click to browse.
Use the trim handles below the preview — drag the left handle to set start, right handle to set end. The selection highlights the kept range.
Hit play to preview the trimmed clip before exporting. Adjust handles if the cuts feel slightly off.
Click Export. The tool plays the clip from start to end at 1× speed in the background while recording the visual + audio stream into a new WebM. Processing time = trimmed clip length (real-time).
Click Download when processing finishes. The file's audio/video is intact at the source resolution and framerate.

How it works

The uploaded video is loaded into a hidden HTML5 video element. We seek to your trim start and start playing, using video.captureStream() to grab a MediaStream with both video and audio tracks. A MediaRecorder writes that stream to a WebM buffer. When the playback head reaches your trim end, we stop the recorder and download the buffer as a file.

Because MediaRecorder runs in real time (no fast-forward mode in the browser API), processing time matches the duration of the trimmed clip — a 60-second clip takes 60 seconds to export. Picture quality is re-encoded at VP8/VP9 using the browser's default bitrate, which is generally good for screen content and slightly soft for high-motion footage compared to the original H.264.

When to use this tool

Cutting a highlight from a longer clip to share on social media.
Removing the dead time at the start/end of a screen recording before posting.
Extracting a quote, demo, or answer from a long interview/panel/talk.
Trimming phone-camera clips down to fit platform-specific time limits (60s for Reels, 3min for TikTok, 15min for Shorts).

When not to use it

Multi-cut editing (remove the middle, keep the start and end) — this is single-range trim. Use a video editor for multi-cut.
Adding music, captions, or transitions — that's editing, not trimming. Use CapCut, DaVinci Resolve, iMovie, or similar.
When you need to keep the original codec/container (MP4 stays MP4) — output is always WebM. For codec-preserving trim, use ffmpeg locally with `-c copy`.
Long videos (>30 minutes of total source) — browser memory becomes a bottleneck. Use a desktop tool for long sources.

Frequently asked questions

Why is the output WebM and not MP4?: Browser MediaRecorder produces WebM — it's the only video format the API can write reliably across browsers. WebM plays everywhere modern (Discord, Slack, YouTube uploads, GitHub, Notion). For MP4, convert the result with ffmpeg locally: `ffmpeg -i trimmed.webm -c:v libx264 trimmed.mp4`.
Why does processing take as long as the trimmed clip?: MediaRecorder records in real time. There's no faster path in the browser API — a 60-second trim takes 60 seconds. For instant trim with no re-encoding, use desktop ffmpeg with `-c copy`, which only rewrites the container and is essentially instant.
Will I lose video quality?: Slightly — the source is decoded and re-encoded at VP8/VP9, so it's a generation-loss step. Typical loss is small (you wouldn't notice in a chat preview), but for archival quality use ffmpeg with `-c copy` to trim without re-encoding.
Can I do frame-precise trims?: Roughly — the trim handles snap to ~30ms keyframe boundaries, and the actual cut point may be the nearest seekable frame in the source video. For frame-perfect editing, use a video editor with native timeline tools.
Does it preserve audio?: Yes. If the source has audio, the trimmed output keeps it (encoded as Opus in the WebM container). To trim WITHOUT audio, use the video-mute tool first, then trim — or trim first and then mute.
Is the video uploaded anywhere?: No. The file is decoded by the browser, played into a hidden video element, captured by MediaRecorder, all in browser memory. Open DevTools → Network during use and you'll see zero outbound requests. Your video stays on your device.

Learn more

Explore more audio, video & voice tools

100% in-browserNo downloadsNo sign-upMalware-freeHow we keep this safe →