AI Toolbox Video Splitter is a free browser-based tool for cutting videos into clips. It runs locally in the browser with FFmpeg/WebAssembly, so users can split videos without uploading files to a server. It is designed for quick trimming, extracting clips, and creating smaller shareable video segments with no signup and no watermark.
Features
Private browser-local video processing
No upload required for supported files
Split by time interval or custom cut points
Fast preview and simple clip export
Free to use with no account required
No watermark on exported clips
Use Cases
Cut long videos into short clips for social media
Extract highlights from screen recordings, webinars, or tutorials
Trim private videos without sending files to a cloud service
Create smaller clips for sharing, archiving, or editing workflows
Comments
3I build & lead the engineering behind AI agents · Co-Founder & VP R&D @ Dial
The privacy-first approach here is gold - doing video processing locally in the browser instead of uploading to a server removes so much friction and security concern. No signup required makes it even better for creators who just need a quick trim. FFmpeg + WebAssembly is a smart technical choice for this.
i write a16z speedrun scout checks within 24hours | Co-Founder & CTO at Dial AI
Browser-local processing removes huge friction. Cloud video uploads = waiting, privacy anxiety, account friction. This runs everything client-side with no servers seeing your files. The ability to split by time or equal parts covers 90% of what people actually need. Works offline too which is a nice bonus. No watermarks on exported clips is the detail that makes this viable for content creators.
The local-first choice is the right one for exactly this kind of tool. I build a reader that parses PDFs and EPUBs in the browser with vendored libraries, and "your files never leave the device" turns out to be the feature people trust most, because they can verify it themselves in the network tab. Curious about the FFmpeg side: long videos can run to gigabytes, so does the whole file have to fit in WASM memory, or do you stream it through in chunks? And did you take on the cross-origin isolation headers the multithreaded build needs, or stay single-threaded? No watermark and no signup is the honest version of free, nice to see.