You tap forward on a post, and nothing happens. No forward icon, no copy option, and selecting the text does nothing either. The channel owner has turned on "restrict saving content", and Telegram is doing exactly what they asked.
This post explains what that setting really blocks, why the usual workarounds fail, and how to legitimately republish posts from a source like that into a channel you run.
It's a channel-level switch in Telegram (Channel settings → Administrators → Restrict saving content). When it's on, Telegram's clients hide forwarding, copying, saving media and screenshots on that content.
Two things are worth being precise about:
That second point is the important one, because it tells you what's actually possible.
Adding a bot to the channel. Bots can only read a channel they've been added to, and you usually can't add a bot to a channel you don't own. Even where you can, Bot API forwarding respects the same restriction.
Screenshot-and-repost. It works for one post. It does not work for forty posts a day, and you lose all the links and formatting.
A "forward bot" you give your login to over chat. Please don't. Anything that asks you to paste a login code into a Telegram chat is asking you to hand over your account, and the code arrives in the same app the attacker is talking to you in. Legitimate tools take your phone number and login code over HTTPS in a web form or Mini App, never in a chat message.
Genuinely the first thing to try, and people skip it. Many owners are happy to be mirrored if they're credited, and some will simply add you as an admin, which sidesteps the whole problem. It costs one message.
This is the mechanism every working tool uses. Instead of asking Telegram to forward message 4,812 — which the restriction blocks — you read the message with an account that has access, then publish its text and media as a new post. From Telegram's point of view your channel is publishing an original message that happens to contain the same content.
Practically this needs:
The trade-off is that a copied post doesn't carry a "forwarded from" label. If you want attribution, you have to add it yourself — a header line, or a footer crediting the source. Some tools do that automatically.
Running this yourself means a server, a Telegram API app, a session file to keep alive, and something to restart it when Telegram flood-limits you. tgcf is a good open-source option if that sounds like a fun weekend. Otherwise a hosted service does the same thing without the maintenance — EzForwardBot is ours, and copying from restricted sources works on the free plan.
Being technically able to republish something is not the same as being allowed to.
The uses that are fine are the ordinary ones: mirroring your own channels into each other, consolidating channels you run, republishing a feed you've licensed or been given permission to carry, or building a private archive of something you have rights to. That's what our acceptable-use terms allow, and we do act on reports.
For the record, end to end:
New posts copy across from that point on, usually within a second or two. The free plan covers four connections with instant delivery and no card, and copying from restricted sources isn't paywalled — see pricing.