Telegram does throttle upload speed on free accounts — but its own developer documentation says that throttle "can only be received when the user has uploaded tens of gigabytes or more." If you are watching a single 400MB video crawl up the progress bar, you are almost certainly not being throttled for lack of a subscription.
That one sentence cuts against the most common advice on this topic, which is "free is slow, buy Premium and it gets fast." The real picture has two halves that both come straight from Telegram: the free-account throttle has a documented trigger threshold, and Premium comes with a documented disclaimer that it may not speed anything up at all.
What Telegram's upload throttle actually is
On the protocol side, throttling is not a setting or a policy page — it is an error code returned mid-transfer. Telegram's MTProto file documentation describes it like this:
"FLOOD_PREMIUM_WAIT_X: Indicates that upload speed is limited because the current account does not have a Premium subscription, and that the query must be automatically repeated by the client after X seconds."
Three things follow directly from that wording.
It is a wait, not a failure. The spec tells the client to repeat the query automatically after X seconds. So a throttled account does not get an error dialog — it gets a transfer that pauses and resumes. Telegram's help centre does not publish the wording of any user-facing message for this, so do not go looking for a specific error string to confirm it.
It is a sales trigger. The same page says that on receiving the error, clients "should display the Telegram Premium subscription modal, offering the user to purchase a Premium subscription to increase upload speed upload_premium_speedup_upload » times." Note that the multiplier is a named config field rather than a constant baked into the protocol — more on that below.
It has a stated threshold. The docs add, verbatim: "This error can only be received when the user has uploaded tens of gigabytes or more." Tens of gigabytes. Not one large video, not a busy afternoon of screen recordings. If your upload was slow the first time you opened the app, the free-account throttle is not the explanation.
Premium speeds up the account, not the pipe
Telegram's Premium FAQ is unusually blunt about the limits of what a subscription buys. Asked whether faster downloads are guaranteed, the official answer is:
"Subscribing lifts any media download speed limits from your account on Telegram's side. If your download speed does not increase, you may be facing other limits caused by your hardware, internet provider, etc."
Read the scope carefully: "on Telegram's side." Telegram is committing to removing its own throttle, and explicitly naming your hardware and your ISP as things it cannot remove.
The speed-up factor itself lives in appConfig, the configuration block Telegram's servers hand to clients at runtime. The sample configuration published in Telegram's API docs includes these fields:
"upload_premium_speedup_download": 10,
"upload_premium_speedup_upload": 10,
"upload_premium_speedup_notify_period": 3600,Because these are server-delivered values rather than constants, the multiplier is something Telegram can change without touching a single client. Treat the sample as a sample — check the current values in the official API documentation if you are building against them.
So the honest decision rule: buy Premium for the 4GB file cap, not for speed. The cap is a hard, documented number — Telegram's FAQ states you can "Send and receive files of any type, up to 2 GB in size each (or 4 GB with Premium)." The speed benefit is real on Telegram's side and openly hedged everywhere else. If you want the full picture on the caps, see the Telegram file size limit breakdown.
The fastest fix: upload fewer bytes
This sounds glib, but it is the only lever you fully control. Telegram's throttle threshold, your ISP's upstream bandwidth and the server's queue are all outside your hands; the size of the file is not.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab — the video is read from disk, re-encoded locally, and handed back. Nothing is uploaded to a compression server, which matters here specifically: an online compressor would make you upload the large file over the same slow connection before you got the small one back, which defeats the purpose entirely.
If you would rather drive the settings yourself instead of accepting a preset, the general-purpose video compressor exposes the same encoder with the knobs visible. Bitrate and resolution do the overwhelming majority of the work.
Other causes, in order of likelihood
1. The file is simply big and your upstream is not. A 2GB file — the free-account ceiling — is a long transfer on any consumer uplink, with no throttling involved. This is the single most common answer.
2. You are posting to a big channel, and the delay is transcoding, not uploading. This one produces a very specific symptom: the progress bar completes, and then the message does not appear. Telegram documents exactly why. "When sending videos to big channels, Telegram will automatically convert them, generating multiple versions in multiple qualities and formats," and because "server-side processing takes some time, videos sent to big channels will not be sent immediately after invoking sendMedia/sendMultiMedia: instead, they will be added to the schedule queue similarly to scheduled messages », with schedule date equal to the approximated server-side conversion date."
Telegram does not define how large a channel has to be to count as "big," nor which quality tiers it generates, so there is no threshold to check — but if the stall happens after the bar fills, and only in channels, this is what you are looking at.
3. The client is chunking inefficiently. Uploads are split into parts, and Telegram notes that "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 docs also require that "All parts must have the same size (part_size)." Telegram does not document which part_size any particular client actually uses, so check the official API documentation if you are building against it.
4. You are hitting a Bot API limit rather than a speed limit. Bots live under an entirely separate set of numbers from user accounts, and a bot that appears to be uploading slowly is often just failing against a cap. If that is your situation, start with the Telegram bot file size limit rundown rather than troubleshooting bandwidth.
5. Your device is out of room to cache. Telegram is cloud-based and keeps a local cache; the FAQ's own remedy is "Settings > Data and Storage > Storage Usage> Clear cache to free up space on your device without logging out." This will not raise your transfer rate.
How to tell it worked
Check the file size on disk before you retry — that number, divided by your measured upstream speed, is roughly the floor on how long the transfer can take. If a compressed file that should take one minute still takes ten, the bottleneck is your connection or the far end, not the file.
And if the progress bar reaches 100% quickly but the message takes minutes to appear in a large channel, stop optimising the upload. That is the conversion queue described above, and compressing further will not shorten it.
FAQ
Why is my Telegram upload so slow? Most often because the file is large relative to your upstream bandwidth. Telegram's documented free-account throttle only applies once "the user has uploaded tens of gigabytes or more," so a single big video on a fresh account is not being throttled. Shrink the file first, then look at your connection.
Does Telegram Premium make uploads faster? It lifts Telegram's own speed limits on your account. Telegram's Premium FAQ explicitly warns that if your speed does not improve, "you may be facing other limits caused by your hardware, internet provider, etc." Buy it for the 4GB upload cap; treat the speed gain as a possibility, not a promise.
Is there a daily upload limit on Telegram? Telegram's documentation does not publish a daily quota. The only figure it gives is the throttle threshold of "tens of gigabytes or more" of uploaded data. Any specific "X GB per day" number you find elsewhere is not from Telegram — check the official documentation before relying on it.
My upload finished but the video never posted. What happened? If it was a large channel, the video was queued for server-side conversion. Telegram states these messages are "added to the schedule queue similarly to scheduled messages" with a send date matching the estimated conversion time. Nothing is broken; it posts when processing completes.
Is it faster to upload on desktop than on my phone? Telegram's FAQ gives one set of limits without distinguishing between platforms, so there is no official basis for claiming one client is capped differently. Any real difference you observe is more likely your network — a wired or Wi-Fi uplink versus mobile data — than the app.
More on where Telegram's ceilings sit and what to do when you hit one: the limits reference hub, the guide to what to do when a Telegram video is too large, and all Clapr tools, which run locally in your browser.
Quotes cited from Telegram's official FAQ, Premium FAQ, and core.telegram.org API documentation, checked 16 September 2026. Telegram changes these values through server-side configuration — verify against the official documentation before relying on them.
