How to add Cross-Origin-Embedder-Policy on Cloudflare
Last updated · Reviewed by a CISSP-certified security practitioner
To add Cross-Origin-Embedder-Policy on Cloudflare, set the header in Rules → Transform Rules → Modify Response Header (or a Worker) with the value require-corp. Requires embedded resources to opt in (enables cross-origin isolation). Purge cache, then check the response with curl -I. Then confirm it with curl -I or a free FixSecurityHeaders scan.
What does Cross-Origin-Embedder-Policy do?
COEP makes the page refuse cross-origin resources that haven't opted in via CORP or CORS. Combined with COOP it enables cross-origin isolation.
Risk if missing: Informational: mainly needed for SharedArrayBuffer and high-precision timers.
What is the Cloudflare configuration?
Add this to Rules → Transform Rules → Modify Response Header (or a Worker):
// Option A: Rules → Transform Rules → Modify Response Header → "Set static"
// Cross-Origin-Embedder-Policy: require-corp
// Option B: Cloudflare Worker
export default {
async fetch(request, env, ctx) {
const res = await fetch(request);
const out = new Response(res.body, res);
const h = out.headers;
h.set("Cross-Origin-Embedder-Policy", "require-corp");
return out;
},
};How do I add it step by step?
- Open Rules → Transform Rules → Modify Response Header (or a Worker).
- Paste the Cross-Origin-Embedder-Policy configuration shown below.
- Purge cache, then check the response with curl -I.
- Run curl -I https://yourdomain.com and look for the cross-origin-embedder-policy line.
- Scan your site on FixSecurityHeaders to confirm the grade improved.
How do I verify it worked?
curl -sI https://yourdomain.com | grep -i "cross-origin-embedder-policy"
# expected:
# cross-origin-embedder-policy: require-corpCheck your site now
Free scan, instant grade, exact fixes for your stack.
What are the common mistakes?
- Easily breaks third‑party images, fonts and embeds. Consider credentialless, and only deploy if you need isolation.
- Transform Rules work on all plans; Workers give full control.
- Cloudflare's own HSTS setting lives under SSL/TLS → Edge Certificates.
Quick reference
| Header | Cross-Origin-Embedder-Policy |
|---|---|
| Recommended value | require-corp |
| Stack | Cloudflare |
| Where | Rules → Transform Rules → Modify Response Header (or a Worker) |
| Compliance | OWASP ASVS V14.4 |
FAQ
What value should I use for Cross-Origin-Embedder-Policy?
A safe default is require-corp. Easily breaks third‑party images, fonts and embeds. Consider credentialless, and only deploy if you need isolation.
Why isn't Cross-Origin-Embedder-Policy showing up on Cloudflare?
Transform Rules work on all plans; Workers give full control. Also clear any CDN or page cache, and check you edited the config that actually serves your domain.
Does Cross-Origin-Embedder-Policy affect SEO or performance?
No measurable performance cost — it's a few bytes per response. It doesn't affect rankings directly, but a misconfigured policy can break page resources, so test before enforcing.
Which compliance frameworks reference Cross-Origin-Embedder-Policy?
OWASP ASVS V14.4.
Related guides
- Cross-Origin-Embedder-Policy explained
- Cross-Origin-Embedder-Policy on Nginx
- Cross-Origin-Embedder-Policy on Apache
- Cross-Origin-Embedder-Policy on IIS
- Cross-Origin-Embedder-Policy on Vercel
- Strict-Transport-Security on Cloudflare
- Content-Security-Policy on Cloudflare
- X-Content-Type-Options on Cloudflare
- X-Frame-Options on Cloudflare