Cut a 3-hour video
into 100 short-form clips.
ClipFlixx is the fastest browser-only video clipper. Drop in any file up to 10 GB, trim it on a thumbnail timeline, auto-split into hundreds of vertical-ready MP4s — and download every clip without anything ever leaving your device.
No sign-up · No credit card · Works on Chrome, Edge, Safari, Firefox
10 GB
Max file size
1000
Clips per batch
3×
Parallel GPU encode
0
Bytes leave device
What is ClipFlixx
A complete video clipper that runs entirely in your browser.
Most video tools upload your file to a server, charge by the minute, and forget privacy exists. ClipFlixx is the opposite — it's a single page that uses the browser's own WebCodecs API (with FFmpeg.wasm as a universal fallback) to trim, crop, overlay, split, and re-encode video without ever touching a backend. The whole pipeline — decoder, encoder, muxer, filesystem — lives in Web Workers on your machine.
Every feature
Built for short-form workflows
Twelve focused capabilities that get from “I have a long video” to “I have a folder of platform-ready clips” in one sitting.
Frame-thumbnail timeline
Drag the red knob handles on a CapCut-style filmstrip. The discarded regions get a diagonal hatched veil so you can see exactly what gets cut.
Scrub-on-drag preview
Every drag tick hits the GPU via `fastSeek` so the preview frame follows your handle in near-real-time. Release for a frame-precise commit.
HH:MM:SS time inputs
Type exact start, duration, and end values. Bidirectional — the inputs and handles stay in lockstep.
Auto-split into clips
Pick 15 s / 30 s / 1 m / 2 m / 5 m or a custom interval. ClipFlixx slices the trimmed range into up to 1000 clips with one click.
Aspect ratios for every platform
Original · 9:16 Reels/Shorts/TikTok · 1:1 Instagram feed · 4:5 vertical · 16:9 YouTube. Drag-pan + pinch-zoom inside the frame to reframe the action.
Text overlays with variables
Add multiple draggable text layers. Use ${i} / ${n} / ${start} / ${end} tokens so each clip auto-numbers (e.g. "Part 3 of 12").
Lossless stream-copy
Trim without re-encoding when no resize/crop/overlay is set — FFmpeg's `-c copy` ships byte-perfect MP4s in seconds, not minutes.
Hardware-accelerated encoding
Modern browsers route to WebCodecs (GPU H.264) via mediabunny. A 3-worker parallel pool encodes 3 clips concurrently on the GPU.
FFmpeg.wasm fallback
Sources or browsers without WebCodecs gracefully fall back to FFmpeg.wasm with multi-threaded core where supported. Nothing fails silently.
Preview + Download per clip
The export page is a card grid. Every finished clip becomes a card with an inline player and Preview / Download buttons — grab files mid-batch.
Download all as ZIP
When the batch finishes, one click bundles every clip into a single ZIP with sanitized filenames like `your-video-clip-001.mp4`.
Custom player controls
Play / pause, skip ±10 s, mute, fullscreen, scrubber that respects the trim range, smooth 60 fps playhead via requestVideoFrameCallback.
One source, every platform
Five aspect ratios. Built-in crop & pan.
Pick a format and the preview swaps to the right frame. Drag inside the cropper to recompose; pinch/scroll to zoom. Each clip in the queue exports at the same target.
Original
Keep the source
source
9:16
Reels · Shorts · TikTok
1080×1920
1:1
Instagram feed
1080×1080
4:5
Instagram tall
1080×1350
16:9
YouTube · landscape
1920×1080
Four-step workflow
From file to folder of clips in minutes
STEP 01
Drop your video
MP4, MOV, AVI, WebM, MKV up to 10 GB. The file is read locally — nothing uploads.
STEP 02
Trim & frame
Drag the red handles on the filmstrip to pick the kept range. Choose an aspect ratio and reframe with pan + zoom if needed.
STEP 03
Split into clips
Pick a duration preset or a custom interval. The queue fills with up to 1000 clips, each within your trim.
STEP 04
Process & download
Click Process Clips → the dedicated export page opens. Preview each clip the second it finishes. Grab one or ZIP them all.
Privacy by architecture
Your video literally cannot reach our servers.
Not “we promise not to look.” Not “encrypted at rest.” The architecture itself makes it impossible — the file is held as a browser Blob and read by Web Workers on your CPU/GPU. There is no upload endpoint. Inspect the network tab: zero bytes of your file leave the tab.
- ✓No account, no email, no cookie banner
- ✓No analytics on your file or its contents
- ✓No server-side processing of any kind
- ✓Refresh = everything gone (no storage layer)
Network requests for a typical session
Three engines, one button
ClipFlixx picks the fastest path for every clip
The export pipeline auto-selects based on what you've configured — so a plain trim is instant and a complex composite still ships.
FFmpeg stream-copy
When you haven't applied any resize / crop / text overlay, ClipFlixx skips the encoder entirely. FFmpeg `-c copy` carves the trim range out of the source byte-for-byte.
Seconds per clip · byte-perfect quality
WebCodecs + GPU H.264
For resize / crop / overlays, mediabunny decodes hardware-side, draws to OffscreenCanvas, and re-encodes via the GPU's H.264 unit. A 3-worker pool runs 3 clips in parallel.
15–60 s per 1-minute 1080p clip
FFmpeg.wasm
Browsers or sources that can't hit the WebCodecs path drop to FFmpeg.wasm with multi-threaded libx264. Slower but universal — nothing fails.
2–9 min per 1-minute 1080p clip
FAQ
Common questions
Is my video actually private?
Yes. ClipFlixx is a single-page web app — there is no backend, no upload API, no analytics on your file. The video stays in your browser's memory as a Blob and is read by WebCodecs / FFmpeg.wasm in a Web Worker. Close the tab and it's gone.
How fast is the export?
Depends on the engine that gets picked. Lossless stream-copy (no transform) is essentially instant — limited by disk write. Hardware H.264 via WebCodecs encodes 3 clips at a time on the GPU; a 1-minute 1080p clip typically takes 15–60 seconds. FFmpeg.wasm software encoding is the slow fallback when WebCodecs isn't available.
What's the file-size limit?
10 GB on desktop. The full file isn't loaded into the WASM heap — it's mounted via WORKERFS or read range-by-range via Blob.slice. Mobile browsers cap WebAssembly heap aggressively, so files over 500 MB on phones may run out of memory.
Why does my MKV go through software encoding?
The browser has to support hardware H.264 at the output's profile/level. ClipFlixx probes the encoder at runtime and uses GPU H.264 whenever the browser accepts it (Chrome/Edge on most platforms, Safari since 16.4). When the probe fails, FFmpeg.wasm runs instead — slower, but it never fails on a supported container.
Does it support audio?
Yes. The WebCodecs path passes the source's encoded audio packets through to the output container without re-encoding (lossless audio, no quality loss). FFmpeg.wasm re-encodes audio to AAC 128 kbps for compatibility.
Can I run it offline?
Once the page is loaded, the editor itself runs offline — WebCodecs and FFmpeg.wasm are in-browser. The page load and the FFmpeg core download (~25 MB, cached after first load) are the only network hits.
No upload · No account · No watermark
Cut your first clip in 30 seconds.
Open the editor, drop a file, drag the handles. That's the whole onboarding.
Open the editor