Skip to main content
With Generate report ticked, Collect Files Pro writes a <project name>_Report file next to the collected project, as .txt, .md, or both, depending on the format you chose. The report records:
  • Report created: date and time (GMT).
  • Project file and root folder: what was collected and where it went.
  • Scope: which collect option was used.
  • Collected compositions: every comp in the collection, marked as a master comp or a precomp.
  • Collected files: every footage file with its path inside the collection and its size, plus totals for file count, proxy count, and overall size.
  • Render folder: where render output points, if you enabled Change render output.
  • 3D renderers: whether any collected comp uses Advanced 3D, Classic 3D, or Cinema4D, so a render machine knows what it needs to support.
  • Effects used: every effect with its match name, how many times it’s used, and in which comps. Handy for checking a render farm has the right plugins installed.
  • Fonts used: every font with its PostScript name, whether it came from Adobe Fonts, and where it’s used.
  • Comments: whatever you typed into the Comments box.

Masters and precomps

Each collected comp is marked as a master or a precomp:
  • A master comp isn’t used inside any other comp; it’s a top-level comp, typically the one you’d render.
  • A precomp is nested inside another comp somewhere in the collection.
This makes the report an instant map of the project for whoever receives it: the masters are the deliverables, everything else is supporting structure.
The Markdown version renders nicely anywhere Markdown is supported (GitHub, Notion, Slack), so it doubles as a handoff document when sending a job to another studio or a render farm.