How to Organize an After Effects Project

Project panel folders organise AE—they do not move your media on disk

An After Effects project stores compositions and references to source files used by footage items. Adobe’s current documentation explicitly notes that folders created in the Project panel exist only in that panel. This distinction matters: dragging footage into an `03_FOOTAGE` folder makes the project easier to read, but it does not relocate the movie file in Finder or Explorer.

A scalable Project panel hierarchy for motion work

The numbers are optional. Their value is predictable sorting on large jobs. A five-second logo reveal does not need nine folders; a broadcaster package with dozens of lower thirds, transitions and language variants probably does. Scale the structure to the project while keeping masters, modules and source media conceptually separate.

Give master, scene and precomp levels different responsibilities

A master composition should be an obvious delivery boundary: duration, frame size, frame rate and final sequence. Scene compositions group narrative or programme sections. Precomps group elements because they form a reusable behaviour, a logical module or a manageable subscene. When every two layers are precomposed without a structural reason, nesting becomes navigation overhead.

1. 01
   Master = deliverable boundary

   Make it obvious which compositions can safely enter Render Queue or Media Encoder.

2. 02
   Scene = sequence responsibility

   Use scene/segment comps to divide meaningful parts of the timeline, not arbitrary layer counts.

3. 03
   Precomp = module or behaviour

   Logo lockups, title engines, repeated transitions and reusable UI/broadcast modules are good candidates.

4. 04
   Avoid nesting as hiding

   If a precomp exists only to make the parent timeline look shorter, ask whether it actually improves ownership and navigation.

Composition names should identify function and variant

Avoid encoding every possible fact in the composition name. Function and meaningful variant are enough. Decide whether version lives mainly in the `.aep` filename or in master-comp names; do not create two conflicting version systems without a reason. In pipelines with automated outputs, keeping a stable master comp name while versioning the project file can be safer.

Sort footage at import time, not after the deadline

Adobe allows footage items and compositions to be organised freely with Project panel folders and provides Project search for criteria such as missing source files. Use that flexibility immediately. After 150 imports, every unlabeled asset looks equally expensive to sort; at import time you still know exactly what it is and why it exists.

• FOOTAGE: camera originals, stock clips, screen captures, image sequences
• GRAPHICS: AI/PSD sources, logos, stills, textures and illustrations
• AUDIO: voice-over, music, SFX and mix references
• REFERENCE/DATA where genuinely required
• Proxy relationships documented where they affect handoff/render behaviour

Timeline layer names are part of the project interface

A perfectly organised Project panel does not help much if the working timeline contains `Shape Layer 47`, `Null 18` and `Text 22`. Layer names become especially important in expression-heavy templates and Essential Properties systems because they tell another designer which layer is content, control, background or effect.

Version before destructive dependency cleanup

Adobe recommends making a backup by incrementing and saving before actions such as removing unused footage, consolidating footage or reducing a project. This matches a useful production principle: create a checkpoint before any operation that can remove project structure or dependencies.

Do not confuse Auto-Save with intentional versioning. Auto-Save helps with crash recovery. A deliberate `v07` can represent a client-revision boundary, a structural refactor, a pre-delivery checkpoint or a cleanup state that you may need to return to later.

• Use sortable versions such as v01, v02, v03 rather than final/final2/latest.
• Add a date when it materially helps archive identification, not as random filename noise.
• Record which version produced the approved output.
• Keep major clean-up operations reversible through a saved previous project file.

Use Dependencies tools deliberately

Reduce Project deserves particular care. Adobe warns that expressions can refer to elements in compositions outside the selected nested hierarchy; those external compositions may be removed by reduction. Run it on a versioned/archive copy and validate the result instead of treating it as a harmless “clean project” button.

Collect Files is the transport/archive step

Adobe’s Collect Files command creates a new folder containing a project copy, selected footage/proxies and a report describing resources such as files, effects and fonts needed to recreate/render the project. Adobe positions it for rendering, archiving and moving a project to another computer or user account.

1. 01
   Choose collection scope

   All, All Comps, Selected Comps and Queued Comps are different archive intentions. Collect what the recipient actually needs.

2. 02
   Resolve proxy behaviour

   Decide whether the package should follow current proxies or carry source+proxy options.

3. 03
   Reduce only when validated

   A smaller package is useful only if it has not removed hidden expression or reference dependencies.

4. 04
   Open the collected copy independently

   After collection, validate the new package rather than assuming it behaves exactly like the original workspace.

5. 05
   Keep the generated report

   It can document effects, fonts and other requirements useful to the next workstation.

My final AE project handoff checklist

1. Can a new designer identify the renderable master compositions immediately?
2. Do scene and precomp boundaries have understandable reasons?
3. Are footage, graphics and audio organised in the Project panel?
4. Are timeline control/content layers named by role rather than defaults?
5. Are expression and plug-in dependencies visible/documented?
6. Do master frame rate, dimensions and duration match delivery requirements?
7. Have obsolete revision comps been separated or removed from the working hierarchy?
8. Have unused/duplicate footage items been reviewed?
9. Was a version/backup created before destructive cleanup?
10. If the project moves machines, has the collected package been reopened and tested independently?