Video editing SDK
Cutforge is a non-linear video editor for the browser: WebGPU compositing, WebCodecs decode/encode, a Rust core. Drop it into your product and the whole pipeline runs client-side. No render servers, no per-minute bills, nothing uploaded.
Why client-side
Exports run on the user's GPU. You ship a license key, not a render farm — your marginal cost per video is zero.
Footage never leaves the browser. Nothing to upload, nothing to store, nothing to leak. A real selling point for sensitive content.
Hardware decode/encode and a WebGPU compositor. A minute of timeline exports in seconds — on the device that's already there.
The math
Cloud editing APIs bill per minute of output. Move that work to the browser and it goes to zero. Drag the slider to your volume.
Cutforge is a one-time license. After that, the render bill is gone — at any volume.
Pricing
1 developer · commercial use · 12 months of updates
Up to 5 developers · ship it in a paid product
Whole team · extended license · SLA
Source-available, commercial license. No open-source redistribution.
FAQ
Chromium-based browsers (Chrome, Edge, Arc, Brave) 105+, plus recent Firefox and Safari. It needs WebGPU/WebGL2 and WebCodecs — the modern web-media stack.
You install the package and drop in a license key. Without a key it runs as a watermarked demo (exports capped at 60s). A valid key unlocks production use — you sell the key, you don’t rent a render farm.
No. Cutforge is 100% client-side — decode, compositing and export all run on the user’s machine. You serve static files; there are no render servers and no per-minute fees.
Whatever the browser decodes natively — H.264, VP8/VP9, AV1, plus the usual audio. Export is mp4 or webm via WebCodecs.