Runway brings reference-frame editing into Aleph 2.0 and Edit Studio

What changed

Runway announced Aleph 2.0 and Edit Studio on 21 May 2026. The company built the editing app around a familiar production task: changing footage that a team already has. A campaign producer might need another product in a shot; a director might want to revisit its lighting. Runway presents the release as a way to make those changes within existing material. Its demonstrations establish the intended uses, rather than a measured success rate across client work.

An editor begins with a source clip and selects a frame that shows the intended change. The editor revises that still, inspects the result, and uses it to guide the video edit. Runway's current help page describes a single-edit mode and an optional range selection for targeting part of the clip. That preview step gives the creative director something concrete to review before the team generates a moving version.

Why it matters

For a fashion campaign, our editorial assessment is that this could change the order of a review meeting. The art director can discuss the chosen color, silhouette or background on a still, then ask the editor to test how it holds through motion. A producer should keep both decisions in the brief. Agreement on an attractive frame does not settle whether the garment stays consistent as a person turns or a hand crosses its surface. That requires watching the finished sequence.

What to do now

Runway's prompting guide recommends naming the requested action and the desired change. Its examples include wardrobe and accessory changes, object replacement and relighting. These are supplier examples. The Human Input has not tested whether a particular logo, fastening or textile survives the process. A useful first trial would use a short, cleared shot with a visible detail that the team can compare against the original.

The upload specification deserves attention before anyone promises delivery. The guide lists a maximum input resolution of 1080p, says footage above 30fps is downsampled, and rejects clips with more than ten cuts. It lists two-to-thirty-second clips in its specification table, while its upload prose uses strict “longer than” and “shorter than” wording. Use an interior duration for a first test and confirm the boundary in the product if it matters. Do not assume that accepting a short sequence amounts to supporting an unrestricted project timeline.

The guide also separates the generated-video cost from frame iterations and premium export formats. For a producer, the estimate should include rejected attempts and review time. A usable comparison would record the original task, time spent preparing references, number of generations and time spent correcting the selected output. We cannot infer a saving from a successful demonstration. A team can make that judgment after testing the same brief through its existing process.

Runway's commercial-use help page says it imposes no non-commercial restriction on content a user creates and describes the user's rights as between the user and Runway. That statement concerns the supplier-user relationship. It does not document permissions for a specific campaign's footage or talent. Before uploading a commissioned shoot, the responsible producer should review the actual agreements and the client's AI policy with the person who handles those approvals. This is an editorial workflow recommendation, not a legal conclusion about a particular contract.

What to watch next

A careful trial can stay small: one cleared shot, one defined change and a side-by-side review at delivery size. Keep the original and the rejected outputs. Ask the reviewer to name any changes the editor did not request, then decide whether another generation or a conventional correction is the better next step. Those records give a studio evidence for its own next job without treating Runway's examples as a guarantee.