Multi-range from one source
Pull several windows out of a single video and export as one file.
Flowcut runs FFmpeg in your browser tab — frame-accurate in/out points, stream-copy export with zero re-encode, thumbnail scrubbing — and saves the trimmed clip locally. The cut lands at the exact frame you set, not the nearest keyframe.
I marks in, O marks out, or drag the handles on the timeline. A thumbnail preview floats as you move the playhead. The cut lands at the exact frame you pick — not at the nearest keyframe, the way most online tools handle it. Cmd+K splits the clip mid-stream so you can lift a section out of the middle.
Whenever possible, no re-encode. Trim a 1GB clip in seconds. Original quality preserved. Auto-falls-back to re-encode only when speed or color is also applied.
Pull several windows out of a single video and export as one file.
The clip never leaves your tab. The trimmed file lands on your disk.
The pattern is the same: upload, queue, watermark, paywall. Flowcut runs the same FFmpeg encoder those tools use under the hood — but compiled to WebAssembly and running in your browser tab. No queue. No upload. No watermark. The trim is frame-accurate and the export is stream-copy when there's no re-encode reason, which means a one-gigabyte clip can finish in seconds.
Yes. Use I for in, O for out, or drag the handles. The cut lands at the exact frame, not the nearest keyframe.
Whenever possible, no — stream-copy means no quality loss and a one-gigabyte clip finishes in seconds. Speed changes or color grading auto-switch to re-encode.
No server cap. The only constraint is your device's RAM. Hour-long lectures and 4K wedding videos trim locally without trouble.
Yes. Cmd+K splits at the playhead. Delete what you don't want, keep what you do. Multiple in/out ranges can stack into a single export.
Yes — Safari on iOS supports SharedArrayBuffer with the COOP/COEP headers Morph sets. The trim runs locally on your phone.
No. Every frame stays in your browser tab. There is no server in the export path.