Runway Aleph AI Video Transformation

Runway Aleph is best when the motion and timing in the source clip are already worth keeping, but the look still needs to change. It works well for approved footage rewrites, alternative art-direction passes on demos or trailers, and source-video transformations where the creative question is how to reinterpret the clip, not how to generate new motion from scratch.

On Rivya, this option is built around one source video plus an optional reference image. Public controls stay focused on transformation essentials: aspect ratio, watermark text, and seed. It is a dedicated video-to-video rewrite option, not a blank-sheet text or image generator.

The first question is whether the source clip already has the motion you want to preserve. If it does, the next decision is whether one prompt and maybe one still reference are enough to steer the new look. In practice, source quality, rewrite clarity, and whether you need repeatable seed tests matter more here than piling on more input complexity.

Rivya currently lists a fixed 90 credits per generation. That is easiest to justify when rerunning the whole shot would be wasteful, because the source clip is already doing the right motion work and the value is in a deliberate rewrite pass.

Choose standard Runway generation when you do not need to preserve motion from an existing clip. Choose Luma Modify Video when a narrower, shorter, lower-cost source-video rewrite is enough. Choose Runway Aleph when you want the broader dedicated rewrite option and the source clip itself is the foundation you are trying to preserve.

Start here when the first result is about finding out whether one existing clip can survive a serious prompt-led rewrite. Use it for approved footage that already has the right motion, but still needs a different visual direction.

This page supports one source video and one optional reference image. Before the first result, you can set aspect ratio, add watermark text if needed, and set a seed for repeatability. The point is to pressure-test a rewrite on top of an existing clip, not to build a new shot from scratch.

First make sure the source clip is actually the one whose motion you want to keep. Then decide whether the rewrite needs the optional reference image, whether the output shape should change, and whether seed repeatability matters for comparisons. Those checks usually tell you more than rewriting the prompt over and over.

The page is public, but the actual rewrite run is still gated behind sign in. Rivya currently lists a fixed 90 credits per generation, so you can inspect the source clip, settle the rewrite goal, and decide on the output shape first, then sign in when you are ready to run it.

Stay on this page while you are checking one source clip and deciding whether the rewrite is working. Open the full Studio once the project needs saved versions, multiple clips, or a longer managed transformation project around the same footage.