What "editable" should mean for AI video, and why an mp4 is not it

You asked for a 30-second cut. It came back, it looked good, and everyone approved it on Friday. On Monday, legal wants the second line of the voiceover changed, and the social team wants a vertical version. If what you have is an mp4 and a chat history, both requests mean running the whole thing again and hoping the parts you liked survive.

That is the wall most people hit with AI video, and it has nothing to do with generation quality. It is about what the tool hands back. This post is about what "editable" should mean, why a rendered file is not it, and four questions you can answer in a minute for any tool before you commit a real project to it.

What a rendered file throws away

A finished video is pixels and a soundtrack. Everything that produced it is gone: where one shot ends and the next begins, the script, the timing decisions, the source generations, the music separate from the voice, the captions as text instead of burned-in shapes. Editors have a word for the thing that keeps all of that: a project. A project is references plus decisions. The clips point at media; the timeline records what was chosen. The render is what you make from a project when you are done deciding.

The clearest statement of the distinction comes from OpenTimelineIO, the open interchange format the film industry uses to move edits between tools. It describes itself as a format for "editorial cut information" and is explicit that it "does not include embedded video or audio. Video and audio media are referenced externally" (OpenTimelineIO docs). The cut is data. The media is media. An mp4 collapses both into one thing you can only play.

Descript's export documentation is a useful concrete inventory of what survives a handoff and what does not. Its timeline export carries the edits, copies of the media and the timecode into Premiere, Final Cut, Resolve and others, and does not carry effects, transitions, titles or sequences (Descript). That list is worth keeping in mind for any tool: the question is never "can I export" but "what comes with it".

What an editable project keeps

Reverse the list. An editable AI video project keeps:

• Shots as separate clips, each with the prompt, the references and the model that produced it, so one can be redone without touching the rest. Which of those inputs a shot depends on is covered in text-to-video vs image-to-video.
• The timeline: order, in and out points, durations, and the decisions behind them.
• Layers: captions as text, overlays, the logo, so any of them can change without re-rendering the footage under it.
• Audio as stems: voice, music and sound design separate, so a line can be swapped without regenerating the bed.
• The brief, script and shot list as data, so a change to the plan can flow back into the cut instead of being re-typed into a prompt.

With that, "change the second line" is a one-clip fix, and "make it vertical" is a reframe of existing frames rather than a new brief.

The existence of a shot-level fix is well established. LTX's retake system regenerates a time window inside a clip and states that "content outside the time window is preserved exactly as it was in the original", with video and audio regenerable independently (LTX). Runway's Aleph 2.0 does "localized edits with precise input video preservation" (Runway). HeyGen re-renders only the avatar scenes whose script, voice or avatar changed (HeyGen). The capability exists. Whether a given tool keeps enough of the project around to use it is the thing to check.

Four questions to ask any tool

Each one has a check you can do from the export menu or the docs, without generating anything.

1. Can I change one shot without regenerating the others?

Two very different things get sold under this heading. One is editing the pixels of a rendered clip in place: replace an object, extend the ending, adjust the lighting. Runway's Aleph and Luma's Modify work this way. The other is re-rolling a shot from its own prompt and references inside a persistent timeline, while every other clip stays byte-identical. LTX's retake, OpenArt's Director, which says it "redoes exactly that, nothing more" when you give feedback on a shot (OpenArt), and HeyGen's per-scene re-render work this second way.

The check: after generation, does the tool still know each shot's prompt and references, or only its pixels? If the shot plan disappears once the video exists, as Kling's own post-production guide implies when it sends users to Premiere or Resolve for anything after generation (Kling), you have a generator, not a project.

2. Can I re-cut to another aspect ratio without a new brief?

There are three mechanisms behind any "reframe" button, and they are not equivalent.

The check: does audio survive the reframe, and does it cost credits? A yes and a no means a real reframe. If the tool cannot say, assume regeneration.

3. Can a person open this in an editor they already use?

Somebody on your team finishes video in Premiere, Resolve, Final Cut or CapCut. The question is whether the AI tool's output arrives as a project they can keep editing or as a clip they can only place.

The check is the export menu. Look for a timeline format alongside the video: Premiere XML, FCPXML, EDL, OTIO, a native .prproj or .drp, plus a media folder, captions as an SRT file and audio stems. Adobe's own note on OTIO support describes what such a file carries: the cut list with clips in position, source in and out points, multiple tracks and markers (Adobe).

What the current field looks like, from each vendor's own documentation:

A ProRes file is a high-quality render. It is still a render. If the only thing that leaves the tool is footage, every future change goes back through the tool.

4. Will it still open next year?

Most AI video projects live on the vendor's servers. The project is a URL. That is fine until the plan changes, the product pivots, or the tool retires a model, which happens regularly: Runway retired Gen-3 Alpha in July 2026 and Google deprecated Veo 3 in favour of 3.1 within the same year. A shot that only exists as "regenerate with the model that made it" is not editable once that model is gone.

The check: is there a file on disk that describes the project? The most durable form is structured source. Remotion projects are code with JSON properties (Remotion); HyperFrames compositions are an HTML file that renders the same frames every time (HyperFrames); an OTIO or XML export with a media folder is the editor-native equivalent. Any of these can sit in a folder or a repository and does not need the vendor to exist. A hosted project with a render-only export cannot.

A fifth question, if you use an agent

Is the brief part of the project? An agent works from a plan: the job, the shot list, the references, the script. If that plan is stored as data alongside the cut, a change to the plan can be re-run as a change to the cut. If the plan lived only in a chat, every revision starts from the pixels. What that plan should contain is the subject of how to brief an AI video agent. HeyGen keeps the script per scene as the editable source; Remotion keeps the plan as properties; Kling's multi-shot plan exists at generation time and is not documented as re-editable afterwards (Kling). For agent-driven work, this is the question that decides whether revisions get cheaper over time or stay as expensive as the first run.

Where Voyager stands

We hold our own output to the four questions above, and we are in private preview, so the honest statement is about intent and current shape rather than a finished spec. Everything Voyager makes is meant to come back as a project: shots as clips with their prompts and references, a timeline, captions and audio as separate layers, and the brief and shot list stored with the cut. Which export formats ship at launch, and exactly how a reframe is performed, are the things to ask us about directly rather than assume from this post. If a specific interchange format matters to your team, tell us which one.

Frequently asked questions

Can I edit an AI-generated video after it is made, or do I have to regenerate everything? It depends on whether the tool kept a project or only a file. Tools with a persistent timeline and shot-level retake, such as LTX, OpenArt's Director and HeyGen's scene-based studio, can redo one shot and leave the rest untouched. Tools that hand back a clip need either an in-place pixel edit or a full regeneration.

How do I change an AI video from 16:9 to 9:16, and will the audio survive? Three ways: reframe the existing frames in an editor, which keeps audio and costs nothing; generative outpaint, which invents new picture and may drop audio; or regenerate at the new ratio. Check which one a tool does before relying on it. Luma's Reframe, for example, documents that its output is visual only.

Can I open a Runway, Kling or Veo video in Premiere or Resolve as a project? As a clip, yes. As a project, not from those tools' documented exports as of September 2026. Runway exports ProRes or PNG sequences and offers a panel that places clips into a sequence; Kling and Flow provide downloadable video. For a project handoff you need a tool that exports XML, EDL or OTIO with media, such as LTX Desktop or Descript.

What is an OTIO or XML file, and why would I want one from an AI tool? A timeline interchange file: a description of which clips go where, with in and out points, tracks and markers, referencing media files kept separately. It is what lets an editor open your cut and keep working instead of starting from footage. OTIO is the open standard; Premiere XML, FCPXML and EDL are older equivalents.

Which tools keep the script and shot list editable? HeyGen stores the script per scene and re-renders only what changed. Descript treats the transcript as the edit. Code-based tools like Remotion and HyperFrames keep the whole plan as source. Among hosted generators, this is the least documented capability, so ask before you assume.