Telegram
telegram.org · Debrid, Storage · 3 records · JSON
- Telegram — MTProto user account + unlimited channels as the volume Storagecaveatemail?card?Rper-object-cap
- Telegram Premium DebridpaidcardcardphoneDper-object-cap
- telegram cloud bot api alone (api.telegram.org) Storagefails: quotaemail?card?R
Telegram — MTProto user account + unlimited channels as the volume Storage
caveatemail?card?Rper-object-cap
| Free tier | No total storage cap, quoted from Telegram: 'you can ... share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each'. Per-file 2 GB free, 4 GB with Premium. Per-account volume is effectively unbounded because you can hold up to 500 channels/supergroups (1000 with Premium) and create up to 50 channels per day, and each channel is a separate unbounded blob store. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Per-object cap | Per-file 2 GB (2000000000 bytes) |
| Retention | not stated |
| Egress | Free and unmetered. Telegram charges nothing for downloads and imposes no transfer quota; the only egress cost is Telegram's own speed shaping. Downloads are free even for files uploaded by Premium users: 'any user can download large 2+ GB files uploaded by premium users'. |
| Identity | email (placeholder) not published |
| Limits |
Per-file 2 GB free / 4 GB Premium — verified against Telegram's own config, not a blog: upload_max_fileparts_default = 4000 and upload_max_fileparts_premium = 8000, times the max part size 524288 bytes = 2,097,152,000 B and 4,194,304,000 B. Upload speed is throttled for non-Premium by an explicit server error, FLOOD_PREMIUM_WAIT_X, which signals 'upload speed is limited because the current account does not have a Premium subscription'; upload_premium_speedup_upload = 10, i.e. Premium is ~10x faster. No published daily byte cap exists — Telegram documents none, and the empirical field report (Teldrive issue #561) is 10-50 GB/day for one user, with a maintainer answering 'I have seen user posting that they upload 400-500gb daily no issues. It depends on how many bots you have.' Treat 20 GB/day as folklore: no primary source found. |
| 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, rclone rest |
| Tooling | Strongest tooling of any provider in this whole research area. MTProto clients: TDLib (github.com/tdlib/td, 9.2k stars, pushed 2026-10-21), MadelineProto (github.com/danog/MadelineProto, 3.5k stars, pushed 2026-10-21, alive). Field-proven storage layer: Teldrive (github.com/tgdrive/teldrive, 3.1k stars) with its own rclone backend (github.com/tgdrive/rclone). CAUTION: Telethon (12.1k) and Pyrogram (4.6k) are both ARCHIVED (Telethon read-only since 2026-02-21, Pyrogram since 2024-12-23) — do not start a new build on either. |
| Composes with | Unbounded by construction: 1 account x 500 channels x unlimited posts = unlimited. A second account carries a second read allowance, not a second storage allowance. Teldrive adds its own layer: 'channel-part-limit: 500000' parts per channel with 'auto-channel-create: true' — it opens a NEW channel automatically when the active one fills, so the sharding is already automated. A 2 GB file is 4000 x 512KB parts, so one channel holds ~250 TB of max-size files before rotation. |
| Reliability | Throttling is the real risk, not deletion: FLOOD_PREMIUM_WAIT_X caps non-Premium throughput and FLOOD_WAIT_X backs off per method. Files persist indefinitely in practice, but a closed account takes its channels with it, and Teldrive's own README warns accounts and stored files 'can become unavailable', so a store that spans several accounts loses only the parts one account holds. |
| Notes | No total storage cap, quoted from Telegram: 'you can ... share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each'. Per-file 2 GB free, 4 GB with Premium. Per-account volume is effectively unbounded because you can hold up to 500 channels/supergroups (1000 with Premium) and create up to 50 channels per day, and each channel is a separate unbounded blob store. |
| 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 | telegram.org/faq | 'share an unlimited number of photos, videos and files ... of up to 2 GB each' (line 77) and 'files of any type, up to 2 GB in size each (or 4 GB with Premium)' (line 338) |
| 2026-10-21 | core.telegram.org/api/config | live JSON: upload_max_fileparts_default=4000, upload_max_fileparts_premium=8000; descriptions state max file size = value x 524288 |
| 2026-10-21 | core.telegram.org/api/files | FLOOD_PREMIUM_WAIT_X: 'upload speed is limited because the current account does not have a Premium subscription ... upload_premium_speedup_upload times' |
Unknown or withheld values (6)
$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.per_object_cap.notesnot-extracted$.retention.notesnot-extracted$.retention.statednot-extracted
telegram cloud bot api alone (api.telegram.org) Storage
fails: quotaemail?card?R
| Free tier | Hard 20 MB download ceiling via getFile and 50 MB multipart upload. getFile links also expire: 'It is guaranteed that the link will be valid for at least 1 hour.' Unusable as a storage API w unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not recorded |
| Retention | not recorded |
| Egress | not recorded |
| Identity | email (placeholder) not published |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | unknown |
| Tooling | not recorded |
| Composes with | not recorded |
| Reliability | Hard 20 MB download ceiling via getFile and 50 MB multipart upload. getFile links also expire: 'It is guaranteed that the link will be valid for at least 1 hour.' Unusable as a storage API w |
| Notes | Hard 20 MB download ceiling via getFile and 50 MB multipart upload. getFile links also expire: 'It is guaranteed that the link will be valid for at least 1 hour.' Unusable as a storage API w |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | core.telegram.org/bots/api/methods/getfile | Hard 20 MB download ceiling via getFile and 50 MB multipart upload. getFile links also expire: 'It is guaranteed that the link will be valid for at least 1 hour.' Unusable as a storage API w |
More fields (1)
{
"dead_end": {
"failure_class": "retention",
"why": "Hard 20 MB download ceiling via getFile and 50 MB multipart upload. getFile links also expire: 'It is guaranteed that the link will be valid for at least 1 hour.' Unusable as a storage API w",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (15)
$.chainingnot-recorded$.confidence_notewithheld$.egress.termsnot-recorded$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.interface_detailwithheld$.limits_noteprocess$.per_object_cap.notesnot-recorded$.per_object_cap.statednot-recorded$.retention.notesprocess$.retention.statednot-recorded$.toolingnot-recorded