Видеоинструменты IT Market
Compress Video to 25 MB
Локально сделайте облегчённую WebM-версию ролика для отправки, черновика или предпросмотра.
Результат
Загрузите видео и нажмите кнопку экспорта.
Видеоинструменты IT Market
Локально сделайте облегчённую WebM-версию ролика для отправки, черновика или предпросмотра.
Tool guide
The number 25 MB follows anyone who sends video around: it is the Gmail attachment ceiling, and plenty of corporate mail gateways enforce the same threshold. Messengers sit lower — free Discord has asked for 20 MB or less since August 2026. This page rebuilds the clip inside the tab against a size budget you choose and hands back a WebM. No server touches it: nothing is uploaded or stored, and every frame runs on your own CPU. See also: get a clip ready for a messenger, pack several files into one archive, make a short GIF instead of a heavy video.
Email is what lands on this number: Gmail rejects attachments above 25 MB and plenty of corporate mail gateways copy the same setting, which is why «Target MB» ships with 25 already in it. Messengers sit lower — free Discord has wanted 20 MB or less since August 2026, so set 20 rather than 25 for it. If your recipient is stricter still, type 10 or 16; the field accepts anything down to 2.
No, it is a target rather than a promise. A bitrate is derived from your duration and budget and the encode runs at it, but the real size depends on content: a static frame compresses far harder than a fast-moving scene, so landing 10–15 percent either side is normal. If you overshoot the limit, set the target to 22 and run it again.
Rough arithmetic: 25 MB is roughly 200 megabits, so a three-minute clip gets about 1.1 Mbit/s. That sustains 854×480 at 24 frames, but not honest 1080p. For a ten-minute recording, drop «Max side px» to 640 and FPS to 12, or the picture will break into visible blocks the moment anything moves.
H.264 is a licensed codec and a web page cannot assemble one on its own; the encoder available to the tab writes WebM with VP8 or VP9. Chrome, Firefox, Telegram, VLC and Android all open WebM, but older Windows Media Player builds and some editing suites will not. Run the finished file through ffmpeg if you need the other container.
Probably not. Encoding happens in real time and saturates the tab, so a long clip looks stuck while it is in fact working. Do not switch tabs or let the screen sleep — browsers throttle background pages and the job stalls. If the file is genuinely huge, cutting out the section you need beforehand saves far more time than waiting it out.
Yes — when the source has sound to begin with. The track goes into the same WebM as Opus, and the «Audio» list holds «Keep sound», which you can switch to «No sound». Sound spends the shared budget: 128 kbit/s when that budget is above 1.2 Mbit/s, 64 kbit/s otherwise. The result card states plainly which of three things happened: the track was recorded and at what bitrate; the source carried no sound, so the whole bitrate went to the picture; or you chose «No sound» yourself. There is one more case — the file has sound but the browser could not extract it, and then the export does not start and says so.
The processing is identical; the defaults and the situation differ. The sibling page opens at a 64 MB target because WhatsApp's document route accepts more. This one defaults to 25 MB for email; for free Discord set it to 20. If you already know the number you need, either page will do — type it into «Target MB» and the output is the same.
Before: 1080p report clip, 3 minutes, 190 MB — the message will not send
After: Target 25 MB, max side 854, FPS 24 — a WebM near 24 MB that attaches cleanly
Before: Game capture, 2 minutes at 60 fps, 320 MB
After: Target 20 MB, max side 1280, FPS 24 — inside the free-account limit
Before: Whiteboard recording, 12 minutes, 640 MB
After: Target 25 MB, max side 640, FPS 12 — handwriting stays readable inside the limit
Your rating and feedback help decide what to improve next.