05
Use the inspector for precise text, media, color, timing, and snapshots
The inspector is where you stop speaking broadly and start changing exact scene parameters.
The inspector is where you stop speaking broadly and start changing exact scene parameters.
Text, typography, color, numeric controls, booleans, local image upload, local video upload, pasted asset URLs, and duration all live here. This is the panel you use when the AI got you close and now you need exact control.
The history area is just as important as the visible design controls. Save a snapshot before a risky change, and restore an earlier scene version if the latest experiment made the motion worse. That is far faster than manually reconstructing a good state from memory.
Steps
- Fix content before style polish: Update the actual message, titles, subtitles, and imagery first. Fine-tuning effects is wasted effort if the underlying content is still wrong.
- Use local uploads when URLs are not stable: For scene media, you can upload local files directly or paste a remote asset URL. Use whichever source is less likely to break during review.
- Save a scene snapshot before branching: Use Save Version before trying a major alternate direction. If the experiment fails, restore the earlier snapshot instead of redoing work manually.
- Adjust duration intentionally: Increase duration for readability, not as a blanket fix. Slow scenes without purpose usually feel heavier, not clearer.
Checklist
- Custom fonts uploaded to the workspace appear in the font picker here.
- Local image uploads are capped at 8MB.
- Local video uploads are capped at 12MB.
- Snapshots are scene-level history, so save them before risky edits on that scene.
When to stop using prompts If you already know the exact text, color, media, or timing value you want, use the inspector directly. Prompts are best for direction; controls are best for precision.