TG-FileStreamBot / filestream.bot — HTTP stream front-end over Telegram files
- Free allowance
- Inherits Telegram's unlimited storage but solves a different problem: turning a stored Telegram file into a plain HTTP URL that a browser, VLC, or a download manager can range-request.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-cap20 MB per file
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Inherits Telegram's unlimited storage but solves a different problem: turning a stored Telegram file into a plain HTTP URL that a browser, VLC, or a download manager can range-request. 1,933 stars, pushed 2026-03-07, actively maintained. unit unlimited; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
Bot-token based, so 20 MB per file via cloud Bot API unless you run the local Bot API server. It streams; it does not cache, so every viewer GET is a Telegram pull unless you add a CDN. |
| Identity | institution (inferred, not read) not published |
| Egress | Free from Telegram, served as HTTP from your host — so Cloudflare-cacheable. Multi-bot load balancing is the advertised scaling lever. |
| Per-object cap | 20 MB per file (20000000 bytes) |
| Retention | Inherits Telegram's unlimited storage but solves a different problem: turning a stored Telegram file into a plain HTTP URL that a browser, VLC, or a download manager can range-request |
| Interface | rest rest |
| Tooling | Go backend, multi-bot workers. The hosted filestream.bot instance describes the architecture plainly: 'Parallel block downloads with configurable concurrency. Prefetch buffers ensure smooth, uninterrupted playback' and 'Distribute API load across up to 50 bot tokens. Round-robin routing prevents rate limiting.' Same family as TheCaduceus/FileStreamBot (134 stars, 2024) and SpringsFern/tgfilestream. |
| Composes with | 50 bot tokens x their own per-account flood budgets = roughly 50x the single-account download concurrency, which is the only lever that moves Telegram read throughput. |
| Reliability | Maintained and the streaming model is sound. The failure mode is a hot file: N concurrent viewers on one file means N independent Telegram pulls, which will hit FLOOD_WAIT quickly without an edge cache. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | filestream.bot/ | 'Multi-Bot Workers ... up to 50 bot tokens. Round-robin routing prevents rate limiting' |
| 2026-10-21 | github.com/EverythingSuckz/TG-FileStreamBot | part of the text of Free tier, above |
| 2026-10-21 | github.com/EverythingSuckz/TG-FileStreamBot | 'instant stream links for telegram files without the need of waiting till the download completes' |
Unknown values 2
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read