FREEFILEKIT FILE GUIDE
How to compress a video without uploading it
Video compression works best when you change the setting that is responsible for the file size. A long recording, a large frame size and a high encoding quality can each make a file bigger. FreeFileKit processes the selected video on your device, so the video itself is not sent to a conversion server.
Start with resolution, then adjust quality
- Open Video Compressor and choose your local video.
- Choose a maximum video edge. The 720 px default is a useful starting point for a smaller viewing copy; choose 1,280 or 1,920 px when readable screen text or fine detail matters more. The tool preserves proportions and does not enlarge a smaller source.
- Choose the compression level. “Smaller file” prioritizes size, “Balanced” retains more detail, and “Higher quality” usually creates a larger result.
- Start processing. Play the result and compare its displayed size with the original before downloading.
Remove time you do not need
Shortening the recording can save more space than lowering quality. Use Trim Video to enter a start and end time in seconds. The selected section is re-encoded as MP4; this is not a lossless cut. If the result needs further compression, download it and open that copy in the compressor.
Why a compressed video can be larger
A file that is already efficiently compressed may grow when re-encoded. Converting a newer codec to a more broadly compatible one can also trade size for compatibility. The size comparison in the result is more useful than assuming that every conversion must shrink the file.
Large files and device limits
The input limit is 2 GB (2,000,000,000 bytes), selected output duration is up to 30 minutes, and output size is capped at 512 MiB. These are acceptance limits, not a guarantee that every device can finish every file. Use a desktop browser, close memory-heavy tabs, keep the conversion tab open and keep the original. For a failed large job, shorten the section or reduce resolution.
FreeFileKit uses FFmpeg.wasm. Its official FAQ explains the browser engine's performance and input-size constraints.