Real-time studio rendering
The studio’s browser composition implementation builds a timeline from prepared media and renders its visual layers during playback. Its browser engine uses WebCodecs for video decoding, WebGL2 for compositing and Web Audio for the audio timeline, with frame updates driven by the browser’s animation clock.
This supports a live authoring and preview experience: play, pause, seek and inspect the prepared story without first treating every preview as a finished exported MP4. Compatible browser capabilities and available source media are required.
Real-time composition means prepared media is assembled for studio playback. It does not mean a generative model produces new footage instantly, and it does not establish that every delivered personalized video avoids a server render.
Interactive features with a clear purpose
Studio playback controls let the person creating the campaign play, pause, seek, adjust audio and inspect the experience. Audience and creative controls let them explore different versions before rollout.
The interactive illustration on the homepage demonstrates the idea directly: change an audience or first name, scrub the composition and open an example next step. It uses prepared artwork and text drawn in the browser. It is a marketing demonstration, not a connection to the product’s video-rendering service.
Try the live composition illustration ↗Studio, export and embed serve different jobs
Real-time browser playback of the prepared creative timeline.
Render a finished MP4 for the supported delivery workflow.
The documented development implementation plays an existing rendered MP4 with controls, branding and a CTA.
The embeddable player is a development implementation; its documentation does not establish a general production rollout. Its supported design includes a configurable call to action, playback commands and events for a host application, using scoped playback sessions.
Branching stories, in-video forms and new personalization driven by host context are not established by that embed implementation. Confirm the exact player, deployment and supported interaction before integrating it.
Evaluate the rendering path you will actually use
Ask whether the target experience is studio preview, an exported campaign video or embedded playback. Then evaluate browser support, media readiness, generation time, export latency, storage and delivery for that path.
A faster preview does not by itself prove lower total cost per delivered video. The performance and evaluation guide outlines the evidence needed for cost, experiments and enterprise rollout decisions.
QUESTIONS, WITH CONTEXT
Go one question deeper.
Explore the details that matter for this part of the workflow.
Real-time composition
Understand what is happening during studio playback.
What does real-time rendering mean in the Engage studio?
Prepared media and visual layers are composed during browser playback so the creator can inspect the story, pause and seek. This is the studio composition path; it does not mean a generative model creates new footage instantly.
Does real-time preview remove the need to export a video?
No. Studio preview and a finished MP4 are different outputs. Preview helps review the prepared timeline; the export path produces the video required by the supported delivery workflow.
Is the homepage animation the actual product renderer?
No. It is an interactive illustration using prepared artwork and browser-drawn text. Its audience, name, playback and action controls explain the idea without calling the product’s video-rendering service.
Playback and embedded experiences
Distinguish established controls from integration-specific features.
Which interactive controls are established in the studio?
Studio playback provides controls to play, pause, seek, adjust audio and inspect the prepared experience. Creative and audience controls help review versions before export. A delivered player’s controls depend on the player integration.
Can an embedded video include a call to action?
The documented development embed implementation includes a configurable CTA, playback controls and host events around an existing MP4. That documentation does not establish a general production rollout; confirm the deployment and supported contract for your integration.
Are interactive forms and branching stories available through that embed?
The documented embed does not establish in-video forms, branching stories or new personalization from host context. Those are separate requirements to verify, not capabilities implied by the presence of a CTA or playback controls.
This guide describes workspace capabilities and documented implementations. Availability depends on deployment, workspace configuration and the integration contract. Confirm the required features for your rollout with Shuffll.
Public API + MCP documentation ↗