Telegram media not downloading on Wi-Fi only is one of those complaints that sounds like a network fault but almost always turns out to be a settings boundary. The pattern is consistent: photos and videos fill in normally while the phone sits on a wireless network, then the same chat shows grey placeholders, blurred previews, or a spinner the moment cellular data takes over. Nothing is broken on Telegram's side, and nothing has been throttled at the server. The app is applying a rule that you, or your operating system, configured earlier — and that rule is keyed to the type of connection the device is currently using.

What follows is a layer-by-layer walkthrough of that chain. There are four places where the Wi-Fi-only behaviour can originate: the app-level auto-download rules, the per-media-type size ceilings attached to those rules, the operating system's per-app data permissions, and the network path itself. Each layer is checkable in a handful of taps, and each demands a different fix. By the end you should be able to identify which layer is holding your media back within about a minute, and decide whether the right answer is to change a setting at all — because in some cases the current behaviour is the sensible one.

Why Telegram Only Downloads Media Over Wi-Fi: The Mechanism Behind the Symptom

Telegram is a cloud-first messenger. Chats, photos, videos, and documents live on Telegram's servers, and each device keeps only a local cache of what it has recently fetched. When you scroll into a chat, the app streams lightweight previews so the conversation looks complete, and it may speculatively pull down full-quality files before you ask for them. That speculative behaviour is what the settings screen calls automatic media download, and it is the piece governed by connection type.

The auto-download screen is organised into connection buckets — typically mobile data, Wi-Fi, and roaming — and inside each bucket sits a set of per-media-type switches such as photos, videos, files, voice messages, and video messages. On mobile platforms each switch is often paired with a size ceiling, so a bucket can be enabled for photos but not for large videos, or enabled for videos only up to a certain file size. Because the buckets are independent, an account can legitimately auto-download everything on Wi-Fi while auto-downloading nothing on cellular. That is not a malfunction; it is the default posture for many users, and it is the single most common explanation for the Wi-Fi-only behaviour.

There is a second, more important distinction underneath all of this. Auto-download is pre-fetching. It is optional and network-sensitive. On-demand download is what happens when you actually tap a media item, and it is not supposed to care which connection you are on. If a file refuses to open even when you tap it directly, you are no longer looking at an auto-download rule — you are looking at an operating-system permission, a storage problem, or a network-level block.

Practical rule of thumb: if the thumbnail appears but the full file never loads, the problem is pre-fetch configuration. If tapping the item produces a spinner that never resolves, look at the system layer instead. This single test eliminates half the possible causes before you open any settings menu.

Why Telegram Only Downloads Media Over Wi-Fi: The Mechanism Behind the Symptom
Why Telegram Only Downloads Media Over Wi-Fi: The Mechanism Behind the Symptom

Auto-Download and On-Demand Download Are Different Pipelines

It helps to think of the preview you see in the chat list as a compressed stand-in, not the file itself. Even with every auto-download switch turned off, Telegram will still show you a rough rendering of an incoming photo so that the conversation reads naturally. Users frequently mistake that preview for a successful download and then conclude that something is intermittently failing when larger media will not resolve on cellular.

The practical consequence is that you should always test with a deliberate tap before changing anything. Open a chat, tap a photo that has never been opened on this device while on mobile data, and watch what happens. A file that downloads on tap but never pre-fetches points squarely at the auto-download buckets. A file that fails on tap points somewhere else entirely, and changing auto-download settings will not help.

Keeping the two pipelines separate in your mind is what makes the rest of this guide fast to apply: every symptom you meet from here on resolves, in the first instance, to a single question — did the file arrive on its own, or did it arrive only after you asked for it?

Five Common Scenarios: Which One Are You In?

Before touching settings, match your symptom to one of the patterns below. Each maps to a different layer, and each has its own verification step. The table is deliberately short — these five cover the overwhelming majority of reports, and the remaining edge cases tend to be variations on the third row.

ScenarioWhat you observeGoverning layer
1. Channel or group media arrives only on Wi-FiPreviews appear on cellular, full files fill in once Wi-Fi connectsApp auto-download buckets
2. Small photos fine, long videos neverPhotos resolve instantly; a video stays as a placeholder even on Wi-FiPer-type size ceiling
3. Nothing downloads, tapping spins foreverFailure on both Wi-Fi and cellular, sometimes with a retry iconOS permission, storage, cache, or network path
4. Media opens in Telegram but never reaches the galleryChat looks normal; the phone gallery has nothingSave to Gallery / Save to Photos
5. Desktop downloads land somewhere unexpectedFiles download but are hard to find, or stop partwayDownload path and disk space

Scenario one is the classic case, and a useful example comes from community administration. An admin running a channel with a six-figure subscriber count will typically have mobile-data auto-download disabled to protect a metered plan, which is a sound decision. The side effect is that when a contributor posts a batch of product photos in a related discussion group, the admin sees only previews while commuting and the full files appear after arriving at the office. Nothing failed — the admin simply never authorised pre-fetching on cellular for that account.

Scenario two is subtler and catches experienced users. Suppose a member of a media-heavy group regularly receives short voice notes and screenshots, all of which resolve immediately, alongside occasional long screen recordings that never do. The temptation is to assume a bug affecting video specifically. In practice the auto-download entry for videos is very often capped at a size far below those recordings, so the app treats them as on-demand items and waits for a tap. Raising the ceiling is the fix, and it is worth pausing to consider whether you actually want multi-hundred-megabyte files pulled onto a phone automatically.

Scenario three is where most misdiagnosis happens, because users read the Wi-Fi-only symptom into a problem that has nothing to do with connection type. If a tap produces a persistent spinner, the auto-download buckets are irrelevant; the file would fail just as reliably on a fast wireless network. Common culprits are a per-app cellular permission being off at the system level, a full device storage, a cache database that has drifted, or a proxy that cannot route the media connection.

Scenario four is a naming confusion rather than a download failure. Telegram can display a photo perfectly while never writing it to the system gallery, because saving to the gallery is a separate, opt-in behaviour with its own per-chat-type switches and per-chat exceptions. A user who migrated from another messenger may reasonably expect automatic gallery saving and then report lost images — when in fact the images are present in the chat and simply not mirrored into the system photo library.

Scenario five is the desktop analogue. Desktop builds do not usually differentiate between connection types the way mobile builds do — a laptop is treated as a single connection context — so the interesting controls there are the per-type enable switches, the size limits, and the download path. A partial or repeatedly failing desktop download is more often a disk-space or path-permission issue than a network-policy one.

With the scenario identified, the remaining work is mechanical. The four fixes that follow are numbered in the order that resolves the greatest number of cases first, so working from the top down is the most efficient route.

Fix 1 — Enable Auto-Download Over Mobile Data on Android

The first and most likely fix lives in Telegram's own data settings. In recent Android builds as of this writing, the path is Settings, then Data and Storage, then Automatic Media Download. The exact labels shift slightly between versions and localisations, but the screen structure has been stable for years: connection buckets listed vertically, media types listed horizontally within each bucket.

Inside that screen you will find the mobile data bucket. Turn on the media types you want to arrive without a tap. Photos are usually safe to enable unconditionally; videos and files deserve more thought because they are the ones that consume meaningful data volume. Many builds attach a size dropdown to each switch, which lets you enable a media type only below a threshold — a reasonable middle ground that keeps previews and thumbnails flowing while leaving large items to deliberate taps.

  1. Open Telegram and go to Settings.
  2. Open Data and Storage, then Automatic Media Download.
  3. Locate the mobile data section (the buckets are commonly ordered as mobile data, Wi-Fi, roaming — verify against your build).
  4. Enable the media types you want, adjusting the size ceiling next to each one where the option is offered.
  5. Repeat for the roaming bucket only if you understand your roaming tariff; leaving it off is the conservative default.

The reasoning behind this layout is worth understanding rather than merely clicking through. Telegram assumes that mobile data is the scarce resource and Wi-Fi is not, so it ships with a cautious configuration and expects the user to opt into cellular pre-fetching. Once you enable a type in the mobile data bucket, downloads proceed identically to Wi-Fi for items within the ceiling. There is no separate quality tier, no server-side flag, and no waiting period.

When not to do this: on a metered or capped plan, on a device that shares a hotspot, or when travelling internationally with roaming enabled. Enabling videos over mobile data without a size ceiling is the fastest way to convert a Wi-Fi-only inconvenience into an unexpected bill. If you need only occasional large transfers away from Wi-Fi, leave the bucket off and tap the specific file — on-demand download still works over cellular.

Watch out for the roaming bucket. It is easy to enable it while hastily ticking switches, and roaming rates are frequently far higher than domestic ones. If you are unsure about your plan, leave roaming disabled and rely on manual taps.

Fix 2 — The Same Change on iOS and What Desktop Does Differently

iOS exposes an equivalent control, though the naming has alternated between Auto-Download and Automatic Media Download across releases. The entry point in recent builds is Settings, then Data and Storage, where you will find the same three-way split by connection type and a comparable list of media categories. The mechanics are identical: enabling a category in the mobile-data section allows pre-fetching on cellular within the applicable size limit.

One iOS-specific nuance is that the operating system imposes its own ceiling on what an app may do in the background. Telegram cannot pre-fetch anything while it is suspended, so media typically resolves when you open the app rather than the instant a message arrives. Users who expect media to be waiting for them after a flight often mistake this for a download failure. It is normal behaviour on iOS, and it applies equally on Wi-Fi and cellular.

iOS also groups some media handling differently from Android — saving to the system photo library is controlled separately from downloading into the app — so if your complaint is specifically that images never reach the Photos app, skip ahead to the section on gallery saving rather than adjusting auto-download switches.

Telegram Desktop takes a different approach because a desktop machine is generally assumed to be on an unmetered connection. In recent desktop builds the relevant screen sits under Settings, then Advanced, and provides per-type enable switches, size limits, and the download path that determines where files land on disk. There is typically no mobile-data or Wi-Fi split at all. If you are troubleshooting a laptop, focus on the size limit for the media type in question and on the destination folder rather than on connection buckets.

Telegram Web sits at the other end of the spectrum. It streams media on demand and exposes very few download controls, so it should be treated as a viewer rather than a managed downloader. If a file will not open in the browser client but opens fine in the desktop app, that is not evidence of a network problem — it is the expected difference in capability between the two clients.

Fix 3 — Raise Size Ceilings and Configure Per-Chat Exceptions

Enabling a media type is only half the job. Each enabled type is filtered by a size ceiling, and anything above that ceiling is silently downgraded to on-demand handling. This is the reason a user can enable videos on Wi-Fi, test with a short clip, see it work, and then conclude the setting is broken when a longer recording never arrives by itself.

The ceilings exist for a defensible reason. Auto-downloading every video in a busy group is a straightforward way to fill a phone's storage with content nobody asked for, and most users only ever re-watch a small fraction of it. Raising a ceiling is therefore a deliberate trade of storage and bandwidth for convenience, and the right value depends on how you use the account.

Alongside the buckets, recent mobile builds offer an Exceptions screen where individual chats can be pinned to always auto-download or never auto-download, overriding the global buckets. This is the most precise control available and the one most people never find. If your build lacks the entry, check whether a per-chat menu inside the conversation exposes equivalent options; availability has varied by platform and release, so treat the exact location as build-dependent.

A concrete pattern worth adopting: leave the global mobile-data bucket conservative, then add only the two or three chats that matter to an always-download exception list. Example: a support engineer whose team coordinates in a single group can auto-download that group's files on cellular while keeping every other chat Wi-Fi-only. The result is targeted convenience without a blanket policy that quietly consumes data across dozens of low-priority channels.

When not to use exceptions: on accounts with many active chats. An exception list that grows past a handful of entries becomes effectively indistinguishable from enabling everything globally, at which point the more honest approach is to raise the global ceiling and audit it periodically.

Fix 4 — Remove Operating-System Blocks: Data Saver, Low Data Mode, Battery Restrictions

If Telegram's own switches are already enabled over mobile data and media still refuses to download, the next layer is the operating system, which can veto an app's network access regardless of what the app itself wants. This is the layer most often missed, because the symptom looks identical to a misconfigured app setting.

Android: Per-App Data Permissions and Aggressive Battery Managers

Android gives users several overlapping controls, and the menu names vary by version and manufacturer. In general terms, look for the Telegram entry in system settings for apps, then a data-related submenu where background data and unrestricted data usage can be granted. On many builds the same screen hosts a battery section where the app can be set to unrestricted rather than optimised.

  • Check whether system Data Saver is active, and whether Telegram has been added to the unrestricted list. Data Saver restricts background traffic for apps that have not been exempted.
  • Check the per-app network permission. Some builds offer separate toggles for mobile data and Wi-Fi, and a Wi-Fi toggle switched off will produce the mirror image of your problem.
  • Check battery optimisation. Several vendor skins are known to suspend background activity aggressively, which can interrupt in-progress downloads when the screen turns off.
  • Check that a system-wide private DNS or firewall app is not filtering Telegram's connections.

The battery point deserves emphasis because it produces a symptom that looks like flaky networking: downloads that start and then stall, or that only complete while the phone is awake. If that pattern matches your experience, setting the app to unrestricted battery usage is a more promising fix than any auto-download switch.

iOS: The Cellular Switch and Low Data Mode

iOS handles this differently and, in some ways, more bluntly. Each app has a single cellular data permission in system settings, and if it is off, no amount of configuration inside Telegram will help — the app is simply not permitted to use cellular at all. This produces exactly the Wi-Fi-only symptom and is a very common oversight after a device restore or a data-saving phase.

  • Confirm the per-app cellular switch for Telegram is enabled in the system settings for mobile data.
  • Check Low Data Mode, which can be enabled globally for cellular and, separately, per Wi-Fi network. It suppresses background transfers and may delay media even on wireless.
  • Check Background App Refresh. With it disabled for Telegram, media only resolves while the app is in the foreground.
  • Remember that iOS will never pre-fetch while an app is suspended, so media appearing only after you open the app is expected.

The distinction between these two platform models matters when you are advising someone else. On iOS, a single system switch explains the whole symptom; on Android, the same symptom can come from three or four overlapping controls, and users often fix one and stop looking.

When Media Will Not Download Even on Wi-Fi

A stubborn minority of cases break the premise of the title: media fails on Wi-Fi too, and the Wi-Fi-only pattern you thought you saw was really an intermittent pattern that happened to correlate with network switches. These cases need a different diagnostic sequence.

Cache, Keep Media, and Free Storage

Telegram keeps a local cache of downloaded media, and it maintains a retention policy for that cache. In the Storage Usage area of the data settings, a Keep Media control determines how long cached media remains on the device before the app reclaims the space, with options ranging from a day up to indefinitely, plus an explicit Clear Cache action.

A short retention window produces a confusing effect: media you downloaded last week is silently evicted, and when you revisit the chat, it must be fetched again. On a slow connection that re-fetch looks like a failure. If your retention window is set to the shortest option, either extend it or accept that revisiting old chats will always trigger a new download.

Storage exhaustion is the other half of this problem. When free space runs low, downloads can fail silently or stall partway, and some devices throttle the app further through battery management. Checking free space is a ten-second step that eliminates an entire class of faults before you start clearing caches.

Clearing the cache is a legitimate remedy for a corrupted cache, but it is not free. Everything cached is discarded and must be downloaded again, which is a poor trade on a metered connection. Treat it as a last resort for a specific chat that misbehaves, not as routine maintenance.

Proxy, privacy tool, and Network-Level Interference

Telegram supports proxy connections configured inside the app, and a proxy that is reachable for messaging but unreliable for large media transfers will produce a highly selective failure pattern. If messaging works perfectly but every file stalls at the same stage, the proxy is the first suspect, not the auto-download rules.

A quick verification is to change only one variable at a time. Disable the proxy and test on Wi-Fi, then on cellular. If behaviour changes, the proxy path is implicated. If nothing changes, the proxy is exonerated and you can move on. The same logic applies to a system-wide privacy tool, to a private DNS resolver that filters domains, and to networks that block or throttle Telegram traffic — some institutional and national networks do so, and the failure appears identically on every connection type.

As an empirical observation from user reports rather than a measured benchmark, the failure signature of network interference tends to be uniform across media types and sizes, whereas a configuration problem is usually selective — photos fine but videos failing, small files fine but large ones failing. Selectivity points inward at settings; uniformity points outward at the network.

Free vs. Premium: Which Download Behaviours Are Actually Tier-Gated?

Because Telegram offers a paid subscription, users reasonably ask whether download behaviour is behind it. The answer is partially yes, and it is important to separate what the subscription changes from what it does not, because the Wi-Fi-only symptom sits firmly in the second category.

ControlFree accountPremium subscription
Per-connection auto-download bucketsAvailableAvailable
Per-type size ceilingsAvailableAvailable
Per-chat exceptionsAvailableAvailable
Cache retention and clearingAvailableAvailable
Save to Gallery / Save to PhotosAvailableAvailable
Upload size ceilingLower documented ceilingHigher documented ceiling
Download speedStandardListed as faster on the subscription page

Every control that governs the Wi-Fi-only behaviour is available on a free account. Telegram's subscription page, reachable from the Premium entry in settings and from the official site, lists benefits such as larger upload limits and faster downloads; the exact benefit list has changed over time as the product has evolved, so the authoritative source is the in-app subscription screen rather than any third-party summary, including this one.

The practical implication is that subscribing will not change which connection types are permitted to pre-fetch media. A Premium account with mobile-data auto-download disabled behaves exactly like a free account in that respect. If your goal is simply to stop the Wi-Fi-only behaviour, the subscription is irrelevant to the fix.

Where the tiers genuinely diverge is at the margins: very large transfers, and the speed at which a large file completes once started. A user whose work involves moving large media archives might notice a difference; a user whose complaint is that a photo does not appear until Wi-Fi arrives will not. Note also that upload and download ceilings are not the same number and have been adjusted over time, so verify current figures in Telegram's own documentation rather than relying on remembered values.

Free vs. Premium: Which Download Behaviours Are Actually Tier-Gated?
Free vs. Premium: Which Download Behaviours Are Actually Tier-Gated?

Common Mistakes That Make the Problem Worse

Most failed attempts at fixing this issue share a small number of root causes. Recognising them saves a surprising amount of time.

  • Toggling only the top-level switch and ignoring the size ceiling beside it. The switch enables the category; the ceiling decides which files actually qualify.
  • Assuming a cleared cache is a fix. It forces re-downloads and can make a metered plan worse without addressing the underlying rule.
  • Confusing in-app viewing with gallery saving. Telegram can display a photo flawlessly while never writing it to the system photo library.
  • Enabling the roaming bucket unintentionally while ticking switches during a hurried setup.
  • Changing several variables at once — proxy off, cache cleared, and buckets enabled in a single session — which makes the eventual result impossible to attribute.
  • Assuming a subscription is required. As covered above, the relevant controls are not tier-gated.

The single-variable rule is the most valuable of these. Change one thing, reproduce the symptom, and observe. If you clear the cache and enable mobile-data videos at the same time and the problem disappears, you have learned nothing about which change mattered, and the next device will be equally puzzling.

Troubleshooting Matrix: Symptom to Cause to Verification to Fix

The matrix below compresses the guide into a lookup table. Use it after you have performed the tap test described at the beginning, since the tap test determines which rows are relevant at all.

SymptomLikely causeVerificationResolution
Previews on cellular, full files after joining Wi-FiMobile-data bucket disabledTap a file on cellular; it downloads on demandEnable the media types in the mobile-data bucket
Photos fine, long videos neverSize ceiling too low for that typeCompare a small clip and a long clip in the same chatRaise the ceiling or accept on-demand behaviour
Tap spins on every networkSystem permission, storage, cache, or proxyTest the same file via a different client or networkGrant background data, free space, or disable proxy
Downloads stall with screen offBattery optimisation suspending the appKeep the screen on and repeatSet the app to unrestricted battery usage
Media opens but gallery stays emptyGallery saving disabledCheck the gallery-saving switches and exceptionsEnable saving for the relevant chat types
Old chats re-download repeatedlyShort cache retention windowCheck the Keep Media settingExtend retention or accept the re-fetch

Read the matrix from the symptom outward rather than working down the rows. The first two rows are configuration issues and take under a minute to resolve. The middle rows are system issues and require leaving Telegram for the operating system settings. The last row is a deliberate policy that you may well decide to keep.

Bots and Third-Party Helpers: What They Can and Cannot Do

It is worth stating plainly that no bot can change your auto-download settings, your system permissions, or your cache policy. Those controls live in the client application and in the operating system, and bots operate entirely inside Telegram's message layer. Any tool claiming to fix download behaviour on your behalf should be treated with suspicion.

What bots genuinely can do is serve media in a more flexible way. A third-party archiving bot, for example, may accept large files, store them, and re-deliver them in smaller segments suitable for a constrained connection. This does not change how your client handles downloads, but it changes the shape of what arrives, which can be a practical workaround on a weak network. Because these are third-party services rather than Telegram features, their behaviour, retention policies, and privacy terms vary and should be reviewed before use.

Follow the principle of least privilege with any such tool. Never share a login code, a two-factor password, or a session string with a bot or a third-party website, because those credentials grant full account access rather than the narrow file-handling capability you were seeking. A file-transfer utility needs nothing more than the ability to receive and send messages in a chat you control.

The honest conclusion is that bots are relevant to workarounds, not to fixes. If your problem is the Wi-Fi-only pattern, the remedy is in your own settings, and no external service can substitute for that.

Reproducible Verification: Confirming the Fix Actually Worked

Claims about download behaviour are easy to make and hard to confirm, so it is worth running a short, controlled test rather than relying on impressions. The protocol below uses only built-in capabilities and requires no special tools.

  1. Create a baseline. Open Saved Messages and send yourself two files: one small photo and one deliberately large file of the type you are troubleshooting. Saved Messages is the cleanest test surface because no other participant can affect it.
  2. Record the current state on Wi-Fi. Note which of the two resolves without a tap and which requires one. This is your reference point.
  3. Switch to cellular only — disable Wi-Fi at the system level rather than relying on signal strength to decide.
  4. Repeat the observation. If the small photo now auto-downloads and the large file still waits for a tap, your ceiling is the operative limit. If neither auto-downloads, the mobile-data bucket is still off.
  5. Change exactly one setting, then repeat steps three and four. Attribute the change before moving on.

For a secondary signal, watch the storage figures. Both Android and iOS expose per-app storage and data counters in system settings, and the cache size reported inside Telegram's Storage Usage screen should grow when auto-download is genuinely working. These counters are operating-system estimates rather than precise instruments, so use them to confirm a direction of change rather than to measure an exact volume.

One caution about interpretation: cache growth over minutes is a weak signal on a fast connection and a strong one on a slow connection. If you want a clean comparison, repeat the test at roughly the same time of day on the same network so that normal variability does not masquerade as a result.

Finally, record the settings you settle on. Users who tune auto-download, then forget the configuration, tend to repeat the same investigation months later after a device migration.

Applicable and Non-Applicable Scenarios

The advice in this guide fits some situations much better than others. Being explicit about the boundary prevents wasted effort.

Where it applies: personal devices where you control both the account and the operating system; cases where media resolves on Wi-Fi and not on cellular; accounts with a metered plan where you want selective rather than blanket pre-fetching; and devices where a recent restore or OS update reset permissions.

Where it does not apply: managed corporate devices where mobile-data permissions are locked by policy and cannot be changed by the user; environments where the network itself blocks Telegram traffic, in which case no client setting will help; and hardware with critically low free storage, where the correct action is to free space rather than adjust download rules.

A middle category deserves a mention. Aggressive vendor battery managers on some Android devices interfere with downloads in ways the user cannot fully control, and the only reliable mitigation is to exclude the app from optimisation. If that option is unavailable on your device, the realistic choice is to keep the media screen awake during large transfers.

Best Practices Checklist for Auto-Download

The following decision rules are intended to be read once and then applied as a standing policy, rather than revisited every time a download misbehaves.

  • Enable photos over mobile data; they are small and rarely problematic.
  • Keep videos and files on Wi-Fi only unless you have a specific need, and use per-chat exceptions for the few conversations that justify the data cost.
  • Leave the roaming bucket disabled unless you know your roaming terms.
  • Set a conservative cache retention window rather than indefinite retention, and audit it after a few weeks.
  • Confirm the system-level cellular permission after any device restore, OS upgrade, or carrier change.
  • Exclude the app from battery optimisation on Android devices with aggressive power management.
  • Change one variable at a time when diagnosing, and write down the final configuration.

Two rules deserve expansion. The first is the photos-versus-videos split: photographs and screenshots are the media most people genuinely need immediately, and they are small enough that pre-fetching them over cellular is rarely a financial problem. Videos are where metered plans get consumed, and they are the category worth gating. The second is the audit habit. Auto-download settings drift over time as you add chats and exceptions, and a five-minute review every few months keeps the configuration aligned with how you actually use the account.

Frequently Asked Questions

Do I need a Premium subscription to download media over mobile data?

No. The per-connection auto-download buckets, the per-type size ceilings, and the per-chat exceptions are available on a free account. Telegram's subscription page lists benefits such as larger upload limits and faster downloads, and that list has evolved over time, so check the in-app subscription screen for the current terms. None of those benefits alter which connection types are allowed to pre-fetch media.

Why does one large video still not download on Wi-Fi after I enabled videos?

Enabling the video category does not remove the size ceiling attached to it. Files above that ceiling are treated as on-demand items and wait for a tap. Compare a short clip and a long recording in the same chat: if the short one auto-downloads and the long one does not, the ceiling is the operative limit and raising it is the fix.

Can a bot or third-party app change my auto-download settings?

No. Auto-download rules, cache retention, and gallery saving are client-side and operating-system controls. Bots operate inside the message layer and cannot reach them. Some third-party bots can re-deliver large media in smaller segments, which may help on a weak network, but that is a workaround rather than a change to your settings. Never share login codes, two-factor passwords, or session strings with any third-party tool.

Will clearing the cache delete my media permanently?

No. Media lives in Telegram's cloud and remains available in the chats; clearing the cache only removes the local copies, which must be downloaded again when you next open them. That re-download is why clearing the cache is a poor first move on a metered connection. Treat it as a targeted remedy for a specific misbehaving chat rather than routine maintenance.

Media works on Wi-Fi but fails on mobile data even though Telegram's toggle is on. What is left?

The operating system layer. On iOS, check the per-app cellular permission and Low Data Mode. On Android, check system Data Saver exemptions, the per-app mobile data permission, and battery optimisation. These controls can deny network access even when the app itself is configured correctly, and they are the most commonly overlooked cause of the Wi-Fi-only pattern.

Conclusion and Next Steps

The Wi-Fi-only pattern in Telegram is rarely a fault. It is the visible result of a layered permission model in which the app, the operating system, and the network each get a veto, and the app-level layer is doing exactly what it was configured to do. The fastest path to a resolution is the tap test: if a deliberate tap downloads the file on cellular, the issue is pre-fetch configuration and the fix lives in the auto-download buckets and their size ceilings. If a tap fails too, leave Telegram and inspect the system permissions, storage headroom, and any proxy in the path.

For most readers the practical next step is small and specific: open the data settings, confirm the mobile-data bucket, decide the size ceiling for videos and files rather than accepting a default, and then use per-chat exceptions for the two or three conversations where immediate delivery genuinely matters. That configuration is a reasonable balance for a metered plan, and it removes the Wi-Fi-only complaint without turning every channel into an automatic download queue. Keep a note of what you chose, revisit it after any device migration, and change one setting at a time whenever something behaves unexpectedly.

One expectation worth setting about the future: this area of the product has been refined repeatedly over the years, and menu labels, the placement of the exceptions screen, and the available size options have all shifted between releases and platforms. The mechanism described here — a connection-aware pre-fetch layer sitting above an opt-in on-demand layer — has been the stable part throughout. When a label no longer matches, follow the structure rather than the wording: find the connection buckets, then the per-type switches and their ceilings, then the system-level permissions, in that order.