Видеоинструменты IT Market
WhatsApp Video Compressor
Сожмите ролик под отправку в WhatsApp или другой мессенджер. Файл обрабатывается локально.
Результат
Загрузите видео и нажмите кнопку экспорта.
Видеоинструменты IT Market
Сожмите ролик под отправку в WhatsApp или другой мессенджер. Файл обрабатывается локально.
Tool guide
WhatsApp caps what it will carry and re-encodes whatever it does accept, so a 300 MB clip straight off a phone either refuses to attach or arrives visibly mushy. Drop an MP4, MOV or WebM here, pick a size target in megabytes, cap the long edge of the frame and lower the frame rate. The re-encode runs inside the tab itself, nothing is uploaded anywhere, and you end up with a WebM small enough to actually send. See also: squeeze a clip under the 25 MB mail limit, strip the audio track and save some weight, make sure nothing broke in the compression, rebuild an iPhone MOV into MP4.
A normal media attachment is capped near 16 MB on most builds, while the same clip sent as a document goes far higher — current versions measure that ceiling in gigabytes. The number shifts between releases and differs between Android and iOS, which is why you get contradictory answers online. Set «Target MB» to 16 if the clip has to send anywhere, or 64 if you are sending it as a file.
A web page can reliably drive the browser's built-in VP8 or VP9 encoder, but it cannot assemble licensed H.264 inside an MP4 container. Most Android handsets play WebM in WhatsApp without complaint; some iPhones will only open it as a document attachment. If you specifically need MP4 with H.264 and AAC, run the output through ffmpeg or a desktop converter afterwards.
Raise «Target MB» before anything else — a bigger budget means more bitrate at the same resolution. If you cannot raise it, cut «FPS» to 12–15 rather than shrinking «Max side px»; viewers forgive lower smoothness far more readily than smeared detail. For fast motion the rule inverts: keep 24 frames and give up resolution instead.
Yes. The page opens in a mobile browser and takes the clip straight from your gallery through the normal file chooser. Encoding is CPU-heavy though, so on a budget handset a long video can take longer than its own runtime, and the tab has to stay in the foreground or the system suspends the work. Anything past a few minutes is easier on a laptop.
Nowhere. The file is read by the tab through the File API, decoded and re-encoded on your own device, and the finished WebM appears as a local download link. Neither the source nor the result is sent to it-market.pro or written to any storage. Close the tab and nothing remains; running it again starts from scratch.
No. This page only controls weight, resolution and frame rate — the fields are «Target MB», «Max side px» and «FPS», and there is nothing else. Duration passes through unchanged. Trim the head and tail somewhere else first, for instance in your phone's gallery editor, then bring the shortened file here. The result also looks better, since the budget covers fewer frames.
Same engine, different defaults and a different job. The sibling page starts at a 25 MB target because that is the Gmail attachment ceiling; free Discord wants less still — 20 MB since August 2026. This one starts at 64 MB, since WhatsApp's document route carries considerably more and there is no reason to throw away bitrate you are allowed to keep.
Three things can cause it, and the result card names the one that did. If the «Audio» list was on «No sound», the card says the export was made without sound on purpose. If the source itself carried no track — filmed with the microphone off, or already put through a silent export — the card says there is no track and the whole bitrate went to the picture. In the ordinary case the line reads that the audio track was recorded, with its bitrate: 64 or 128 kbit/s depending on the budget. There is a fourth outcome too: the file has sound but the browser could not extract it, and then the export never starts and shows a message.
Before: 4K 60 fps, 1 min 20 s, 412 MB — WhatsApp refuses to attach it
After: Target MB 64, max side 1280, FPS 24 — a WebM near 55 MB that still reads fine on a phone
Before: 1920×1080 screencast, 6 minutes, 280 MB
After: Target MB 25, max side 1280, FPS 12 — interface text stays legible after the re-encode
Your rating and feedback help decide what to improve next.