Don't trust us. Verify.

Every "we care about your privacy" page on the internet is a promise. This one is a procedure — 30 seconds, no expertise needed.

1. 1 · Open the Network tab

   Press F12 (or ⌥⌘I on a Mac), switch to Network, and leave it open.

2. 2 · Import a real clip and edit

   Open the editor, drop a file — the bigger the better — trim it, split it, add a title and some music.

3. 3 · Export and read the evidence

   Run a full export while watching the panel. You'll see the page's own assets load (HTML, JS, fonts) — and then nothing while your multi-gigabyte project imports, edits and renders. No POST, no PUT, no WebSocket streaming your footage anywhere. There is no server that could receive it.

4. 4 · The airplane-mode version

   Load the editor, then turn Wi-Fi off entirely. Import, edit, export — the whole journey still works, because decoding, compositing and encoding are your device talking to itself. Clipforge is an installable PWA; offline isn't a degraded mode, it's the architecture.

How it actually works

Modern browsers ship the same hardware video decoders and encoders that native apps use (the WebCodecs API) plus GPU compositing (WebGL2). Clipforge reads your files from disk, copies them into your browser's private local storage so projects survive crashes, decodes and composites frames on your GPU, and encodes the export back to your disk. The only network traffic this site ever makes: loading the page itself, an optional anonymous page-view beacon you can block without breaking anything, and — only if you buy Pro — a license check that sends a key and an anonymous device hash. Never file data, never frames, never audio.

Compare that with upload-based editors: CapCut, Clipchamp, Kapwing and VEED all upload your footage and render it server-side — your NDA'd client material sits on their infrastructure under a deletion promise. Structural privacy beats policy privacy: a server that never gets the file can't leak it, sell it, train on it, or be subpoenaed for it.