2026-09-16
Telegram’s file size limit is 2GB free, 4GB with Premium — and the one-way gap almost nobody notices (by Telegram’s own numbers)
The file that finally hits Telegram's wall is rarely the one you'd expect — a two-minute screen recording of a bug for a coworker, a continuous take from a phone propped up during a lesson, an entire event exported in one piece instead of trimmed first. Telegram's own numbers on file size are generous by messaging-app standards. When the upload fails anyway, the problem is almost never the cap itself — it's that the file reaching it was never compressed to begin with.
The two numbers, in Telegram's own words
Telegram states its limit plainly, twice, in nearly identical language on its own FAQ page: you can "share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each," and, describing what groups can do, "Send and receive files of any type, up to 2 GB in size each (or 4 GB with Premium)." Telegram's own Premium FAQ lists "4 GB File Uploads" as one of the subscription's headline features, alongside faster downloads. There's no separate, stricter number for video specifically — the 2 GB / 4 GB ceiling covers any file type uploaded from the app itself, video included.
The gap almost nobody notices: it's the sender's tier that matters, not yours
The detail worth knowing sits one line below that headline feature, in the same Premium FAQ: "any user can download large 2+ GB files uploaded by premium users." Read that again — a free account can receive a 3.5 GB video without ever paying for anything, as long as whoever sent it has Premium. The 2 GB ceiling only ever applies to what you personally can upload; it's never a limit on what you're allowed to receive. Whether a given file clears the wall depends entirely on the sender's account, and nothing about the recipient's.
Why the wall is almost never your own compressed video
Run NearVid's own quality presets through the math and 2 GB stops looking like a tight limit at all. Convert to WebM's High preset — 2Mbps of video plus roughly 128kbit/s of audio, per NearVid's own bitrate table — would need close to two hours and five minutes of footage before the export even approaches 2 GB, and about four hours eleven minutes to approach 4 GB. Even Convert to MP4's High preset, heavier at 4Mbps on browsers where WebCodecs H.264 encoding is available, takes roughly an hour and five minutes to reach 2 GB. None of that is a live-encode measurement — it's the same labeled "≈" bitrate-times-duration approximation NearVid's own export screen shows before you commit, not a real test encode. Either way, the conclusion holds: a file NearVid actually produced would have to run for hours to threaten either ceiling.
What actually gets there fast is footage nobody has compressed yet. The extreme, precisely documented case: Apple's own ProRes white paper puts the target data rate of ProRes 422 — a professional editing codec, not a phone default — at "approximately 147 Mbps at 1920 x 1080 and 29.97 fps," which the same paper's own data-rate table works out to 66 GB per hour. At that rate, 2 GB is gone in under two minutes. Almost nobody is shooting plain ProRes day to day — it's an optional, off-by-default, Pro-tier capture mode, not something a phone records unless you specifically turn it on — but the shape of the problem is the same at a smaller scale for anything straight off a camera or a screen recorder: a long, unedited, un-re-encoded capture accumulates size fast, and a 2 GB or 4 GB ceiling that looked generous a minute ago starts to feel tight the moment a clip runs past a few minutes at full quality.
What actually gets you under either cap
The fix follows the same order as sending anything over a size-limited channel: cut first, compress second. NearVid's Trim is a lossless stream copy — no re-encode, no quality loss — so cutting a 20-minute screen recording down to the 90 seconds that matter shrinks the file by roughly the same fraction as the runtime, before any re-encoding enters the picture at all. From there, Convert to WebM — or, where WebCodecs H.264 support is detected, Convert to MP4 — re-encodes at a quality preset you choose, with an "≈" size estimate shown on the export screen before you commit. That means seeing, in advance, that a given trim and preset lands comfortably under Telegram's free 2 GB cap, instead of finding out only after an upload fails partway through.
What this doesn't fix
NearVid has no way of knowing whether you or the person you're sending to has Telegram Premium, and it doesn't touch Telegram at all — it only prepares the file before you open the app yourself. And the ProRes figure above is an illustration, not a compatibility claim: NearVid's tools work with ordinary containers and codecs (MP4, MOV, WebM, MKV and similar), but a professional codec like ProRes isn't something we've specifically tested end to end, so a file in that format may or may not open cleanly — worth trying on a copy first if that happens to be what you're working with.
The honest summary
Telegram's own FAQ puts its file size ceiling at 2 GB free, 4 GB with Premium, and its Premium FAQ adds the detail most people miss — a free account can still receive a file above 2 GB, as long as a Premium account sent it. NearVid's own compressed output, at any quality preset, would need well over an hour of footage to threaten either number, per its own bitrate table; what actually hits the wall is uncompressed or lightly compressed footage straight off a camera or screen recorder, an extreme version of which — per Apple's own ProRes white paper — can burn through 2 GB in under two minutes. Trim to the part worth keeping, then convert at a size you can see in advance, entirely on your own device, and a cap that looked tight turns out to have plenty of room.