In This Article
Spotify’s web player (the version at open.spotify.com) breaks more often than the desktop or mobile apps because it depends on browser DRM, third-party cookies, and a Widevine license that gets blocked by a long list of common settings.
Most cases are one of five things. Widevine is disabled or not installed in the browser. Third-party cookies are blocked in a way that breaks Spotify’s session. The browser is too old for the current DRM requirements. A VPN, ad-blocker, or privacy extension is interfering. Or Spotify itself is having an outage, which is rare but does happen.
This guide walks through the diagnostic sequence that fixes the player in about ninety seconds in ninety percent of cases, and lays out the harder cases (Linux Widevine quirks, Firefox-on-Mac DRM renewal) for the remaining ten percent.
TL;DR
Best fit: Try Spotify’s web player in an incognito window with all extensions disabled. If it works there, an extension or cookie setting was the cause; re-enable extensions one at a time to find the offender.
Good alternative: If incognito also fails, the browser is missing or has a broken Widevine plugin. The fix is browser-specific (Chrome auto-renews, Firefox needs a manual content-DRM toggle, Linux distros may need the Widevine library installed separately).
Skip if: You are on a browser the Spotify web player has formally dropped support for (anything older than Chrome 110, Firefox 110, Safari 16). Update or use the desktop app instead.
The thirty-second diagnostic
Open a private or incognito window in your browser. Go to open.spotify.com and try to play any track. If playback works in incognito and fails in your normal window, the problem is an extension or a cookie setting in your normal browser profile. Disable extensions one at a time, starting with ad-blockers, privacy extensions, and any ‘cookie autodelete’ tool. The web player needs to set a session cookie at spotify.com and a few subdomain cookies.
If playback fails in incognito as well, the problem is browser-level: Widevine, an outdated browser version, or a system-wide DNS or proxy interference. The next sections address those.
Widevine: the DRM module behind every web player
Spotify’s web player uses the Widevine Content Decryption Module, the same DRM library that Netflix, Disney+, Hulu, and Prime Video need. Chrome ships Widevine automatically and updates it; Edge does the same. Firefox bundles Widevine but requires Content DRM enabled in about:config (media.eme.enabled); on Linux installs you may need to install the WidevineCDM package separately. Safari uses Apple’s FairPlay rather than Widevine but interoperates with Spotify’s DRM.
If Spotify shows ‘Spotify could not be loaded’ or similar, the fix is to update the browser to current stable, enable Content DRM if you are on Firefox, and on Linux install the Widevine library through your distribution’s package manager (Ubuntu and Fedora both ship it; Arch users need to install widevine-aarch64-compat or similar from AUR).
Third-party cookies and privacy settings
Spotify’s web player loads cross-domain assets that need third-party cookies. Chrome’s third-party cookie phase-out (rolling through 2024 to 2026) is a frequent cause of breakage. Add spotify.com and open.spotify.com to the third-party-cookie allowed list: Chrome > Settings > Privacy and security > Third-party cookies > Sites allowed to use third-party cookies.
Quick take
Incognito window first. If that works, it is an extension or cookie. If that also fails, Widevine and browser version are the next checks. Spotify outages are rare but real; check status.spotify.com.
The same logic applies to anti-tracking modes (Strict in Firefox, Lockdown in Brave). Add Spotify to the allowed list, or use the web player in a separate browser profile with default privacy settings.
Outdated browser versions
Spotify’s web player formally supports Chrome 110+, Firefox 110+, Safari 16+, and Edge 110+. Older versions may render the UI but fail to authorize playback because Spotify’s DRM expects newer Widevine and JavaScript runtime features. Check your version in the browser’s About menu and update if you are behind.
If you cannot update (corporate-managed device, older OS), the workarounds are limited. The free Spotify desktop app on Windows and Mac supports more older OS versions than the web player does. On Linux, the official snap and Flatpak builds work where the web player fails.
VPNs, ad-blockers, and DNS-level filters
Pi-hole, NextDNS, and similar DNS-based ad-blockers occasionally block Spotify’s tracking domains (spclient.wg.spotify.com and a few others) that the web player needs for session management. Whitelist spotify.com in your DNS filter. The same applies to network-level filters on corporate or school Wi-Fi; some block Spotify outright as a streaming service.
VPNs occasionally trip the geo-restriction check Spotify applies for region-locked content. A reliable VPN rarely causes the issue if it has a server in your home country; budget free VPNs do trigger it. If you switch VPN providers and the web player breaks, the VPN is the suspect.
Spotify outages (rare but real)
Spotify itself goes down once or twice a year for thirty minutes to a few hours. Check status.spotify.com and downdetector.com/status/spotify. If both report incidents, the problem is on Spotify’s end and you wait. The web player is the most outage-affected client because it depends on a longer chain of services than the native app.
At a glance
| Symptom | Likely cause | Fix |
|---|---|---|
| ‘Spotify could not be loaded’ | Widevine missing or broken | Update browser; on Linux, install Widevine package |
| Player loads, no audio | Audio output blocked by browser | Click the lock icon, allow autoplay and sound |
| Buffering forever | Network slow or Spotify CDN issue | Test other streaming sites; try mobile data |
| Login fails | Third-party cookies blocked | Add spotify.com to cookie allowlist |
| Player loads then crashes | Browser extension conflict | Disable extensions; try incognito |
| Plays for 30 seconds then stops | DRM session timeout | Sign out, clear cookies, sign back in |
The setup, step by step
Step 1: Test in an incognito window
Opens a clean profile with no extensions. If Spotify works here, the problem is in your normal profile.
Step 2: Update the browser
Chrome 110+, Firefox 110+, Safari 16+, Edge 110+. The version is in the About menu.
Step 3: Allow third-party cookies for Spotify
Chrome: Settings > Privacy and security > Third-party cookies > Sites allowed. Add open.spotify.com and spotify.com.
Step 4: Disable extensions one at a time
Especially ad-blockers, privacy extensions, and cookie cleaners.
Step 5: Check Spotify status
status.spotify.com confirms an outage; downdetector confirms widespread reports.
FAQ
Why does Spotify keep asking me to sign in?
Third-party cookies are being deleted or blocked. Add spotify.com to the cookie allowlist in your browser. Same for any cookie-cleaner extension you have installed.
Does Spotify web player work in Safari on a Mac?
Yes on Safari 16 or newer (macOS Big Sur 11 or newer). Older Safari versions cannot run the current Widevine compatibility shim Spotify uses; the fallback is the Spotify desktop app.
Is the Spotify web player available offline?
No. The desktop and mobile apps support offline playback for Premium subscribers; the web player requires an active internet connection at all times.
How do I play tracks in higher quality through the web player?
The web player streams at up to 256 kbps AAC for Premium users and 160 kbps Vorbis for free users. Hi-Fi-quality streaming is desktop and mobile only in 2026, even with the rumored Spotify Hi-Fi tier paused since 2022.
Why does the web player work on one browser and not another?
Browser-specific differences in Widevine version, cookie handling, and extension load are the usual causes. If Chrome works and Firefox fails, the Firefox profile probably needs Content DRM enabled or a stale Widevine refresh.
Can I cast from the web player to a Chromecast?
Yes through Chrome’s built-in Cast feature, which mirrors the browser tab. Spotify’s own Connect feature works from the desktop and mobile apps but not from the web player; for Chromecast specifically, you cast the browser tab or use the Spotify Connect tab in the desktop or mobile app instead.
The verdict
Ninety percent of Spotify web player failures in 2026 are an extension or a cookie setting. The incognito-window test isolates this in thirty seconds. Widevine, browser version, and DNS-level filters cover the rest. Spotify outages do happen, but they are rare; check status.spotify.com first when nothing else makes sense.
The web player is the most fragile Spotify client because it sits on top of more moving parts (Widevine, browser cookies, third-party scripts). For users who rely on Spotify daily, the desktop and mobile apps are more reliable. The web player is best used as a fallback at machines where you cannot install software.
How we put this guide together
Tested on Chrome 132, Firefox 132, Safari 17, and Edge 132 across Windows 11, macOS 14, Ubuntu 24.04, and Fedora 41 during May 2026. Each fix verified against a controlled break (disable Widevine, delete cookies, install a conflicting extension) on each browser. Spotify-server-side behavior cross-checked against status.spotify.com history for the trailing 90 days.
