Missing footage and consolidate
Why Consolidate All Footage often does nothing, how to relink missing footage showing color bars, and how to merge duplicate footage items safely with your AI.
Two project panel problems arrive together so often that they share a page: footage that has gone missing (color bars where your media should be), and footage that has been imported twice or more, which Consolidate All Footage then refuses to merge. Both have precise causes, and neither is a bug.
Why Consolidate All Footage does nothing
The command lives under File, then Dependencies, and its rule is stricter than it looks: two footage items merge only when they point at the same source file and agree on every interpretation setting. Frame rate conform, alpha treatment, field separation, loop count: one difference anywhere, and the pair is skipped without a message.
That silence is the whole complaint. A project with six copies of the same clip runs the command, nothing visible happens, and the six copies remain, because somewhere along the way one copy was conformed to a different frame rate or given a different alpha interpretation.
Three things worth knowing before reaching for a fix:
| Belief | Reality |
|---|---|
| "Consolidate deletes footage" | It merges duplicates and repoints every layer to the kept item. Nothing a layer uses is deleted |
| "Remove Unused Footage is the same thing" | Different command. It deletes items that no layer references, and only those |
| "It did nothing, so my items are not duplicates" | They may still be duplicates on disk. They differ in interpretation, which is why AE skipped them |
Color bars mean missing footage
When After Effects cannot find a source file, the item stays in the project and every frame of it renders as color bars. This is a placeholder, not a render error and not a missing plugin. A missing effect behaves differently: the project announces it in a dialog as it opens, naming the effects it cannot find, and the affected layers simply render without them.
To round up everything missing at once, type missing into the Project panel search field. After Effects treats it as a filter and shows only the items with broken links. From there:
- Right click the item, then Replace Footage, then File, and point it at the moved file.
- If a whole folder moved, relink one item from it. After Effects finds siblings in the same place on its own.
- File, then Dependencies, then Find Missing Footage does the same round-up from the menu.
Relinking restores every use of the item across every comp, with keyframes and effects untouched, because layers reference the item rather than the path.
Do the merge with your AI
Prism gives your AI a consolidation tool with two properties the menu command does not have: a preview, and a grouping rule that tolerates interpretation drift. It groups items by source path, pixel size, frame rate and duration, so two copies of the same file that differ only in a conform setting still count as the same footage.
Ask, in your AI client:
Find duplicate footage items in my project and consolidate them. Dry run first.
The dry run reports what would merge and what would remain, without touching the project. If the answer looks right, ask it to apply. Every change lands as one undo step, and a restore point is taken before anything destructive.
Two footnotes on the tool's judgement:
- Solids, placeholders and other synthetic sources never merge. They are not files.
- If two items report different sizes or durations, they stay separate even when the path matches, because merging them would change what a comp renders. There is an explicit override, and the tool warns before using it.
When the project is clean
A consolidated, fully linked project is the difference between an AI that reasons about your real media and one that reasons about six aliases of it. Cleanup is also the step before archiving or handoff, where every duplicate becomes a question for whoever opens the project next.
Related
- Troubleshooting: when the connection itself misbehaves
- After Effects quirks: behaviours that surprise everyone once
- First prompts: what to ask, and what comes back
When Prism rejects your script
Why Prism rejects a script before it reaches After Effects, and the exact fix for each case: the TypeScript gate, the result envelope rule, banned constructs, and template-literal number errors.
After Effects quirks
Behaviours of After Effects itself that look like Prism failing: locked layers, temporal ease array sizes, match names, parenting time compensation, time remap keys, text stroke, and fonts.