Video compression comes down to a small set of details that matter: resolution cap, frame-rate target, bitrate range, codec choice, and the input limits that decide whether the tool will start. A video compressor does not make any file smaller by magic; it re-encodes the source with a constrained set of parameters and then lets you inspect the actual bytes. Four details drive output size: resolution (pixels per frame), frame rate (frames per second), bitrate (bits allocated per second), and codec efficiency (how well the encoder represents motion and texture). On top of those sit the input limits — file size, duration, and pixel area — which decide whether the tool accepts your file at all. With a browser-based, local utility like Video Compressor, these details are not hidden behind a CRF slider or a two-pass encoder; they are surfaced as three named presets with disclosed numeric targets. Understanding each detail, and which ones the tool lets you change, is the difference between a meaningful size reduction and a file that ends up the same size or even larger than the source.
The Core Details That Drive Video Compression
File size is dominated by bitrate multiplied by duration. Resolution, frame rate, and codec only matter to the extent that they change the bitrate required to keep the picture looking acceptable. A 60-second clip encoded at 4 Mbps is about 30 MB (4,000,000 bits × 60 seconds ÷ 8 bits per byte = 30,000,000 bytes); the same clip at 8 Mbps is about 60 MB. Doubling the bitrate roughly doubles the file at the same duration, all other things equal.
Resolution sets the pixel count of every frame. Higher resolution means more pixels per frame, which generally requires more bits per second to keep detail from looking blocky. Frame rate sets how many of those frames are encoded per second. Going from 30 fps to 24 fps drops the frame count by one-fifth, which usually shrinks the output by a similar share when motion is moderate. Codec efficiency is the fourth lever: VP9 typically produces smaller files than VP8 at comparable visual quality, but the browser picks the codec, not the user, and not every browser exposes both.
Bitrate is the variable you actually push to shrink the file. Lowering bitrate reduces size, but past a point it shows up as blocky artefacts, banding in skies, smearing on grain, and lost detail. The right bitrate depends on resolution, frame rate, motion, and noise, which is why presets that estimate a target bitrate from resolution and frame rate usually produce a usable result without manual tuning.
Input Limits That Decide Whether Compression Can Start
Before any of the encoding details matter, the tool has to accept the source. Video Compressor enforces a fixed set of limits that bound memory use, Canvas allocation, and real-time work. The source must be browser-decodable, no larger than 500 MiB, no longer than five minutes (300 seconds), no more than 4096 pixels on either side, and no more than 3840 × 2160 pixels of decoded area. Each limit independently gates the job; a 499 MiB file that is six minutes long is still rejected.
A valid file extension does not make the codec decodable. Files named MP4, WebM, MOV, M4V, or Ogg are accepted, but whether the browser can actually decode them depends on the codecs installed in the current browser. A codec the browser does not recognise produces an error and no download, rather than a silently truncated output. This is the detail most often missed: people rename files without re-encoding, then assume the new extension alone opens the door.
How Presets Translate Into Concrete Numbers
The three presets are transparent product choices rather than promises about a universal optimum. Each preset sets a maximum output width, a target frame rate, and a bitrate target that is then clamped into a disclosed range.
| Preset | Maximum output width | Target frame rate | Bitrate clamp |
|---|---|---|---|
| Small | 640 px | 24 fps | 180 kbps – 8 Mbps |
| Balanced | 1280 px | 30 fps | 180 kbps – 8 Mbps |
| Quality | 1920 px | 30 fps | 180 kbps – 8 Mbps |
All three presets preserve the source aspect ratio and never enlarge the source — a 480p video stays at 480p no matter which preset you pick. Output dimensions are rounded down to even pixel values so the codec has clean numbers to work with. The bitrate the recorder actually uses is chosen by a bits-per-pixel heuristic based on the output resolution and frame rate, then clamped to the 180 kbps to 8 Mbps range. That is why two runs of the same file can produce slightly different sizes even with the same preset: the heuristic and the available codec both vary between browsers.
Compress a Video Locally With Video Compressor
- Open Video Compressor in a desktop or mobile browser and confirm the source file is browser-decodable, no larger than 500 MiB, no longer than five minutes, and no more than 3840 × 2160 pixels of decoded area.
- Pick the file from your device. Files named MP4, WebM, MOV, M4V, or Ogg are accepted, but actual decoding still depends on the codecs installed in the current browser.
- Choose a preset. Small limits output width to 640 px and targets 24 fps, Balanced limits width to 1280 px and targets 30 fps, Quality limits width to 1920 px and targets 30 fps. None of the presets enlarge the source.
- Start compression. Encoding runs in real time because MediaRecorder observes the Canvas stream while the source plays, so a two-minute source takes roughly two minutes. Keep the tab open while the source plays.
- Wait for the tool to report the output dimensions, input bytes, output bytes, and the signed percentage change. The percentage is calculated only from the two actual blob sizes, so a positive value means the output is larger.
- Download the WebM, then play the full file in a media player before deleting the original. Confirm picture, sound, duration, and compatibility with your destination.
Switching the file, changing presets, cancelling, or closing the tab invalidates the active job and releases temporary object URLs, so there is no partial output to clean up if you change your mind mid-run.
What the Tool Does and Does Not Preserve
The output is always a WebM file. Browser support for generated MP4 through MediaRecorder remains inconsistent across platforms, so the recorder tries VP9 first, then VP8, then a generic WebM MIME, in that order. Two browsers can produce different output for the same input even with the same preset, because the codec and encoder implementation differ.
Audio is included only when the current browser exposes an audio track through HTMLMediaElement captureStream. If it does, the captured track is appended to the recorder stream and ends up in the downloaded WebM; if it does not, the output is silent. The source plays audibly during real-time processing when it contains audio, so use device volume rather than assuming the speaker mute switch has no effect on the captured track.
Subtitles, chapters, attachments, rotation tags, color metadata, HDR signalling, and most other container features are not preserved. The tool does not normalise volume, mix tracks, repair damaged media, or strip metadata according to any certified standard. For archival masters, professional delivery specifications, exact codec profiles, two-pass rate control, fixed keyframe intervals, subtitle preservation, or deterministic cross-platform output, the tool's own documentation points to a maintained desktop encoder such as FFmpeg with a reviewed command.
Verify the Result Before Deleting the Original
The reported percentage is computed only from the two actual blob sizes; the tool never labels a larger file as a reduction. Compression is content dependent. A low-motion animation can shrink dramatically, while noisy footage, grain, camera shake, rapidly changing detail, or an already efficient source can produce a file the same size or larger than the input. When the result does not fit the destination, try another preset or a different source.
Because nothing leaves the tab until you click download, the original file is still on your device. Keep it until you have played the downloaded WebM end to end and confirmed size, duration, picture, sound, and compatibility with the target platform or recipient. Reading the result file with a desktop player is the only way to catch codec quirks that a browser preview might paper over; for a closer look at how to read those numbers, see how to check the result after video compression. For broader workflow habits, Video Compressor tips and common mistakes to skip covers the failure modes that show up most often.
If a destination requires features the tool cannot preserve — a specific MP4 profile, embedded subtitles, deterministic output across browsers — treat the output as a draft and finish the job with a desktop encoder.