AI&Design
All change articles

Runway · Announcement · Official source

Runway Aleph 2.0 lets editors preview a change before re-rendering the shot

A spring scene became a snowy forest in Cole Bielecki’s May 30, 2026 Edit Studio tutorial. He started with sunny spring footage, chose a still, and prompted for a winter scene. The tutorial’s chapters lead from reference-frame selection to a video render with falling snow. That last step matters. A still can establish the intended lighting and appearance of the snow, while the video render has to carry those choices through time and make the snow move. Bielecki also compared separate shot edits with a combined pass. His takeaway was that the combined edit worked best when close, medium and wide shots shared a consistent background. The creator’s description and chapters document the exercise. They give no attempt count or frame-by-frame continuity measurement. Bielecki’s tutorial and render breakdown

What changed on May 21

Runway introduced the original Aleph in July 2025 as an in-context video model capable of adding and removing objects, relighting scenes, transforming appearances and generating new angles. The app changelog records its all-paid-plan availability on July 31. Editing an existing clip already belonged to the product. On May 21, 2026, Aleph 2.0 and Edit Studio brought an explicit visual approval step to that task. Runway announced the new app for paid plans on desktop web, with edits on clips up to 30 seconds at 1080p. The announcement said the model could apply a targeted change across relevant shots in a sequence and preserve the surrounding footage. Those are vendor descriptions of what the model is designed to do. Original Aleph introduction · Product changelog · May 21 release announcement

The documented single-edit workflow starts by uploading an existing video or choosing one from Runway assets. The editor selects a timeline frame, prompts for a change, and previews the resulting image. After refining the still, the editor generates a video version. The optional motion prompt gives the editor a separate way to specify movement. The source stays accessible alongside generated versions, so another attempt can start from the original or build on an iteration. The still preview answers whether the look is right at one moment. The rendered clip puts the look, original action and continuity to the test together. Creating with Edit Studio

What early operators tried

Maciej Dziuba’s May 28 tutorial labels a product-swap demonstration in Edit Studio and separates its review from the prompting step. The chapter index breaks the instruction into the action, the target and the change. A curated Runway example gives that decision a concrete shape by asking for red sneakers in existing sneaker footage. Together the sources identify a particular use for the frame stage in product work. The editor can judge the proposed color in the actual shot’s context before asking the model to carry it through the clip. The accessible account of Dziuba’s demonstration gives the procedure without a measured fidelity result. Runway’s sneaker example supplies no attempt count or confirmed campaign delivery. Dziuba’s product-swap chapter · Runway sneaker example

The public Reddit search for May 14 through June 4 found general complaints about Runway credits and brief replies mentioning the new model, with no sufficiently specific original submission about the launch workflow in the inspected results. On June 29, an r/runwayml user working with 1080p ProRes source material on Enterprise asked whether Aleph 2.0 in Edit Studio could return anything beyond H.264 MP4. That question is evidence of a delivery concern for one user. The June 29 submission came 39 days after launch and describes neither a verified export nor a launch-week reaction. Runway subsequently dated its ProRes 4444 and PNG sequence addition to August 10. May 23 Reddit discussion · June 29 export question · August 10 changelog

Where the revised clip still needs editorial work

The demonstrations support trying a colorway or a change of season on a take whose performance and camera movement already serve the edit. Bielecki’s comparison suggests that a new angle with a materially different background deserves a separate continuity check. For a product swap, a frame that reads well can still hide problems that appear when the product turns, moves behind an object or crosses a cut. An editor can review the full render against the source, adjust the still or prompt, or render the troublesome shot separately. If the underlying performance or camera angle fails the brief, a retake remains a separate production decision. The sources establish demonstrations and iteration controls, with no measured reduction in retakes, finishing time or rejected shots. Snow and multi-shot comparison · Product-swap consistency review · Edit Studio versions and export controls

Later updates changed where the render could be made and where it went next. Runway Dev documented the API route on June 2, with optional images attached to specific timestamps. The July 14 changelog added an Edit Video tool for Runway MCP. On September 8, Runway described its Premiere Pro and After Effects panel as a way to select an existing timeline clip, restyle its anchor frames, and place a render of the same duration into the sequence or composition. Those surfaces have their own controls and handoff paths. The evidence for the May release concerns the desktop web app, where the main change was the chance to decide what the edit should look like before paying for a video render. Runway Dev API changelog · July 14 product changelog · September 8 Adobe announcement