Editable project vs locked MP4: why the project is the asset

A locked MP4 is a finished answer to a question nobody has finished asking. The moment a client says "can the title come in later" or "the second shot feels too warm", a flattened render forces you to start again, while an editable project lets you change one thing and keep everything else. That is the whole argument: in production, the project is the asset and the render is a by-product.

This matters more now that so much footage arrives as generated clips or as one-click exports from AI tools. Below we look at what a flattened file throws away, how to rescue footage that arrives that way, and how to set up work so that every decision stays changeable until delivery.

What a flattened render throws away

A video file stores pixels and samples. Everything that produced them is gone. In practice that means:

• Edit decisions. Cut points, handles and the unused frames on either side of each shot. You cannot extend a shot by six frames if those frames were never kept.
• Layers. Titles, graphics, logos and lower thirds are now part of the picture. Fixing a typo means covering it or regenerating the whole thing.
• The grade. Colour is baked in, often in an 8-bit, heavily compressed file. Pushing it further brings banding and blocking.
• The mix. Dialogue, music and effects are summed into one stereo track. Turning the music down under one line is no longer a fader move.
• Captions. Burned-in subtitles cannot be corrected, translated or switched off.
• Versions. There is no history, no alternate take, no way back to the cut from last Tuesday.

None of this matters if the file is truly final. The trouble is that almost nothing is final the first time.

The re-roll loop

Generated video makes the problem sharper. When a clip comes out of a text-to-video tool as a single file, the only fix many tools offer is to generate again. A recurring complaint among practitioners is exactly this loop: the hand is wrong, so you re-roll, and the new version fixes the hand but changes the lighting, the framing and the actor's face.

Re-rolling treats every note as a reason to throw away everything. Editing treats every note as one change. The difference adds up quickly across a project with twenty shots and three rounds of notes. If you are paying per generation, it also adds up on the invoice, which we cover in the hidden cost of AI video credits.

How to rescue clips that arrive as MP4s

You will still receive flattened files: generated shots, client exports, archive material. Treat them as raw footage, not as finished pieces.

1. Ask for the best version available. If the tool or the sender can supply ProRes or a high-bitrate master, take it. Compression artefacts compound with every later step.
2. Ask for elements separately. Clean picture without text, music and voice as separate files, subtitles as a sidecar file. Many tools can export these if someone asks.
3. Generate longer than you need. Extra seconds at the head and tail become handles for transitions and timing changes.
4. Bring everything into a real project. Put the clips on a timeline, rebuild titles as live text, put audio on separate tracks and grade on top of the footage rather than inside it.
5. Keep originals untouched. Work from copies and keep the delivered files in a read-only folder.

From that point on, the MP4s are just shots. Every decision that follows lives in the project, where it can change.

Design the work so it stays editable

The best protection is a habit: never let a decision happen anywhere it cannot be revisited.

• Keep titles and graphics live until delivery. Text should be text, not pixels.
• Grade non-destructively, with versions you can compare.
• Keep captions as a track and export them as files. Burn them in only for the deliverable that needs it.
• Snapshot versions at every review round, so "go back to version two" is a click, not an archaeology project.
• Export interchange files (XML, EDL, OTIO, AAF) when a project needs to travel, rather than a picture file someone has to reverse-engineer. Our guide on moving a cut between Premiere, Resolve and Final Cut explains the formats.

The render becomes what it should be: one export from a living project, repeatable at any time.

How cinemaOS keeps decisions alive

cinemaOS is not a text-to-video generator. It is a Mac-native editor and finishing suite that treats the project as the asset, and almost every tool in it is built to leave something you can change later.

• Live titles. Titles and graphics from the CREATE chip stay editable on the timeline. An old baked title can be right-clicked and turned live with Make Live.
• Grades as settings. In Finisher, Grade > Color works with Input LUTs, wheels, curves, qualifiers, tracked windows and grade versions. Shot Match from a reference still lands as editable sliders, not a baked LUT.
• Captions as data. Transcription and subtitles live as caption tracks and export to SRT, WebVTT, EBU-STL, IMSC1 and other formats. Burn In is a choice you make for a specific deliverable.
• Design that returns to the cut. In Atelier, a Video Composition can be sent to the timeline as a live composition clip rather than a rendered file.
• History that survives. Version snapshots, checkpoints and backups keep earlier states of the project. Masters never overwrite an existing file.
• Interchange both ways. Export FCPXML, Premiere XML, EDL, OTIO, ALE or AAF (linked media) when the cut needs to travel.

When J.A.R.E.D. makes a change for you, it also lands on the timeline as ordinary edits that undo with ⌘Z. That is the same principle applied to AI: the output of an assistant should be a project state, not a file. More on that in when an AI editor says done but the cut is wrong.

FAQ

Is it ever fine to deliver only an MP4?

Yes, for the final deliverable. The point is to keep the project behind it. A platform upload or a client review copy should be an export, never the only copy of the work.

Can I turn an MP4 back into an editable project?

Not fully. You can detect shot changes and split the file at those points, which gives you a rough timeline, but titles, separate audio and the original grade cannot be recovered. Ask for the elements instead.

What should I archive at the end of a job?

The project file, all source media, any graphics and fonts, the delivered masters and the subtitle files. A self-checking archive, such as cinemaOS's Verified Archive, makes it easier to confirm nothing is missing.

Next step

On your next job, try the rule: nothing gets baked until delivery. If you want an editor built around that rule, cinemaOS runs on Apple silicon Macs, and the 60-day free trial needs no card. Bring in a few generated clips and see how much stays changeable.