Target a real size
Presets map to WhatsApp, Discord, email, Nitro and Slack. Custom accepts any megabyte cap the form actually prints.
Choose a size target. Files under about 500 MB compress on this device. Larger clips, or a weak computer, can use cloud.
Browse by category
Why this compressor
Most pages offer a quality slider and hope the file fits. This compress video workflow asks for the real cap first — Discord 8 MB, WhatsApp 16 MB, email 25 MB — then estimates before it encodes.
Presets map to WhatsApp, Discord, email, Nitro and Slack. Custom accepts any megabyte cap the form actually prints.
The page reads duration and dimensions, then shows whether the chosen cap should fit. You can drop to 720p before wasting a pass.
Everyday files encode in this tab. Bigger clips, or a weak computer, can use signed-in cloud credits from the same page. No watermark on either download.
If a second pass still cannot beat the original, the tool returns the source instead of handing you a larger MP4.
How to compress video
The tool reads duration and dimensions, estimates a bitrate from the target size, and encodes H.264 video with AAC audio. If the first result exceeds the target by more than five percent, a second lower-bitrate pass can run. A result that would be larger than the source is rejected in favor of the original. Start with the original file instead of a copy that has already been re-encoded. Follow the steps below, keep the tab open while progress is moving, and play the downloaded result before deleting the source. This compress video workflow does not accept a remote video URL and does not fetch media from YouTube, TikTok, cloud drives, or social accounts.

Step 01
Choose the file and wait for duration and dimensions.

Step 02
Select Discord, WhatsApp, email, Nitro, Slack or a custom MB target.

Step 03
Compress, review the savings card, then download and play the MP4.
What it is
Use this compressor when a video is too large for a message, attachment, review link, or storage budget. Presets cover Discord, WhatsApp, email, Nitro and Slack, while Custom accepts a target in megabytes. compress video online on this page means selecting a file you already have permission to use, completing the job locally, and downloading an MP4 file sized for the selected target. The tool reads duration and dimensions, estimates a bitrate from the target size, and encodes H.264 video with AAC audio. If the first result exceeds the target by more than five percent, a second lower-bitrate pass can run. A result that would be larger than the source is rejected in favor of the original.
WhatsApp sharing: Target the messaging allowance and use 720p when a long phone clip needs more bitrate per pixel. Discord uploads: Choose the relevant free or Nitro budget instead of guessing with a quality percentage. Email attachments: Leave headroom below the provider limit because message encoding can add overhead. Private review drafts: Shrink unreleased demos without sending the source to a third-party encoding queue. These are distinct reasons to compress video; they are not promises that every codec or file size will work on every device.

Platform caps
File size is bitrate times duration. The same 8 MB budget looks sharp on a 20-second clip and muddy on a three-minute one. Pick the largest cap the destination allows, then drop resolution before starving the bitrate.
16 MB
WhatsApp is one of the tightest chat caps. Use the WhatsApp preset, keep the clip short, and switch to 720p if the estimate turns yellow. Confirm the downloaded MP4 in WhatsApp before deleting the master.
8 MB · 50 MB Nitro
Free Discord uploads are treated as 8 MB here so the file still posts after container overhead. Nitro uses the 50 MB preset. A long clip at 8 MB needs 480p or 720p more than it needs another encode pass.
25 MB
Gmail and Outlook still bounce attachments around 25 MB. The Email preset aims under that line. Leave a little headroom, because the message itself can add a few hundred kilobytes.
100 MB
Slack's free workspace cap is generous next to chat apps. The Slack preset targets 100 MB, which usually keeps 1080p usable for several minutes without a second downscale.
Use cases
Target the messaging allowance and use 720p when a long phone clip needs more bitrate per pixel.
Choose the relevant free or Nitro budget instead of guessing with a quality percentage.
Leave headroom below the provider limit because message encoding can add overhead.
Shrink unreleased demos without sending the source to a third-party encoding queue.
Quality
File size comes from bitrate, duration, resolution, frame complexity and audio. For a very small target, lowering 1080p footage to 720p usually preserves more visible detail than starving full-resolution video of bitrate. MP4, MOV and WebM with browser-decodable codecs are the safest inputs. Very large 4K clips can exceed tab memory even though the interface accepts them. A local browser tool cannot make lossy re-encoding mathematically lossless. Keep the master file, compare motion and audio after export, and change one setting at a time if the first result is not suitable.
Unlike upload-based compressors, the encode starts after the browser loads its media modules and does not wait for an upstream transfer. Unlike a simple quality slider, target-MB presets make the delivery constraint explicit. A desktop editor remains the better choice for multi-track timelines, frame-accurate finishing, color work, subtitles, or archival masters. CompressVideo is intended for a focused compress video job where a quick local result matters more than a full editing suite.
A 30-second clip at 8 MB has far more bits per second than a two-minute clip at the same 8 MB. When compress video has to hit a hard cap, trim unused seconds first, then lower height.

Privacy
Local compress video stays on this device. Cloud compress video uploads after you sign in, spends credits, and deletes job files after about a day. Close the tab after downloading on a shared computer, and follow workplace policy when a browser tool is not approved for confidential material.
MP4, MOV and WebM with browser-decodable codecs are the safest inputs. Very large 4K clips can exceed tab memory even though the interface accepts them. If the job fails, first try a current desktop Chrome or Edge build. Next, close memory-heavy tabs, shorten the source, or use a smaller resolution. An H.264/AAC MP4 is the most dependable fallback input for video workflows. A retry cannot fix a codec the browser cannot decode, so repeated failures with the same file usually require a compatible source export.

Practical notes
1. Choose the file and wait for duration and dimensions. 2. Select Discord, WhatsApp, email, Nitro, Slack or a custom MB target. 3. Choose original resolution or a lower output height. 4. Check the estimated size and platform-fit status. 5. Compress, review the savings card, then download and play the MP4. The output is an MP4 file sized for the selected target. Review the file name, extension, playback, duration, dimensions, sound, and size before sharing it.
The tool reads duration and dimensions, estimates a bitrate from the target size, and encodes H.264 video with AAC audio. If the first result exceeds the target by more than five percent, a second lower-bitrate pass can run. A result that would be larger than the source is rejected in favor of the original. File size comes from bitrate, duration, resolution, frame complexity and audio. For a very small target, lowering 1080p footage to 720p usually preserves more visible detail than starving full-resolution video of bitrate. This is the practical difference between a real browser media tool and a page that only renames a file extension. The result is produced from decoded media samples or a validated conversion path, subject to the codec support exposed by the browser and device.
Return to the tool above when you are ready to compress video. Use the source master, choose the smallest change that completes the task, and compress video once. If the result is wrong, adjust the relevant setting instead of repeatedly re-encoding the same output. This keeps the compress video workflow understandable and limits avoidable quality loss.
FAQ
Choose the WhatsApp preset, then use 720p if the estimate remains tight. Verify the downloaded MP4 in WhatsApp before deleting the original.
Yes. Choose Custom and enter 10 MB. The encoder aims below that target, but content complexity and container overhead mean the final byte size can vary.
Not completely. Re-encoding is lossy, but a sensible resolution and bitrate can keep the visible change small. Keep the master and avoid repeated passes.
The tool avoids inflating it. If a new encode is not smaller, the original file is returned instead of making a larger copy.
Choose the Discord free preset for the 8 MB cap, or Discord Nitro for 50 MB. Check the estimate, compress video, then upload the downloaded MP4 in Discord before deleting the master.
Short clips can compress video online in mobile Safari or Chrome on the phone. Long 1080p files should use cloud compress — a phone tab often freezes before the encode finishes.
On a computer, keep local compress under about 500 MB. From 1 GB, or about 150 MB on a phone, the page sends you to cloud compress. Cloud also stops at 4 GB. Weak devices get a prompt even on smaller files.
Local compress stays free and does not use an account. Cloud compress needs a sign-in. Free accounts get 60 credits each month, and one credit covers about five minutes of cloud encode. Extra credits sell from the pricing page as Basic and Pro.
Local video compression stays free and does not require an account. Cloud video compression needs a sign-in. Free accounts get 60 credits each month, and one credit covers about five minutes.
Local compress video stays in the browser and is not uploaded. Cloud compress video uploads the file after you click that button, then deletes the job files after about a day. Analytics must not include local file contents, names, frames, audio, or exported media.
Desktop Chrome or Edge is the safest choice for local compress video because codec support depends on WebCodecs. MP4, MOV and WebM with browser-decodable codecs are the safest inputs. Very large 4K clips can exceed tab memory even though the interface accepts them. Cloud compress video can run from the same page after sign-in if the tab is too weak.
No watermark on either path. Local downloads stay free. Cloud jobs spend credits. Extra credits sell on the pricing page as Basic and Pro.
Mobile Safari or Chrome can open a file already on the device. Desktop Chrome or Edge is more reliable for long or high-resolution sources because WebCodecs coverage and memory are stronger there.
MP4, MOV and WebM with browser-decodable codecs are the safest inputs. Very large 4K clips can exceed tab memory even though the interface accepts them. Start with an H.264 MP4 when a special camera file fails. A remote URL or social-network link is not fetched.
Drop a file, set the output, and download. Local stays on this device. Cloud is optional.
Compress video now