Browser-based media tools can process video on the device using web platform APIs. That does not automatically mean every tool is private or offline: inspect its behavior and privacy statement. VideoCompact uses local file access and browser recording without sending the selected file to a server.
Local processing means device work
The browser decodes the chosen video, renders frames and records a new stream. This uses memory, CPU/GPU and battery on the device. Large or long source files may be slow or fail.
A file picker is scoped access
When you select a file, the browser gives the page access to that chosen file for processing. The page should explain whether it uploads data. VideoCompact processes the selected file locally and does not upload it.
Browser support can differ
MediaRecorder and canvas capture capabilities vary. A browser may report a MIME type as supported while actual encoding still fails due to device resources.
A practical checklist
- Read the tool’s privacy explanation.
- Choose a non-sensitive sample if you are evaluating a new tool.
- Check browser support and keep the tab open during processing.
- Stop if the device overheats, slows down or runs out of memory.
Common mistakes to avoid
- Assuming every “online compressor” works locally.
- Closing the tab before saving the output.
- Selecting a sensitive recording without knowing where it will be processed.
Questions people ask
Does VideoCompact upload my video?
No. Compression runs in your browser and the selected video is not uploaded to VideoCompact.
Can a local browser tool process every video?
No. Supported input codecs and resource limits vary by browser and device.