URL Uploader (@uploadbot)
- Free allowance
- The bot's own description: 'Quick way to upload files to telegram by url.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- any-phoneno card, phone required
- Binding limit
- volume-quota1 GB/day on the free tier
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | The bot's own description: 'Quick way to upload files to telegram by url. Maximum file size allowed 500MB Daily upload limit 1GB, /upgrade for more'. 18 717 monthly users on the same page. unit GB; metered on uploaded-bytes; 1 GB/day is the published ceiling, not a measurement |
|---|---|
| Price | none stated |
| Limits | |
| Binding | volume-quota 1 GB/day is about 30 GB/month, so the day counter fails long before 1 TiB. The 500 MB object cap is the second wall and the 20 MB getFile cap only bites on retrieval. |
| Identity | any-phone A Telegram account is needed to message any bot. The bot asks for no API key, token or email of its own. |
| Egress | No charge. Delivery is a normal Telegram file message, so a later scripted download is capped by the Bot API's 20 MB getFile limit unless the bot streams it over MTProto. free allowance: none published |
| Per-object cap | 'Maximum file size allowed 500MB' - a quarter of Telegram's own 2 GB object ceiling. (500000000 bytes) |
| Retention | The fetched file is delivered into the chat that asked for it, so it follows cloud-chat retention; the bot's copy of the URL is not described. |
| Interface | rest A Telegram chat. Programmatic use means driving the Bot API or an MTProto client to send a URL to @uploadbot; there is no other endpoint. |
| Tooling | Any Telegram client; no API key, token or account with the operator. |
| Composes with | A free 500 MB-per-file URL fetch into Telegram, which is the cheapest way to park a public HTTP file in the cloud without running anything; the 1 GB/day ceiling makes it a per-object tool, not a store. |
| Reliability | An undocumented daily reset and an unpublished retrieval path: after the file lands, whether the bot can hand it back above 20 MB depends on machinery it does not describe. |
| Notes | Abandon if the description loses the 1 GB/day line or the monthly-user count falls to zero. The paid '/upgrade' tier's price was not read. |
| Evidence note | documented The quota sentences are the bot's own Telegram description, read, with its monthly-user count. What would raise it: one measured upload at the stated cap and one retrieval above 20 MB. |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | t.me/uploadbot | 'Quick way to upload files to telegram by url. Maximum file size allowed 500MB Daily upload limit 1GB, /upgrade for more', with 18 717 monthly users |
| 2026-10-23 | core.telegram.org/bots/faq | 'Use the getFile method. Please note that this will only work with files of up to 20 MB in size.' - the ceiling on retrieving what this bot stores |