August 19, 2026

Zendesk Guide articles are edited in a rich-text editor with a source view, and by default the platform sanitises markup that it considers unsafe -- iframes included.
There is an administrative setting governing this, which makes embedding possible and is worth a moment's thought first.
Zendesk Guide has a setting that permits unsafe HTML in articles, and enabling it is what allows iframes to survive saving. Find it in Guide admin settings; the exact wording and location have changed across Zendesk versions, so search your admin rather than following a fixed path.
Understand what it does before enabling it: it relaxes sanitisation for everyone who can author articles, not only for you. On a large team that is a real decision rather than a formality.
Many organisations will not relax HTML sanitisation across a help centre, and that is a defensible position. Use a linked screenshot instead -- it is unaffected by sanitisation and works in every theme.
Label it with what the demo shows and how long it takes, since help centre readers are mid-problem and impatient.
The ones your agents link most often. Pull the list of most-viewed articles and most-linked macros, and start there -- that is where a demo removes the most repeated explanation.
Setup and configuration articles benefit most, because they describe multi-step UI work that prose handles badly and a demo handles naturally.
Click through it — the same kind of demo you can record of your own product.
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →