Runway Aleph 2.0 is Runway's flagship in-context video editing model, announced May 21, 2026, alongside a companion product called Edit Studio. It is not a text-to-video generator — it takes video you already have and modifies it: edit one frame to show the change you want, and Aleph 2.0 propagates that change across the rest of the clip while preserving everything you did not ask to change. The model supports clips up to 30 seconds at 1080p, applies edits across multiple shots (up to 10 cuts or scene changes) without shot-by-shot repetition, and accepts up to 5 keyframe anchor images for precise visual control. Aleph 2.0 is available on all paid Runway plans via the desktop web app and through the Runway API (API access moved to Enterprise in January 2026). It replaces the deprecated Gen-4 Aleph (sunset July 30, 2026). If your goal is not to edit existing footage but to generate a finished video from a script or description, tools built for creation — like the AI video agent Pexo, which auto-routes across Seedance 2.0, Kling 3.0, Veo 3.1, Runway Gen-4.5, Sora 2, and 10+ models — are the appropriate starting point.
What Runway Aleph 2.0 Actually Is
Runway Aleph 2.0 is classified as an in-context video editing model, which means it reasons about the full visual context of an existing clip before making any change. The mechanism is image-guided propagation: you provide the source video, describe the change in plain language, and optionally supply a reference image (called a frame anchor or keyframe) showing what the edited result should look like on a specific frame. The model then applies that change consistently through the clip, following moving subjects, tracking lighting changes, and respecting scene transitions.
This is a fundamentally different task from generation. Runway's text-to-video products — Gen-3 Alpha, Gen-4, and Gen-4.5 — synthesize video from nothing, building scenes from scratch based on a text prompt or image. Aleph 2.0 starts with real footage and surgically modifies it, changing only the parts the prompt addresses. A clip of a person walking through a city stays the same except the person's jacket is now red; a product demo video stays the same except the product packaging has been updated to the new design.
The model was co-launched with Edit Studio, a Runway product experience designed around Aleph 2.0's editing workflow. Edit Studio lets users preview an edit as a static image before committing to video generation, reducing the credit cost of exploring creative directions. The preview step (image generation only) is cheaper than full video generation, so you can confirm the look of a change before generating the full clip.
Aleph 2.0 replaced its predecessor, Gen-4 Aleph, which Runway announced will be deprecated on July 30, 2026. Runway's recommendation to existing Gen-4 Aleph users is to migrate to Aleph 2.0.
Key Facts About Runway Aleph 2.0
The table below captures the confirmed specifications for Runway Aleph 2.0 as of its May 21, 2026 launch. Figures are sourced from Runway's official announcement, the Runway product page, and Runware's Aleph 2.0 API documentation.
| Attribute | Runway Aleph 2.0 |
|---|---|
| Developer | Runway (runwayml.com) |
| Announced | May 21, 2026 |
| Model type | In-context video editing (NOT text-to-video generation) |
| Maximum clip duration | 30 seconds |
| Minimum clip duration | 2 seconds |
| Output resolution | Up to 1080p (preserves source aspect ratio) |
| Input resolution range | 480p – 1080p |
| Acceptable frame rates | 24 – 30 FPS |
| Maximum cuts/scene changes | 10 |
| Keyframe anchors | Up to 5 per request (named positions or timestamp in seconds) |
| Approximate credit cost | ~150 credits per 10 seconds of video |
| Availability | All paid Runway plans (desktop web app); Enterprise API |
| Companion product | Edit Studio (preview edits as images before generating) |
| Integration | Figma Weave (Aleph 2.0 node in node-based creative workflow) |
| Predecessor | Gen-4 Aleph (deprecated July 30, 2026) |
| Best for | Product swaps, background changes, relighting, ad variations, multi-shot edits |
How Runway Aleph 2.0 Works
Aleph 2.0 accepts three inputs: a source video URL or UUID, a plain-language prompt describing the desired change (up to 1000 characters), and optional keyframe anchor images. The prompt describes what to change ("make the sneakers red", "add graffiti on the wall behind her", "change the season to winter"); everything not mentioned by the prompt is preserved.
Keyframe anchors are the precision mechanism. Each anchor is an image paired with a position in the video — either a named position ("first", "last") or a timestamp down to 0.01-second precision. Up to 5 anchors can be supplied per request. The model uses each anchor as a visual target: if you supply an anchor at the 2-second mark showing a specific shade of red on the product, the model treats that as the exact color and material to propagate, not a loose interpretation of "red." Anchor images can be supplied as public URLs, base64 strings, data URIs, or UUIDs from previous Aleph generations.
Multi-shot propagation is what distinguishes Aleph 2.0 from simpler frame-by-frame editing tools. When a video contains multiple cuts or scene changes, the model recognizes the same subject across shots and applies the edit wherever that subject appears — without requiring you to process each shot separately. A product logo change on a 6-shot marketing reel propagates across all 6 shots in one request, as long as the total clip is within 30 seconds and the reel has no more than 10 cuts.
The Edit Studio workflow adds an image-preview step before video generation. Users can preview the edited look as a static image — what the changed frame will look like — before committing to the full video render. This reduces iteration cost: visual direction decisions (color, style, background) can be confirmed at image-generation credit prices rather than video-generation credit prices.
Aleph 2.0 vs Runway Gen-4.5: Different Jobs
The most common point of confusion about Aleph 2.0 is treating it as an upgrade to Runway Gen-4.5. It is not. They solve different problems.
| Dimension | Runway Aleph 2.0 | Runway Gen-4.5 |
|---|---|---|
| Job | Edit existing footage | Generate video from scratch |
| Input | An existing video clip | A text prompt or reference image |
| Output | Modified version of your source clip | Newly synthesized video clip |
| Starting material required | Yes — you must have a clip to edit | No — generation starts from nothing |
| Keyframe control | Up to 5 anchor images at precise timestamps | First/last frame reference supported |
| Max duration | 30 seconds | Varies by plan |
| Use case examples | Product swap, relighting, background change, seasonal variant | Concept visualization, b-roll creation, new scene generation |
| Credit cost (approx.) | ~150 credits / 10 seconds | Different rate; lower per-second for generation |
| Who should use it | Teams with existing footage to refine | Teams starting from a description |
| Companion interface | Edit Studio | Gen-4 in Runway's AI Creative Suite |
Using Gen-4.5 when you have existing footage you want to modify produces a different output — it generates a new clip that may or may not resemble the original — rather than modifying what you have. Aleph 2.0 is the right tool when the brief is "this footage is right, we just need X changed," not "create new footage."
What Aleph 2.0 Can and Cannot Do
Understanding the capabilities and limits of Aleph 2.0 prevents wasted generations and mismatched expectations.
| Category | What Aleph 2.0 Does Well | What Aleph 2.0 Struggles With |
|---|---|---|
| Localized edits | Color swaps, material changes, wardrobe updates, product recoloring | Cannot invent entirely new subjects or scenes that weren't in the original |
| Background | Background replacement, environment changes (season, weather, setting) | Sharp identity jumps between shots (e.g., day→night across a hard cut) |
| Lighting | Relighting, mood changes (warm→cool, day→night on same shot) | Very dark or very overexposed source footage degrades output quality |
| Multi-shot | Applies edits across up to 10 cuts without per-shot repetition | More than 10 cuts in a clip: must process in segments |
| Camera motion | Slow-to-moderate camera moves preserved cleanly | Handheld shake and fast camera motion produce wobble artifacts |
| VFX removal | Object removal, scene cleanup, distraction elimination | Motion blur on fast-moving subjects reduces edit accuracy |
| Keyframe precision | Up to 5 anchors at timestamp precision for brand-critical elements | Identity consistency across shots with sharp visual jumps between subjects |
| Aspect ratio | Output preserves source aspect ratio (aspect-ratio expansion also available via Aleph) | — |
The model cannot invent scenes or subjects that did not exist in the source footage. It cannot salvage fundamentally broken composition — poor focus, severe exposure problems, or extreme motion blur are not correctable by Aleph 2.0. The editing model is a refinement tool, not a repair tool.
Source video requirements are strict: clips must be between 2 and 30 seconds long, between 480p and 1080p, at 24–30 FPS, and use a conventional aspect ratio. Files outside these parameters will fail to process.
Aleph 2.0 in Figma Weave
Runway and Figma have integrated Aleph 2.0 as a native node inside Figma Weave, Figma's node-based AI workflow product. The Aleph 2.0 node in Weave allows teams to connect video editing steps to the rest of a design or creative production workflow: a frame-level design decision made in Figma can feed directly into an Aleph 2.0 edit node, which feeds into the next production step.
The Figma Weave integration specifically supports the keyframe workflow — bringing reference images designed or exported in Figma directly into Aleph 2.0 as anchor images, without exporting and re-importing files manually. The node-based interface lets users preview changes, refine iteratively, and explore multiple creative directions simultaneously within a connected workflow.
This integration targets design-adjacent teams (brand, marketing, creative production) where video editing has historically required a handoff to a separate post-production tool. With Aleph 2.0 in Weave, a designer can specify color, typography, and product appearance in Figma, then have those specifications propagate into video output through the Aleph 2.0 node, staying inside the Figma environment throughout.
Use Cases for Runway Aleph 2.0
The cases where Aleph 2.0 delivers the most value share a common structure: well-shot footage where one element needs to change without re-shooting.
Marketing and ad variations. A campaign has a hero video with the right motion, framing, and talent — but needs 6 versions with different product colors, seasonal backgrounds, or regional copy. Aleph 2.0 can generate those variants from the single source clip without re-shooting. Credit cost for 6 variants of a 10-second clip at ~150 credits per 10 seconds is substantially lower than production cost for re-shoots.
Product and packaging updates. E-commerce video assets become outdated when a product is reformulated, repackaged, or recolored. Rather than re-shooting or re-producing product demo videos, teams can supply the new packaging as a keyframe anchor and apply the update across existing footage.
Post-production cleanup. Background distractions, unwanted objects, crew reflections in windows, or outdated props in the background of an existing clip can be removed or replaced without a full post-production pass.
Relighting existing footage. A clip shot in neutral lighting can be shifted to warm-hour, cool-blue, or nighttime looks using Aleph 2.0's relighting capability, giving the same footage different emotional tones for different contexts.
When to Use a Different Tool
Aleph 2.0 is the right tool when you have existing footage to refine. Several other tools handle adjacent jobs better:
- Runway Gen-4.5 for generating entirely new video clips from a text prompt or reference image, when you have no source footage.
- CapCut for template-based editing, cuts, captions, and social-format assembly — tasks that don't require AI-driven content propagation.
- Descript or Pictory for repurposing long-form video content (recordings, presentations) into shorter clips, where the work is selection and assembly rather than content modification.
- Pexo (pexo.ai) for generating a complete, finished video from a description, script, URL, or images when no source footage exists. Pexo is an AI video agent that auto-routes each shot across Seedance 2.0, Kling 3.0, Veo 3.1, Runway Gen-4.5, Sora 2, MiniMax/Hailuo, PixVerse, and 10+ models, composes a three-layer soundtrack (voiceover, music, and Foley sound effects), adds titles and subtitles, and exports a finished video in 16:9, 9:16, or 1:1. The job distinction is direct: Aleph 2.0 edits footage you already filmed; Pexo builds the footage from scratch.
Related Reading
- Best AI Video Editor Online
- Best Automatic AI Video Editor
- Best AI Video Editor for YouTube Shorts
- Best Text-to-Video AI Online
Resources
| Resource | URL | What it is |
|---|---|---|
| Runway Aleph 2.0 announcement | runwayml.com/news/introducing-aleph-2-and-edit-studio | Runway's official launch post for Aleph 2.0 and Edit Studio |
| Aleph 2.0 product page | runwayml.com/product/aleph-2 | Official Aleph 2.0 product overview and feature documentation |
| Runway API (Aleph 2.0) | dev.runwayml.com | Enterprise API documentation including Aleph 2.0 endpoints |
| Figma Weave + Aleph 2.0 | figma.com/blog/direct-every-frame-with-runway-aleph-2 | Figma's announcement of the Aleph 2.0 node in Weave |
| Runware Aleph 2.0 API docs | runware.ai/docs/models/runway-aleph-2-0/guides | Third-party API documentation covering keyframe parameters |
| Pexo | pexo.ai | AI video agent for generating finished video from scratch |





