One Spotify Song Greys Out and Skips While the Playlist Keeps Playing

Two faults get reported with the same sentence and they need opposite fixes. In the first, a single track sits greyed out and the app jumps straight past it. In the second, the track starts, the progress bar moves, and then playback cuts to the next song early. Sorting which one is on screen takes about thirty seconds and removes most of the guesswork that follows.

Fastest split: open the same track from Search rather than from the playlist. If it plays there, the cause lives in that playlist. If it greys out there too, the cause lives on the account or in the catalog. If it plays but ends early, nothing is greyed out at all and the problem is a transition setting or a plan limit.

Sort the Fault Before Changing Any Setting

Spotify uses one on-screen message for content it will not start: "This content is not available." That message covers several unrelated conditions, which is why "greyed out" alone is not a diagnosis. Spotify's own FAQ on greyed-out content lists five reasons the message appears, and they split cleanly into playlist-level and account-level causes.

Run the Search test first, then check one more thing: whether the greying follows the track everywhere or stays in one place. A track hidden inside a playlist "can still be played in other playlists where you haven't hidden them," in Spotify's wording. A track pulled from the regional catalog greys out in every playlist, in Search, and on the artist page at the same time.

The Five Documented Reasons a Track Will Not Start

1. The track was hidden inside that playlist

Hiding is the cause most often mistaken for a bug, because the result is exactly the reported symptom. Spotify's own description of what hiding does is blunt: "The song will be grayed out and skipped." It is a one-tap action sitting in the same overflow menu as Add to playlist, so it gets triggered by accident constantly.

Hiding applies to playlists made by Spotify or by someone else, not to playlists you built yourself. To reverse it on phone or tablet, tap the menu dots next to the greyed track and choose Show in this playlist, or tap the remove icon beside it. On desktop, the remove icon next to the track toggles the state both ways. Because hidden state is per playlist, the same song still plays normally everywhere else, which is the fingerprint that separates this from a licensing removal.

2. The explicit content filter is switched off

When playback of explicit-rated content is disabled, tracks carrying the explicit tag grey out and get skipped. The paths, as published by Spotify:

• Phone and tablet: profile picture > Settings and privacy > Content and display > Allow Explicit Content
• Desktop: profile picture > Settings > Explicit Content > Allow playback of explicit-rated content

One detail that explains the "it changed by itself" reports: on a Premium Family plan, the plan manager can allow or block explicit-tagged content for other members from the family account page. If the switch on the device looks correct and the tracks are still greyed, the setting may be enforced from the plan side rather than the device side.

3. The artist is blocked on that account

Spotify lists blocked artists as a cause of greyed-out content. Blocking is account-wide, so every track by that artist greys out at once across playlists and Search. If an entire discography went grey on the same day rather than one song, check this before assuming a catalog change.

4. The regional catalog changed

This is the cause people mean when they say a song "expired." Spotify states that content availability "may vary over time and between countries" and that this "depends on permissions from rights holders." Nothing about that is device-side, so restarting, reinstalling, and clearing cache all do nothing.

Spotify's own confirmation method is comparison: try the track on another device or another account, ideally one in a different country. If it fails on your account but plays on an account in another region, the track is out of catalog where you are. There is no setting that overrides this and no published date for when a de-licensed track returns.

5. It is a local file that is no longer on the device

Imported local files grey out when the underlying file is gone, moved, or on a drive that is not mounted. On desktop, the folder list Spotify reads from is at profile picture > Settings > Library > Show Local Files, then under Show songs from, where the folders it is allowed to read are toggled on. A track imported from a folder that has since been renamed will stay in the playlist and stay unplayable until the folder is added back.

When the Track Starts and Then Cuts Out Early

Nothing above applies here. If the progress bar moves and then playback jumps, three published playback settings are the first place to look, and all three sit under Playback.

Crossfade is the usual culprit for "the song ends before it finishes." Spotify describes it as overlapping two tracks by fading out of the first while fading in the next. Set high, the tail of every track disappears under the head of the following one, and on tracks with long outros that reads as premature skipping. Drag the slider to zero, or switch Crossfade songs off on desktop, and play the same track again.

Automix produces the same complaint on a narrower set of content: Spotify says it gives beat-matched seamless transitions on select Spotify playlists and that it "works even on Shuffle." It is scoped to certain Spotify-curated playlists, which is why the behaviour appears on some playlists and not others with the setting untouched.

Gapless playback works in the other direction, removing pauses between tracks. It is worth checking when the complaint is that two songs run into each other rather than that one gets cut short.

One constraint applies to all three and is easy to miss: Spotify states these features cannot be used with Spotify Connect. If playback is being pushed to a speaker, a TV, or a car head unit through Connect, changing crossfade on the phone will not change what the speaker does.

Two plan-level and account-level causes of skipping

Skip limits on the free plan. Spotify's description of Premium benefits includes "unlimited skips and full control over what plays next," which means the free plan does not have them. Its shuffle documentation also states that Smart Shuffle is always active on mobile for listeners on the free plan. Between forced shuffle and a capped skip allowance, a free account on a phone can produce a play order nobody chose, and it is not a fault.

Another device took over. Spotify's device documentation states plainly: "You can only play on one device at a time, per Spotify account." If the account is shared, or a second device is signed in somewhere in the house, playback stopping mid-track is the expected outcome rather than a playback bug. Checking the device list before touching cache saves a lot of wasted effort.

Downloads That Are Present but Refuse to Play

Offline listening has three hard numbers published by Spotify, nearly every report of downloads vanishing lands on one of them.

Spotify's offline article gives the ceiling as "as many as 10,000 tracks on each of up to 5 different devices," and the check-in requirement as "at least once every 30 days to keep your downloads." Exceed five devices and downloads are removed from the device used least recently, which is why a rarely used tablet is usually the one that comes back empty.

A separate and very common trap: Offline mode left switched on. With it on, everything that is not downloaded greys out, which looks identical to a catalog problem until the switch is found. It sits at profile picture > Settings and privacy > Data-saving and offline > Offline mode on phone and tablet. On the Windows desktop app the route is the three horizontal dots at the top of the screen > File > Offline Mode; on Mac it is the Spotify menu in the Apple menu bar, then Offline Mode.

Cache, Storage and Reinstall, in That Order

Clearing cache is the correct step when playback stutters or stalls rather than when a single track is greyed out. The published paths, current as of the August 2026 support articles:

• iPhone and Android: profile picture > Settings and privacy > Data-saving and offline > under Storage, tap Clear next to Clear cache
• Desktop: profile picture > Settings > scroll to Storage > Clear cache

Free space is worth checking at the same time, and the two Spotify articles that mention it give different figures: the playback troubleshooting article asks for at least 250MB of available memory, while the storage article recommends "at least 1GB of free memory on your device for Spotify." Treat 1GB as the working target since it is the higher of the two.

One documented consequence of clearing cache: Spotify's Offline Backup feature, which is described as being "filled with music you can play offline, no downloads required" on Premium for mobile phones, Android Auto and CarPlay, may not appear if the cache has been cleared or the app was recently reinstalled. If a car head unit stopped showing offline music right after a cache clear, that is the documented behaviour rather than a fault.

Reinstalling comes last, and only for stalls that survive everything above, because reinstalling removes downloads and they have to be fetched again.

What Spotify Does Not Publish

Several numbers that get quoted confidently around this symptom are not in any Spotify support article, and guessing at them is how bad troubleshooting advice spreads.

• The crossfade range in seconds. Both the crossfade article and the track transitions article describe a slider and never state its minimum or maximum.
• The exact free-plan skip allowance. Spotify states Premium gives unlimited skips; it does not publish the number of skips a free account gets, or the window it resets in.
• Whether clearing cache deletes downloads. The storage article describes cache and downloads as two separate stores but never states what clearing one does to the other. Assume downloads may need re-fetching and confirm on the device.
• Which playlists Automix covers. "Select Spotify playlists" is the whole specification; there is no published list.
• When a de-licensed track returns. Availability depends on rights holder permissions, and no timeline is published.
• Codec or buffer behaviour. Spotify publishes nothing about internal decoding or buffering thresholds, so any explanation of skipping built on those is invention.

When This Doesn't Apply

This frame assumes one or a few tracks misbehave while the rest of the library is fine. It does not fit these situations:

• Nothing plays at all. A whole library that will not start points at sign-in state, network, or a service-side incident. Check Spotify's status account and the Ongoing Issues board before touching settings.
• The progress bar moves but there is no sound. That is an audio output problem, usually a Bluetooth device holding the stream. Playback is working; routing is not.
• Podcast episodes rather than music. Episode availability follows a different rights and hosting model, and an episode pulled by its publisher will not be recovered by any of the steps above.
• Playback through a car, TV or smart speaker. Once Spotify Connect is in the chain, the transition settings above are out of play and the integration's own behaviour dominates.
• Modified or third-party clients. Nothing in Spotify's documentation describes their behaviour, and none of these paths are guaranteed to exist in them.
• Managed accounts for young listeners. Content restrictions on those accounts are set by the plan manager, so the device-side explicit switch may not be the control that matters.

The Order to Work Through

1. Play the track from Search. Plays there but not in the playlist means it was hidden in that playlist.
2. Confirm Offline mode is off, on every device involved including desktop.
3. Check Allow Explicit Content on the device, then on the family plan page if the account is on Premium Family.
4. Check whether the artist is blocked, especially if a whole discography greyed out at once.
5. Test on a second account or a second region to confirm a catalog change. If it fails everywhere, no local fix exists.
6. For early cut-offs, set Crossfade to zero and retest the same track, then check Automix and Gapless playback.
7. Confirm no second device is signed in and playing, since only one device at a time can play per account.
8. For downloads: confirm the account has been online in the last 30 days, that fewer than five devices hold downloads, and that at least 1GB is free.
9. Clear cache, then update the app, then reinstall, in that order, and only for stalling rather than greying.

Working in that sequence keeps the cheap, reversible checks ahead of the destructive ones. Reinstalling first, which is the most common instinct, costs every download on the device and fixes none of the five documented causes of a greyed-out track.