Compress video without uploading it
A private client clip or unpublished product video should not need an upload just to make a smaller copy. BatchCrunch processes selected media inside your browser. Start with one short clip, inspect the exported result, then apply the same settings to the rest of the batch.
Open the video workbench · Free for three files per batch; $19 once removes the batch-count limit.
A practical first run
- Open the workbench while connected so that the page and processing engine can load.
- Add a supported video under 200 MiB. The picker accepts MP4 and WebM; the codec inside the file must also be supported.
- Select the output format and inspect the available compression and resize controls. Try a smaller resolution when the destination does not need the source dimensions.
- Choose whether settings apply to this file or all files. Process the clip and keep the tab open.
- Download the result, open it in a player, and compare visual quality, audio, duration and file size with the source.
Smaller is a trade-off to inspect
A lower resolution or different encoding setting may reduce size at the cost of detail. Text, fast motion and fine patterns can reveal artifacts that are hard to see in a small preview. Check the actual exported file at the size your audience will use.
Already compressed videos may offer little room for improvement. A converted file can even become larger. BatchCrunch does not promise a particular percentage reduction or a fixed processing time; file content, codec, device and settings all matter.
What offline means here
Your media is processed locally. The site still downloads application assets and the WebAssembly encoder, and checkout, licence redemption and feedback need a network connection. Let the required assets finish loading before testing a disconnected run. A fresh browser without those assets cannot load the tool offline.
You can verify the processing behavior with a non-sensitive test clip and the browser Network panel. See the privacy details for the distinction between file processing and usage counters.
Know the limits before starting a large batch
The per-file ceiling is 200 MiB, including with a paid licence. A 1 GB recording is outside that limit. A high-resolution clip may also exceed browser memory even when its file size is below the ceiling. Large editing projects and long recordings may be better handled by an installed video editor.
If processing fails, try a short clip and another supported output format first. Save a verified result before processing the rest. Your originals are not overwritten.