Room iframe
Embed the full MediaSFU meeting experience inside an existing page or WebView.
- Best for
- Portals, classrooms, support rooms, and rapid prototypes
- Setup
- Room URL + iframe permissions
- Control
- Room configuration and credential handoff
Start with a complete room, add a focused website action, or build natively with an SDK. “Prebuilt” describes ready-made experiences; iframe embedding is only one available delivery path.
Begin with the smallest surface that solves the workflow. You can move between iframe, widgets, and SDKs without changing the backend.
Embed the full MediaSFU meeting experience inside an existing page or WebView.
Add a join button, click-to-call, AI agent, meeting portal, or operator surface without embedding an entire room.
Use framework-native prebuilt components for speed, or headless APIs and hooks when your product owns the interface.
Simple rule: use an iframe for a whole room, a widget for one visitor action, and an SDK when your application must own the UI or respond directly to MediaSFU events.
Three steps — no build tools, no package installs.
Create a room via the dashboard or REST API. You receive a URL like https://meeting.mediasfu.com/room/...
Paste the URL into an <iframe> with allow="camera; microphone; display-capture; autoplay". Done.
Participants open your page and land in the room. Layouts, controls, and reconnection are handled by MediaSFU.
Iframes suit complete rooms. Widgets and SDKs are better when the entry point or application behavior must be more specific.
Build click-to-call, AI agent, meeting portal, or dashboard embeds in Widget Studio, then secure them to approved domains.
Mount ready-made meeting components when speed matters. Choose headless hooks, events, and media APIs when your own interface must drive the experience.
Use the iframe for a complete room, or start in Widget Studio when the page only needs a focused call, join, or AI action.