Torrs
github.com · Debrid · 1 record · JSON
Torrs (self-hosted torrent-to-Telegram bot) Debrid
caveatany-phoneno cardphoneDper-object-cap
| Free tier | No fee. A self-run bot: magnet, hash or .torrent in, selected files out into the chat. Requires a Telegram bot token and, for the full path, a local Bot API server. unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | Files above 1.9 GB are split into 7-Zip volumes because 'the self-hosted Bot API server limit is 2 GB per file'. |
| Retention | Whatever the chat keeps; the project caches by Telegram file_id so a repeat request re-sends instead of re-downloading. |
| Egress | Telegram's; the bot's host carries the swarm traffic and the upload. free_allowance: no allowance published |
| Identity | any-phone api_id/api_hash from my.telegram.org, hence a phone-registered Telegram account, plus a host to run TorrServer and the Bot API server. |
| Limits | |
| Binding | per-object-cap The project documents the sequence exactly: 50 MB without a local server, 2 GB with one, and a 1.9 GB split above that. Nothing about flood control appears, because at these object counts it does not bind. |
| Interface | rest, cli A Telegram chat in front of TorrServer, plus a CLI-style configuration; lossless FLAC needs a second, user-account (MTProto) session because the Bot API only accepts .mp3/.m4a audio. |
| Tooling | Docker or source, TorrServer, and the tdlib Bot API server for the >50 MB path; 7-Zip is mandatory for objects above 1.9 GB. |
| Composes with | The reference implementation of the whole lane: a torrent leeched on somebody else's VM, uploaded to Telegram through a local Bot API server, split at 1.9 GB, and re-sent by file_id on request. |
| Reliability | A ban risk the project acknowledges in its own README; a self-run stack also means the Bot API server must be moved with logOut or updates are lost. |
| Notes | Software, not hosted. It is the only source found that states the 50 MB -> 2 GB -> 1.9 GB-split chain in one place, which makes it the best independent confirmation of the platform caps. Abandon if the README's limit table changes. |
| Evidence rung | documented The 50 MB / 2 GB / 1.9 GB progression is stated in the project's README read today. Nothing was built. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | github.com/stxlvn/Torrs | 'files larger than 1.9 GB are automatically split into 7-Zip volumes (the self-hosted Bot API server limit is 2 GB per file)' |
| 2026-10-23 | github.com/stxlvn/Torrs | 'without it Telegram cuts file uploads to 50 MB, with it the limit is 2 GB' |
| 2026-10-23 | github.com/stxlvn/Torrs | for lossless FLAC a second Telegram account ('userbot', via MTProto) is used because the Bot API only accepts .mp3/.m4a for sendAudio |