Cut video without uploading it anywhere

Really. Your browser reads the file from disk with the File API and holds it in memory. No network request carries the video data. You can confirm it by opening DevTools, switching to the Network tab, and cutting a file - nothing outgoing will contain your footage.

The simplest test: load the page, then turn off your wifi. Drop in a local file and cut it. Everything works. That's only possible if no server is involved at any point in the process.

The page itself is downloaded from a web server when you first visit, and it loads fonts from Google Fonts. That's HTML, CSS, and typefaces - not your video. Save the page to your desktop and open it locally, and even those requests stop.

In your browser's memory, referenced by a temporary blob URL. When you close the tab, that reference is released and the memory is freed. Nothing is written to disk except the cut you explicitly download.

None imposed by us. Because the file is read from disk rather than uploaded, multi-gigabyte recordings open normally. The practical ceiling is whatever your browser can decode and your machine can hold.

For local files, yes - once the page has loaded, no connection is needed for loading, cutting, previewing, or exporting. Only URL loading and the sample videos need the network, since the footage lives elsewhere.

No. There's no sign-up, no email, no login. There's also nowhere for an account to be stored - no backend means no user database.

No. It's opened read-only. The cut is written as a completely separate new file in your downloads folder, so your source stays byte-for-byte identical.

The browser records your selection in real time while it plays - that's how MediaRecorder works. A 40-second cut takes about 40 seconds. It's the direct trade-off for not shipping your file to a server that could encode it faster.

WebM with full audio at 8 Mbps. Browsers can only encode WebM natively; producing MP4 would require a server or a heavy conversion library. Converting afterwards is one step: ffmpeg -i cut.webm -c:a aac cut.mp4.

That's precisely the use case this suits - the footage never leaves your machine, so it can't be exposed by a breach of a service you don't control. That said, check your own organisation's policies; they may have requirements about approved tooling regardless of architecture.

Architecturally it avoids the main risk - no third party ever receives the file. But compliance regimes often require documented tooling and audit trails, which a free web page can't provide. Treat this as a reason to talk to whoever owns that policy, not as a compliance answer.

No. When you paste a URL, your browser fetches the video directly from that source. The request goes from you to them; we're not in the middle. Nothing is sent to us at any point.

There's no telemetry on your footage - no filenames, durations, or content data is transmitted. There's no server to receive it. The video simply never enters our reach.

Usually yes, since there's nothing to install - it runs in the browser you already have. Some corporate networks block external sites entirely, in which case saving the HTML file locally lets you run it without any network access at all.

Anything your browser can play: MP4, MOV, WebM, MKV, AVI, M4V, OGV, and 3GP among others. If it plays in the preview, it will cut. The output is always WebM regardless of input.

Slightly, because the segment is re-encoded during capture. At 8 Mbps it's very hard to see on typical footage. For a mathematically lossless cut you'd need FFmpeg's stream-copy mode on your desktop.

Yes. After downloading one cut, move the handles to a new span and cut again. The source stays loaded, so you're not re-reading the file each time, and each output filename carries its own timestamps.

Yes - the timeline handles are touch-friendly and the layout adapts. Real-time export works on modern mobile browsers, though the device needs to stay awake for the whole export, so long cuts are more comfortable on a desktop.

You can type timecodes to the millisecond, and arrow keys step one frame at a time. The actual cut lands on the nearest frame boundary, typically within 33–42 ms depending on frame rate.

Because they're genuinely better at some things: faster-than-real-time export, MP4 and GIF output, AI auto-clipping, and heavy effects. If you need those and the footage isn't sensitive, uploading is a perfectly reasonable trade.

No. The exported file contains exactly the frames you selected - no logo, no intro, no overlay, nothing added.

Nothing needs to happen. The blob URL is released, the memory is freed, and your original file on disk is untouched. There's no server-side copy to expire, because none was ever created.

Yes - save the page as an HTML file and open it whenever you like. It's fully self-contained apart from the web fonts, which simply fall back to system fonts when offline.

No. There's no data collection to monetise and no ads. It's free because the cost of running it is genuinely near zero - no bandwidth, no storage, no compute. Your browser pays for the work in CPU cycles you already own.