Project Setup
BatchRender maps data onto your project purely by name. Setting up a project means naming text layers and footage items after the columns in your data.
Text layers
Section titled “Text layers”Rename each text layer that should receive data to exactly match its column name. Layer names are what count, not the text content.

In this template, flavor, headline, price, cta and badge are the
visible text. color and accent are hidden text layers that expressions
read to recolor the ad (see collecting values in one comp).
For each row, every text layer whose name matches a column gets that cell as its text. Layers keep all their styling and animation; only the text content changes. An empty cell clears the layer’s text.
Footage items
Section titled “Footage items”For image or video swapping, rename the footage item in the project panel (not the layer) to match the column. Every comp and layer using that footage item updates at once.

A footage cell holds one of:
- a full path to a file, used as-is
- a bare filename such as
blood-orange.png, looked up in the Footage Path folder - a link to a file on the internet, see Files from Links
The value must include the file extension: shoe instead of shoe.png
fails the row. A file that cannot be found fails the row too, so a row never
renders with the wrong image.
An empty footage cell leaves the footage item as it is. After an earlier row,
that is the file the earlier row used. The log and
br-warnings
name the file the row used.
Optional: collect values in one comp
Section titled “Optional: collect values in one comp”BatchRender fills every matching text layer anywhere in the project, so naming the layers in your designed comps is all a project needs. For templates that span several comps, it can be easier to put one text layer per column in a comp of its own and let the rest of the project read from it with expressions.
The comp can have any name and does not need to be rendered. The examples
below call it data. Any layer can pick a value up with an expression on its
Source Text:
comp("data").layer("headline").text.sourceTextThe layer keeps its own font, size and color; only the text comes from the data comp. This pays off in several ways:
-
One value, many places. A headline that appears in multiple compositions is filled once and read everywhere.
-
Not having to worry about layer naming in the compositions.
-
Drive more than text. A number column can set a scale, a position or a duration, for example on a Scale property:
s = parseFloat(comp("data").layer("logo-size").text.sourceText);[s, s] -
Derived text. Combine values in the expression instead of adding columns, for example
"Only " + comp("data").layer("price").text.sourceText + " today". -
An overview at a glance. One comp shows every value of the current row.
Comps and projects
Section titled “Comps and projects”The comp column names the composition each row renders. Different rows can
target different comps in the same project, for example one comp per aspect
ratio:
| comp | output | headline |
|---|---|---|
| Promo-16x9 | promo_wide | Big Sale |
| Promo-9x16 | promo_story | Big Sale |
If your versions live in different project files, add a project column with
an absolute path to the .aep. BatchRender opens that project before
rendering the row. Rows without a project value render in whatever project
is open, and a row whose project is already open keeps it open as-is.
Otherwise BatchRender closes the current project and opens the new one without saving.