After Effects Collect Files, Explained: How to Archive Projects on Mac Without Missing Assets

Every motion designer has opened an old After Effects project to a wall of color bars. The .aep file was saved, the delivery went out, the project felt done. But an .aep is a list of references: footage, audio, stills, precomps pointing at files that lived wherever they lived on delivery day. Move or lose any of them, and the project file opens as a skeleton.

Archiving an After Effects project is a two-part job. Part one is gathering everything the project references into one folder, which is exactly what Collect Files does. Part two is making sure that folder exists as verified copies on storage that outlives your laptop. After Effects gives you a real tool for part one and nothing for part two.

Why the .aep file alone is worthless

An After Effects project file stores your compositions, layers, keyframes, and effect settings. It stores none of your media. A 40 MB .aep can represent 80 GB of footage that exists only as file paths. This is by design (imagine every save duplicating 80 GB), but it means the project file and the project are different things.

macOS makes the references extra fragile: renaming a parent folder, reorganizing a drive, or migrating to a new Mac silently breaks every absolute path. After Effects will hunt for missing files in nearby folders when you relink one, which helps, but only if the files still exist somewhere.

So before anything touches an archive drive, the project needs to become self-contained.

How to use Collect Files properly

Clean the project first, then collect:

1. Remove what you don't need. File > Dependencies > Remove Unused Footage drops imported items no comp uses. If the project accumulated versions (v1 through v14 comps), consider Reduce Project on a copy of the .aep with only the final comps selected, so the archive doesn't carry 13 dead versions of everything.
2. Fix anything already missing. Collect Files cannot gather footage After Effects can't find. Search the Project panel for missing items (the color-bars icon) and relink or delete them now, not in three years.
3. Run the collection. File > Dependencies > Collect Files, set Collect Source Files: All. After Effects copies the .aep and every referenced asset into a new folder you choose, organized into a (Footage) folder, and writes a text report listing everything it gathered, plus the effects used per comp.

The result is a folder that opens on any Mac with After Effects installed, no relinking. Target it at the project's final resting place, or collect to your working drive and archive the folder from there.

For big projects, do the collection when the project wraps. The morning after delivery is the last time you'll reliably remember which of the five final_FINAL comps was actually final.

What Collect Files misses (and what to do about it)

The collected folder is self-contained for media, and only media:

• Fonts. Not collected. Adobe Fonts in particular deactivate when a subscription lapses or the font leaves the service. List the fonts in a text file inside the archive folder, and where licensing allows, keep the font files themselves in it.
• Plugins and scripts. Effects from third-party plugins (Red Giant, plugins like Element 3D with their own asset libraries) are installed software, not project files. The collect report lists which effects each comp uses; keep that report, and consider pre-rendering plugin-heavy comps to ProRes so the visual result survives even if a plugin never gets a Silicon update.
• The disk cache. Not collected, and you don't want it: it's regenerable preview data, often tens of gigabytes. Keep your disk cache on a fast scratch location and exclude it from any backup.
• Anything already missing. Collect Files gathers what After Effects can resolve. Missing stays missing, which is why step 2 above comes first.

Auto-save protects your session, not your project

After Effects auto-saves by default every 20 minutes, keeping the most recent versions (5 by default) in an Adobe After Effects Auto-Save folder next to your project file. After a crash, open the newest auto-save and you've lost minutes, not the afternoon. Raise the version count in Preferences > Auto-Save if you make aggressive changes; the files are project-file sized, so the cost is trivial.

But note what auto-save is versioning: the .aep, on the same drive as the project. Like the project file itself, auto-saves die with the drive. They're crash insurance, not a backup.

Archiving the collected folder: two destinations or it didn't happen

A collected project folder on a single external drive is one drive failure away from being no archive at all. The 3-2-1 standard applies to motion work the same as to footage: three copies, two storage types, one offsite. In practice: the collected folder on your working or archive drive, a second copy on another drive, a third in a cloud bucket (B2, R2, S3).

Keeping that current manually across every wrapped project is the part that fails. This is what Tusk is built for. Make your archive folder (or each client's folder) a project with two backup destinations, and Tusk copies every file to both and verifies each transfer with a BLAKE3 checksum, so a copy counts only once the bytes are confirmed intact. The file table then shows, per file and per destination, what's backed up where, including on drives that are sitting unplugged on a shelf. When a client's revision request arrives a year later, you see which drive holds the project without plugging anything in (more on that in tracking files across drives).

The payoff for a working Mac: once every file of a wrapped project shows verified on both destinations, Delete local clears it off your machine. Tusk physically re-checks every destination first and refuses if anything is missing, so "I archived it" and "it's actually safe" stop being different statements. Restore pulls the project back from the fastest available source when revisions come.

The honest boundary: Tusk backs up and tracks the files in your project folders. It does not scan an .aep, collect dependencies, or repair broken links; that's Collect Files' job inside After Effects. Run the collection first, then let the backup layer take over. Each tool covers what the other can't.

The wrap checklist

1. Remove Unused Footage, relink or delete anything missing.
2. Collect Files, source files: All, into the project's archive folder.
3. Drop a FONTS_AND_PLUGINS.txt (or just keep the collect report) in the folder; pre-render plugin-critical comps.
4. Back the folder up to two destinations, one offsite, verified.
5. Only then: Delete local, reclaim the space, move on.

Ten minutes per project. The alternative is explaining to a client why the re-edit starts from color bars.