WebCodecs in this tab
The browser demuxes, decodes, and re-encodes on this device with WebCodecs. The file stays in this tab.
Telegram · Video Compressor · No upload
Compress a video for Telegram.
Compress a video for Telegram?
Encoding stays on this device. Telegram’s FAQ states a gigabyte cap. This page does not turn that cap into a megabyte target. Telegram’s FAQ says you can share an unlimited number of photos, videos, and files (doc, zip, mp3, and so on) of up to 2 GB each.
Gmail Help: Send attachments with your Gmail message; WhatsApp Help: media and documents; WhatsApp Help: longer videos; Telegram FAQ
Last updated
Encoding stays on this device. Telegram’s FAQ states a gigabyte cap. This page does not turn that cap into a megabyte target.
100% Local
No Upload
Your video never leaves this device
Privacy clean output
What Telegram’s FAQ says
Telegram’s FAQ says you can share an unlimited number of photos, videos, and files (doc, zip, mp3, and so on) of up to 2 GB each. The same FAQ later says you can send and receive files of any type, up to 2 GB each, or 4 GB with Premium. The FAQ does not define that gigabyte as a decimal or binary megabyte count, so this page does not fill the size box with a converted megabyte number. If you set a size here, it is this site’s encoding target, not Telegram’s byte definition, and not a promise that Telegram will accept the file. Telegram FAQ. Video Compressor.
One local ffmpeg encode, 28 October 2026
ffmpeg 6.1.1-3ubuntu5 encoded an 8.000000 second 1280×720 test pattern with a 440 Hz tone. The source command used libx264 ultrafast at 8000k video and AAC at 160k. The output command used libx264 medium at 800k video, maxrate 800k, bufsize 1600k, AAC at 96k, and +faststart. The 800k figure is that video bitrate. It is separate from Telegram’s 2 GB and 4 GB FAQ figures. The compress control on this page was not used for the row. See how Telegram send-as-file treats a photo.
| File | Bytes | SHA-256 | Video bitrate | Audio bitrate |
|---|---|---|---|---|
| source.mp4 | 7765296 | 18a7a8a652c23fbfe86b728c2d91d2c9d3a8ade784025806a30c406c6ed22c20 | 7597883 | 158677 |
| out-800k.mp4 | 934887 | 580103c56aa11d5be1d592e9609d070087709a226a82b6c0430956629b966210 | 828420 | 96282 |
The output is smaller: 7765296 bytes in, 934887 bytes out. Duration stayed 8.000000 seconds. The record is docs/evidence/runs/2026-10-28-night-telegram-encode.json.
A second local ffmpeg encode, 29 October 2026
ffmpeg 6.1.1-3ubuntu5 wrote a 12.000000 second 1280×720 test pattern with temporal noise and a 440 Hz tone. The source command used libx264 ultrafast at 25000k video, minrate 22000k, maxrate 25000k, bufsize 25000k, and AAC at 160k. The output command used libx264 medium at 800k video, maxrate 800k, bufsize 1600k, AAC at 96k, and +faststart. On 29 October 2026 the Telegram FAQ still said files of up to 2 GB each, and later “up to 2 GB in size each (or 4 GB with Premium).” 38452098 bytes is under 2 × 1,000,000,000. The compress control on this page was not used. See how Telegram send-as-file treats a photo.
| File | Bytes | SHA-256 | Duration | Video bitrate | Audio bitrate |
|---|---|---|---|---|---|
| over.mp4 | 38452098 | 2264db081de45e4c28c85c52f486bd38ba2525e8d7d0fdddc1dc7f2d2d2069f1 | 12.000000 s | 25467306 | 159291 |
| under.mp4 | 567974 | 8fc2fb34da274b86bb2ed42983b5f09b4a507f38a6e7e131176ccc071e5f18e9 | 12.010000 s | 273442 | 96236 |
The output is smaller: 38452098 bytes in, 567974 bytes out. ffprobe duration on the output is 12.010000 seconds. The record is docs/evidence/runs/2026-10-29-comp-fixtures.json.
▶
Drop an MP4, MOV, or WebM
MKV is accepted when the browser can decode it. Processing stays in this tab.
No preview
Video
— · source stays on this device
Destination target:
Detecting…
Compressing0%
- Elapsed
- 00:00
- Remaining
- —
- Processing FPS
- —
- Source duration
- —
- Bytes written
- —
- Ratio so far
- —
- Path
- —
- Target resolution
- —
Compressed locally
- Original
- —
- Compressed
- —
- Saved
- —
- Time
- —
- Speed
- —
- Codec
- —
- Engine
- —
- Resolution
- —
Privacy clean output
Saved directly to the file you chose.
Verify it yourself (F12 Network)
This workflow processes your file in this browser tab. Opening DevTools is optional; it is the simplest way to watch what the page actually requests.
- Press F12 (or ⌥⌘I). Open DevTools, then the Network tab, before you start.
- Start the local job (clean, OCR, compress, merge).
- You can also disconnect the network after the page has loaded its UI. Same-origin engine/WASM/language files may still be cached from an earlier visit.
- Your file bytes are not POSTed to CreatorPrivacyKit for this step. Page HTML, CSS, and same-origin runtime assets still load over the network when they are not cached.
Expected Network activity: this site’s CSS/JS, and — after you run the tool — same-origin WASM, codec, or OCR language data. That is a download of our engine, not an upload of your file.
- Processing location
- This browser tab
- Media upload to our servers
- Not part of this workflow
- Remote analysis of your file
- No
This panel is a product fact, not a live packet sniffer. We do not invent a request counter. Ads, extensions, and your own later clicks can still create network traffic.
How compression runs in this browser, with no upload and no server queue
Decode, scale, and encode happen in this tab. CreatorPrivacyKit does not take the video for a server transcode.
No upload to this site
Frames and audio stay in this tab’s memory and temporary browser storage. There is no compressor upload API. That is a real difference from a converter that needs the whole file first.
Watch the Network panel
Open Developer Tools, switch to Network, and start a compress. The media file is not posted to a CreatorPrivacyKit transcode endpoint. Disconnecting the network is a rough extra check, not a formal audit.
Compare the exported bytes
Compare the download with the input. The page shows the byte change. A megabyte target is the upper size you set.
Local browser versus a cloud converter
Upload converters need the whole file first. This page compresses on this device. That is the upload difference. It is not a claim that nothing can go wrong on this computer.
| What you are comparing | This page (browser, no upload) | Typical upload converter |
|---|---|---|
| File upload | No upload The source stays in this browser. | Full upload The whole file is sent to a remote host. |
| Queue | Starts on this machine. There is no shared transcode line. | Often queued. Free tiers delay or cap jobs. |
| Size plans | No paid file-size plan. You are still limited by this device. | Free tiers often cap megabytes and charge for more. |
| Where the file sits | We do not keep a copy of your video on our servers. | Files commonly sit on the converter’s disks for a while. |
| What still can go wrong | No upload to this site. Malware on this device, a browser bug, or you later uploading the output are still possible. | A server breach, staff access, or a misconfigured bucket can expose the original. |
| Container metadata | Re-encoding writes a new MP4 (H.264) or WebM (VP9/AV1) and drops supported container metadata. Pixel-domain watermarks stay. | Behavior varies. Some keep camera headers or add converter tags. |
Size targets for Discord, email, and chat apps
These figures come from vendor help pages checked in September 2026. Apps change limits. A preset is a target — look at the file you actually get.
Discord
20 MB non-Nitro (FAQ, Aug 2026) · 50 MB Nitro Basic · 1 GB NitroDiscord’s File Attachments FAQ lists 20 MB for non-Nitro chat attachments as of August 2026, with 50 MB on Nitro Basic and 1 GB on Nitro. Discord also says it is testing other caps for some users, so the number in your app wins. The in-tool 19 MB Discord target is a margin under the stated 20 MB, not a send guarantee. Nitro was 500 MB. Server Boost Level 2 is 50 MB and Level 3 is 100 MB, for members of that boosted server only. Discord checks file size before its own compression, including on mobile. Open the Discord compressor or read the 20 MB field note.
Source updated August 2026 · checked September 21, 2026 Official source
Email attachments
Gmail consumer ~25 MB then Drive · Outlook.com and internet accounts 20 MB message size · Exchange default 10 MBGmail Help says consumer accounts typically allow about 25 MB of attachments and then insert a Drive link. Workspace attachment size is set by the administrator. Outlook on Outlook.com and internet accounts uses a 20 MB message size, which includes the attachment and the message. The Exchange default is 10 MB, and an administrator can change it. MIME/Base64 can make the sent size larger than the file on disk. Compress for Gmail or Outlook or read the email attachment note.
Checked September 21, 2026 Official source
WhatsApp Help puts a 64 MB ceiling on videos sent as video. Faster connections may default to 100 MB / 720p. Sending as a document is a separate 2 GB path. Those are upload caps, not a promise WhatsApp will keep your bitrate.
Checked September 21, 2026 Official source
LINE
Chat has no official MB cap · VOOM ended 30 Sep 2026LINE chat still has no official universal video MB cap. LINE VOOM, including Official Account VOOM posts, ended 30 September 2026 (around 11:00 JST) per LINE Help. Account rollout varies, and some Official Account content remains in LINE Home. Historic VOOM posts were 500 MB; that was not a chat limit. Official Account broadcast video is still 200 MB. Chat and broadcast messaging continue. Check the size LINE shows before you send.
Source updated July 2026 · checked September 30, 2026 Official source
Telegram
2 GB free · 4 GB Telegram PremiumTelegram’s FAQ lists 2 GB per file on a free account and 4 GB on Premium. Send-as-file can keep container metadata such as GPS. See the send-as-file metadata note.
Checked October 14, 2026 Official source
Local creator workflows
No upload here — still limited by this deviceFor client reviews and unreleased footage, keep the camera master offline and make a smaller MP4 on this device. Video compression guide · Compress without uploading.
Questions
The FAQ says 2 GB, or 4 GB with Premium. It does not define those gigabytes as a display-megabyte count.
The FAQ says 4 GB with Premium, and 2 GB otherwise.
No. Encoding stays in this browser.