Build with scenes and templates

A scene is one ordered story beat with its own duration, objects, timeline state, background override, audio relationships, camera state, and transition into it. A project plays scenes in order on one global timeline.

A template is reusable project data. Depending on its type, it can add content to one scene, replace one scene, or replace the complete project.

The distinction matters: scene management changes the structure you already have; template application can create or replace structure.

Activeuserdesktopmobile26 minutes

Verified against [email protected]

When and why to create a new scene

Create a separate scene when one or more of these changes:

• the audience's task or message;
• the background or visual environment;
• narration topic;
• camera framing strategy;
• the set of objects that should remain editable together;
• the pacing or transition; or
• the reusable template you want to apply.

Keep content in one scene when it is one continuous beat and only object timing changes. Too many tiny scenes make narration, transitions, and later reordering harder to manage.

Useful scene names describe intent: Problem, Three benefits, Product demo, and Call to action are more helpful than a list of generic names.

Understand the scene manager and global time

123456

Two default 15-second scenes produce a 30-second project. The second scene begins at global time 0:15.

Screenshot callouts

1. 1
   Scene count

   The scene manager reports two ordered scenes in this project.
2. 2
   New Scene

   Creates a scene immediately after the active scene and selects the result.
3. 3
   First scene

   The card reports its order, name, duration, object count, and scene-play action.
4. 4
   Transition into the next scene

   The scissors control sits between cards; its transition belongs to the incoming scene.
5. 5
   Active second scene

   The blue outline identifies the selected scene; its card starts immediately after Scene 1.
6. 6
   Global playhead at 0:15

   Scene-local time 0:00 in the second scene maps to global project time 0:15.

The timing model

Scene start time is the sum of the durations of every earlier scene.

For the screenshot:

• Scene 1: global 0:00–0:15;
• Scene 2: global 0:15–0:30; and
• total project duration: 0:30.

Changing the duration or order of an earlier scene changes the global start time of later scenes. Always preview the full project after either operation.

Workflow A: create and select scenes

1. Pause playback.
2. Select the scene after which the new beat should appear.
3. Choose + New Scene.
4. Confirm the new scene becomes active.
5. Rename it immediately.
6. Set a duration based on narration, reading time, and animation.
7. Add content only after confirming the correct active scene.

A new scene defaults to 15 seconds. On Desktop, creating it pauses playback, disables loop playback, inserts it after the active scene, selects it, and seeks to its global start.

Selecting another Desktop scene also pauses playback and disables loop so a stale loop range cannot pull the playhead back. If that scene has a valid remembered playhead position, the manager can restore it; otherwise it seeks to the scene start.

Workflow B: rename and label a scene

1. Open the scene card's ⋯ actions.
2. Choose Rename.
3. Enter a non-empty descriptive name.
4. Press Enter or commit the edit; use Escape to cancel on Desktop.
5. Optionally set a short thumbnail label such as Intro or CTA.
6. Optionally choose a thumbnail color to scan a long project faster.

Names explain narrative purpose. Thumbnail labels and colors are organization aids; they do not change the canvas background.

Workflow C: duplicate a scene safely

Duplication is the quickest way to preserve visual continuity while changing one beat.

1. Finish the source scene's essential layout.
2. Open ⋯ → Duplicate, or use the Mobile Lite copy action.
3. Confirm a new scene named with (Copy) appears immediately after the source and becomes active.
4. Rename the copy.
5. Change its scene-local content. Inspect shared objects before editing their content, since that edit also affects the source scene.
6. Preview both scenes and their boundary.

The duplicate command copies scene-local objects with new IDs, remaps their timeline and scene state, and clones supported scene audio relationships. A shared multi-scene object keeps its canonical object ID and gains membership in the copy; its scene-local tracks and managed pose are copied for the new scene. Choose independent local copies when content should diverge.

Still verify manually: external or unavailable media cannot be repaired by ID remapping, and a copied transition or duration may not suit the new story beat.

Workflow D: reorder scenes

1. Pause playback.
2. Drag a scene's reorder handle toward its new position.
3. Drop it on the intended index.
4. Confirm the scene order and active selection.
5. Scrub every affected boundary.
6. Preview narration, object timing, camera behavior, and transitions from at least one scene before the moved scene.

Desktop uses the ⋮⋮ drag handle. Mobile Lite uses a touch/pointer drag handle and disables reordering during playback.

Reordering preserves the scene but changes its global start time. Project-level audio or markers may therefore relate differently to the visual sequence after the move.

Workflow E: set scene duration

Duration must accommodate:

• spoken narration;
• reading time after text is fully visible;
• all object animations and draw steps;
• camera movement;
• scene-scoped audio; and
• the transition into the next scene.

Desktop

1. Open the scene card's ⋯ menu.
2. Select the current duration.
3. Enter a value from 1 to 30 seconds.
4. Desktop accepts millisecond precision through a 0.001 second step.
5. Commit with Enter or ✓; cancel with Escape.

Mobile Lite

1. Tap the displayed duration or open the scene menu.
2. Enter 1 to 60 seconds.
3. Save the value.

The shared scene state clamps updates to 1–60 seconds, while the current Desktop control deliberately exposes the narrower 1–30 second range. Changing the active Desktop scene duration updates its playback range immediately.

Let narration lead

Record or place the narration first when it controls pacing. Set the scene to cover the spoken line, then add a short reading or transition margin.

Workflow F: add a transition

The control between two scene cards edits the transition into the next scene.

1. Pause playback.
2. Select the scissors/transition control between the outgoing and incoming scenes.
3. Choose a transition type.
4. Set its duration.
5. Preview from before the end of the outgoing scene.

Current transition choices include:

• None (Cut);
• Fade to Black and Crossfade;
• Wipe in four directions;
• Slide in four directions;
• Zoom In and Zoom Out; and
• Iris In/Open and Iris Out/Close.

Desktop starts a newly chosen transition at 500 ms and exposes 200–2,000 ms in 100 ms steps. Mobile Lite exposes 100–2,000 ms in 50 ms steps.

Use cuts for speed and continuity. Use a transition only when it communicates a meaningful change; repeated long transitions consume reading time and slow the project.

Workflow G: delete a scene

1. Select the scene and verify its name, content, and position.
2. Save or package a recovery copy if the scene contains irreplaceable work.
3. Choose Delete.
4. Read the confirmation and confirm only the intended scene.
5. Verify the remaining active scene and global timeline.

The delete command removes the scene, its local objects, and associated timeline data. A shared object survives while another scene still contains it. Desktop explicitly warns that the action cannot be undone. Mobile Lite prevents deleting the final remaining scene and displays You must have at least 1 scene.

Keep one object across scenes

Shared scene membership lets one canonical object appear in several scenes. Use it for an identity that should remain the same—a logo, presenter, product illustration, or recurring title. Text, style, and base geometry edits affect that one object wherever it appears. Scene-local property tracks and Draw Steps can still give it different timing in each scene.

Availability and verification

Scene membership and Scene Pose are currently authored through compatible agents in the Desktop web editor. Existing scene-manager buttons do not expose these settings. The contracts and regression coverage were reviewed on 7 October 2026. Mobile Lite can preserve and play the scene-local pose data; the authoring capabilities declare Desktop availability.

1. Create the scenes and the object you intend to keep identical.
2. Ask the agent to inspect object.scene_membership.get for that object's exact ID, then inspect the current scene IDs.
3. Discover object.scene_membership.set. Supply objectId and sceneIds, an array naming all scenes that should contain the object. The array is a complete membership list, not a list of additions.
4. Inspect each scene. Content edits should appear everywhere; local timing should stay local to its owner scene.
5. Use a Scene Pose for scene-specific placement, or duplicate a local object when wording, style, or independent identity should diverge.

One scene ID yields local membership; more than one yields shared membership. The command normalizes membership to project scene order and requires at least one existing scene. It supports eligible text, images, SVG, SVG paths, drawing, native shapes, and unbound Smart Lines/Arrows. Locked objects, groups and group children, video, attached connectors, and Path Follow followers cannot be shared through V1.

Removing a scene membership is refused while that scene still references the object through property tracks, poses, Draw Steps, StoryBeats, camera authoring, connectors, dependent anchors/clips, Path Follow, or audio bindings. Clear or revise those references first. Clip source/target membership changes and an anchor-bound dependent's membership changes also require clearing the relationship. These checks protect scene-local work from becoming dangling data.

Deleting an object is broader than removing one membership: deleting the canonical shared object removes it from every scene and cleans its related references. Inspect membership before using normal object deletion. Keep a .scribe backup for structural revisions.

Give a shared object a Scene Pose

A Scene Pose changes a shared object's static X, Y, rotation, or uniform scale in one scene, while retaining its common content and canonical base geometry. It authors managed scene-local Timeline keys at local time zero. It does not animate a transition between scenes.

Capability	Inputs
object.scene_pose.get	Required objectId, sceneId; reports managed values, canonical base, and conflicting tracks
object.scene_pose.set	Required objectId, sceneId, plus at least one of x, y, rotation, scale; scale must be at least 0.01
object.scene_pose.clear	Required objectId, sceneId; optional properties array of x, y, rotation, scale; omission clears all eligible managed pose fields

1. Confirm the object is shared and belongs to the scene you want to pose.
2. Inspect its pose and existing Timeline ownership.
3. Set only the fields the scene needs. For example, change X/Y to place the same product at the right in an explanation scene.
4. Preview that scene and every other member scene. Content stays shared; only the requested pose fields change in the selected scene.
5. Clear a managed field to show the canonical shared value again. Undo restores an accepted pose edit as one action.

Scene Pose will not replace ordinary Timeline authoring on the same binding. Adding manual keys to a managed pose transfers that binding to Timeline authoring; the pose clearer then protects it instead of removing those keys. Slide In owns X/Y, scale-owning presets conflict with pose scale, and enabled Path Follow owns placement. Pose on a bound Path Follow path is deferred. Resolve the reported owner before setting a pose. Adding membership alone copies no pose; duplicating a scene copies its scene-local pose ownership.

Evaluated poses can drive a local Anchor Binding, attached Smart Connector, and Follow Object camera. Use anchor relationships for labels that should follow the posed source, and review the camera workflow at scene boundaries.

Managed Scene Pose is a live authoring operation. Do not invent a separate scenePose field or duplicate object IDs in AI JSON to imitate shared identity. Use the supported template contract for portable content, then discover the current continuity capabilities when working in an open project.

Choose the correct template type

Template type determines application behavior:

Type	Existing-project behavior	Confirmation
Block	Adds new elements to the active scene; existing content remains	No impact confirmation
Scene	Starts an empty target scene or replaces the current scene's contents; other scenes remain	Yes
Project	Starts a pristine project or replaces the entire current project, including scenes and project-level content	Yes

Never infer type from the preview alone. Read the BLOCK, SCENE, or PROJECT badge and the impact text.

Browse the template library

1234567

This screenshot shows 33 built-in templates in the captured build; catalog counts can change.

Screenshot callouts

1. 1
   Search

   Matches template name, description, and tags.
2. 2
   Type filter

   Narrow results to scene, block, or project templates before selecting one.
3. 3
   Aspect-ratio filter

   Desktop filters by All Sizes, 16:9, 9:16, or 1:1.
4. 4
   All, Recent, and Favorites

   Recent keeps the last 50 applied template IDs; Favorites are device-local while signed out and sync when signed in.
5. 5
   Project template card

   The PROJECT badge signals complete-project impact. Built-in identifies its source.
6. 6
   Scene template card

   A SCENE template targets the active scene and does not replace the other scenes.
7. 7
   Full Template Library

   Opens the advanced library when the quick picker is not enough.

Apply a template without losing work

1. Pause playback and select the intended target scene.
2. Save, duplicate, or package the current project before applying a Scene or Project template to valuable work.
3. Open Templates.
4. Filter by type first.
5. Filter by aspect ratio close to the target canvas.
6. Search by purpose, not only appearance—for example, walkthrough, carousel, intro, or comparison.
7. Select a card.
8. Read:
   • the type badge;
   • Adds to scene, Starts/Replaces scene, or Starts/Replaces project;
   • source such as Built-in; and
   • any reported impact count.
9. Choose the apply action.
10. For Scene or Project impact, read the confirmation:
    • cancel leaves the current work unchanged;
    • confirm continues with the stated replacement.
11. If the template exposes editable slots, complete the customization form before final application.
12. Wait for completion, then read warnings.
13. Inspect scenes, objects, timeline, backgrounds, camera, audio, and total duration.
14. Preview the complete affected range.

What the apply pipeline does

• Block: inserts remapped objects into the active scene. A table block additionally asks for row and column counts.
• Scene: replaces only the target scene's scoped content and timing state, resolves its background, loads draw behavior, and restores supported camera behavior.
• Project: creates a new project instance from the complete template and hydrates its scenes, objects, audio settings, and timeline data.
• IDs are remapped to avoid collisions with existing objects, scenes, tracks, and bindings.
• Validation warnings are shown rather than silently ignored.

ID remapping prevents structural collisions. It does not guarantee that missing external assets, unsupported fonts, or an unsuitable aspect ratio will look correct.

Customize template slots

Some templates declare editable slots for text or visual replacements.

1. Select the template and choose its apply action.
2. When the customization form opens, review every named slot.
3. Replace only the intended values.
4. Check required slots before applying.
5. Apply with the completed slot values.
6. Inspect framing, wrapping, and timing in the real canvas.

The slot form appears before the template is committed. If you cancel it, the pending template is not applied.

Limits, safety, and offline behavior

• Built-in templates are validated JSON/project data and previews, not arbitrary scripts.
• Applying a template does not execute third-party code or plugins embedded in its content.
• Built-in templates can work offline after their manifest, JSON, previews, and required assets are available to the app.
• Cloud or account-owned template sources, favorite sync, and unavailable remote assets require their host services.
• Recents and signed-out favorites use local device storage. Up to 50 recent template IDs are retained by the quick picker.
• A template may carry canvas dimensions that differ from the current project. Filtering by aspect ratio reduces surprises but does not guarantee automatic responsive layout.
• Scene and project replacement are intentionally confirmed because their effect is broader than normal object insertion.
• Template warnings require review; “applied” does not mean every optional asset or visual constraint was perfect.

Desktop and Mobile Lite differences

Task	Desktop	Mobile Lite
Scene access	Docked or floating Scene Manager	Quick scene switcher plus Manage scenes modal
Edit during playback	Scene commands pause or coordinate playback	Scene editing controls are disabled; the sheet says Pause playback to edit scenes
Duration control	1–30 s, 0.001 s step	1–60 s
Reorder	Drag ⋮⋮ handle	Touch/pointer drag handle
Delete final scene	Destructive confirmation path	Explicitly blocked; at least one scene required
Transition duration	200–2,000 ms, 100 ms step	100–2,000 ms, 50 ms step
Template filters	Search, type, 16:9/9:16/1:1, All/Recent/Favorites	Type, size including 4:3, search, and quick tags such as Social, Short, List, Compare
Template impact	Typed confirmation and slot customization	Same impact model and slot customization in a touch layout

Verify the result

After scene changes:

• scene order tells the intended story;
• names and thumbnail labels are unambiguous;
• every object belongs to the intended scene;
• narration and scene duration agree;
• global timeline offsets remain correct;
• transitions point into the intended scene; and
• the full project plays through without an unexpected seek or loop.

After template application:

• the applied type matches your intent;
• no unrelated scene or project content was replaced;
• editable slots contain final values;
• IDs, tracks, draw steps, and camera behavior load;
• required assets and fonts resolve;
• backgrounds and aspect ratio are correct; and
• warnings have been addressed or consciously accepted.

Troubleshooting and recovery

Symptom	Likely cause	Recovery
New content appears in the wrong scene	A different scene was active	Undo if available, select the intended scene, and insert/apply again
New Scene button or Mobile scene controls are disabled	Playback is active	Pause playback and retry
Scene begins at an unexpected global time	Earlier scene duration or order changed	Recalculate from earlier scene durations and inspect the global timeline
Duplicate is missing content	Source had unavailable external assets or unsupported state	Keep the source, restore assets, then duplicate again
Rename does not save	The new name is blank or unchanged	Enter a non-empty descriptive name
Desktop rejects a 45-second duration	Desktop UI exposes 1–30 seconds	Split the beat or use Mobile Lite's 1–60 second control only when the longer scene is intentional
Transition seems attached to the wrong card	Transitions belong to the incoming scene	Edit the control between cards and verify the label says transition into the next scene
Delete is blocked on Mobile	It is the only remaining scene	Create another scene before deleting
Template card adds instead of replaces	It is a BLOCK template	Use a SCENE or PROJECT template only after reading its impact confirmation
Current scene disappeared after template apply	A SCENE template replaced its contents	Restore the backup/copy, or cancel before confirmation next time
Entire project changed	A PROJECT template was confirmed	Restore the saved/package copy; do not rely on object-level recovery for complete replacement
Template looks stretched or clipped	Aspect ratio or required assets differ	Restore, choose a matching size filter, or reposition content after apply
Apply reports warnings	Optional/required content could not map perfectly	Read each warning, fix missing assets/fonts, and preview before continuing
Favorites differ across devices	Signed-out favorites are local or sync is pending	Sign in, reconnect, and allow favorite sync to complete

Related guides

• Scenes Complete Guide
• Template System Reference
• Add images, assets, and backgrounds