How to Send Large Files on Telegram

upload_file The ceiling, and the thing it applies to

The limit is per file, not per account. Two gigabytes for a free account and four with a subscription, with no cap on how many you send or how long they stay. A conversation holding several hundred gigabytes of material is unremarkable and costs nobody anything.

Two properties of that are worth stating plainly because they change how the feature is used.

The recipient does not need a subscription. A four-gigabyte file sent by a subscriber downloads perfectly well for somebody who has never paid for anything. The limit governs uploading, not access.

The chat is the storage. Once a file is in a conversation it stays there, retrievable from any device you sign in on, without occupying space on your phone — the cache from Step 043 holds a temporary copy at most. You do not need to keep a local copy of something you have sent, which is a genuine change of habit for anybody used to attachments.

rule Four routes, and what actually arrives

The choice made at the moment of attaching decides what the other person receives, and it cannot be revisited afterwards.

The first two rows are the decision people get wrong most often, and the reason is that the compressed route looks better in the chat. A photograph sent as a photograph appears immediately and fills the bubble; sent as a file it is a grey rectangle with a name. The grey rectangle is the one that still contains the detail, and Step 011 is the whole argument for when that matters — screenshots, scans, documents, anything with text in the image.

group What a large file costs everybody else

This is the part the subject usually leaves out. Sending two gigabytes into a group of four hundred people is not a decision about your connection. It is a decision made on behalf of four hundred phones.

Whether it lands on their device without being asked for depends on their auto-download settings from Step 044, which most people have never opened. For those who have not, a large file in a busy group can arrive over mobile data while they are on a train.

Three habits follow from that, and none of them are onerous. Say what it is — a filename and a line of context lets somebody decide before tapping. Prefer a link for the very large, since a link costs nothing until it is wanted. And use a direct message when only one person needs it, which sounds obvious and is routinely ignored in work groups.

The same logic applies to channels, more sharply, because the audience is larger and cannot reply to object. A channel that regularly posts multi-gigabyte files is asking a great deal of subscribers in countries where data is expensive, and the cost is invisible to the person posting.

sync_alt When a transfer stops part way

Large transfers fail in ordinary ways and there is a specific place to look, which almost nobody knows about.

When anything is downloading, an indicator appears near the search bar at the top of the chat list. It opens a list of everything in flight, where each item can be paused, resumed, prioritised or cancelled. If something appears to have stalled, this is where it is, and a pause followed by a resume usually restarts it.

For uploads, the progress ring on the message itself is the control — cancelling there removes the pending message. An upload interrupted by the connection dropping does not need intervention; it continues when you are back on a network.

One case behaves differently and is worth knowing: if the sending device runs out of storage or the app is closed by the operating system mid-upload, the transfer may need starting again. Sending something very large from a phone with a nearly full drive is the scenario where this happens, and it is another argument for doing the biggest transfers from a computer.

touch_app Try it now — five minutes

Four steps. The second is the one that changes what you send from now on.

1. Find the download list Start something large downloading and look near the search bar. Pause it, resume it, cancel it. Knowing this exists turns a stuck file from a mystery into a button.
2. Send the same screenshot twice, both ways Once as a photograph, once as a file. Open both and look at the small text. This comparison is more convincing than any description of compression.
3. Move one large file using Saved Messages From a computer to your phone, or the reverse. Step 046's transfer route is faster than everything else available on either device.
4. Give one file a proper name before sending it Search only reads names, never contents, as Step 045 explains. A file called by its date and subject is findable in two years; one called by a camera's numbering is not.

play_circle Watching before it has arrived

Large media does not have to finish downloading before it is usable, and this changes the calculation about what is reasonable to send.

A video sent as a video begins playing almost immediately and continues fetching while you watch, in the way a streaming service does. A two-hour recording is watchable on a phone without waiting for two hours of file to land, and without that file being kept once you have finished with it. Audio behaves the same way, with a player that follows you around the app so a long recording continues while you read something else.

A video sent as a file does not do this. It is a document as far as the app is concerned, so it downloads completely and then opens in whatever your device uses for video. That is the right choice when somebody needs the original to edit or archive, and the wrong one when they only need to watch it — which is the case more often than people assume.

So the compression decision from the table above has a second axis that nobody mentions. Sending as a video is not only smaller; it is watchable at once. Sending as a file is not only larger; it makes the recipient wait for all of it before seeing any of it. For a long recording posted to a group, that difference decides whether anybody watches it.

help Common questions at this stage