Ray 3.2 vs Runway Gen-4.5: Which Fits Your Shot?

Choose Ray 3.2 for lower-priced 720p iterations, 1080p output, or a wider choice of text-to-video aspect ratios. Choose Runway Gen-4.5 when a landscape shot needs its 8-second duration at fixed 720p. Ray 3.2 is available on HiAPI: open its model page to start with the lighthouse or rice-valley prompt below.

For the directly matched 5-second/720p tier, Ray costs $0.429 per clip and Runway costs $0.8575. The two sample pairs below show how each interprets the same scene; use them to choose what to examine in your own footage.

Which Differences Affect the Choice?

At 10 seconds/720p, the prices are $1.286 for Ray and $1.715 for Runway. Ray is about 50% lower at the matched 5-second tier and about 25% lower at 10 seconds. The Ray pricing guide includes the full tier table and batch budgets.

What Do the Same Prompts Produce?

Each pair uses the same prompt, 5 seconds, 720p, and 16:9, with one generation per model. Look at camera position, subject size, and where the shot ends when choosing a direction for your own edit.

A Lighthouse Keeper at Dusk

A lone lighthouse keeper climbs the spiral stairs at dusk, storm waves crash against the rocks below, the beam sweeps across the sea, slow cinematic crane shot

Generate the lighthouse shot with Ray → Choose 5 seconds, 720p, and 16:9 separately; the link fills the prompt.

In this pair, Ray moves upward outside the tower: the exterior spiral staircase, small keeper, and rough sea sit in a cool-blue scene. Runway follows a dark-coated keeper inside the tower, with the sea visible through arched windows and a greyer, greener palette. The Ray sample gives more space to the building and coastline; the Runway sample brings the person closer. Choose the framing that serves your edit.

An Aerial Rice-Valley Shot

Aerial establishing shot drifting slowly over a terraced rice valley at golden hour, a low sun raking across flooded paddies that mirror an amber sky. Thin mist pools in the lower terraces. The camera moves laterally with a slow, patient pace, gradually revealing a single farmer walking a narrow dirt path. Warm high-dynamic-range lighting, rich greens and golds, cinematic haze. Negative: no text, no watermark, no flicker, no distorted geometry.

Generate the rice-valley shot with Ray → Select 5 seconds, 720p, and 16:9 to use the sample settings.

Ray shows the terraces from a higher, downward-looking position, with a small farmer and field boundaries filling the frame. Runway keeps a lower viewpoint: the sun and horizon enter the composition, while a farmer in a conical hat pushes a cart. For this pair, the practical distinction is landscape scale versus a more prominent human subject. State the framing explicitly when that choice is central to your shot.

Which Model Fits Your Shot?

For repeated short scene drafts, start with Ray at 540p. Its 5-second entry tier costs $0.2145, so $10 covers 46 whole generations. Settle the camera move and composition, then generate at the resolution your edit needs.

For 1080p or a 21:9 text-generated scene, use Ray. Its text-to-video endpoint also accepts 1:1, 4:3, and 3:4, which makes square or portrait composition a direct input choice.

For an 8-second landscape text shot, use Runway. Its 16:9 mode offers that intermediate duration. For vertical text-to-video, both models offer 5 or 10 seconds.

For an image sequence with a defined ending, use Ray image-to-video. Supply the first frame in image_url and the intended last frame in end_image_url. That mode produces a fixed 5-second clip.

For an existing still that needs 8 or 10 seconds of motion, use Runway image-to-video. It accepts one image in image_urls and supports 16:9, 9:16, 1:1, 4:3, and 3:4. It center-crops the first frame to the chosen ratio, so keep the subject inside that crop.

For either model, plan the soundtrack in your editing workflow: both return silent MP4 files.

What Changes When You Switch APIs?

Both use POST https://api.hiapi.ai/v1/tasks, return a taskId, and support the same asynchronous status-check workflow. Keep that job handling and map the input fields to the destination model:

• Change model between ray-3.2/text-to-video and runway-gen-4.5/text-to-video.
• Send an integer duration supported by the selected aspect ratio.
• Send resolution for Ray; Runway fixes output at 720p and takes no resolution field.
• For image-to-video, map Ray's image_url to Runway's single-item image_urls array. Keep end-frame requests on Ray. When moving to Ray image-to-video, remove duration and aspect_ratio: that endpoint uses a fixed five-second length and follows the input image. When moving to Runway, select aspect_ratio explicitly so its default landscape crop fits your source image.

Start the switch with a prompt within both length limits and a shared 16:9/5-second configuration. Then check the output against your shot requirements before moving a batch. The Ray API guide covers submission and result handling.

FAQ

Is Ray always the lower-priced choice? Compare the same output tier: Ray is lower at matched 5-second and 10-second 720p. Its 1080p tiers carry higher prices, while Runway outputs 720p.

Can both generate vertical video from text? Yes. Choose 9:16 with 5 or 10 seconds on either model.

Can a prompt link set the whole request? It fills the prompt. Select duration, resolution, and aspect ratio on the model page before generating.

Open Ray with the lighthouse prompt filled in →, then use 5 seconds, 720p, and 16:9. For more scenes, continue with the Ray 3.2 prompt recipes, or open Runway Gen-4.5 to try your chosen shot there.