Act-Two suits a character cutscene where delivery matters: you record the timing, expression and movement, then transfer that performance to a character reference. A still image allows gesture transfer; a character video keeps its existing body and camera motion while Act-Two changes the facial performance. Rehearse and approve the driving footage first, then review the result for identity and gesture drift. The output is rendered video, so keep the shot separate from the game’s reusable rig, collision and skeletal animation. Clear the rights to both inputs before uploading.
Commercial use & license
Proprietary hosted model governed by Runway’s service terms and your access plan. No downloadable weight license is listed for this route.
Adult content rules
Runway prohibits adult nudity and sexually explicit content on its hosted services. It may also restrict sexually suggestive imagery, including lingerie.
What you need
For API use, select act_two with a Runway developer project, API key and funded credits. The web app requires Standard or higher. Supply a driving performance video and a character image or video. Use one subject with a visible face, waist-up framing and an uninterrupted take. Gesture transfer requires a character image; character videos retain their own body and camera motion. The web guide lists clips up to 30 seconds.
Ranks are recommendations for the task described, based on reviewed documentation. Model ranks cover non-explicit development work. We have not run practical benchmarks. Check content policies and commercial terms separately. How the ranks work →
Sources & further reading +
- Runway model catalog and endpoint IDs ↗
- Runway API reference ↗
- Runway usage policy ↗
- Runway Act-Two performance and input guide ↗
Last checked 5 October 2026.