Runway is useful when you want to animate a visual concept rather than manually build every frame. Its controls and model availability change, so always confirm the selected model before generating.

Original editorial illustration for From a still image to a cinematic clipScreenshot is unavailable in this browser. Open the original.
INTERFACE SCREENSHOT · CGWORLD — screenshot of Runway Gen-4 interface ↗. Interfaces may change.

Step 1 — prepare the source frame

Use a clear image with an obvious subject, clean edges and room for the motion you want. Image-to-video relies on the source image for its visual starting point. If a label must stay readable, keep it large and test for distortions.

Step 2 — choose a supported video model

Open Runway’s creation workspace and select a model supporting image-to-video. Runway’s official Gen-4.5 documentation describes both text-to-video and image-to-video controls. Your account, plan and the interface may differ from screenshots.

Official Gen-4.5 setup guide

Step 3 — prompt the motion

EXAMPLE PROMPT · PRODUCT SHOT

A smooth, slow dolly-in toward the glass bottle on the desk. Reflections shift naturally as the camera moves. The bottle remains stationary, with consistent shape and label. Soft daylight, single continuous cinematic shot.

The best video prompt explains what changes over time: subject movement, environment movement and camera movement.

Step 4 — generate, inspect, revise

  1. Choose the intended clip length and aspect ratio.
  2. Generate a short test before making multiple variations.
  3. Review details such as hands, lettering, physics and sudden jumps.
  4. Revise one motion parameter, then render again.
  5. Export only after checking licensing and use rights in the current plan.

Common mistakes

Too many simultaneous camera directions make the scene hard to control. A short, physical description often works better than a long list of vague adjectives. Consult the official Image to Video Prompting Guide for examples.

Primary sources

Official vendor documentation was used to verify the workflow. Some options depend on plan, region, product version or account access.