Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Plan
Premium
Country
Argentina
Device
(Macbook Pro late 2020)
Operating System
(macOS 15.4.1 (Sequoia))
My Question or Issue
Hi everyone,
I’m working on a web-based project where I embed public Spotify playlists using the official embed URL format:
https://open.spotify.com/embed/playlist/{playlistId}
Until yesterday, everything was working perfectly: users with an active Spotify session could see the embed and play music directly from the iframe, no extra login required. Then, overnight, this behavior broke — without any changes on my end.
The embed still loads visually, but tehre are no playback controls. The browser console throws the following error:
Refused to frame 'https://accounts.spotify.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors https://open.spotify.com".
This suggests that Spotify is now blocking iframe playback from external domains, even when the user is already logged in via the browser.
Confirmed the playlist is public.
Used the official Spotify embed URL as recommended.
Ensured the user is logged in to Spotify in the same browser.
Removed all query params like view=list or theme.
Tried in different browsers and environments (dev + production).
Despite all this, the embed no longer allows playback and consistently throws the same CSP error.
Has there been an official change to the embed behavior or CSP restrictions recently?
Is there any supported way to enable playback from the embed iframe without using the full OAuth + Web Playback SDK flow?
Is this the expected behavior now, or is this an unintended regression?
This change happened literally overnight. I implemented the embeds yesterday, tested across devices — everything worked. Today, it’s broken without touching a line of code.
Any clarification or guidance would be greatly appreciated. Thanks!
i am facing same issue also
Me too !
I'm having the same problem using Chrome on a 2015 MacBook Pro and brand new M4 MacBook Pro, but players are working perfectly on my Chromebook.
And then just like that it was working again . . . .
Would be nice to know what happened, and why?
Same error with my project, I double checked that the embed creation popup code matches mine.
This issue seems to have reappeared today.
Can confirm, it seems to work sometimes but 9/10 of times I get 503 or 504 error codes.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…