A Telegram video message and a video file are two different media types, not two sizes of the same thing. The round clip that arrives in a chat as a circle is not a regular video that has been cropped small — in Telegram's own API it carries a dedicated flag, has its own send method, and measures its size with a parameter of its own.
So if you are trying to "make a normal video round," you are not fighting a UI setting. You are looking at a different object.
The proof is in the protocol
Telegram documents its media layer publicly, and the distinction shows up at the lowest level. Every video carries an attribute called documentAttributeVideo, whose parameter table lists, among others:
round_message | flags.0?true | Whether this is a round video
supports_streaming | flags.1?true | Whether the video supports streaming
nosound | flags.3?true | Whether the specified document is a video file with no audio tracksround_message is a standalone boolean flag, sitting beside streaming support and audio presence. It is not a crop rectangle, an aspect ratio, or a display preference: a video either has that bit set or it does not. Roundness is a declared property of the media, decided at send time.
What the Bot API says a video message is
The Bot API spells the definition out in plain English. sendVideoNote is described verbatim as:
"Use this method to send a rounded square MPEG4 video of up to 1 minute long. On success, the sent Message is returned."
Three constraints are packed into that one sentence:
- Rounded square — the shape is part of the definition, not styling applied afterwards.
- MPEG4 — the container is named explicitly for this method.
- Up to 1 minute long — a duration ceiling written into the method description itself.
One limit on that third point: this is the Bot API's wording. Telegram's help centre publishes no maximum recording length for round video messages in the regular app, so do not read "1 minute" as a documented phone-app limit — check the official documentation instead.
The length parameter gives it away
One detail settles the argument: how sendVideoNote describes its size parameter. Regular videos take a width and a height. A video note takes a single parameter called length, documented as:
"Video width and height, i.e. diameter of the video message"
Diameter. Telegram is describing a circle in its own API reference, collapsing two dimensions into one number because for this media type there is only ever one number to give.
A second restriction shows how special-cased video notes are. For the video_note parameter you may pass a file_id or upload a new file with multipart/form-data — and then:
"Sending video notes by a URL is currently unsupported."
On the receiving side, the Message object has a dedicated field for them — "Optional. Message is a video note, information about the video message" — separate from the field a normal video arrives in. Different flag, different send method, different size parameter, different field on the message.
What a "video file" is, by comparison
A regular video takes a different path. The Bot API's sendVideo describes it like this:
"Use this method to send video files, Telegram clients support MPEG4 videos (other formats may be sent as Document). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future."
Two things to pull out of that.
First, the 50 MB is a bot limit, and Telegram flags it as changeable — keep the "this limit may be changed in the future" caveat attached whenever you quote it. Human accounts run on different numbers: Telegram's FAQ says you can share files "of any type, up to 2 GB in size each (or 4 GB with Premium)."
Second, and more useful day to day: "Telegram clients support MPEG4 videos (other formats may be sent as Document)." That single parenthetical is the official explanation for a .mkv or an .avi that uploads fine and then arrives as a Document rather than as video. Note the hedge in Telegram's own wording, though: may be sent as a Document. It is not published as a whitelist or a blacklist.
A regular video can also declare that it streams: sendVideo exposes supports_streaming, documented as "Pass True if the uploaded video is suitable for streaming."
The third path: sending as a file on purpose
The third way a video can reach a chat is a protocol-level path, not a UI quirk. The inputMediaUploadedDocument constructor has a flag documented as:
"force_file | flags.4?true | Force the media file to be uploaded as document"
That is "send as file" made explicit. Note what Telegram does not document: nothing in the help centre says what this flag does to bitrate, resolution or quality. The widely repeated claim that "send as file preserves 100% of the original quality" has no official source, so treat it as folklore.
A neighbouring flag on the same constructor explains a genuinely confusing behaviour:
"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)"
It documents a default most people never figure out: a video with no audio track gets the animated attribute, not the plain video treatment. That is why a silent screen recording or an exported timelapse can end up in the animation category rather than the video one. Telegram's sendAnimation method confirms that category exists: it handles "animation files (GIF or H.264/MPEG-4 AVC video without sound)."
So which one should you send?
- Use a video message (round note) for something short and conversational — a reaction, a spoken answer where your face matters. It is a chat gesture, not a delivery format.
- Use a regular video for anything someone will actually watch: it can be marked streamable, it keeps its real width and height, and on a normal account it can be far larger than a one-minute note.
- Use send-as-file if you want the
force_filepath — remembering that Telegram documents nothing about its effect on quality.
If your problem is the second one — you sent a video and it showed up as a document instead of a player — look at the container before the settings. Clients support MPEG4 and "other formats may be sent as Document," so converting to MP4 is the first thing to try:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
It runs inside your browser tab: the file is read from disk, converted locally, and handed back, with nothing uploaded to a server. The rest of the toolkit is at all Clapr tools, and if the problem is size rather than format, use compress video.
For the full picture, see Telegram's supported video formats. The same "arrived as a file instead of a player" pattern shows up on other chat apps — see Slack MOV file not playing.
What Telegram does not document
Telegram publishes no maximum recording length for round video messages in the regular apps (only the Bot API's "up to 1 minute long"), no compression parameters for normal sending — no target bitrate, resolution ceiling or codec — and no statement on whether a video sent as a document gets re-encoded. For any of these, check the official documentation rather than a forum number.
FAQ
How do I send a round video message on Telegram?
It is a distinct media type with its own send method — sendVideoNote in the Bot API, described as "a rounded square MPEG4 video of up to 1 minute long." Roundness is a flag (round_message) set on the media when it is sent, not a display option applied afterwards.
Why did my video send as a file instead of playing? Most likely the format. Telegram's documentation states that "Telegram clients support MPEG4 videos (other formats may be sent as Document)." Note the word may — this is not published as a whitelist or a blacklist, so it is not a guarantee either way. Converting to MP4 is the usual first fix.
Why does my video loop like a GIF with no sound?
Most likely because it has no audio track. Telegram's nosound_video flag exists precisely to override this: without it, "the documentAttributeAnimated attribute" is set even for videos without audio, so a soundless clip is handled as an animation rather than as a video. Telegram does not document how each client then renders that category.
Is a video message lower quality than a video file?
Telegram does not publish the encoding parameters for either path, so there is no sourced answer on bitrate or resolution. What is documented is structural: a video note is a rounded square MPEG4 sized by a single length value Telegram calls the "diameter of the video message," while a regular video keeps a real width and height and can declare streaming support.
Can a bot send a video note from a URL?
No. The sendVideoNote documentation is explicit: "Sending video notes by a URL is currently unsupported." Pass a file_id for something already on Telegram's servers, or upload the file with multipart/form-data.
API behaviour cited from Telegram's official Bot API reference, the documentAttributeVideo / inputMediaUploadedDocument constructor pages and telegram.org's FAQ, checked 16 September 2026. Telegram revises these documents — verify against the official pages before relying on a specific number.
