• Telegram has no built-in auto-forward, so it takes a bot, a tool on your own account, or forwarding by hand.
• Tools that edit posts copy them rather than forward them, so the copies carry no “Forwarded from” label: credit the source yourself.
• Skip chats with content protection, get permission for everything else, and pace every destination.

Telegram has no built-in auto-forward as of 30 September 2026, so you need automation. That is how to auto-forward Telegram messages today: a bot that the channel’s admin has added, or a tool running on your own account, copies each new post to your channels and groups. Forward only what you own or have permission to share.

Forward or copy: what Telegram does by itself

Telegram gives you two ways to move a post from one chat to another, and your readers see the difference. A forward keeps a link to the original: the post shows where it came from, and Telegram’s FAQ says a channel post’s view counter also counts views of its forwarded copies. A copy is a new message. The Bot API describes its copyMessage method as analogous to forwarding, “but the copied message doesn’t have a link to the original message.”

When you forward by hand, you can drop the label. Since August 2021, Telegram’s forward preview has let you hide the sender’s name or the captions on media before you send (Telegram blog). The API has the same switch: its drop_author flag forwards messages “without quoting the original author” (messages.forwardMessages).

Forwarding and copying compared

Many auto-forwarding tools copy rather than forward, because only a copy can be edited on the way. That puts attribution on you: if the source deserves credit, and it usually does, add the credit yourself.

How to auto-forward Telegram messages: the three ways

Telegram’s apps let you forward a post by hand or schedule one of your own, but none of the announcements on the Telegram blog from January to August 2026 adds a rule that reposts new posts automatically. Chat Automation, added on 7 May 2026, lets a bot reply to messages on your behalf (Telegram blog), but it doesn’t repost a channel’s posts. So people take one of three routes.

1. Forward by hand. Native, free and always within the rules, but someone has to do it for every post. It suits a channel that shares a few posts a day.
2. A bot. You create a bot with Telegram’s Bot API. In a channel it can only be an admin, so the source’s owner has to add it; in groups it can be a member, and there it posts under its own name.
3. Your own account, through the Telegram API. A tool signs in as your user account, sometimes called a userbot, reads what that account can read and posts wherever that account may post.

Before you pick one, check whether you need copies at all. If the aim is only to help readers find your other chats, a Community may be enough: since July 2026, several groups, channels and bots can be linked into one, and members “can see its other chats and join them instantly” (Telegram blog). And if you want your own posts to go out at set times rather than follow another channel, a scheduler fits better: see how to schedule messages on Telegram.

Bots or user accounts: what each can read and post

The route decides what the automation can see. Telegram’s bot FAQ says every bot receives “all messages from channels where they are a member”, but a bot can join a channel only as an admin: the API’s own error list says “Bots can only be admins in channels” (channels.inviteToChannel). So the bot route works for sources you run, or whose admin agrees to add your bot. In groups, privacy mode is on by default, so a bot receives mainly the commands and replies meant for it, unless it was added as an admin or its privacy mode is turned off.

A user-account tool sees whatever your account sees: the channels it has joined and the groups it is in. That makes it the practical route when you don’t control the source, which is exactly where you most need permission. Telegram’s page on obtaining an api_id warns that using the API “for flooding, spamming, faking subscriber and view counters of channels” gets an account “banned forever”, and that accounts that sign in through unofficial API clients are “automatically put under observation”. The Telegram API Terms of Service also forbid “making actions on behalf of the user without the user’s knowledge and consent”.

A user-account tool holds a session that can act as you, whether it runs on your own device or on someone else’s server. Use one you trust, keep Two-Step Verification on, and end sessions you no longer use under Settings > Devices, or Privacy and Security > Active Sessions, as Telegram’s FAQ describes.

Bots and user accounts compared

Neither route is safer in itself: what decides whether you stay within Telegram’s rules is what you forward, from whom, where to and how often.

Step by step: set up an auto-forward from a source channel

The steps are much the same in any tool that copies posts. Take them in this order.

1. Confirm you may repost. Use a source you run, or get the owner’s permission in writing. Check that the source doesn’t have content protection turned on.
2. Choose the reading account. Pick the bot or account that is in the source and can post in every destination. In a channel, that means admin rights that include posting.
3. Add the destinations. List each channel or group by its @username or chat ID. Make sure the account isn’t restricted there, and note any group with slow mode on.
4. Decide which posts qualify. Add keywords to include and to exclude, and choose the media types that go through.
5. Decide what changes. Rewrite or remove links, adjust mentions and hashtags, handle captions, and add a header or a footer with a credit line.
6. Set the pace. Give destinations a delay and an hourly cap, and keep the rule to the hours your readers are awake.
7. Test, then watch the log. Run the rule on a sample message, turn it on, and read the log after the first real posts arrive.

Filters and edits: keywords, media types, links and captions

Filters decide which posts go through; edits decide how they look when they arrive. A few patterns cover most needs.

Keyword, media and time filters

• Include keywords to pass only posts that mention a topic, such as the pairs a signal channel covers.
• Exclude keywords to drop ads and promotions, for example posts that contain “promo”.
• Media types to pass only text, photos, videos or documents.
• Active hours to forward only on certain days and at certain times, in the timezone you choose.

A filtered rule is only as good as its log. Check what was filtered and why, and loosen a keyword that blocks posts you wanted.

Links, mentions and captions

Links are where most edits happen. You can keep them, remove them or replace them with your own, allow or block domains, and add utm_source and utm_medium so your web analytics can tell which channel sent a visit. Mentions and hashtags can be removed or swapped, and the captions on photos, videos and documents can be kept, removed, replaced or added to.

Keep the credit in. A copy has no “Forwarded from” label. If you remove the source’s @mention or links, a footer that names the source is the simplest way to credit it; on photos and videos, put the credit in the caption.

To group the channels you forward into, see Telegram Communities.

Why you can’t forward messages from some Telegram channels

When Telegram refuses a forward, the chat usually has content protection on. Group and channel owners can “restrict message forwarding from their chat, which also prevents screenshots and limits the ability to save media from posts”, a setting Telegram added in December 2021 as Restrict Saving Content (Telegram blog). In the API such a chat carries the noforwards flag, which the Channel object describes as “protected, thus does not allow forwarding messages from it”. Single messages can be protected too: the Message object has its own noforwards flag, for a message that is “protected and thus cannot be forwarded”.

One-to-one chats have their own version, Disable Sharing, added on 1 March 2026 for Premium users, and Secret Chats can’t be forwarded at all: see how Disable Sharing works in private chats.

Other errors look similar but have different causes; for the same codes on ordinary sends, see why a Telegram message isn’t sending. The descriptions below are Telegram’s own, from the messages.forwardMessages and messages.sendMedia pages.

Errors when forwarding or copying

Protected means no. Content protection is the owner saying no. Whatever the method, forward or copy, don’t repost a protected post: a responsible tool reads the protection flags itself and skips it. If the channel is public, share a link to the post instead, or ask the owner.

Delays, hourly caps and rate limits across many destinations

Telegram publishes sending limits for bots only: in a single chat, “avoid sending more than one message per second”, and in a group bots can’t send “more than 20 messages per minute” (bot FAQ). For user accounts it publishes no numbers. When an account sends too fast, Telegram answers with a flood wait, FLOOD_WAIT_X, meaning “a wait of X seconds is required” (API errors). For what to do when one arrives, see what a Telegram flood wait means and how to handle it.

One source post fanned out to ten destinations is ten sends from one account at the same moment. Three settings keep that calm:

• A delay per destination, with a little random extra, so your channels don’t all post in the same second.
• An hourly cap per destination, so a burst in the source doesn’t become a burst everywhere.
• A pace for the whole account, with daily and hourly caps and a minimum gap between messages, shared by everything that account sends.

Pacing makes flood waits rarer, not impossible, because Telegram doesn’t publish the thresholds. Treat a flood wait as a sign to send less, never as a reason to retry harder.

Permission, attribution and copyright when you repost

Auto-forwarding is only as legitimate as the content it moves. The safe pattern is short:

• Forward from channels you run, or from sources that have agreed in writing.
• Skip anything with content protection on, even where a tool could copy it.
• Credit the source in a header or a footer, because copies carry no “Forwarded from” label.
• Don’t use forwarding to fill channels with other people’s work, or to post into groups that didn’t ask for it.

Copyright applies on Telegram too. Its FAQ explains how a copyright owner, or an agent acting for them, can complain about a public channel, bot or group that infringes their copyright. If you also cross-post to Facebook, Meta has its own rules on reposted content; the guide to Facebook’s unoriginal content and reposting rules covers them.

FAQ

Can a bot forward from a channel I don’t own?

Only if that channel’s admin adds it. Telegram lets a bot join a channel only as an admin, and its API lists the error “Bots can only be admins in channels”, so you can’t point a bot at someone else’s channel by yourself. A user-account tool can read any channel the account has joined, but reading isn’t permission: ask the owner first and agree how you will credit them.

What does “You can’t forward messages from a protected chat” mean?

It is Telegram’s description of the CHAT_FORWARDS_RESTRICTED error. The source group or channel has content protection on, which its owner sets under Restrict Saving Content, or the message itself is protected. The answer isn’t technical: ask the owner for the content another way, or share a link to the post if the channel is public.

Can auto-forwarded posts drop the “Forwarded from” label?

A copy never has one, because it is a new message. When you forward by hand, you can hide the sender’s name in the forward preview, and the API’s drop_author flag does the same. Either way the credit disappears, so add a footer that names the source whenever you repost someone else’s post with their permission.

How quickly does an auto-forward go out?

That depends on the tool. A bot receives new channel posts as updates, and a user-account tool either listens for new posts or checks the source at intervals. Any delay you set for a destination comes on top, and so does a flood wait if Telegram asks the account to pause. Test with a sample post before you rely on the timing.

Can I auto-forward from a group as well as a channel?

Yes, if the tool reads groups. A user-account tool sees every message in a group the account belongs to, members’ messages included, so get the group’s agreement and add keyword filters before you copy what members write. A bot sees mainly commands and replies in a group unless it is an admin or its privacy mode is off.

Sources

• Telegram API: messages.forwardMessages (accessed 2026-09-30)
• Telegram API: messages.sendMedia (accessed 2026-09-30)
• Telegram API: the Channel constructor (accessed 2026-09-30)
• Telegram API: the Message constructor (accessed 2026-09-30)
• Telegram API: channels.inviteToChannel (USER_BOT: Bots can only be admins in channels) (accessed 2026-09-30)
• Telegram API Terms of Service (accessed 2026-09-30)
• Telegram API: error handling (accessed 2026-09-30)
• Telegram API: obtaining api_id, and the rules on abuse (accessed 2026-09-30)
• Telegram Bot API: forwardMessage and copyMessage (accessed 2026-09-30)
• Telegram bots FAQ: what bots receive, and broadcasting limits (accessed 2026-09-30)
• Telegram bot features: privacy mode (accessed 2026-09-30)
• Telegram FAQ: channels, Secret Chats, sessions and copyright (accessed 2026-09-30)
• Telegram blog: Protected Content (7 December 2021) (accessed 2026-09-30)
• Telegram blog: Flexible Forwarding (31 August 2021) (accessed 2026-09-30)
• Telegram blog: Disable Sharing (1 March 2026) (accessed 2026-09-30)
• Telegram blog: Communities (14 July 2026) (accessed 2026-09-30)
• Telegram blog: Chat Automation (7 May 2026) (accessed 2026-09-30)
• Telegram blog: all announcements (accessed 2026-09-30)

Originally published on the Dripl.ai blog.

Disclosure: this guide was generated with AI and checked against the sources listed above.