Privacy
Crop a video without uploading it
VerCut decodes, crops and encodes the video inside the tab using browser APIs, so the file is never sent to a server. You can verify it in about 30 seconds by watching the Network tab of the developer tools while a clip exports.
The difference is not a promise on a privacy page: it is a network request that does not exist.
How to verify it in 30 seconds
Open the editor with developer tools
On Chrome, Edge or Safari: F12 (or ⌥⌘I on a Mac) and switch to the Network tab. Tick “Preserve log” if you want the record to survive navigation.
Load a video and crop it
You will see requests for the HTML, the CSS, the JavaScript and the three fonts. None of them is the size of your file.
Export and check the Size column
During the export no request appears with the weight of the video. The work happens in the tab: CPU and GPU, not bandwidth.
What does travel over the network
| What | When | Content |
|---|---|---|
| HTML, CSS and JavaScript | On page load | The application, a few hundred KB. |
| Fonts | On page load | Three woff2 files served from vercut.pro. |
| Session and quota | Only if you sign in | Email, plan and export counter in Firebase. |
| Project document | Only with a session and edits | Cuts, framing and speed: data, not the file. |
| The video | Never | There is no endpoint that receives it. |
What is stored on your machine
So a project can be resumed, the browser stores a copy of the file and its document in IndexedDB, and the export counter in localStorage. None of it leaves the device: it is removed when you delete the project and it disappears if you clear site data.
Why it is also faster
With no upload there is no wait proportional to file size, and with no queue there is no turn. A two-minute clip starts exporting the moment you press the button. The limit becomes your machine: a recent laptop handles it easily; an old phone decoding 4K will feel it.
When this decides the tool
- Client material under a confidentiality agreement.
- Unreleased content: launches, episodes, campaigns.
- Footage with minors or with personal data on screen.
- Slow or metered connections: no bandwidth spent uploading the file.
- Teams whose policy forbids uploading material to third-party services.
Frequently asked questions
Is my video stored anywhere?
In your browser, yes: a copy in IndexedDB so the project can be resumed without picking the file again. On a server, no. It is deleted when you delete the project or clear site data.
Does Firebase see my file?
No. Firebase Auth and Firestore receive identity, plan and the project document —cuts, framing, speed— which is a few KB of data. The video is never written to Firestore or Storage.
Can I work offline?
The first visit needs a network to load the application. After that, the file and the render are local. Offline the export counter cannot update, so it is better to export with a connection.
Is it more secure than an editor that uploads the file?
It removes a copy on someone else’s server and the transfer of the file, two real risks. It does not protect against a compromised machine or replace disk encryption. The concrete difference is that no third party receives the footage.
What about the free plan watermark?
It is drawn on the canvas itself during export, on the client. No server-side process adds anything to the file.