Choosing the Balanced preset in Video Compressor means capping the output width at 1280 pixels, targeting 30 frames per second, and letting a bounded bits-per-pixel heuristic pick a recorder bitrate that is then clamped between 180 kbps and 8 Mbps. The preset is the middle option in a three-preset local WebM re-encode — Small sets the ceiling at 640 pixels and 24 fps, while Quality raises the ceiling to 1920 pixels at 30 fps. All three preserve the source aspect ratio, never enlarge a smaller source, and round output dimensions down to even pixel values for broader codec compatibility. Balanced is not a guarantee of file-size reduction; the page reports the actual input and output bytes and the signed percentage change between them, so a result that grew is shown as a growth. If your goal is a presentable clip for chat apps, slide decks, or quick review rather than a full-resolution master, Balanced is the preset most readers reach for first.
What the Balanced Preset Actually Sets
The label "Balanced" is a transparent product choice rather than a claim about a universal optimum. Behind the label, three concrete parameters are set before the recorder starts: a maximum output width of 1280 pixels, a target frame rate of 30 fps, and a per-pixel bit budget that scales with resolution. From that budget, the page computes a requested bitrate, then clamps the result between 180 kbps and 8 Mbps so the value stays inside the practical range that browser WebM recorders can handle. Output dimensions are derived from the source: the page picks the smaller of the source width and 1280 px, divides the source height by the same factor to keep the aspect ratio, and rounds both numbers down to even integers.
Because the page draws each displayed source frame into a Canvas and records that canvas, the encoder never sees the original raw frames. Anything the source shows is what gets recorded — including on-screen artifacts, hard cuts, and motion blur. The recorder runs in real time as the source plays in the tab, and tracks stop when the source ends. The actual file is a WebM produced by the browser's MediaRecorder implementation, not by an external service, so the codec that lands in your download depends on which WebM MIME the current browser reports as supported.
Balanced Compared to Small and Quality
The three presets only differ in their width ceiling, frame rate target, and the resulting bit budget. They do not change container, codec attempt order, audio handling, or the local-only processing model.
| Preset | Max output width | Target frame rate | Bitrate behavior | Typical fit |
|---|---|---|---|---|
| Small | 640 px | 24 fps | Lower per-pixel budget; result clamped to 180 kbps–8 Mbps | Previews, thumbnails, embedded chat clips where detail loss is acceptable |
| Balanced | 1280 px | 30 fps | Mid per-pixel budget; result clamped to 180 kbps–8 Mbps | Sharing, slide decks, review links where 720p-looking motion matters |
| Quality | 1920 px | 30 fps | Higher per-pixel budget; result clamped to 180 kbps–8 Mbps | Closer to source detail when storage or bandwidth is not a constraint |
The percentages and exact byte counts shown after a run come from the two actual Blob sizes in that run, so the comparison between presets only becomes meaningful after you try them on your real source. The tool does not promise any preset is universally smaller; a low-motion animation can shrink dramatically under Balanced, while noisy, shaky, or already-efficient footage can land equal to or larger than the source.
When Balanced Is the Right Choice
Balanced fits sources where you want enough resolution to read text on screen, recognize faces at normal viewing distance, and follow fast motion without obvious smearing — without paying the storage cost of the Quality preset. Common cases include screen recordings and product walkthroughs that need to remain legible on a laptop, short clips embedded into presentation decks, and review links sent to a teammate on a constrained connection. The 30 fps target is also closer to the cadence most consumer cameras and conferencing tools record at, so Balanced usually avoids the "slideshow" feel that 24 fps can introduce for sports, gameplay, or hand-held phone footage.
Reach for Small instead when the clip is only meant to preview a longer video, when bandwidth is the main constraint, or when the source itself is already small and any further reduction has to come from lower resolution rather than smarter encoding. Reach for Quality when the destination is archival, a portfolio piece, or a delivery target with explicit resolution requirements that 1280 px cannot meet. If you are unsure which one your source actually needs, the practical move is to start with Balanced, read the output dimensions and the signed percentage change, and only switch presets if the result does not match the destination's expectations.
How to Use the Balanced Preset Step by Step
- Open the Video Compressor page in a desktop or mobile browser that can decode your source. Pick a file at or under 500 MiB, five minutes, and 3840 × 2160 pixels of decoded area; a valid file extension does not guarantee the codec is decodable in your browser, so check that the source plays in a normal tab first.
- Select Balanced from the preset list. Leave the page tab open and do not navigate away during compression.
- Press start. The source plays in real time at the preset's frame cadence, and the page records the canvas stream. A two-minute source therefore takes approximately two minutes; this is not an instant conversion.
- When the source ends, the page reports the output dimensions, the input and output byte counts, and the signed percentage change between them. Treat those numbers as the result for that specific preset and source.
- Download the WebM, play the complete file from start to finish, and confirm picture, sound, duration, and size match what you need before deleting the original.
Reading the Result After Compression
The percentage shown is calculated only from the two actual Blob sizes — there is no predicted ratio. A negative number means the WebM is smaller than the source by that amount; a positive number means it grew. The tool never relabels a larger file as a reduction. Output dimensions are derived numbers, not the source's native resolution: at 1280 px, a 1920×1080 source becomes 1280×720 (rounded down to even pixels), while a 1280×720 source stays 1280×720. A source that is already smaller than the preset's ceiling is never enlarged; Balanced simply records it at its existing size.
If the result is the wrong size for your destination, change the preset and try again rather than tweaking anything in the recording pipeline. If the result is the right size but the picture looks off — blocky, smeary, or washed out — that is a sign that Balanced's bit budget is too tight for the source content, and a few preset-specific tips usually resolve it without changing tools.
Limits That Can Override Your Preset Choice
The preset is one input among several, and the page enforces hard limits before the recorder starts. Inputs above 500 MiB, longer than five minutes, larger than 4096 pixels on either side, or with more than 3840 × 2160 pixels of decoded area are rejected with an error and produce no download. The page validates extension or MIME, positive byte size, decoded duration above zero, and the per-side and area limits; if any check fails, no file is offered. The codec inside the container also has to be decodable by the current browser — a .mp4 extension does not make an unsupported codec decodable, so a file that plays in a system player may still fail inside the tool.
Encoding runs at the source's playback speed because MediaRecorder observes the canvas stream while the source plays. A ten-minute source therefore takes roughly ten minutes, and closing the tab, picking a new file, switching presets, or navigating away invalidates the active job and revokes the temporary Object URLs. None of these limits depend on which preset you choose, but they bound what Balanced can be applied to in a single run.
Audio, Privacy, and Browser Differences
Audio is included in the output only when the browser exposes a capturable audio track through HTMLMediaElement captureStream. The source plays audibly during real-time processing when it contains audio, so use device volume if needed, but do not assume muting has no effect on the captured track. Subtitles, chapters, attachments, rotation tags, HDR signaling, and many container or color metadata fields are not preserved. WebM is the only output container because browser MediaRecorder support for generated MP4 remains inconsistent, and the recorder tries VP9, then VP8, then generic WebM according to what the current browser reports — so the exact bytes of two outputs run on the same source can differ between browsers.
Every decoded frame, encoded byte, and downloaded file stays inside the current tab; nothing is uploaded and no video, thumbnail, duration, filename, codec, or result is sent off the device. For archival masters, professional delivery specifications, exact codec profiles, two-pass rate control, fixed keyframe intervals, subtitle preservation, or deterministic cross-platform output, the right tool is a maintained desktop encoder such as FFmpeg with a reviewed command — the browser preset is for fast, local, single-run compression rather than for delivery-grade mastering.
Related reading: How to Choose Quality When Compressing a Video.