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 signup · No watermarks · Hardware accelerated · Works on Chrome, Edge, Safari, Firefox
10 GB
Max file size
No size cap on locally read files
1000
Clips per batch
Slice long videos infinitely
3×
Parallel GPU encode
Multi-threaded hardware speed
0 B
Bytes leave device
100% private in-browser logic
Architecture First
A complete video clipper that runs entirely in your browser.
Most video tools upload your file to a server, charge by the minute, and ignore privacy completely. ClipFlixx is the opposite — it's a single-page app 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, and filesystem — lives in Web Workers on your machine.
Product Capabilities
Built for short-form workflows
Twelve focused capabilities designed to get you from a long raw video to a folder of platform-ready short clips in minutes.
Frame-thumbnail timeline
Drag the red knob handles on a professional filmstrip timeline. The discarded outer regions get a dynamic 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 sync — the input values and timeline handles stay in perfect lockstep.
Auto-split into clips
Pick 15s / 30s / 1m / 2m / 5m presets or configure a custom interval. Slices the trimmed range into up to 1000 clips with one single click.
Aspect ratios for every platform
Original · 9:16 Reels/Shorts/TikTok · 1:1 Instagram feed · 4:5 vertical feed · 16:9 YouTube. Drag-pan + pinch-zoom 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") automatically.
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 ±10s, mute, fullscreen, timeline scrubber that respects trim range, smooth 60 fps playhead via requestVideoFrameCallback.
Platform Formats
Five aspect ratios. Built-in crop & pan.
Pick a format and the preview viewport fits instantly. Drag inside the cropper frame to recompose and reframe action; pinch or use the zoom slider for exact crops.
Original
Keep the source aspect
source
9:16
Reels · Shorts · TikTok
1080×1920
1:1
Instagram feed
1080×1080
4:5
Instagram tall feed
1080×1350
16:9
YouTube · landscape
1920×1080
Simple Workflow
From raw file to batch exports in seconds
Drop your video
MP4, MOV, AVI, WebM, MKV up to 10 GB. The file is read locally — nothing uploads.
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.
Split into clips
Pick a duration preset or a custom interval. The queue fills with up to 1000 clips, each within your trim.
Process & download
Click Process Clips → export page opens. Preview each clip the second it finishes. Grab one or ZIP them all.
Privacy by architecture
Your video files literally cannot reach our servers.
Not “we promise not to look.” Not “encrypted at rest.” The core client-side architecture itself makes it physically impossible — the video file is held locally as a browser Blob and read dynamically by CPU/GPU Web Workers. There are zero upload APIs. Inspect the browser network traffic tab: zero bytes of your video ever leave the page.
- ✓No account, no email, no cookie consent banners
- ✓No trackers or telemetry analyzing your files
- ✓No server-side queuing or encoding latency
- ✓Reloading the page instantly purges all loaded files
// Loading core page and scripts
Dynamic Pipelines
ClipFlixx picks the fastest path for every clip
The smart export engine probes browser features and clips settings automatically, selecting the optimal processing path so plain trims copy instantly and overlays complete without crashes.
FFmpeg Copy Engine
If you only trim files without reframing, scaling aspect ratios, or adding overlays, ClipFlixx bypasses re-encoding. FFmpeg -c copy carves out the selection byte-for-byte in near real-time.
WebCodecs GPU H.264
For vertical crops and texts overlays, mediabunny decodes hardware side, draws canvas clips, and encodes H.264. A 3-worker parallel thread pool handles 3 exports concurrently.
FFmpeg.wasm (Software)
For legacy source codecs or configurations where WebCodecs fails hardware probe checks, ClipFlixx drops back to custom multi-threaded WebAssembly FFmpeg. Slower, but fully functional.
Troubleshooting & Mechanics
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 everything is permanently cleared.
How fast is the export?
Depends on the engine that gets picked. Lossless stream-copy (no transform) is essentially instant — limited by disk write speeds. 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 universal compatibility.
Can I run it offline?
Once the page is loaded, the editor itself runs completely 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.
Zero Signup · Zero Subscriptions · Zero Watermarks
Cut your first clip in 30 seconds.
Launch the canvas editor directly, drop in your video file, drag selection handles, and process. That is the entire, frictionless workflow.