For years, Spotify users have run into a familiar frustration: open the phone’s storage settings, and Spotify is sitting near the top, holding onto gigabytes of space nobody remembers agreeing to give it. According to a report from Android Authority, which dug through the Spotify app’s code, a fix may be on the way in the form of a new “Cache Limit” feature.
The root of the problem is how streaming apps typically work. Every time a song or podcast plays, Spotify stores a temporary copy of that data, along with cover art, on the device. That’s a fairly standard practice across the streaming industry, and it exists for a reasonable reason: it keeps playback smooth and reduces data usage when something gets replayed. The issue is that this cache has operated as a black box. Users can’t set a limit on it, so it accumulates in the background, separate from the offline downloads people actually choose to save.
Right now, the only workaround is manual. Users can clear the cache through Settings, Data Saving & Offline, then Clear Cache, but that’s a repetitive chore rather than a real solution, and it’s one that Spotify’s own community forums and Reddit threads have been requesting a fix for going back nearly a decade.
Based on code found in Spotify for Android version 9.1.88.815, the upcoming feature would let users set a maximum size for the cache directly, rather than clearing it blind and hoping for the best. The interface reportedly includes contextual warnings: choosing a smaller limit triggers a note that a small cache may affect playback and increase data usage, while a larger limit comes with the opposite trade-off, smoother playback at the cost of more storage. A “Spotify recommended” default appears to be included for users who’d rather not fine-tune the number themselves. The prompt would also reportedly surface right after a user manually clears their cache, closing the loop between clearing space and setting a boundary so the problem doesn’t just return.
Crucially, this is described as a cache limit, not a downloads limit. Saved songs and podcasts marked for offline listening are stored separately and wouldn’t be affected by whatever ceiling a user sets.
This kind of change matters more now than it might have a few years ago. Storage prices have climbed, and the cost gap between base and upgraded storage tiers on many phones has widened, making wasted space a more tangible cost to consumers rather than just an abstraction. Rival streaming and media apps have faced similar criticism over hidden storage consumption, so a user-facing cache control, if it ships, would put Spotify more in line with basic expectations for app storage transparency rather than ahead of the curve.
It’s worth treating this as unconfirmed for now. The feature was found in app code rather than announced by the company, Spotify hasn’t commented publicly, and there’s no indication yet of a rollout timeline. Features like this typically surface first in beta testing before reaching the wider user base, and code discovered in an APK doesn’t always make it to a public release in the same form, or at all.
What is clear is that the appetite for this kind of control has existed for a long time. Whether Spotify follows through will say something about how seriously the company takes small, cumulative frustrations versus flashier feature announcements.
