Learning center
CutScene best practices
Structure your projects for speed, consistency, and clear organization.
Treat projects like playbooks
Every production should start from a documented structure. Create folders for research, AI generations, edits, and exports. Label nodes with campaign names and goals so anyone you share exports with understands the context.
- Use clear naming conventions for prompts, renders, and timelines.
- Add descriptions to nodes detailing where they appear in the final story.
- Archive unused experiments with notes explaining why they were cut.
Prepare for manual collaboration
| Habit | Impact |
|---|---|
| Leave timeline markers with notes today | Keeps context ready when you review feedback manually |
| Share exports early | Surfaces blockers before deadlines even without in-app review links |
| Track approvals in an external log | Documents sign-off history for compliance even without built-in approvals |
Optimize credit usage
- Test prompts at lower resolutions, then rerun the final version at full quality.
- Reuse assets across campaigns by building collections of evergreen footage.
- Combine multiple requests into a batch when possible to avoid idle credits.
Keep revisions manageable
- Duplicate timelines before major edits so you can revert quickly.
- Render a few wildcards into a clearly labeled folder on your drive so you can A/B ideas without nuking the original.
- Write short changelog entries when you push updates; it keeps stakeholders aligned even without built-in comments.
Continuous improvement
Review performance metrics—watch time, conversions, social engagement—and jot the highlights into your living project log. A tidy recap turns every production into a reusable blueprint for the next one.