Telegram Drive
telegram-drive.com · Debrid · 1 record · JSON
Telegram Drive (desktop, caamer20) Debrid
caveatany-phoneno cardphoneDper-object-cap
| Free tier | 'Every feature is free. The optional $5 license only removes sponsor placements.' Files live in the client's Saved Messages and channels; there is no separate storage account. unit unlimited; metered on stored-bytes; again, 'unlimited' is Telegram's account claim |
|---|---|
| Price | none stated |
| Per-object cap | 'The application caps a Telegram object at exactly 2,000,000,000 bytes.' and 'Files over 2 GB are skipped and logged.' (2000000000 bytes) |
| Retention | Until deleted from the account. The site answers the storage question with 'No. Storage and file handling follow Telegram's account, service, and per-file limits.' |
| Egress | Telegram's; the app streams from Telegram's media DCs and keeps only caches locally. free_allowance: no allowance published |
| Identity | any-phone The client's own Telegram account credentials; no account with the project. |
| Limits | |
| Binding | per-object-cap The app's own 2e9-byte cap is marginally stricter than Telegram's and is the one a user meets; neither leaves a 1 TiB month with fewer than ~550 objects. |
| Interface | unknown A GUI application over MTProto (Rust/Tauri/Grammers per the repository); no public HTTP API or CLI is documented. Desktop folder sync is the automation surface. |
| Tooling | Windows, macOS (Intel and Apple Silicon), Linux, Android and Google TV builds, released on GitHub. |
| Composes with | A client-side drive over one Telegram account: no server, no database, and a hard 2e9-byte object cap, so it composes with a free compute tier only as a sync target. |
| Reliability | The vendor's own warning: 'Telegram Drive should not be treated as literally unlimited storage or as the only backup of important data.' Files above 2 GB are skipped, not split. |
| Notes | Software, not a hosted service. Abandon if the 2e9 cap or the free-everything claim changes; the $5 licence is cosmetic and does not gate a feature. |
| Evidence rung | documented Both the 2e9 cap and the skip behaviour are stated on the vendor's site and repository, read today. No install was run. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | telegram-drive.com/ | 'Every feature is free. The optional $5 license only removes sponsor placements.' and 'No. Storage and file handling follow Telegram's account, service, and per-file limits.' |
| 2026-10-23 | telegram-drive.com/ | 'Files over 2 GB are skipped and logged.' and 'Telegram-Drive currently limits a Telegram object to roughly 2 GB' |
| 2026-10-23 | github.com/caamer20/Telegram-Drive | 'The application caps a Telegram object at exactly 2,000,000,000 bytes.' and 'Telegram Drive should not be treated as literally unlimited storage' |
Unknown or withheld values (1)
$.interfaceinterface-unknown