Telegram's 2GB limit, and why your video still looks worse

Telegram's FAQ states the limit in one clause: you can "send and receive files of any type, up to 2 GB in size each (or 4 GB with Premium)". The limits page tracks that figure with the date it was last checked.

That is more than a hundred times WhatsApp's 16MB, and it means almost nobody arrives at a compressor because Telegram refused a file. They arrive because of what Telegram did to the file it accepted.

Two ways to send a video, with two different results

When you attach a video from the gallery, Telegram treats it as media: it generates a preview, plays inline, and re-encodes it on the way up. The output is smaller, at a resolution and bitrate Telegram chose and does not publish. A 4K clip typically arrives as something close to 720p or 1080p, visibly softer in motion.

When you attach the same video through the file option (Attach, then File, on both the mobile and desktop apps), Telegram sends the bytes unchanged. The recipient gets exactly what you had, up to the 2GB or 4GB limit, and has to download it to play it rather than watching inline.

Sent as	Re-encoded?	Plays inline?	Size limit	Quality
Video (media)	Yes, by Telegram	Yes	2GB / 4GB	Telegram's choice
File (document)	No	No; download first	2GB / 4GB	Yours

The same split exists on WhatsApp, where the document route also skips the re-encode, with a much tighter limit on the media side. On Telegram the limits match, so the choice is purely about quality versus convenience.

Why sending as a file is not always the answer

Sending the original as a file preserves quality, and also preserves the size. A three-minute 4K phone clip is a gigabyte or more, and every recipient downloads all of it, on whatever connection they have, before they can watch a second. On a group chat with thirty members that is thirty gigabytes of other people's data for a clip that would have looked identical on their phones at 60MB.

The phone that recorded it spent a generous real-time bitrate to keep up. A careful re-encode gets the same picture at a quarter of the bytes, and that is a different thing from the re-encode Telegram does, because you choose the number.

Choosing the number yourself

The useful move is to re-encode once, to a size you picked, and then send the result as a file so Telegram leaves it alone. You get a predictable size, the quality that size allows, and no second encode on top.

Sensible targets, from the formula MB = Mbps x seconds / 8:

Clip	Target	Bitrate	Resolution that holds up
30 s highlight	20MB	5.3 Mbps	1080p, comfortably
2 min phone video	50MB	3.3 Mbps	1080p
5 min recording	100MB	2.7 Mbps	1080p, or 720p if there is a lot of motion
20 min lecture	100MB	0.67 Mbps	480p; consider a link instead

Each of those lands under the number by encoding on your own machine, measuring the real output and re-encoding on a corrected bitrate if the first pass came in over. The file is never uploaded anywhere but Telegram, as the file you chose.

Codec: stick to H.264

Telegram's apps play H.264 in an MP4 container inline on every platform. H.265 (HEVC) files from an iPhone's High Efficiency setting may play on some devices and not others, and AV1 support is patchier still. The codec comparison makes the case in full; the short version is that a file sent to someone else should be H.264, because a smaller file that does not play is a support conversation rather than a smaller file.

A re-encode to H.264 is also what the media route does anyway, so doing it yourself at a chosen size costs nothing in compatibility and gains control.

When the 2GB limit actually bites

Rarely, and almost always with recordings rather than clips: a full lecture, a two-hour screen capture, a wedding video off a camera. Those are also the files that no chat app is the right transport for, because a recipient on mobile cannot sensibly download 2GB. A link to cloud storage is the better answer, and if a file must travel, how long a video fits at each size and resolution tells you whether it can be made small enough to be worth sending at all.

Premium's 4GB is the same story twice over.

FAQ

What is the maximum file size on Telegram?

2GB per file on a free account and 4GB with Telegram Premium, for files of any type, according to Telegram's own FAQ. It applies to videos, documents and archives alike, and it is high enough that the limit itself is rarely why a video needs compressing.

Does Telegram compress videos?

Yes, when a video is sent as media from the gallery: Telegram re-encodes it to a resolution and bitrate of its own choosing so it plays inline, and the result is noticeably softer than the original. Sending the same video with the File option transmits the bytes unchanged, with the same 2GB or 4GB limit, but the recipient must download it before playing.

How do I send a video on Telegram without losing quality?

Attach it as a file rather than as a video. Telegram does not re-encode files, so the recipient gets exactly what you sent. If the original is a large phone recording, re-encoding it yourself to a chosen size first, then sending that as a file, gives a predictable size at the quality that size allows, with no second encode by Telegram on top.

Why does my Telegram video look blurry on the other end?

Because it was sent as media and Telegram re-encoded it. The original on your phone is unchanged; the copy that went out was reduced to Telegram's inline-playback settings. Send it as a file to avoid that, or re-encode it yourself at a bitrate you choose, which for a 1080p clip means 3–5 Mbps to look like 1080p.