How to Recover an Unsaved Video Project

The worst moment in video editing is not a hard problem. It is an app disappearing and the two seconds before you find out how much you lost.

First, do not do anything

The instinct after a crash is to reopen the app and immediately start rebuilding. That is the single most likely way to lose the thing you are trying to recover.

Reopen the app and wait. Recovery is normally offered on next launch, and it needs a moment to find the state it saved. If you start a new project first, you are writing over the situation.

Do not delete or move the source clips. A recovered project is a set of edits pointing at media. Move the media and the recovery succeeds and then cannot find anything.

What autosave actually saves

It is worth understanding, because it sets your expectations correctly.

Autosave saves the edit, not the video. Your cuts, your captions, your zooms, your grade, your titles: a description of what to do to your clips. It does not save a rendered file, which is why recovery is fast and why the source media has to still be there.

That is also why a recovered project opens instantly rather than re-rendering: nothing was rendered, so nothing was lost.

How autosave actually works covers the timing and what triggers a save.

Version snapshots, the other safety net

Autosave protects you from crashes. It does not protect you from yourself.

The more common disaster is not a crash: it is realising that the version from an hour ago was better, after autosave has faithfully saved every step of making it worse. Autosave is the wrong tool for that, because it only ever holds the latest state.

Version snapshots are the answer, and going back to an earlier version of your edit covers them. Zella keeps six.

If recovery is not offered

Work through these in order.

Check for the project in the app's own project list. Recovered work often just reappears there rather than as a prompt.

Look for a version snapshot. If the current state is broken or empty, an earlier snapshot may be intact.

Check the source media is where it was. A project that cannot find its clips can look like a lost project when it is actually a broken link. Relinking is a fix rather than a rebuild.

Reboot before concluding anything. More recovery failures than you would expect are the app failing to start cleanly rather than the data being gone.

The habit that makes this a non-question

Export a rough cut early.

Not because you need it, but because a rendered file is the one artefact that cannot be corrupted by anything that happens to the project afterwards. Five minutes into a serious edit, export whatever you have. If everything goes wrong later, you are recovering from a worse version rather than from nothing.

This is more useful than any amount of manual saving, because it protects you from the failure modes that autosave does not: a corrupted project file, a deleted source clip, an edit you made worse over two hours.

Why editors crash at all

For context rather than comfort, three causes account for most of it:

Memory. Video editing holds a lot in RAM. Long timelines, high-resolution sources and many effects at once are the pressure points, and a machine that is also running a browser with forty tabs has less to give.

Codec edge cases. An unusual file from an unusual camera or a partially written recording can hit a decoder path that fails.

Disk. A full disk during a write is an underrated cause and an easy one to rule out.

If a specific project crashes repeatedly and others do not, it is usually one clip. Remove clips until it stops, and you have found it.

What good looks like

You should be able to force-quit an editor mid-edit and lose nothing that matters. That is the standard, it is achievable, and it is what continuous autosave plus snapshots is for.

If you are still in the habit of pressing save every few minutes out of anxiety, that is a reasonable instinct formed by older software. It costs nothing to keep. But the modern answer is that the app should already have done it.

Apple's Final Cut Pro guide documents the same model: continuous saving plus periodic library backups, with no manual save command at all.

Common questions

What should I do first after a crash? Reopen the app and wait. Recovery is normally offered on next launch. Starting a new project first is the action most likely to overwrite the state you want back.

Does autosave save my rendered video? No. It saves the edit, meaning the list of instructions. That is why recovery is instant and why moving your source clips breaks a recovered project.

What if recovery is not offered? Check the project list, look for a version snapshot, confirm the source media has not moved, and reboot before concluding the work is gone.