Compressing a video to 8MB means producing a WebM file that weighs roughly sixty-four megabits, with a per-second video bitrate set by dividing that total by the clip's length in seconds. A 30-second clip needs about 2.1 Mbps of average video bitrate to land at 8MB, while a two-minute clip needs only about 533 kbps, and a five-minute clip bottoms out near 213 kbps. The Video Compressor on Lizely re-encodes a browser-decodable video into a WebM file in your own tab with three transparent presets, Small, Balanced, and Quality, and then reports the actual input bytes, output bytes, and signed percentage change so you can see whether the new file truly hit the size you needed. Nothing leaves your device, the encoding runs in real time, and the final WebM is the only file you download. Because the tool never promises a universal optimum and instead exposes the resolution and frame rate behind each preset, you can reason about which one is most likely to land near 8MB for a given source before you start.
How 8MB Translates to Resolution, Duration, and Bitrate
Eight megabytes sounds small until you convert it to the units a video encoder actually uses. A megabyte is roughly eight megabits, so 8 MB is about 64 megabits in total. The total bit budget has to cover every second of the clip, which is why the same 64 megabits feel generous on a 30-second clip and tight on a five-minute one. Once a target size and a duration are fixed, the only knob left is the average video bitrate, and bitrate in turn trades off against resolution, frame rate, and the amount of motion on screen. Knowing the math up front helps you pick the right starting preset and judge whether a given result is reasonable.
Working through the math once, in decimal units that match the bitrate scale used in streaming: 8 MB × 8 bits/byte = 64 megabits total. A 120-second source aimed at 8 MB therefore needs 64 Mbit ÷ 120 s = 0.533 megabits per second, or about 533 kbps of average video bitrate. That sits well above the 180 kbps floor of the tool's clamp and leaves room for some audio. A five-minute source aimed at the same 8 MB has only about 213 kbps to work with, which is the regime where the encoder is most likely to fall short of the target and where the Small preset's tighter resolution matters most.
How Video Compressor Targets a Specific Output Size
Video Compressor is a browser-based video compressor that re-encodes a single file into WebM in the current tab and reports the actual input and output bytes when it finishes. There is no upload step, no account, and no server-side pass: the source is decoded, drawn frame by frame into a Canvas at the preset's cadence, and recorded with whatever WebM codec the browser currently exposes. The tool tries VP9 first, then VP8, then generic WebM, according to the MDN HTMLCanvasElement.captureStream reference and the MediaRecorder support the page can detect.
The tool ships with three transparent presets rather than a single hidden profile, so the trade-off you are making is visible before you click start. A bounded bits-per-pixel heuristic picks the requested video bitrate based on the preset's resolution and frame rate, and the result is clamped to a range of 180 kbps through 8 Mbps. Each preset preserves the source aspect ratio, never enlarges the source, and rounds output dimensions down to even pixel values for broader codec compatibility.
| Preset | Maximum output width | Target frame rate | Where it fits in the 8 MB trade-off |
|---|---|---|---|
| Small | 640 px | 24 fps | Closest match for tight 8 MB targets and short clips |
| Balanced | 1280 px | 30 fps | General-purpose share when the 8 MB cap is generous on duration |
| Quality | 1920 px | 30 fps | Higher fidelity, larger files, less suited to 8 MB unless the clip is very short |
Compress a Video to 8MB in Your Browser
The 8 MB target lines up most naturally with the Small preset, because that preset's lower width, lower frame rate, and tighter bits-per-pixel target all push the encoder toward smaller files. The complete procedure is the same regardless of which preset you choose, and it runs entirely in your current tab.
- Pick a browser-decodable source. The file must be 500 MiB or less, five minutes or less, at most 4096 pixels on either side, and at most 3840 × 2160 in decoded area. The extension can be MP4, WebM, MOV, M4V, or Ogg, but the codec has to be one your current browser can actually decode, so a valid extension is not enough on its own.
- Open Video Compressor and load the file. The page will start a local decode and surface the three preset choices: Small, Balanced, or Quality. For an 8 MB target, choose Small to keep width at 640 pixels and the target cadence at 24 fps.
- Start compression and keep the tab open. Encoding runs in real time, so a two-minute source takes about two minutes to finish, and a five-minute source takes about five minutes. The source keeps playing audibly while the encoder records the Canvas stream; if you do not want to listen, lower your device volume but do not assume that muting has no effect on a captured track.
- Wait for the actual byte report. When the source ends, the tool reports the output dimensions, the input bytes, the output bytes, and the signed percentage change. The number is computed only from the two Blob sizes, so a larger file is never labeled as a reduction.
- Download the WebM, play the full file, and only then delete the original. Confirm size, duration, picture, and sound match what the destination expects before you discard the source.
Why the Same Source Can Produce Different 8MB Results
The same source can produce noticeably different output sizes between runs and between browsers, because WebM compression depends on motion, noise, source codec, and the encoder the browser happens to ship. A low-motion animation often shrinks dramatically, while noisy footage, grain, camera shake, rapidly changing detail, or a source that was already encoded efficiently can come out similar in size or even larger. The percentage change shown at the end is honest in that respect: it is the signed change between the two actual Blobs, with no rounding up in your favor.
If the result does not fit your 8 MB target, the most productive moves are to switch presets, trim the clip shorter, or pick a less noisy source. A two-minute clip is much easier to land at 8 MB than a five-minute one, because the per-second bit budget rises as the duration drops. WebM is the only output container because MediaRecorder support for browser-generated MP4 remains inconsistent across browsers, and the recorder tries VP9, then VP8, then generic WebM according to what the current browser reports, so two machines running the same preset on the same source can produce files that differ slightly in size.
What the 8MB WebM Keeps and What It Drops
The 8 MB WebM is not a complete copy of the source. Audio is included only when the browser exposes a capturable audio track through HTMLMediaElement captureStream, which most browsers do but not all; you should verify both picture and sound on the downloaded file rather than assuming the audio came along. Subtitles, chapters, attachments, rotation tags, color metadata, and HDR signaling are not preserved, and the tool does not normalize volume, mix tracks, remove metadata to a certified standard, repair corrupt media, or transcribe captions.
Output dimensions are whatever the preset allows once aspect ratio and the even-pixel rule are applied, and the source is never enlarged: a 480-pixel-wide source stays at 480, even on the Quality preset. Nothing is silently truncated either, so an invalid file, unsupported decoder, over-limit duration, over-limit frame, missing Canvas stream, or unavailable WebM recorder produces an error and no download. The result is a clean, finite-duration WebM that plays in any modern browser, which is usually what an 8 MB target needs in the first place.
When 8MB Needs a Different Tool
For an everyday 8 MB share file destined for email, a chat cap, or a form upload, the local WebM is usually enough. A walkthrough tailored to email attachment caps is in Send Large Videos by Email After Compressing Them Locally, and the same shape of workflow covers most messaging apps. For a different kind of deliverable, the trade-offs change. Archival masters, professional delivery specifications, exact codec profiles, two-pass rate control, fixed keyframe intervals, deterministic cross-platform output, subtitle preservation, or color-managed workflows are all things Video Compressor explicitly does not promise, and trying to force them through a real-time browser encoder will fight you. In those cases, a maintained desktop encoder such as FFmpeg with a reviewed command gives you the knobs you actually need. For the 8 MB target in front of you, though, the local re-encode is the right shape of tool: fast to try, easy to verify, and confined to the tab you already have open.