Convert
Compression is not one action — it is three separate trades: bitrate, resolution and frame rate. Each one costs you a different kind of detail, and the loss compounds every time the file is encoded again. This page covers what each lever actually removes, so you can decide which one to move; for the practical task of hitting a target file size, see the video compressor page.
STEP 01
Find the size or resolution limit the platform enforces before you change any setting.
STEP 02
Adjust the export options and produce one version aimed at the number you found.
STEP 03
Open the compressed file at full size, check faces, small text and motion, and keep the version that still holds up.
A clip that is fine on a laptop can still fail a Discord upload, a web form, or an email gateway. The useful question is not how small a file can get, but what the destination accepts and how much detail you can keep inside that ceiling. Start there, then pick settings.
Bitrate is the main lever on file size. Resolution decides how much detail survives when bitrate drops. Frame rate matters for screen recordings and fast motion, less for a talking-head clip. Change one at a time and re-check the same shot, otherwise you cannot tell which setting caused the damage.
Compressing in the browser avoids a round trip to a desktop tool, and the source stays in the project, so a rejected export is a settings change rather than a lost edit. Supported inputs, output options and limits follow the current workspace.
Common questions about this task, its limits and how to judge the result.
It depends on the starting bitrate. A file already compressed at a similar setting has little left to remove; a high-bitrate screen recording or camera original usually shrinks a lot.
Not without any trade. Reduce bitrate first, since it costs the least visible quality, and compare the same detailed shot before and after.
Lower the bitrate first. Drop resolution only when the target is still out of reach, because small text and fine detail are what resolution loss destroys first.
Yes, if you work backwards from the limit that service enforces. Confirm the reported file size before uploading so you do not repeat the attempt.
Trial access and output limits follow the current workspace. Compare the same detailed shot after compression before publishing.
