How Telegram Bots Work — Explained Clearly

Most people who use Telegram bots only half-understand what they are or what limits they have. That gap creates confusion when a specific bot doesn't do what you expected — like TubeDisk's bot, which accepts forwarded videos but ignores YouTube URLs. This guide explains how Telegram bots actually work, what they can and cannot do by design, and why the constraints exist.

What is a Telegram bot, really?

A Telegram bot is just a regular account that's run by a computer program instead of a person. To Telegram's servers, it looks like a user: it has a username (with a bot suffix), it can send and receive messages, it can be added to groups. What's different is that a server somewhere is reading the bot's incoming messages and responding programmatically.

The Telegram side of this is called the Bot API — a set of HTTP endpoints that lets external software receive messages from Telegram, send replies, and a handful of other actions. Anyone can register a bot through @BotFather; the infrastructure of running it (the actual server reading messages and deciding what to do) is up to the bot operator.

What bots can do

Receive direct messages from users who message them.
Receive group messages in groups where they're added — but only mentioned messages by default, unless the bot is configured for "privacy mode off" (which most bots aren't).
Send messages to users who have first interacted with the bot.
Receive forwarded files when users forward a message to the bot. The bot can download these files via the Bot API.
Handle inline queries (the @botname-prefix search bots).
Send buttons and keyboards that users can click for predefined actions.

What bots cannot do

Read past messages in a channel they're not in. Even adding a bot as a channel admin gives no access to historical messages.
Read private chats they're not part of. Including users' chats with each other.
Read secret chats at all. Secret chats are client-encrypted end-to-end and never touch Telegram's servers in decrypted form.
Forward content from channels with "restricted forwarding". Telegram blocks this at the protocol level.
Take actions on a user's behalf in another chat. A bot can only act in its own conversations, not impersonate the user elsewhere.

The 20 MB / 2 GB file-size split

Standard Telegram Bot API has a 20 MB limit per file. This is a firm limit imposed by Telegram for the public API. A bot using this standard endpoint cannot receive or send files larger than 20 MB.

There's a workaround: Telegram open-sources its Bot API server code, so any operator can run their own instance instead of using Telegram's hosted one. A self-hosted Bot API server lifts the file limit to ~2 GB per file (the same limit as regular Telegram users have). TubeDisk runs a self-hosted Bot API server for this reason — which is why our bot can accept the typical large video files that get shared in chats.

Why TubeDisk's bot doesn't accept URLs

This is the question we get most often: "I sent the bot a YouTube link and nothing happened. Why?" The answer is structural, not a missing feature:

The TubeDisk bot is a Telegram bot — it can receive files forwarded to it. That's a Telegram-native action with clear semantics.
For URL downloads (YouTube, TikTok, Instagram), TubeDisk has a web dashboard. Pasting a URL there fires up our fetch pipeline, which handles source-specific quirks (DASH muxing for YouTube, signature decoding, anti-bot headers).
Mixing the two — accepting URLs inside the bot — would mean duplicating the entire web-dashboard URL-handling code into the bot. Doable in principle, but it introduces a new attack surface (rate limiting, abuse detection have to be redone for the bot context), and most importantly, it confuses users about which channel does what.

We chose clarity: the bot is for forwarded files (Telegram-native). The web dashboard is for URLs (everything else). Both write to the same cloud destination you've configured.

How to safely use any Telegram bot

Verify the username. Bots can impersonate each other with similar usernames. The official TubeDisk bot has exactly one username — verify it from our website.
Don't share secrets via bots. Anything you send to a bot is readable by the bot's operator. Treat it like email to that operator, not a secret-chat conversation.
Don't grant admin rights to channels casually. An admin-bot has more capabilities than a regular-member bot. Only grant for bots you actually need to manage your channel.
Periodically audit your authorized bots. Telegram's settings list every bot you've started a chat with — remove any you no longer use.

Common Telegram-bot misconceptions

"A bot in my group can read everything we say"

By default, no. Bots in groups operate in "privacy mode" — they only see messages that mention them (e.g., @botname hello) or replies to their messages. Privacy mode can be turned off by the bot operator, but that's typically done only for moderation bots, and is visible in the bot's settings.

"I can use a bot to read messages from a channel I'm not in"

No. A bot can only read messages from chats it's actively participating in. Even if you're not in the channel, the bot needs to be — and even then, only messages posted after the bot joined.

"Telegram bots can scan all my private chats"

No. Bots only see their own conversations with you and any groups they're part of. They have zero visibility into your other private chats, unless you forward content to them.

"My bot got banned, what does that mean?"

Telegram revoked the bot's API access — usually because it violated the platform's bot policy (excessive spam, illegal content distribution, abuse). The bot's token stops working; it can't receive or send messages. Bot bans are usually permanent.

FAQ

Why does TubeDisk's bot send back a confirmation message every time?

For two reasons: so you know the file was actually received and saved (Telegram doesn't tell you that automatically), and so the saved file's URL is visible in your chat history with the bot for easy reference later.

Can the bot save messages to my Google Drive automatically when posted to a channel I admin?

No. As explained above, bots can't read channel history or proactively watch for new posts in channels they're not in. The practical limit is "forward what you want saved, the bot saves it".

What happens if I block the TubeDisk bot?

Blocking the bot stops it from messaging you. Your already-saved files remain in your cloud unaffected. To resume use, unblock it and send /start again.

Can multiple users share one TubeDisk account through the bot?

Each TubeDisk account links to one Telegram user. For team workflows, the recommended pattern is one account per team member, each pointed to the same shared cloud folder (Drive or Dropbox) through the destination settings.

Frequently asked questions

What's the difference between "forward-bot" and "URL-bot"?

URL bots accept a link in chat: you paste the YouTube URL, the bot returns the file. Forward bots accept message forwards from other channels: you forward a video message, the bot grabs the attached media. These are different pipelines - URL parsing uses yt-dlp on our server, forward uses Telegram's Bot API to download the original attachment. TubeDisk supports both: URL entry via web and Telegram, forward entry via Telegram only.

Is it safe to forward private links to a bot?

The link travels through Telegram's MTProto-encrypted connection. On our servers, we use the URL only to extract the video stream (yt-dlp), then push the file to your connected cloud and delete it from temporary storage. URL and metadata may appear in our access logs (standard for any web service) - retained 30 days, then auto-deleted. We do not sell or share URLs with third parties.

Telegram bot file size limits - how does TubeDisk handle them?

Telegram's standard Bot API caps outgoing files at 50 MB. For larger files, we use Telegram Local Bot API Server (our self-hosted instance) - that increases the cap to 2 GB. So TubeDisk can send 4K hour-long videos through the bot pipeline directly, while sandbox bots on free servers cannot. If the file exceeds 2 GB, we upload it to your cloud and send the link via the bot instead.

Why does the bot take 30-60 seconds to respond?

Response time has three components: 1) yt-dlp parsing video metadata (3-10s depending on source), 2) downloading from source to our server (depends on file size and source bandwidth), 3) transferring back to Telegram or uploading to your cloud. Paid tiers get priority queueing.

How Telegram Bots Actually Work — and Why TubeDisk's Bot Doesn't Download URLs