Choose Runway by the media you already have: animate a still, transform an existing clip or investigate a performance-transfer workflow. The app audit identifies AIML-hosted routes and important older-name aliases, so the selected label must not stand in for the actual model identity.
Editorial starting points, not a performance ranking. Check current app access before choosing a model.
Animate an approved starting image
AIML’s Gen-4 Turbo contract requires image_url. Use a still with a clear subject and enough space for the requested movement, then describe the motion rather than replacing the composition with a contradictory scene.
Tradeoff: The starting image anchors the request but does not guarantee frame-by-frame preservation. Inspect logos, faces, edges and background objects throughout the clip.
Gen-4 Aleph is a video-to-video route with a source video and an edit prompt. Define one change and a clear preservation list so you can judge whether the edit respects the original shot.
Tradeoff: The reviewed AIML schema specifies five seconds, while the app audit records a ten-second card label. Do not plan delivery around the larger label without verifying the actual request and result.
Official documentation describes the named model or gateway—not every feature available in this app.
Image animation: exact host schema
AIML documents model runway/gen4_turbo through POST /v2/video/generations, requiring an image URL. It lists 5- or 10-second requests, six aspect ratios, optional tail_image_url and seed. These host fields are not evidence that all six ratios or an ending-image control are available in EZ Ai Assist.
runway/gen4_aleph requires model, prompt and video_url. The host schema sets duration to five seconds and offers frame-size presets plus an optional image reference. This is the Gen-4 Aleph contract, not the newer Aleph 2 contract listed in Runway’s direct catalog.
Runway lists Gen-4.5 and Gen-4 Turbo as separate direct models. AIML’s generation API creates a job and returns a completed video later using generation_id. A completed file does not by itself identify an app alias’s target, and another direct model’s capabilities cannot be assigned to that alias.
Every existing catalog entry for this provider is linked below. Status labels come from the individual website guides; catalog coverage is not a guarantee of current app access. Historical and snapshot pages remain references, not extra active models.
Original prompt examples, not generated-output demonstrations. They have not been generation-tested.
Workflow 1
Add motion without redesigning a package
Attach an approved image you have permission to use. Start with a product that is fully visible and a camera movement small enough to judge against the still.
Use the attached photograph of the cream tea tin as the starting frame. Make a very slow camera arc to the right while a soft reflection crosses its lid. Keep the tin shape, label wording, colors and table position unchanged. Preserve the background and lighting direction; add no hands, extra products, captions or opening lid.
Check the result: Compare several frames with the original. Reject changed lettering, duplicated edges or a moving product when only the camera was meant to move.
Supply a short source clip with simple motion. Write down which objects, timing and camera path must remain unchanged; do not treat the prompt as a replacement for the required video.
Using the supplied clip of an empty tiled courtyard, change only the wall paint to a soft terracotta color. Preserve the tiles, doors, plants, shadows, shot length and original camera movement. Keep the paint consistent across frames. Do not add people, furniture, text, new lighting or additional architectural details.
Check the result: Scrub the entire clip for color flicker, shifted geometry or unrequested objects. Check the returned duration before replacing the source shot in an edit.
Official provider or gateway documentation supports the cited API capabilities. App mappings come from owner-supplied audits labeled October 9, 2026, not live generation tests. A listed model and a provider feature do not establish current app access or parameter forwarding.
Owner audit · October 9
Required inputs in the app audit
Gen-4 Turbo requires a starting image. Gen-4 Aleph requires a source video on the client and forwards a seed; server-side enforcement of the media requirement was not established. Both routes are recorded as AIML-hosted.
Owner audit · alias mapping
Legacy names are not extra models
The older runway-gen4-5 and runway-gen4-5-turbo IDs map to Gen-4 Turbo. The Gen-4.5 page is retained as a provider reference, while Gen-4.5 Turbo is a legacy alias whose distinct provider model identity is unverified. Every existing URL is preserved.
Documented evidence gaps
Other routes still need verification
Gen-3a Turbo has an audit-versus-host model-prefix discrepancy. Act Two needs character and driving-performance media, but its complete app input flow is not verified. Tail images, full ratio selection, native sound and successful generation were not tested for these routes.
Before you rely on a result
Limits, costs and tradeoffs
AIML host limits and Runway direct limits can differ. In particular, do not replace the exact Gen-4 Aleph contract with Aleph 2 specifications or use a direct API price as the app’s charge.
Source media must be usable and permitted, including consent for identifiable performers. An apparently smooth clip can still change identity, product detail or camera continuity; review the complete output.
The catalog includes references and aliases as well as audited app choices. Counting the six website pages as six independently selectable Runway models would be misleading.
Explore prompt-led Seedance shots when you are starting from a written scene rather than editing source footage.
Common questions
Runway, without the assumptions
Does the Gen-4.5 Turbo link select a separate model?
The owner audit maps that older label to Gen-4 Turbo. A distinct Gen-4.5 Turbo provider model was not verified. The URL stays available to explain the alias rather than silently renaming it.
Can Gen-4 Aleph work with only a prompt?
Not under the cited host contract, which requires source video and a prompt. The audited client also requires video. A detailed written scene is not a substitute for that required input.
Are all Runway website features included here?
No. This guide distinguishes exact AIML routes, direct Runway references and owner-audited app controls. Studio tools, newer models and endpoint-specific options are not automatically part of this integration.
Highlighted provider contracts reviewed . Individual model guides carry their own review dates. Sources can change; these pages do not perform live health checks.
Official provider or gateway documentation supports the cited API capabilities. App mappings come from owner-supplied audits labeled October 9, 2026, not live generation tests. A listed model and a provider feature do not establish current app access or parameter forwarding.