A repeatable guide to reducing resolution, bitrate and file size while checking motion, text, audio sync, export time and playback compatibility.
Re-encode a video to a lower resolution or bitrate to reduce file size.
Begin with the actual destination
Before compressing, identify where the video will be used: a website, a messaging app, a learning platform, a presentation, an archive or a social feed. Each destination may have its own current limits for dimensions, duration, codec and file size. Check the destination’s official requirements instead of relying on a permanent universal preset.
The goal is not the smallest possible file. It is the smallest file that still meets your viewing requirements. A screen recording with tiny text needs different treatment from a talking-head clip or a static slide deck.
Understand the main size drivers
A video file contains encoded video, audio and container overhead. Average bitrate multiplied by duration gives a useful rough estimate. For example, 4.0 Mb/s of video plus 128 kb/s of audio for 60 seconds is approximately (4.128 × 60) ÷ 8 = 30.96 MB before overhead. Variable bitrate, metadata and audio behavior mean the exact size will differ.
Resolution controls how many pixels are represented. Reducing 1920×1080 to 1280×720 leaves about 44% of the original pixel count, but the image also loses detail. Frame rate describes how often frames are represented; reducing it can help static footage but make fast motion less smooth. Bitrate controls the data available to encode each second, with greater needs for complex motion, grain and fine texture.
Change one variable at a time
Start by choosing the smallest resolution that still preserves needed information. For screen recordings, watch text and fine interface elements carefully. Next, adjust frame rate only if the content can tolerate the change. Finally, compare bitrate or recording settings. If you change every variable at once, you will not know which adjustment caused a quality problem.
This Vaultxon tool uses browser-based recording and exports WebM. It does not expose every parameter available in a desktop encoder and cannot guarantee a target size or a specific MP4/H.264 delivery profile.
Use a representative test segment
Create a short sample that includes movement, small text, gradients, a dark scene and whatever the video makes most demanding. Compare the source and export at the same display size. Look for blocky motion, banding, unreadable text, missing details, audio drift and cut-off frames.
Record the source size, output size, duration, dimensions and playback result. If the output is larger, its recording bitrate may exceed the source’s average, or the chosen codec may be less efficient for the content. Do not assume the button must always reduce the file.
When to choose another tool
If you must meet a strict size ceiling, use an encoder that exposes a target bitrate or two-pass rate control, then verify the delivered file. If you need H.264 in MP4, several audio tracks, subtitles or chapter preservation, use a media tool with explicit stream controls. Browser capture is useful for a quick copy but not every professional workflow.
Do not rename a WebM file to .mp4. The extension does not change the container or encoding. Keep a high-quality master and make delivery copies from it rather than compressing the previous export again and again.
Troubleshooting
Blurry text: raise resolution and use a representative UI-heavy sample. Blocky motion: relax compression or keep a higher bitrate. Choppy motion: preserve frame rate for fast content. Missing or drifting audio: test a shorter supported clip and compare the output in a second player. Export stalls: close heavy tabs, use a shorter video and keep the page active.
Final review checklist
Keep the source. Test a short section first. Compare the result at the destination display size. Confirm duration, dimensions, audio and synchronization. Check the destination’s current upload limits. Use only media you own or have permission to modify. Do not replace the source until the exported copy has passed review.
Worked size estimate
Suppose a 90-second clip averages 3.2 Mb/s of video and 160 kb/s of audio. The combined rate is about 3.36 Mb/s. A rough estimate is (3.36 × 90) ÷ 8 = 37.8 MB before container overhead. This is an estimate, not a promise, because actual bit rate can vary across scenes and the output encoder may use different settings.
If the goal is a smaller upload, test a representative 15-second section first. If it looks good, record the settings and apply them to the full clip. If it looks bad, identify the visible failure: unreadable text usually points to resolution; blocky motion suggests insufficient data for complex frames; a jerky clip can indicate frame-rate reduction; and audio drift points to a timing or recording issue rather than image quality.
Frequently asked questions
Can I guarantee a 50% size reduction?
No. Compression depends on the source, duration, content complexity, codec and settings. Measure a test export.
Why did compression create a larger file?
The recorded output may use a higher average bitrate or a less efficient codec for the content.
Will 720p always look good on a phone?
Not always. Small text or fine detail can become unreadable; test at the intended display size.
Can Vaultxon produce every MP4 profile?
This browser workflow exports WebM. Use a dedicated encoder for a required container or codec profile.