Loading video tools…
Loading video tools…
Loading video tools…
Reduce video file size by adjusting quality and resolution settings.
Large video files are slow to upload, get rejected by email attachment limits, and eat through phone storage fast. This tool shrinks video files by reducing bitrate and resolution, right inside your browser — no server upload, no waiting for a processing queue. Pick a resolution target, adjust the bitrate, and preview the size savings before you download. Processing happens locally using the Canvas and MediaRecorder APIs, so your footage stays on your device throughout. It's built for anyone who needs to shrink a clip for email, messaging apps, or a strict upload limit without installing a desktop video editor.
Your video never leaves your browser. All processing runs locally using Canvas and MediaRecorder.
Drop a video to compress
or click to browse — max 500 MB · MP4, WebM, MOV, AVI
Your video files never leave your device
All processing runs directly in your browser using built-in Web APIs — the Canvas API, Web Audio API, and WebAssembly. Nothing is uploaded to any server. There is no account, no email, and no data retention. You can verify this yourself: open your browser's DevTools Network tab and watch zero outbound file requests while the tool processes your video files.
GDPR-friendly · Works offline after page load · No file size limits beyond your device memory
Upload your video
Drag and drop or click to select your video file.
Adjust quality settings
Pick a bitrate or resolution target.
Click Compress Video
The compressed clip is rendered instantly in your browser.
Download the result
Save your smaller video file.
You need to compress a video when its current file size is too large for where you want to share, store, or upload it. Here are the most common scenarios:
Choosing the right bitrate and resolution depends on your use case. Higher values mean better quality but larger files. Here's what to expect for a 10-minute video:
| Use Case | Resolution | Recommended Bitrate | 10min File Size | Visual Quality |
|---|---|---|---|---|
| High Quality (YouTube, archiving) | 1080p (1920×1080) | 5-8 Mbps | 375-600 MB | Excellent — sharp detail, minimal artifacts |
| Standard Web Streaming | 1080p (1920×1080) | 2-3 Mbps | 150-225 MB | Good — acceptable for most viewing |
| Social Media (Instagram, Facebook) | 720p (1280×720) | 2-2.5 Mbps | 150-188 MB | Good — platforms re-compress anyway |
| Email / Messaging Apps | 480p (854×480) | 1-1.5 Mbps | 75-113 MB | Acceptable — fine for small screens |
| Tight Restrictions (10-25 MB email caps) | 360p (640×360) | 0.5-0.8 Mbps | 38-60 MB | Low — noticeable pixelation but watchable |
| Ultra Low (data-constrained) | 240p (426×240) | 0.3 Mbps | 23 MB | Very low — only for extreme constraints |
720p or 480p is plenty for phone screens. Going higher just wastes bandwidth since phone displays can't show the extra detail anyway.
1080p at 3-5 Mbps is the sweet spot for larger screens. 4K requires 10-20 Mbps and produces massive files (1 GB+ per 10 minutes).
480p at 1 Mbps gives you sub-100 MB files for 10 minutes of footage — fast to upload even on slow connections and fits most email limits.
Video codecs are the algorithms that compress and decompress video data. Different codecs offer different trade-offs between file size, quality, encoding speed, and device compatibility. Here's what each codec offers:
| Codec | Also Known As | Compression Efficiency | Device Support | Best For |
|---|---|---|---|---|
| H.264 | AVC, MPEG-4 Part 10 | Baseline (1×) | Universal — 100% of devices since 2010 | Maximum compatibility, older devices, standard use |
| H.265 | HEVC (High Efficiency Video Coding) | 2× better than H.264 | 95%+ modern devices (iPhone 6+, Android 5+) | 4K video, mobile devices, halving file sizes |
| VP9 | Google's open-source codec | 1.5-2× better than H.264 | All modern browsers, Android, Chrome devices | YouTube, web streaming, royalty-free encoding |
| AV1 | AOMedia Video 1 (next-gen open codec) | 2-3× better than H.264 | Growing — Chrome 70+, Firefox 67+, Edge 121+ | Future-proof, extreme compression, streaming |
What compression efficiency means:
"2× better" means you can achieve the same visual quality at half the file size, or better quality at the same size. H.265 at 2 Mbps looks like H.264 at 4 Mbps.
Which codec does this tool use?
This browser-based tool uses your browser's built-in encoders: WebM (VP9 or VP8) in Chrome/Firefox/Edge, and H.264 (MP4) in Safari. You don't choose the codec directly — the browser picks based on what it supports natively.
Why not H.265 or AV1?
Browser support for encoding (not just playback) is limited. H.265 requires licensing fees that browser vendors avoid. AV1 encoding is still too slow in JavaScript. For those codecs, use a desktop tool like Handbrake or FFmpeg.
Video file size is driven by three main factors: resolution (how many pixels each frame contains), bitrate (how much data is allocated per second of playback), and duration. Compression reduces file size by lowering one or both of the first two. Dropping resolution — say from 1080p down to 720p — means each frame has fewer pixels to store, which shrinks the file substantially since resolution has a squared effect on data volume. Lowering bitrate keeps the resolution the same but allocates less data to represent each second of video, meaning the encoder has to be more aggressive about which visual detail it keeps and which it discards or approximates.
This tool applies both levers in the browser using Canvas and the MediaRecorder API: it decodes your source video, redraws frames at your chosen resolution, and re-encodes the sequence at your target bitrate. Unlike server-based compressors, no copy of your video is transmitted anywhere — the entire decode-redraw-encode pipeline runs on your device. That matters for anyone compressing footage that hasn't been publicly shared yet, like an unreleased edit, a private recording, or client work under an NDA.
The most common real-world triggers for compressing video are email attachment limits (typically 25 MB), messaging app caps, and slow upload speeds on mobile connections. Compression is also worth doing before archiving old footage you want to keep but don't need at full quality forever. It pairs naturally with Trim Video — cutting a clip down to just the segment you need reduces duration, which combined with a lower bitrate or resolution gives you the smallest possible file for a given piece of footage.
One nuance worth understanding: bitrate reduction and resolution reduction affect quality differently. Aggressive bitrate reduction at full resolution tends to show up as blocky compression artifacts, especially in fast motion or high-detail scenes, because the encoder doesn't have enough data budget to represent complex frames accurately. Resolution reduction is more forgiving — a smaller frame simply has less detail to begin with, so the eye doesn't notice missing high-frequency detail the way it notices blocky artifacts. For video destined for phone screens or small embedded players, reducing resolution first is usually the better tradeoff.
Unlike most online tools, Toolivon processes everything directly in your browser using the Web APIs built into Chrome, Firefox, Safari, and Edge.
Last updated: