About

Built for speed.
Designed for privacy.

Clipr exists because trimming a video shouldn't require a server, an account, or trust in a third party.

Why Clipr exists

Every major "free" online video editor has the same model: upload your file to their servers, wait in a queue, receive a watermarked export, and discover that the "free" tier has a 500 MB cap. Your footage passes through infrastructure you don't control, with terms of service you probably didn't read.

Clipr takes the opposite approach. The entire tool runs inside your browser. There is no upload step because there is no server to upload to. Modern browsers expose powerful APIs — File, MediaRecorder, captureStream — that make fast, private video processing possible without any backend. We used them.

Part of the RuntimeHub ecosystem

Clipr is built and maintained by RuntimeHub, a growing suite of browser-native utilities that share one architectural principle: your files stay on your device. Squeezy (image compression), Zippy PDF (PDF processing), Harmonics (audio editing), and a dozen other tools follow the same model. No uploads, no accounts, no surveillance.

RuntimeHub tools are funded by non-intrusive advertising — not by monetizing user data or locking output behind paywalls. The ads pay for the domain and CDN; the tools stay free and uncompromised.

Technical philosophy

Clipr is built with vanilla HTML, CSS, and JavaScript — no frameworks, no build steps, no npm dependencies bundled into a 3 MB script. The entire codebase loads in under 50 KB. This is intentional: small bundles mean faster first paint, simpler auditing, and fewer attack surfaces.

The trimming engine uses the browser's native captureStream() and MediaRecorder APIs, which means it benefits from hardware acceleration on every platform without shipping any codec code of our own. The output quality is the best your browser can produce for the given format.

Limitations

We're transparent about what Clipr can and can't do. Because we use MediaRecorder rather than a native codec like FFmpeg, frame-perfect cuts at keyframe boundaries may produce a brief fade on some browsers. Complex multi-track editing, audio normalization, and subtitle burning are out of scope — Clipr is a trimmer, not a full NLE. For those tasks, a desktop editor is the right tool.

Contact & feedback

Clipr is part of the RuntimeHub ecosystem. For feature requests, bug reports, or partnership enquiries, reach us on Instagram at @run.time.0 or through the RuntimeHub website. We read everything.