Cut MP4 files into exactly what you need

Yes - no subscription, no trial, no watermark, no daily limit, and no account. The tool runs entirely in your browser, so there are no server costs to recover.

No. Your browser reads the file directly from your disk using the File API. Nothing is transmitted anywhere - you can disconnect from the internet after the page loads and the cut will still work.

Browsers can decode MP4 but can only encode WebM natively. Producing an MP4 would require either uploading to a server or loading a heavy conversion library. We chose to keep your file local. Converting WebM to MP4 afterwards takes one command or one drag into HandBrake.

Run ffmpeg -i cut.webm -c:a aac cut.mp4 in a terminal, or drag the file into HandBrake and pick an MP4 preset. Both are free. At 8 Mbps the single conversion introduces no visible quality loss.

There's no imposed limit. Because the file is read from disk rather than loaded into memory all at once, multi-gigabyte recordings open normally. The practical ceiling is whatever your browser can decode.

A small amount, because the segment is re-encoded during capture. At 8 Mbps the difference is very hard to see on typical footage. If you need a mathematically lossless cut, use FFmpeg's stream-copy mode: ffmpeg -ss 30 -to 60 -i in.mp4 -c copy out.mp4.

The browser records the selection in real time as it plays - that's how in-browser capture works without a server. A 40-second cut takes about 40 seconds. Server-based cutters are faster but require uploading your file first.

Yes. After the first download, drag the handles to a new span and cut again. The source stays loaded, and each output filename includes its own timestamps so nothing overwrites anything.

You can type timecodes to the millisecond, and arrow keys step a single frame at a time. The actual cut lands on the nearest frame boundary - typically within 33–42 ms depending on the video's frame rate.

Yes. The timeline handles work with touch and the layout adapts to small screens. Real-time export works on modern mobile browsers, though the device needs to stay awake for the duration, so long cuts are easier on a desktop.

Proportionally, yes - a 20-second cut from a 20-minute video is roughly a sixtieth of the footage, so the output is much smaller. But that's from keeping less video, not from compression. The bitrate stays high.

Not in a browser. Lossless stream-copy cutting requires direct access to the container's frame index, which is only possible with a native tool. FFmpeg's -c copy mode does exactly this if you need it.

Trimming removes footage from the start and/or end of a file. Cutting extracts a span from anywhere, including the middle. In practice both use the same start/end controls here - the terms just describe which part of the timeline you're targeting.

Not directly - this tool extracts one continuous span rather than deleting a span and joining what remains. To do that, cut the two segments you want to keep separately, then join them with FFmpeg's concat feature or any video editor.

Yes. Audio is captured along with the video and included in the output as Opus inside the WebM container. Volume, channels, and sync are all preserved.

Yes, if your browser can decode 4K smoothly. The export records at the video's native resolution, so a 4K source produces a 4K output. Older machines may drop frames during export - check the preview before relying on it.

Yes - paste a direct link to an MP4 file and it loads for cutting. Some servers block cross-site media capture (CORS), in which case the video will play and preview but export will be unavailable. Downloading the file first always works.

Anything your browser can play: MOV, M4V, WebM, MKV, AVI, OGV, and 3GP all work alongside MP4. The output is WebM regardless of what went in.

Yes - screen recordings are ordinary video files. MP4s from Windows Game Bar and OBS, and MOV files from macOS QuickTime, all load and cut normally.

iPhone videos are usually MOV files with H.264 or HEVC inside. H.264 works everywhere. HEVC needs browser support - Safari handles it natively, and recent Chrome and Edge versions do on hardware that supports it. If it plays in the preview, it will cut.

No. The output contains exactly the frames you selected and nothing else - no logo, no intro, no overlay, no branding of any kind.

The tool imposes no restrictions on output. What matters is the rights to the source footage - if you own it or have permission to edit it, the cut is yours to use however you like.

The export encodes at a high, fixed 8 Mbps to protect quality. If your source was heavily compressed, the output can be larger per second than the original. Running it through a compressor afterwards will bring the size down if that matters.

Burned-in subtitles are part of the picture, so they carry through. Separate subtitle tracks aren't captured - the browser records the rendered video, not the container's side channels. You'd need to re-attach a trimmed subtitle file afterwards.

Nothing at all. Your original file on disk is untouched, and the temporary blob URL the browser created is released the moment you navigate away. Nothing was ever stored elsewhere.