Skip to content
Klipzo Open editor

How Klipzo works

Klipzo runs entirely in your browser. When you open a photo or video, the file is read from your device into your browser’s memory and edited there. It is never uploaded to a server, never sent to us, and never shared with a third party. There is no account, and everything is cleared when your session ends. This isn’t a promise we ask you to take on faith — it’s how the app is built, and you can verify it.

The short version

  • Nothing is uploaded. Your media stays on your device from open to export.
  • No account, ever. No sign-up, no email, no login, no user database.
  • Session-only. Your work lives for the current session and is clearable at any time.
  • Completely free. No paywalls, no feature gates, no watermarks on exports.

Why a browser can do this now

For years, “online” editors worked by uploading your file to a server, processing it there, and sending it back. That’s slow, and it means a company holds a copy of your media. Klipzo takes a different path made possible by modern browser technology:

  • Canvas & WebGL render and adjust images on your device’s GPU — the brightness, contrast, filters, crop, and text all happen locally.
  • WebCodecs gives the browser hardware-accelerated video decoding and encoding, so trimming and converting video happens on your machine.
  • WebAssembly provides a fast, universal fallback for formats and operations the native APIs don’t cover — still fully on-device.
  • OPFS (Origin Private File System) is a private, on-device scratch space so even large files can be handled smoothly and survive an accidental refresh — without ever leaving your computer.

What happens to your files

When you import a file, Klipzo reads it locally and keeps your working project in memory (and in on-device OPFS scratch for large media). When you export, the result is encoded on your device and offered to you as a normal download. At no point does your media travel over the network. When you click Clear session — or simply close the tab — the scratch storage is wiped.

Verify it yourself

You don’t have to trust us. Open your browser’s developer tools (right-click → Inspect → Network), then import, edit, and export a file. You’ll see Klipzo load its own code, but no upload of your photo or video. That transparency is the whole point.

What we do collect

To keep the lights on, Klipzo shows ads on its guide and landing pages and measures anonymous usage (for example, that an export happened) so we know which tools people use. We never send your file names, file contents, thumbnails, or anything derived from your media to analytics or anywhere else. Full detail is in our Privacy Policy.

Open the editor →

Frequently asked questions

How can Klipzo edit my video without uploading it?

Modern browsers can decode, process, and encode media directly on your device using WebCodecs, WebGL, and WebAssembly. Klipzo uses those APIs, so your file is opened from your disk into your browser’s memory and never sent over the network.

How do I know nothing is being uploaded?

You can verify it yourself: open your browser’s developer tools, go to the Network tab, and edit and export a file. You’ll see no upload of your media. The app is static — there is no server endpoint that receives files.

Where are my files stored while I work?

In your browser’s memory, and for large files in the Origin Private File System (OPFS) — a private, on-device scratch area. It never syncs anywhere. You can wipe it any time with the ‘Clear session’ button, and Klipzo also clears it when you close the tab.

Do you keep any copy of my photos or videos?

No. There is no account and no server storage of your media. We literally cannot see your files — they never leave your device.