Create a smaller delivery copy using quality, resolution or target-size settings. Processing happens locally in your browser. Check the completed size, picture, sound and destination compatibility before sharing.
Supported MP4, MOV, WebM and other inputs · One file at a time · Up to 2 GiB; device limits apply
Required video APIs are unavailable in this browser. Try an updated supported browser and device; codec support also depends on the operating system.
Output uses an MP4 container. H.264 video and AAC audio are preferred, with supported alternatives possible. Read the result details; compatibility and target size are not guaranteed. Sizes use 1 MB = 1,000,000 bytes. Keep the tab visible during processing.
Choose a video to get started.
The available controls are quality mode, target size, resolution and sound. This page does not provide trimming, a frame-rate selector or dedicated app presets. Prepare a shorter clip in a separate editor if that is the right compromise.
Balanced, Smaller file and High quality request different video bitrates based on dimensions and the source’s estimated frame rate. They are starting points, not measured quality scores. Already compact sources may shrink little or even produce a larger result. Keep whichever copy best meets your purpose.
Auto keeps the source dimensions in quality modes; in target-size mode it can reduce them when the budget is tight. Resizing preserves the intended aspect ratio subject to pixel rounding. Smaller dimensions remove detail, so compare tutorial text, faces and fast-moving scenes before accepting a result.
For illustration, a 25 MB file over 120 seconds has a total average budget of about 1.667 Mbps before overhead. Audio consumes part of that budget. This tool reserves initial container headroom and can retry up to twice if output overshoots; it can still report Target not met. Always read the final byte count.
Use the destination’s current size and codec requirements. No fixed preset here guarantees acceptance by an email provider, chat app or upload form. See the size-budget guide for arithmetic and examples.
The tool re-encodes primary video and audio. It is not a lossless archive, a full editing suite or a certified metadata scrubber. Extra tracks and subtitles should not be assumed to survive. Keep the original separately; see the quality comparison guide and playback troubleshooting.
The compressor reads the selected file and creates the output locally in your browser; its video-processing module has no file-upload request. Loading the website and any shared services can still involve network requests. Local video processing does not mean that the entire website collects no request, analytics or advertising information.
One file is processed at a time. The input ceiling is 2 GiB (2,147,483,648 bytes, about 2.15 decimal GB). That is a validation limit, not a guarantee the device has enough memory: the output is buffered in memory. Save the result before leaving or reloading the page.
Speed depends on source complexity, encoder availability and device resources. There is no fixed completion time. Keep the tab visible and follow the displayed error if processing stops. Browser and OS support determine the available codecs; an up-to-date browser does not guarantee every file can be read or encoded.
The current compressor processes the selected file locally in the browser and does not upload its contents as part of conversion. The website itself still loads resources and may use shared services; local processing is not a blanket statement about all site data collection.
MP4, MOV, WebM and other recognised containers are candidates. Success also requires browser support for the codecs and properties inside the file. A video extension alone does not guarantee that it can be read.
No. The tool prefers H.264 and AAC but can select other supported video or audio codecs. Read the result details and test the downloaded file in the destination.
No lossless mode is provided. The tool re-encodes video, and a lower resolution removes detail. Compare important scenes and keep the source for editing or archiving.
No. The tool can make additional attempts, but it can still report Target not met. Check the completed byte count and the receiving service’s rules.
No. The current interface does not provide those controls. It offers quality mode, target size, resolution and sound removal.
It may work when the mobile browser and device support the required decoding and encoding. Memory and processing constraints can still prevent completion, especially for large files.
The compressor adds no watermark and requires no account to run. Keep a separate original because the output is a new delivery copy.
Guide checked by eToolPlus · 16 October 2026 · Video processing by Mediabunny (MPL-2.0)