When Telegram shows your video as a file row instead of a player, it is telling you it did not classify that file as a video it renders inline. The upload itself almost never failed; something about the file pushed it into a different category on Telegram's side.
Two separate reasons cause that, and only one is the container-and-codec story every other article tells you. The second sits in Telegram's protocol reference and is almost never quoted: a video with no audio track is not handled as a video at all.
What "sent as file" actually means
Telegram carries anything: the FAQ says "files of any type (doc, zip, mp3, etc)", and the per-file ceiling is roomy — Telegram's file size limit covers the figures and who they apply to. Getting the bytes up there is rarely the problem.
Rendering is a separate decision made after the upload. The Bot API documentation for sendVideo states the rule in one sentence:
"Telegram clients support MPEG4 videos (other formats may be sent as Document)."
That is the official explanation for the most common version of this complaint. A .mkv or an .avi uploads fine, then lands in the chat as a grey row with a download button. Nothing errored; Telegram just did not treat the file as a video.
Read the hedge in the original carefully: "may be sent as Document". Telegram publishes no whitelist of what renders inline. So the correct conclusion is not "format X is banned" — it is "MPEG4 is the target Telegram names, aim at that."
There is also a deliberate version of this behaviour. Telegram's inputMediaUploadedDocument constructor carries a flag whose entire job is to override the normal path, defined verbatim as:
"force_file | flags.4?true | Force the media file to be uploaded as document"
So "send as file" is a real route at the protocol level: a video that arrived as a document may simply have been sent that way on purpose.
One caveat: Telegram's user-facing help center says nothing about a "send as file" option, and publishes no compression parameters — no target bitrate, no resolution ceiling, no codec. Any article promising that "send as file preserves 100% of the original quality" is inventing it: the flag is documented, its effect on your picture is not. Check the official documentation.
The fastest fix: re-encode to MP4
Since classification happens on the file you hand over, hand over one matching the description Telegram gives: an MPEG4 video — in practice, MP4 with H.264 inside.
On the codec side, the documentAttributeVideo constructor's video_codec field names three values — "h264", "h265", or "av1" — but introduces them with "i.e.", as examples rather than a closed list, so "Telegram only supports those three" is not what the page says.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab: the file is re-encoded locally and handed straight back, so nothing goes to a third-party server. If your source is a WebM, WebM to MP4 is the same operation with a different input; if the clip also needs to get smaller, start from the video compressor instead.
The cause nobody explains: a silent video is not a video
This is the part that makes people think their MP4 "turned into a GIF".
The same constructor has a second flag whose official definition gives away the mechanism:
"nosound_video | flags.3?true | 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)"
Unpack that. The flag exists to suppress a default: by default, a video without an audio track gets the animated attribute — Telegram's animation class, the one GIFs live in. To have a silent clip treated as an ordinary video, the sender has to say so explicitly.
The Bot API corroborates it, defining the animation category to include silent video outright:
"Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound)."
And the video attribute itself carries a matching marker: "nosound | flags.3?true | Whether the specified document is a video file with no audio tracks".
So the absence of an audio track is not a cosmetic detail on Telegram — it is a routing decision. Files that routinely arrive with no audio track include screen recordings captured with audio disabled, timelapse and slow-motion exports, and anything run through a command line with audio stripped.
If one of those shows up as an animation rather than in the video player, you now know why. What Telegram's clients actually do with an animation — autoplay, loop, mute, no scrub bar — is client behaviour the official documentation does not spell out, so judge that by what you see rather than by anything claimed as spec.
The practical fix is to give the file an audio track. The default Telegram documents applies to "videos without audio"; a clip that carries an audio track is not the case that definition describes.
Other causes, in order of likelihood
It plays, but you cannot scrub until it fully downloads. Streaming is its own flag, not an automatic property of being a video. documentAttributeVideo has "supports_streaming | flags.1?true | Whether the video supports streaming", and the Bot API's matching parameter reads "Pass True if the uploaded video is suitable for streaming". What a client does with a file that carries no such flag is not something Telegram's documentation spells out — check the official documentation.
You posted to a large channel and nothing appeared. Telegram's API docs: "When sending videos to big channels, Telegram will automatically convert them, generating multiple versions in multiple qualities and formats". Because "server-side processing takes some time, videos sent to big channels will not be sent immediately" — the message is queued until conversion finishes. Telegram does not publish what counts as "big", nor which qualities it produces.
A bot is in the loop. Bots run on entirely different numbers — getFile states: "For the moment, bots can download files of up to 20MB in size." A bot can sit in a chat and be unable to fetch a video you watch perfectly well.
Someone tried to re-send it as a different type. The Bot API is blunt about this: "It is not possible to change the file type when resending by file_id." A file already on Telegram's servers as a document does not become a video by forwarding it.
You expected a round video message. Those are a distinct class, not a normal video that turned circular. The Bot API describes sendVideoNote as sending "a rounded square MPEG4 video of up to 1 minute long", sized by a single length value — "diameter of the video message" — and notes that "Sending video notes by a URL is currently unsupported." Those are the Bot API's constraints; Telegram does not publish the equivalent limits for recording one in the app.
How to tell it worked
Two checks, in order:
- The chat shows a player, not a grey row with a file name and a download arrow.
- There is a scrub bar you can drag before the whole file has arrived — the streaming flag doing its job.
If it still lands as a file after a clean MP4/H.264 re-encode with an audio track present, the remaining variable is on the sending side: a deliberate "send as file" choice, which no amount of re-exporting will undo.
FAQ
Why does Telegram send my video as a file instead of a video?
Because it did not classify the file as an MPEG4 video. Telegram's Bot API documentation says clients "support MPEG4 videos (other formats may be sent as Document)" — note the "may": there is no published whitelist, so a .mkv or an .avi can land as a plain document row rather than always doing so. Re-encoding to MP4 with H.264 aims at the format Telegram does name.
Why does my MP4 play like a GIF on Telegram?
Almost certainly because it has no audio track. Telegram's protocol docs define a nosound_video flag whose purpose is to send a file "as a video even if it doesn't have an audio track", and spell out what setting it prevents: "if set, the documentAttributeAnimated attribute will not be set even for videos without audio". The animation attribute is the default for silent video, in other words, and the flag is there to suppress it.
Does sending as a file keep the original quality?
Telegram's protocol confirms a force_file flag exists — "Force the media file to be uploaded as document" — but the official help center documents nothing about what normal sending does to quality, bitrate or resolution. Check the official documentation.
Why can I not skip ahead in a video someone sent me? Streaming is a separate flag the sender's client sets: Telegram's video attribute includes "supports_streaming" — "Whether the video supports streaming" — and the Bot API asks senders to "Pass True if the uploaded video is suitable for streaming". Telegram does not document what clients do when that flag is absent.
Why is my video stuck uploading to my channel? If it is a big channel, it may not be stuck: Telegram converts videos for big channels server-side and says they "will not be sent immediately" — queued until processing finishes. Telegram does not define how big a "big channel" is.
Same symptom on another app? See Slack MOV files not playing and Discord video not playing, browse the rest of the fix guides, or go straight to all Clapr tools — every one of them runs in your browser, so your video never leaves your device.
Quotes cited from Telegram's FAQ, Bot API and MTProto documentation, checked 16 September 2026. Telegram changes client behaviour without notice — verify against the official pages before relying on them.
