iframes in Zendesk Guide
You paste an iframe into a Zendesk article, save, and it disappears. Here's why that happens and what actually works instead.
Why your iframe vanished from Zendesk
Almost every report of "iframes do not work in Zendesk" comes down to the same thing: the article editor sanitises HTML. Guide runs your content through a filter, and elements it does not consider safe get stripped on save. You paste the embed, it looks fine, you hit save, and the markup is gone.
The first fix is to use the source code view rather than the rich text editor. The rich text editor is not a reliable place to author raw HTML at all. Switch to source, paste the markup there, and save from there.
The second thing to know is that the sanitiser isn't the same everywhere. Content in a theme template, which you control, is treated differently from content typed into an article by an agent, which Zendesk treats as untrusted. That is deliberate. An unfiltered HTML field that any content author can write to is an XSS hole, and Guide is not going to hand you one.
What generally works
Well known embed providers tend to survive, because Guide recognises them.
What tends not to survive is anything with inline JavaScript, <script> tags, event handler attributes like onclick, or an iframe pointing at an obscure or self-hosted domain. Anything requiring a script tag alongside the iframe is very unlikely to work in an article body.
Test properly. Paste it, save, then reload the published article as a signed-out end user in a private window. An article that looks right in the editor and right to you as an admin can still be broken for everyone else.
The things that break embeds even when the HTML survives
Your markup can save cleanly and the embed can still show a blank box. Three usual suspects.
The target site refuses to be framed. Plenty of sites send X-Frame-Options: DENY or a restrictive frame-ancestors policy. That's the other site saying no, and there is nothing you can configure in Zendesk to override it. Check the browser console: a refused-to-frame message tells you immediately that this is the problem and saves an afternoon.
Mixed content. Your help centre is HTTPS. If the iframe source is HTTP, browsers block it silently. Always use HTTPS sources.
Authentication. An embed pointing at something behind a login shows a login screen or nothing, and third party cookie restrictions in modern browsers make embedded authenticated content increasingly unreliable. Do not build a process on it.
Safer alternatives, mostly better anyway
Before you fight the sanitiser, ask whether an iframe is the right shape at all.
That last one is the answer more often than people expect. If you find yourself pasting the same iframe into article after article, it belongs in the template.
If you genuinely need it in the article
Keep it to one embed per article, use HTTPS, prefer a well known provider, set explicit width and height so the page does not jump while it loads, and add a plain text link to the same content immediately below it. That link is your fallback for every reader whose browser, network or corporate policy blocks the frame, and there are more of them than you think.
Then check it again after any theme update. Guide changes, sanitiser behaviour changes, and an embed that worked last year is exactly the kind of thing that silently stops working without anyone noticing until a customer mentions it.
Frequently asked questions
Can you embed video in a Guide article?
Yes, and that's the main legitimate case. Embed video Zendesk Guide articles through the source editor, and a Zendesk help center embed of anything else is likelier to be stripped.
Why does Zendesk remove my iframe when I save?
The article editor sanitises HTML it doesn't consider safe. Use the source code view rather than the rich text editor, and expect scripts and unknown domains to be stripped.
Can I embed a YouTube video in a Zendesk article?
Yes, that is the case that works most reliably. Paste the standard embed iframe in the source view and check the published article as a signed-out user.
My iframe saves but shows a blank box. Why?
Usually the target site refuses to be framed via X-Frame-Options or a frame-ancestors policy. Check the browser console. Mixed HTTP content is the other common cause.
Is there a way to allow any iframe in Guide articles?
No global switch to disable sanitising, and you would not want one. For content you fully control, put the embed in the theme template instead of the article body.
What's the best alternative to an iframe?
A screenshot with a link underneath, in most cases. It loads faster, works on mobile, and never breaks because somebody changed a security header.
Embeds don't answer questions
A help centre reduces tickets. Removing duplicates removes the ones that got through twice.
Start free trial14-day free trial. No credit card required.