Third-party cookie blocked in Chrome
The user, or a Chrome setting, blocks third-party cookies. The page in your frame is on another site, so its cookies are third-party, and Chrome does not send or keep them.
- Chrome
- Firefox
- Safari
Updated
Third-party cookie blocked in Chrome due to Chrome flags or browser settings
The frame loads without its cookies. The Issues tab of DevTools shows a cookie issue for the blocked cookie.
Third-party cookie blocked in Chrome due to Chrome flags or browser settings
The frame loads without its cookies.
Cookie “session” has been rejected as third-party.
The frame loads without its cookies. Safari blocks third-party cookies by default.
On this page
What it means
Why it happens
Check the page
See the headers the page sends now
Fix it if you own the site
Set-Cookie: session=abc123; Path=/; Secure; HttpOnly; SameSite=None; Partitioned
A partitioned cookie is a separate copy for each top site. A user who signs in on your site in a new tab is still signed out in the frame.
If you do not own the site
- Open the page in a new tab
Link to the page so the user signs in on the site itself, where its cookies work.
- Use the official embed
Some services give an embed that needs no login, or one that is made for frames.
- Ask the owner
Ask them to set their cookie with SameSite=None, Secure and Partitioned.