TG-FileStreamBot / filestream.bot
github.com · Storage · 1 record · JSON
TG-FileStreamBot / filestream.bot — HTTP stream front-end over Telegram files Storage
caveatinstitutionno cardRper-object-cap
| 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 |
| 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 |
| Egress | Free from Telegram, served as HTTP from your host — so Cloudflare-cacheable. Multi-bot load balancing is the advertised scaling lever. |
| Identity | institution derived from the record's prose, not from an identity field, and no signup was executed: roughput. 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 y |
| 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. |
| Binding | per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota |
| 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. |
| Notes | 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. |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
| 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 | 1,933 stars, pushed 2026-03-07 |
| 2026-10-21 | github.com/EverythingSuckz/TG-FileStreamBot | 'instant stream links for telegram files without the need of waiting till the download completes' |
Unknown or withheld values (3)
$.free_tier.notesprocess$.per_object_cap.notesnot-extracted$.retention.notesnot-extracted