Telegram's FAQ states a per-file limit of 2 GB, or 4 GB with Telegram Premium. If a video will not send, that is the number to measure it against — and if you found a smaller number somewhere, there is a good chance you found it on Telegram's own website.
Why the number you found is probably wrong
Search for Telegram's file size limit and one of the results you are likely to land on is telegram.org/blog/files-on-steroids, on Telegram's own domain. Its opening sentence reads:
"Many of you love Telegram for the ability to send huge files up to 1.5 Gb."
The byline on that post is March 25, 2015.
It is an announcement from more than a decade ago, describing the limit as it stood then. Because it sits on the official domain it carries the authority of documentation while giving a figure that no longer applies. When we checked the results for "telegram file size limit" on 16 September 2026, that 2015 post was still ranking — the only official page there, and the wrong one.
So before you compress anything: check the date on whatever page gave you your number. The current figures live in Telegram's user-facing FAQ, not in the blog archive.
What Telegram's FAQ actually says today
Two separate places in the FAQ give the same figure. On how Telegram differs from WhatsApp:
"Unlike WhatsApp, Telegram is a cloud-based messenger with seamless sync. As a result, you can access your messages from several devices at once, including tablets and computers, and share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each."
And in the feature list for groups, under file sharing:
"Send and receive files of any type, up to 2 GB in size each (or 4 GB with Premium), access them instantly on your other devices."
| Account | Per-file upload limit |
|---|---|
| Free | 2 GB |
| Telegram Premium | 4 GB |
Worth being pedantic about: Telegram writes "2 GB" and "4 GB" and never publishes a byte count. Anyone quoting an exact byte figure is doing arithmetic Telegram did not do — if your file sits within a rounding error of the line, shave a bit more off rather than trying to land on the boundary.
The cap applies to the sender, not the recipient
This is the part that most write-ups get wrong.
The 2 GB / 4 GB split is an upload limit. Telegram's Premium FAQ is explicit that receiving is not restricted: there are "no restrictions on communication between Premium and non-Premium users", and "anyone can download 4 GB files uploaded by premium users". Even more directly:
"Some premium features can be accessed by users who did not subscribe, provided that a subscriber uses them first. This also applies to files: any user can download large 2+ GB files uploaded by premium users."
The practical consequence: if the person on the other end has Premium and you do not, they can send you a 4 GB file and you will receive it and be able to download it. The reverse does not work — you still cannot upload it. Note the exact verb Telegram uses, which is "download". Nothing here says a free account can upload past its own cap.
Why the ceiling has moved over the years
The limit is not a constant baked into Telegram's protocol. It is a server-delivered configuration value, which is precisely why the 2015 blog number could go stale without anything visibly changing in the apps.
Telegram's MTProto documentation describes uploads as a file split into parts, and says:
"Note that the limit of uploadable file parts does not account for the part_size: thus the total file size limit can only be reached with the biggest possible part_size of 512KB, which is actually the recommended part_size to avoid excessive protocol overhead."
The part count itself comes from two fields the server hands to the client — upload_max_fileparts_default for non-Premium users and upload_max_fileparts_premium for Premium users. The config documentation describes the first as:
"The maximum number of file parts uploadable by non-Premium users (integer, the maximum file size can be extrapolated by multiplying this value by 524288, the biggest possible chunk size)"
The sample config Telegram publishes shows 4000 and 8000 for those two fields. Do the multiplication if you like, but do not treat the result as an officially published figure — for a number to quote, use the FAQ's 2 GB and 4 GB.
The fix: get the file under the cap before Telegram sees it
If your video is genuinely over the line, it has to get smaller.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
If you would rather understand the knobs than accept a preset, how to compress a video without losing quality walks through what actually costs you picture quality. For a QuickTime file straight off a Mac or iPhone, MOV to MP4 swaps the container, and compress video is the general-purpose version of the tool above.
Other reasons a send fails that are not about size
Being under 2 GB does not guarantee a clean send.
It sent, but it shows as a plain file instead of a video. Telegram's Bot API documentation for sendVideo states: "Telegram clients support MPEG4 videos (other formats may be sent as Document)." Note the "may" — this is not a published whitelist. It is, however, the documented reason a .mkv or .avi can arrive as a file icon rather than something that plays in the chat. Telegram's supported video formats covers the codec side in detail.
Your silent clip is looping like a GIF. There is a real flag behind this. Telegram's upload constructor has a nosound_video option, documented as: "Whether to send the file as a video even if it doesn't have an audio track (i.e. if set, the documentAttributeAnimated attribute will not be set even for videos without audio)." In other words, a video with no audio track is treated as an animation by default. If your export dropped the audio stream, that is why it behaves like a GIF.
You posted to a large channel and nothing appeared. Telegram's documentation explains this one directly: "When sending videos to big channels, Telegram will automatically convert them, generating multiple versions in multiple qualities and formats." Because that processing takes time, such videos "will not be sent immediately after invoking sendMedia/sendMultiMedia: instead, they will be added to the schedule queue similarly to scheduled messages." Your upload finished; the post is queued behind a server-side transcode. Telegram does not publish what counts as a "big" channel.
The upload crawls. Telegram documents a specific throttle for free accounts, FLOOD_PREMIUM_WAIT_X, but with a condition people usually drop: "This error can only be received when the user has uploaded tens of gigabytes or more."
You are sending through a bot. Bots live under completely different numbers. Telegram's Bot API says bots "can currently send video files of up to 50 MB in size, this limit may be changed in the future", while getFile notes that "for the moment, bots can download files of up to 20MB in size" — a bot can send more than it can fetch. See Telegram bot file size limits.
How to tell it worked
Check the file size on disk before retrying — that is the number Telegram measures. If it is comfortably under the cap and the send still fails or renders wrong, the problem is not size, and the MP4 container question above is the next thing to look at.
FAQ
What is the maximum video size I can send on Telegram? 2 GB per file on a free account, 4 GB with Telegram Premium, per Telegram's FAQ. If you found 1.5 Gb, that came from Telegram's own blog post dated March 25, 2015 and no longer reflects the current figure.
Can I send a 4 GB video without Premium? No. The 4 GB ceiling applies to uploading. What you can do without Premium is receive one: Telegram states that "any user can download large 2+ GB files uploaded by premium users." If a Premium friend is available, having them upload it is a genuine workaround.
Does "send as file" keep my video at full quality?
Telegram's protocol does have a force_file flag, documented as "Force the media file to be uploaded as document", so the separate path is real. But Telegram's help centre does not describe what that path does to resolution, bitrate, or codec, and it publishes no compression parameters at all. The widely repeated claim that it preserves quality perfectly has no official source — check the official documentation rather than trusting it.
Why did my video send as a document instead of playing in the chat?
Because of the container. Telegram's Bot API documentation for sendVideo states that Telegram clients support MPEG4 videos and that other formats may be sent as Document. That "may" is Telegram's own wording, and it does not publish a full list either way, so MP4 is the container the documentation names — not a guarantee about every other one.
Figures quoted from Telegram's FAQ, Premium FAQ and developer documentation, checked 16 September 2026. The 1.5 Gb figure comes from Telegram's 2015 blog post and is included here only as the thing to ignore. Hitting the same wall elsewhere? See WhatsApp video too large to send and Discord says your file is too large, browse the rest of the fix guides, or see all Clapr tools.
