About this project
A small independent tool, run by two people, with no company behind it and no relationship with Telegram.
Why it exists
In early 2024 one of us was trying to move a large archive out of a public Telegram channel onto a desktop machine. The mobile app crawled, the transfer failed twice, and the desktop client would not resume. The existing web tools were worse, most were dead, and the ones that worked wanted a login.
So we built a bridge: give it a public post link, get back a plain HTTP URL that any download manager can handle. It was for us at first. We put it online because it seemed unlikely we were the only ones annoyed.
How it is funded
Advertising on the site, plus occasional donations. That is the whole model. There is no paid tier, no quota you can buy your way past, and no plan to introduce one. Bandwidth is the dominant cost and advertising currently covers it.
We do not sell data, because we do not collect anything worth selling. There are no accounts, so there is no profile of you to sell.
What we will not build
We get asked regularly for a few things, and the answer is consistently no:
- Access to private channels. This would require holding Telegram accounts and joining groups under false pretences. It is a straightforward violation of people's expectations about their own private spaces.
- Bypassing content protection. When a channel owner switches on Restrict Saving Content, that is a deliberate choice we intend to respect.
- APK downloads. Sideloaded Android packages passed around on Telegram are a well-worn malware route, and we cannot inspect them. Declining them outright is the only responsible option.
- Anything requiring your Telegram login. There is no field for it and never will be. If a site asks for your Telegram credentials to download a public file, close it.
Reliability
The service has run continuously since launch and handles millions of requests. It is not perfect. Telegram's API has bad days, and when it does, so do we. The troubleshooting section is written from failures we have actually watched happen, and it grows every time someone emails us about a case we had not seen.
Get in touch
Bug reports and feature requests both land in the same inbox, and we read all of them. The contact page has the details.
