Files To Links Fast
t.me · Debrid · 1 record · JSON
Files To Links Fast (@dlgram_bot) Debrid
caveatany-phoneno cardphoneDper-object-cap
| Free tier | Free, no account: 'Files To Links Fast', with its implementation published at github.com/musa-42/streamer_file. No quota is stated. unit none; metered on unstated |
|---|---|
| Price | none stated |
| Per-object cap | Not published. Telegram's 2 GB per object is the only documented ceiling. |
| Retention | Not stated. The file remains in its chat; the link's lifetime is the operator's. |
| Egress | Free HTTP links; no allowance stated. free_allowance: not published |
| Identity | any-phone A Telegram account; no bot token needed to use the hosted instance. |
| Limits |
|
| Binding | per-object-cap Same reasoning as the other file-to-link bots: no published quota, and the platform ceiling is the only documented wall. |
| Interface | rest A Telegram chat; the source is public, so the bot can also be run by the client instead of used hosted. |
| Tooling | Hosted bot today; the linked repository makes a self-run copy possible on a free VM. |
| Composes with | The only member of the file-to-URL class with public source, so a hosted outage has a fallback: run the same code on a free compute tier. |
| Reliability | Hosted by one operator; the public repository is the mitigation, not a guarantee that the hosted instance matches it. |
| Notes | Abandon if the repository is deleted or the bot stops resolving. This is the one record in the class where the fallback is verifiable, so it is the one to test first. |
| Evidence rung | documented The description and the repository link are on the bot's page read today. The repository's own limits were not read line by line. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | t.me/dlgram_bot | 'Files To Links Fast' with 'https://github.com/musa-42/streamer_file' in the description |