Credentialless cross-origin embedding
Allows selected cross-origin no-CORS resources to load without credentials under COEP.
Support in current browsers
Checked against the current browser versions recorded in MDN browser data 8.0.7.
| Browser | Minimum | Outcome | Reason |
|---|---|---|---|
| Chrome | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Edge | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox | 152 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Safari | 26.5 | Not supported | At least one required mapped feature is not available at this browser baseline. |
| Chrome for Android | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Firefox for Android | 152 | Not supported | At least one required mapped feature is not available at this browser baseline. |
| Safari on iOS | 26.5 | Not supported | At least one required mapped feature is not available at this browser baseline. |
| Android WebView | 150 | Works | Every required mapped BCD feature is available without a recorded qualification. |
| Samsung Internet | 29.0 | Works | Every required mapped BCD feature is available without a recorded qualification. |
What this feature can and cannot do
Helps protect against
- Credential-bearing cross-origin resource inclusion
- Isolation deployment gaps
Does not guarantee
- Public resource disclosure
- Application authorisation
- CORS correctness
What you need before using it
- COEP deployment
- A resource inventory that tolerates credential omission
Fallback to keep in place
Use require-corp with explicit CORS or CORP opt-in from embedded resources.