Does Telegram Forwarding Keep Running When My Computer Is Off?

The short answer

Rules run on our servers, around the clock. Once a rule is saved you can close the browser, put the phone in a drawer, let the battery die, uninstall the Telegram app, get on a plane. Messages published in the source chat keep being delivered to the destination while all of that is true.

What has to stay valid

One thing, and only one: the Telegram login you created when you connected your account. It is what allows the chats you chose to be read. It does not depend on your device being awake, but it does end if it is revoked — and in practice it is revoked in one way: someone ends that session from Telegram, either from Settings and Devices or by tapping the button on the alert Telegram sends when the login is created.

That is worth knowing in advance, because the alert looks like a security warning. If you want to stop forwarding, disconnect from your dashboard instead: it stops cleanly, and reconnecting later takes one click.

What does not affect it

• Closing the dashboard, or logging out of the website.
• The phone being off, out of battery, or without a network.
• Uninstalling Telegram, or switching to a new phone.
• Your computer being asleep or shut down.
• Travelling, changing country or changing SIM, as long as the login itself stays valid.

How this differs from a script on your own machine

A self-hosted script has no monthly fee, and that is a real advantage. What it also has is an uptime problem that becomes yours: it forwards only while the machine is powered on, connected, awake and not mid-update. A laptop that closes at midnight stops forwarding at midnight, and the messages published overnight are not queued anywhere, they are simply missed.

A hosted service moves that problem to somebody whose job it is. It is the only meaningful difference between the two, and it is the one that matters at three in the morning.

What happens if something is briefly unreachable

Deliveries that cannot go through immediately are retried rather than dropped, with a growing gap between attempts, and a destination that keeps refusing for a permanent reason — a removed permission, a chat that no longer exists — is reported next to the rule instead of being retried indefinitely. Endless retrying against a refusal is what gets Telegram accounts limited, so stopping and telling you is the safer outcome.

And the messages published before the rule existed?

Those are a separate job. A rule handles what is published from the moment you switch it on; bringing across older messages is a history import, which has its own page and its own caps.