How it works
Video processing happens inside the browser.
Choose a file, set the output, and download the result. The selected file is not sent to a conversion server.
The local processing flow
Choose a file
The browser receives your selected video from your device.
Prepare the task
The tool prepares the task only after you choose to start.
Process locally
The selected file is written into browser memory and transformed there.
Download result
The output becomes a local browser download link.
Why this is different from many online converters
Many online converters upload your video to a server, process it remotely, then ask you to download the result. That can be convenient for huge files, but it creates a trust problem for private videos.
VideoToolDeck starts with the opposite tradeoff: small and medium files can be processed locally, with no account and no server-side file storage path.
When local processing is the wrong tool
Very large files
Multi-GB videos can exceed browser memory. A desktop app or paid cloud workflow may be better.
Long editing projects
This version is for quick utilities, not a full timeline editor with project storage.
Batch jobs
Batch compression is intentionally deferred until the single-file flow is reliable.
Product manager notes
The user flow is intentionally short: land on the exact job, read the privacy promise, choose a file, process, download. Any feature that makes this flow slower should be treated as future scope.