Scripts, plugins and Templater automate three different layers of an After Effects job, and picking the wrong layer is how a team can end up with a folder of clever tools and a pipeline that still needs a person at every step. A script automates a task inside one open project. A general plugin adds a capability to After Effects itself. Templater, which is a plugin, adds something larger, a way to turn a list of rows into a list of finished videos.
We make Templater, so we have a stake in this question and we will say so now. We will also say where a script or a smaller plugin is the better buy, because a team that solves a small problem with a large tool is just as unhappy as a team that does the reverse. The goal here is to give a producer, a developer or a marketer a way to sort their own situation in a few minutes.
Three layers, and what each one touches
It helps to stop thinking of these as three competing products and to think of them as three places where automation can attach. Each one reaches a different distance from the person at the keyboard.
A script is a file of code that runs inside After Effects and acts on the project that is open. In Dataclay’s own documentation, ExtendScripts used as Templater event scripts are described as scripts that interact with objects inside the project file, such as assets, compositions, layers, keyframes and effect parameters. That is a good summary of the category. A person opens a project, runs the script, and the script changes things faster and more consistently than a mouse would. This is general practice, and a specific script from any author should be checked against its own description. Renaming layers by rule, spreading keyframes, building a repeated structure of comps and tidying a project before handoff are the kind of jobs a script suits. Each one is a task a human could do and would rather not.
A general plugin adds a capability to After Effects that was not there before. It might arrive as an effect you apply to a layer, a panel you dock in the workspace, or a mix of both. The host program still owns the project and still renders the pixels, and the plugin changes what After Effects is asked to do or how the work is organized. We wrote a longer explanation in what an After Effects plugin is, so we will not repeat the whole definition. For this decision the point is narrower. A plugin is built as a tool for the person sitting at the machine. It speeds up their work. It does not, on its own, decide where a list of jobs comes from or who presses go.
Templater is a plugin in the sense that matters for installation. The Templater panel lives inside After Effects, you design your composition there, and the workflow starts like any other After Effects workflow. What makes it a different layer is what it is built around. You rig a template, which means marking the parts that should change, such as text, images, colors, branding and embedded footage, and mapping each one to a column or key in a data source. Then you pair the rigged template with that data source, and every row becomes one version of the video. The data source can be Google Sheets, a tab-separated file exported from a spreadsheet application, a JSON file or feed, or QUE, our own data tool.
So the three layers differ in what they take as input. A script takes a project. A general plugin takes a project plus a person’s choices. Templater takes a project plus a table. That one difference explains the rest of this article.
Script vs Templater
Scripts handle tasks; Templater handles lists
- What does it take as input?
- ScriptA project
- TemplaterA project plus a table
- Who starts the work?
- ScriptA person runs it every time
- TemplaterBot checks the data source on its own
- How do failures appear?
- ScriptNo built-in knowledge of bad input
- TemplaterRow gets an error code such as ERR::MEDIA or ERR::AFXHOST
- Maintenance burden?
- ScriptOne author; burden stays with that person
- TemplaterVendor moves that burden to the vendor
Use a script when the job is a task. Use Templater when the job is a list.
Three automation layers
Each tool touches a different layer of the job
| Tool | Takes as input | What it adds |
|---|---|---|
| Script | An open project | Faster, more consistent task on layers, keyframes, comps |
| General plugin | Project plus a person’s choices | A capability not in After Effects before |
| Templater | Project plus a table | Every row becomes one version of the video |
The questions that decide it
Before comparing features, answer four plain questions about your own work. The answers sort the options faster than a feature table can. Treat what follows as general practice for choosing any After Effects automation, not as a rule that only favors us.
The first question is where the variation comes from. If the thing that changes between jobs is a decision you make while looking at the screen, such as how a title should enter or which shot holds longer, you are automating craft, and a script or a smaller plugin is the right shape. If the thing that changes is data that already exists somewhere, a name, a price, a language, a clip, a score, then you are automating a list, and the list is the problem to solve. A script can be taught to read a list, but then its author is building a batch system, and a batch system is a bigger piece of software than the script anyone originally bought.
The second question is who starts the work. A script runs when a person runs it. A panel runs when a person clicks. If the answer to “who starts it” is “a person, every time,” you have not removed the person, you have shortened their afternoon. That can be exactly right. It is wrong only when the real requirement is that videos appear without anyone at the keyboard. Templater’s top edition, Bot, exists for that case. It checks the data source on its own, picks up rows that are marked ready, and runs them through. Developers can also push data in through the command line or build their own web or mobile front end that feeds the data source. We do not ship that front end. We provide documentation so a developer can build it, and it is fair to count that development time when you weigh the options.
The third question is what happens when row 212 breaks. A batch of any size can meet bad input, a missing footage file, a headline twice as long as the design expected, a font without the right glyphs. A script that only edits layers has no built-in knowledge of any of this, because those events live around the edit and not inside it. A system built for batches has to treat failure as a normal state. In Templater’s Bot, each row carries a render-status that moves from ready to queued to processing to done, and when something goes wrong the row gets an error code such as ERR::MEDIA for an asset problem or ERR::AFXHOST for an After Effects error. A bad row becomes a visible row in your sheet instead of a mystery in the morning. If you build your own loop around a script, you will need to design that behavior yourself.
The fourth question is who will maintain it in a year. A script written by one person is a small piece of software with one author. When that person leaves, or After Effects changes, or the template gets redesigned, someone has to understand the code. A plugin from a vendor moves that burden to the vendor, with the usual trade that you take what the vendor builds. We went through the build-it-yourself side in building custom After Effects scripts in-house versus using Templater, and the fragile-expression version of the same problem in when an expression is too fragile to maintain.
A hypothetical case, followed through each layer
Here is an example we made up, a hypothetical case, so treat the details as illustration and not as a report from a customer. A producer at a company with offices in many cities has a fifteen-second promo. Every office wants its own version with the office name, a street address and a local photo. The design is finished and approved. The only remaining work is making all the versions and getting them delivered.
With scripts alone, the producer finds or writes a script that swaps text and an image in the open project. It works well. They run it, render, run it again with the next office’s values, render again. The script did exactly what it was meant to do, and the producer is still the loop. They type or paste each set of values, they start each render, and they rename each output by hand. For a small number of offices this is a perfectly good afternoon. As the list grows, the time cost grows with it in a straight line, and so does the chance of a mistyped address on a version nobody checks.
With a general plugin, the producer might add a panel that handles the swapping with a nicer interface, or an effect that adjusts the layout when a name runs long. This is a real improvement in comfort. The producer is still the one who feeds the work in and starts it. The plugin made the producer’s hands faster. It did not move the list out of the producer’s head and into a file.
With Templater, the producer rigs the composition once. The office name, the address and the photo each become a dynamic layer tied to a column. The offices go in a sheet, one row each, with column names that match the layer names. Layout rules can scale and align each dynamic layer relative to its composition, and attach it to its neighbors so that layers chained beneath it follow when it changes. Preview with data lets the producer step through jobs before committing, which is the cheap way to find the row that breaks the design. Then Templater Pro renders the batch, and a custom output name built from the data source keeps each file identifiable. The Rig edition prepares the project, Pro adds batch render and replicate, and Bot adds the unattended operation described earlier. The producer’s work moved from running the loop to designing the template and keeping the sheet clean.
None of this makes the first two layers wrong. If the producer needed one office’s version once, the script would have been the faster tool, and Templater would have been more than the job deserved. The case only shows where the loop lives, and the loop is the thing that decides which layer you want.
They are not rivals, and where Templater is the wrong buy
The cleanest way to hold the three layers in your head is as a stack. You can combine them, and in Templater’s own design you are expected to. Templater Bot supports event scripts, which are scripts that hook into the moments Templater broadcasts as it works, such as before data is retrieved, after a job, or after a batch. Event scripts can be ExtendScripts that reach into the project, or shell scripts that do outside work like moving files, sending notifications, updating a database or transcoding. Event scripts only run in Templater Bot, so they are an edition-level feature and not something every license includes. We cover the idea in event scripts explained and the ExtendScript side in using ExtendScript with Templater events. In practice this means the script you already trust does not have to be thrown away. It can become one step in a larger pipeline, run at the right moment for the right row.
Templater also reads its data into After Effects expressions, which gives a designer a way to build small behaviors on top of the data without writing a standalone script. That is covered in using Templater data in After Effects expressions.
Now the honest part. Templater is the wrong tool in several situations, and it is better to know them before you install anything.
It is the wrong tool when the work is craft and not data. If you are animating a one-off piece, a script that tidies a project or a plugin that adds an effect is what you want. A data-driven system pays for itself when the same design is made many times, and it costs setup time when the design is made once.
It is the wrong tool when your team does not use After Effects. Templater requires Adobe After Effects, because it is a plugin that lives there. A team that wants video generated entirely outside After Effects, from a web editor or an API, is shopping in a different category. We wrote about how that category compares in our other posts, and we would rather you pick the right category than force-fit ours.
It is the wrong tool when you need a customer-facing interface and have nobody to build one. Templater does not come with a front-end, web or mobile application. We designed it so developers can build the interface they need on top, and our command line support is there for that reason. If you lack the staff for that build, the interface is a cost to plan for and not a feature that arrives in the box.
It can also be more than you need for a small, steady job. Dataclay’s trial includes all features for all versions, with a watermark on dynamic layers, and the command line is available in the trial. Using the trial on your real template is a cheap way to find out whether your job is a list problem or a task problem before you commit to anything. We would rather a team learn that from the trial than from a purchase.
Before you buy
Check these before choosing Templater
- Confirm the same design will be produced many times from a table of data
- Confirm your team already builds in After Effects
- Plan for developer time if you need a web or mobile front end, Templater does not ship one
- Run your real template through the trial before committing, the trial includes all features, with a watermark on dynamic layers
One more caution applies to every option, ours included. Automation does not replace the design thinking. Rigging a template means deciding which layers are dynamic, what a long name should do and what happens when an image is missing. A script has the same requirement in a different form, because someone has to decide what it should do when the project is not shaped the way the author expected. The tool carries out decisions. It does not make them.
How to choose, in one pass
Start with the loop. If you are the loop and you are happy to be the loop, buy or write a script, or add a small plugin, and move on. That is a good outcome, and a modest one that costs little.
If the loop is a table of rows that already exists, and the number of rows is going to keep growing or keep changing, you are in the territory Templater was built for. Rig the template, point it at the sheet or the feed, preview a few rows, and let Pro render the batch. A step-by-step version of that sits in our guide on rendering versioned video in a batch process with Templater.
If nobody should have to start the batch, the question moves from Pro to Bot, and the planning moves to the data source and whatever feeds it. In that case the useful reading is on what happens when a batch fails mid-queue, because failure handling is the part that separates a demo from a system you can leave running.
If you cannot tell which case you are in, run one real template through a trial. The result will show you whether your job is a task or a list, and that is the only question that matters in the end. Our learn section collects the rest of the material, and the QUE page explains the data tool for teams that want their jobs queued from a central place.
The short version is this. Use a script when the job is a task. Use a plugin when the job is your own speed. Use Templater when the job is a list. And when the job is all three at once, use them together, with the scripts hanging off Templater’s events instead of standing alone.
We covered a lot of ground above. Here are answers to the questions a team has once it has sorted its own case into one of these layers.
Frequently Asked Questions
Is Templater a script or a plugin?
Templater is a plugin. Its panel lives inside After Effects, and you design your composition there as you would for any other project. What sets it apart from a single-purpose plugin is that it is built around a data source. You rig a template, pair it with a spreadsheet, a JSON file or feed, or QUE, and each row becomes one version of the video. It also supports scripts of your own through event scripts, so the two ideas work together.
Can I keep using my own After Effects scripts if I adopt Templater?
Yes. Templater Bot supports event scripts, which are ExtendScripts or shell scripts registered to run before or after specific Templater events, such as before data, after a job or after a batch. Your existing script can become one step in the pipeline and run for each row at the right moment. Event scripts only run in Templater Bot, so confirm the edition you need before you plan around them.
When is a script enough and Templater too much?
A script is enough when the work is a task you run yourself on one project, such as renaming layers by rule or cleaning a project before handoff. Templater is more than you need when you make a design once, or when a person starting each run is fine. It pays off when the same design must be produced many times from a table of data. The free trial includes all features, so you can test your own template before committing.
Do I need a developer to automate After Effects with Templater?
Not to rig a template and render a batch. A motion designer can map layers to columns, preview with data and render from the panel. A developer becomes useful when you want videos created without anyone present, for example from a web or mobile front end that feeds the data source. Templater does not ship with that front end. We provide documentation and a command line interface so a developer can build it.
What happens when one row has bad data?
In Templater Bot, each row carries a render-status that moves from ready to queued to processing to done. If a row fails, it gets an error code instead, such as ERR::MEDIA for an asset problem or ERR::AFXHOST for an After Effects error, so the problem shows up in your sheet. Previewing with data before a large batch is the cheap way to catch the row that will break the design before it costs a render.
Does Templater read an Excel file directly?
No. Templater does not read an Excel file directly. You export the data to a tab-delimited file first, or you use a Google Sheet, a JSON file or feed, or QUE. Whichever source you choose, the column names or keys need to match the names of the dynamic layers in your composition, because that match is how each row finds its layer.
Does Templater work without After Effects?
No. Templater is an After Effects plugin and needs After Effects installed on the machine where it runs. If your team wants video generated entirely outside After Effects, a plugin is not the right shape for that goal. If your designers already build in After Effects, keeping the work in the same program means the design they approved is the design that gets versioned.
