The symptom is simple: you open a channel in your browser, click Preview channel — and the page just blinks and stays put. No posts. Below is a short diagnostic that will tell you what's going on within a few minutes.
| Cause | How it shows up | Who can fix it |
|---|---|---|
| Channel restricted by Telegram moderation | Channel works in the app, but t.me/s/... is empty |
Telegram support only |
| Channel isn't public | Only an invite link exists, no t.me/name address |
Channel owner |
| Stale preview cache | It used to work, then stopped for no obvious reason | @WebpageBot |
| Temporary Telegram-side failure | Started suddenly and affects many channels at once | Nobody — it resolves itself |
A web preview is generated only for channels with an open address. Open the channel's info card and confirm it has a t.me/name link. If the only link is an invite of the form t.me/+AbCdEf, there will be no preview. That's normal behaviour, not a malfunction.
Open this manually:
https://telegram.me/s/channel_name
telegram.me mirrors t.me. If the feed loads there but not on the main address, the problem is most likely local: DNS, blocking, or browser cache. Try incognito mode and a different network.
Telegram caches link metadata. Send the channel link to @WebpageBot and it will re-fetch the preview. This is the fastest way to rule out caching as the cause.
If steps 1–3 changed nothing, a restriction on Telegram's side is the most likely scenario. The telltale sign: the channel works perfectly for subscribers, but its public web page is gone — and no notification was ever sent.
There's no way to verify this yourself. You have to ask support.
Where to write:
What to include so the review goes faster:
t.me/name);Ask the question directly: "Is this channel restricted, and has web preview been disabled for it?"
No. The channel works normally in the app. Only the public web page is affected.
Not a legitimate one — this is a server-side Telegram feature, not a channel setting. Workarounds such as third-party mirrors or scrapers aren't recommended: they violate the terms of service and don't address the underlying problem.
No guaranteed timeframe; it depends on the queue. If you hear nothing for several days, send a follow-up with the same text so it lands in a fresh queue.
With a cache issue or a temporary failure, yes — usually within a day. With a restriction, only after it's lifted.
The order of operations: channel publicness → alternate domain → @WebpageBot → support. Everything you can check yourself is covered by the first three steps. If those come back clean, the issue is almost certainly a restriction on Telegram's side, and only official support can resolve it.
© Copyright. All Rights Reserved.