Webflow sets restrictive X-Frame-Options to prevent sites from being embedded in iframes. This security setting cannot be edited directly through the Webflow Designer or hosting settings.
1. Webflow’s Default Behavior
- All Webflow-hosted sites automatically send the HTTP header X-Frame-Options: SAMEORIGIN.
- This prevents other domains from displaying your site inside an iframe, unless it’s being embedded on the same origin (i.e., same domain/subdomain).
2. No Way to Modify This via Webflow
- Webflow does not provide access to server-side settings where you could remove or change the
X-Frame-Options
or implement a Content Security Policy (CSP) to allow iframe embedding. - There is also no Webflow setting, custom code, or workaround (such as inserting meta tags) that will override the server-level header.
3. Alternative Solutions
If iframe embedding is a must, consider:
- Hosting the site elsewhere: You can export your Webflow site’s code (for paid plans) and host it externally on a custom server (e.g., Netlify, Vercel, or traditional hosting) where you control server headers.
- On the external host, you can remove or customize the
X-Frame-Options
header or use a Content-Security-Policy that includes frame-ancestors
, like: Content-Security-Policy: frame-ancestors yourdomain.com;
.
Summary
Webflow does not allow modification of X-Frame-Options headers, so you can’t embed a Webflow-hosted site in an iframe on another domain. To allow iframe embedding, export the site and host it elsewhere where you can control HTTP headers.