A read-only embed places a live copy of a diagram inside another page, like a wiki, a doc, Notion, or your own site. It shows the canvas, hides all the editing tools, and stays up to date as the diagram is edited. It is the simplest way to keep a diagram visible where your readers already are.
What an embed shows
The embed is built from a share link, so it carries that link's diagram, but it is always read-only regardless of the link's role. Even an edit link, when embedded, renders as a viewer; editing happens in the full editor, one click away.
Inside the frame, the embed:
- shows the canvas with pan, zoom, and pinch,
- hides the header, tabs, and every floating panel, leaving a clean view,
- defaults to the hand (pan) tool, since there is nothing to select,
- keeps a small Open in livediagram badge in the corner that opens the full share view in a new tab,
- shows a compact tab switcher when the diagram has more than one tab.
Because the embed joins the same realtime room as any viewer, it live-updates: when the diagram changes, the embedded view follows along.
Adding an embed to a page
<iframe> snippet.The snippet comes with a sensible default size and a hairline border, which you can adjust in the markup. If the diagram has a share password, readers are prompted for it inside the embed frame, and the dialog notes this when you copy.
Privacy and self-hosting
An embed only exposes what the share link exposes, and only as a read-only view, so there are no editing actions to misuse. Embeds also work on self-hosted instances with no external services: the snippet builds its URL from your own origin, so a self-hosted diagram produces a self-hosted embed.
Embedding several diagrams across a wiki is a tidy way to keep architecture and flow diagrams beside the docs that reference them, always showing the latest version.
Was this article helpful?