Telegram storage limits and what gets deleted from their servers first
Telegram markets itself as offering unlimited cloud storage for free. That claim is technically true and practically misleading at the same time, and if you run any kind of active account, channel, or bot setup, you need to understand the gap between the marketing and the mechanics.
What “unlimited” actually means
Telegram’s cloud storage applies to messages, photos, videos, documents, and voice notes that live in the Telegram Cloud, meaning they sync across every device you use and stay accessible unless you or the other party deletes them. There’s no storage quota tied to your account in the way Google Drive or Dropbox enforces a cap. You will not get an email saying you’re at 90% of your limit.
But “unlimited” only describes the ceiling, not the floor. Telegram’s infrastructure is built around active retrieval and caching, not archival guarantees. The company has never published a hard number for total per-account storage, and that’s not an oversight. It’s because the real constraint isn’t a quota, it’s usage patterns and cost to Telegram of keeping data warm on distributed servers.
The single file size cap
The one hard number that does exist is per-file size. Telegram caps individual file uploads at 4 GB for verified accounts using the current client versions, after an earlier limit of 2 GB was raised. This applies to any single document, video file, or archive you send through a chat, channel, or bot. If you’re running a media archive or a backup pipeline through Telegram, this is the number that actually constrains your workflow, not some mythical total storage ceiling.
Bots historically had a lower ceiling on file downloads through the Bot API, which matters if you’re using automation to pull files rather than a standard client. Anyone building storage or backup tooling on top of Telegram needs to check the current Bot API limits directly, because bot-side constraints and client-side constraints are not the same thing and Telegram has adjusted both independently over time.
Inactive accounts get purged, not throttled
Here’s the part that actually determines what disappears first: Telegram’s self-destruct policy for inactive accounts. If you don’t open Telegram on any device for a set period, currently defaulting to six months but adjustable by the user between one month and up to a year in privacy settings, the account itself gets deleted. Not archived. Deleted.
When an account is deleted this way, every one-on-one chat you were part of goes with it on the other person’s side too, since those messages aren’t stored independently of the account graph in the same way channel content is. Group chats and channels you were a member of don’t disappear, but your presence and any messages you personally sent inside them can be affected depending on how the group or channel handles departed members.
This is the actual “deletion” mechanism most people never think about. It’s not Telegram trimming your media cache because you’re over some invisible quota. It’s the entire account timing out from lack of activity. If you’re using Telegram for hosting archives, running a channel, or maintaining a proxy-connected account for business use, the six-month inactivity clock is the first thing to check and the first thing to extend in settings if you’re not logging in through the primary client regularly.
Cache versus cloud, and why this confuses people
A lot of confusion around “storage limits” comes from mixing up two different things: what’s stored in Telegram’s cloud infrastructure, and what’s cached locally on your device.
Local cache is what eats your phone’s storage. Telegram downloads media as you scroll and keeps a local copy so you’re not re-fetching it every time you open a chat. This local cache has nothing to do with server-side limits and can be cleared from Settings without touching anything on Telegram’s servers. People who complain about Telegram “filling up their storage” are almost always talking about this local cache, not the cloud.
The cloud copy is what stays server-side regardless of whether you clear your device cache. That’s the part with no advertised quota. The two systems are independent, and clearing one has zero effect on the other. If your goal is long-term retention of something, the local cache clearing has no bearing on it either way.
What actually gets removed, in order
If you’re trying to understand what disappears first from Telegram’s side, it breaks down roughly like this, from most to least fragile:
Self-destructing content. Messages set with a timer, whether in Secret Chats or the newer self-destruct timers available in regular chats, get deleted on schedule regardless of activity. This is deliberate and immediate, not a storage management side effect.
Secret Chat content on lost devices. Secret Chats are device-specific and not stored in the cloud at all. If you lose the device or log out, that content is gone. This is a fundamentally different storage model than regular cloud chats and worth remembering if you’re using Secret Chats for anything you need to keep.
Content in accounts that hit the inactivity window. As covered above, six months of no login (or whatever the user has set) triggers full account deletion, taking associated one-on-one message history with it.
Content you or a chat partner manually deletes. Obvious, but worth stating: Telegram doesn’t override manual deletion. If someone deletes a message for both sides, it’s gone from the cloud on both accounts.
Everything else. Regular cloud messages, channel posts, group content, and files under the 4 GB cap in active accounts effectively persist indefinitely. There’s no evidence of Telegram silently pruning old, low-engagement content to save space. Their storage model is built around keeping things retrievable, which is the entire pitch of Telegram Cloud versus a locally-stored messaging app.
Why this matters for anyone running infrastructure on Telegram
If you’re managing hosted Telegram setups, whether that’s channels, bots, or proxy-connected accounts for business communication, the practical takeaways are narrow but important.
First, the inactivity timer is the real risk, not storage capacity. An account that goes untouched for six months can vanish along with its chat history. If you’re running accounts for clients or for archival purposes, make sure something is logging in on a regular cadence, even automated, to keep the account inside the active window. Adjusting the self-destruct period in settings to the maximum available is a cheap insurance policy if you know an account will go quiet for stretches.
Second, don’t build workflows around the file size cap changing. The 4 GB ceiling per file is enforced at the protocol level. If your use case involves large files, plan for chunking or external storage rather than hoping Telegram raises the limit again. It has moved before, from 1.5 GB to 2 GB to the current 4 GB, but each move took years, and you shouldn’t architect around a future increase you can’t schedule around.
Third, understand that proxy and connection stability has nothing to do with any of this. Storage limits, inactivity timers, and file caps are account-level and server-level behaviors that apply the same way whether you’re connecting through a standard connection or through a configured MTProto or SOCKS5 proxy. Proxy setup affects connectivity and, in some regions, whether you can reach Telegram’s servers at all. It doesn’t touch storage policy in any way.
The bottom line
Telegram’s storage is unlimited in the sense that matters for casual use: you won’t hit a wall of “storage full” the way you might with a photo backup service. But the account-level inactivity clock is a real deletion mechanism that catches people off guard, especially anyone running accounts that go quiet for months at a time. The 4 GB per-file cap is the only hard technical ceiling worth designing around. And local device cache, which is what most people actually notice filling up their phone, has no bearing on any of this.
If you’re setting up or maintaining Telegram accounts for business use, whether that’s hosting, proxy configuration, or making sure an account doesn’t fall out of the six-month window unnoticed, that’s exactly the kind of infrastructure work we handle. Take a look at what we offer at telegramvault.org.
Get new guides and videos first — join the Telegram channel.