A project that renders perfectly on your desk will fail on another machine if even one file, font or plugin it depends on is missing there. The fix is rarely clever. You decide where every dependency lives, you make that place reachable from every machine that renders, and you test on the render machine before the real job starts. This article walks through how to do that for linked footage, dynamic assets and fonts when the render happens somewhere other than where you built the project.
Most of the pain comes from the same quiet fact. After Effects does not store your footage inside the project file. It stores references, which are paths to files. Those paths make sense on the computer where you worked and may mean nothing on another one.
What actually breaks when a project moves
Consider a designer named Priya who builds product spots on a Mac. The template pulls a background loop from a folder on her external drive, a product photo for each row from a shared folder, a logo from a project folder, and uses a brand font she installed last year. The studio’s render machine is a Windows computer in the equipment room, and for busy weeks they rent a Windows Server machine in the cloud. She copies the project file across, starts the batch and watches every item fail.
The error that appears is one our FAQ covers. After Effects reports “Failed at N/A” on the render queue items. That message means After Effects did not find one or more assets, footage files or font dependencies in the location the project specified. Often the files were moved or deleted. In Priya’s case nothing was deleted. The files simply do not exist at those paths on the new machine.
Three separate things are hiding in that one error, and it helps to keep them apart.
Static footage. The background loop, the logo and the music bed are the same for every video. They are referenced in the project and have to exist at a path the render machine can resolve.
Dynamic assets. The product photo changes by row. Its location comes from your data, so the path or address is a value in a column rather than a fixed reference in the project. These break differently, because the project can look fine while one row fails.
Environment. Fonts and plugins are not files in your project at all. They are installed on the computer. A font that is missing on the render machine either fails the job or substitutes something else, depending on how the application handles it, and a substituted font changes your layout in ways a text-fitting rule cannot predict.
A fourth thing sits behind all three, and it is the version of the software. The render machine needs After Effects and Templater installed. Dataclay publishes different Templater builds depending on your After Effects version, and older After Effects releases need the Legacy installer. If the machines differ, you can build a project on one and have it behave differently on the other.
Choosing where assets live
You have a small number of real choices, and the right one depends on how many machines you have and how fast they change.
Keep everything in one project folder and move the folder. This is the simplest approach and it works for a single render machine. Put the project, the static footage and a folder for the per-row images side by side, and move the whole thing as a unit. Collect files into a consistent structure before you start building, because untangling a project that has drawn from a dozen places on a drive is painful after the fact. This is the approach for a small studio with one or two machines.
Use a shared network location. If several machines render, give them all a path to the same place. Everybody sees the same files, and an update to a logo is an update for everyone. The weak point is the path itself. A drive mapped as one letter on one machine and another letter on a second machine is the single most common cause of mysterious failures in a mixed studio. Standardize the mount on every machine, and write it down. This is general practice, not a Templater rule, and it applies to any renderer.
Reference remote files. Templater can reference local or cloud-based footage, so a data row can point at a file that lives on a web server or in cloud storage rather than on a disk. That removes the “is it mounted” problem, and it suits per-row images that are already hosted somewhere. It adds a different one, which is network access. The render machine has to reach the address, and a slow or unavailable source becomes a slow or failed row. We wrote a separate post on tapping remote footage with Smart URL Processing, and it is the place to start if your assets already live online.
Copy assets to each machine ahead of time. For a fixed set of static files, local copies on each render machine are fast and predictable. The cost is housekeeping, because someone must keep the copies in step. This is a good fit for fonts and plugins in particular, since those cannot be shared across a network the way footage can.
Many studios end up with a mix. Static brand assets and fonts are installed locally and updated on a schedule, per-row images arrive from a shared or hosted location, and the project file travels on its own.
Preparing the project on the render machine’s terms
This is where Templater’s Rig edition earns its keep. Rig lets an artist prepare an After Effects project for a different machine running Pro or Bot. It maps the data to composition layers and previews how the layers change as data is processed, but it does not render batches. That makes it a sensible seat for the person who builds and checks the project, while Pro or Bot seats do the rendering. Our piece on the value of Templater Rig describes where it fits on a team.
A few Templater features are specifically useful here.
Project file presets. Templater can store the data source, footage folder and output folder references within the After Effects project file itself, so you do not have to set them again every time the project opens. When the render machine needs different paths from your desk, that is the point where you change them once, deliberately, rather than discovering at render time that they still point at your Mac.
A footage folder setting. The folder you give Templater is a clear place to put the dependencies a job expects. If you adopt a convention where the render machine’s footage folder mirrors your own structure, the rows in your data can keep using the same relative names on both.
The Templater log. When a batch fails, the log tells you what Templater was doing at each step, which is far more useful than a general error banner. Read it before you start changing things.
Spot checks. In Pro and Bot, export a few spot checks of the data-merged composition on the render machine, before the real batch. If a font is substituted or a footage layer is blank, it will show up in the still. This is the cheapest test in the whole process. See our guide to generating spot checks with Templater.
Running more than one render machine
Once several machines render, the project is no longer the only thing that has to travel. Every machine needs to be a faithful copy of the environment.
Templater Bot can run on several machines in parallel against one data source. Our documentation covers setting up your data source for multiple Bots, and the data source is how the machines know which rows still need rendering. For that to work, every machine must be able to resolve every path the data contains. A row that renders on machine one and fails on machine two is almost always an asset or font that only machine one has.
If you manage jobs through QUE, there is a related rule in our FAQ. QUE does not load balance jobs between satellites at this time. You can assign jobs to specific satellites yourself, but you need to verify that all required assets and resources, including fonts and plugins, are installed or available on any satellite you assign a job to. Satellites are the computers running After Effects and Templater that process your jobs, so the checklist is a checklist for every machine you name. The dashboard in QUE shows each job’s status and the utilization of rendering machines, which makes a row that keeps failing on one satellite easier to spot. You can read more on the QUE page.
If one of your machines is in the cloud, the rules are the same and a few extra points apply. Templater can run on Windows Server machines in a cloud environment such as AWS, and no special license from Dataclay is needed for that. After Effects, however, has to be installed there, and Adobe’s standard license does not permit After Effects on a server, so you need to talk to Adobe about the right license. Plan for how your assets get there too. A cloud machine does not see your office drive. It needs the footage uploaded, mounted from cloud storage, or fetched from an address it can reach. Our post on on-premise video creation discusses the trade-offs of keeping media local.
Projector is worth mentioning for the opposite direction, which is output. It can archive finished files to AWS S3 and deliver to supported platforms, so the rendered files do not have to sit on the render machine waiting for somebody to collect them. That helps when the render machine is a rented one you plan to shut down.
The per-row asset problem, which is its own problem
Static files are easy to reason about because there are few of them and you can list them. Per-row assets are harder, because the list is your data, and your data is longer than you can eyeball.
Three habits keep this manageable. The first is a naming convention that the data and the files agree on. If the column says a product code and the file on disk is named after that same code, the connection is mechanical. If someone has to translate between the two, a typo will eventually get through. The second is a check of the data before the batch rather than during it. A short script, or even a spreadsheet filter, can list rows whose asset address is blank or whose file is not where the row says. Finding a handful of bad rows in advance takes a few minutes. Finding them as failures in the middle of a render takes the rest of your day. The third is a decision about what a bad row should do. A missing photo might mean skip the row, use a placeholder, or stop and ask. Make that call once, in the plan, instead of leaving it to whichever machine hits the problem first.
Dataclay’s Time Sculpting and layout rules help the template adapt to footage of different length and size once it arrives, but they cannot conjure a file that is not there. The delivery of the file is a separate job from the design of the template, and it deserves its own attention. If you want the bigger picture of how data feeds a template, our post on making hundreds of personalized videos from data goes through the flow.
How other approaches treat the same problem
Every renderer has to answer the question of where assets live, and it is worth knowing how the alternatives answer it so you can pick the one that matches your studio.
Nexrender is an open-source Node.js tool that renders After Effects projects without launching the interface. According to its README, it copies the project to a temporary folder, replaces the assets, and then renders. A job is a JSON document that names the project and its assets, and asset sources include local files, HTTP and HTTPS addresses, and inline data URIs built in, with Google Cloud Storage, S3 and FTP available through plugins. Its server queues jobs and workers pick them up, so several machines can act as a render farm. If your team is comfortable writing JSON jobs and running its own infrastructure, that is a reasonable fit. It does not describe a spreadsheet connection on its page.
Plainly takes the other route. You upload After Effects templates, connect a data source, and it renders on cloud-based After Effects infrastructure. Because the rendering happens in its environment, the machine you are worried about is not yours to configure. If you would rather not maintain render machines at all, that is the better fit, and you can see how it is priced on its pricing page.
Templater’s position sits between those. You keep the After Effects project and the machines under your control, and you choose how assets reach them. That gives you the freedom to keep media on your own network, which matters to some teams, and it means the checklist above is your responsibility rather than someone else’s. We think that is the right trade for studios that already own the hardware and care where their media goes. It is not the right trade for everyone.
A routine you can reuse
When you set up a new render machine, run through the same short routine each time.
First, match the software. Install the same After Effects family and the correct Templater installer for it, and activate it. Activation needs to contact a licensing server, and antivirus or firewall software can block that. A machine with no internet access can use Offline Activation instead.
Second, install fonts and plugins. List them from the project, then install each on the new machine. Fonts are the item people forget, because the project opens without complaint and only the render betrays them.
Third, place assets. Copy or mount the static folders, and confirm the per-row paths in your data resolve from this machine specifically.
Fourth, render one real row, then a spot check on the awkward one. Compare the result with what you saw on your own computer.
Fifth, keep a short written note of what the machine needs, so the next one is a copy rather than a reconstruction.
This can feel like a lot of ceremony for a project that “just needs to render.” It is much less ceremony than a batch that fails on the three-hundredth row at the end of the day.
Bottom line
A render machine is a different computer, so treat it like one. Decide where every footage file, per-row asset and font lives. Make those places reachable from every machine that renders, using one folder, a shared location, remote addresses or local copies, and standardize paths so a mapped drive does not mean different things on different computers. Prepare the project with Rig, store the references in the project, and test on the render machine with a real row and a spot check before the batch begins. If the same row fails on one machine and works on another, look for the missing dependency before you suspect Templater.
Moving a project to another machine raises the same practical questions again and again. Here are the ones we hear before a first render on new hardware.
Frequently Asked Questions
Why does my project fail with Failed at N/A on another machine?
After Effects shows that message when it cannot find one or more assets, footage files or font dependencies at the location the project specifies. The files are usually moved, deleted, or simply absent at that path on the new computer. Check the footage paths, the per-row asset addresses in your data, and the fonts installed on the render machine, in that order.
Does After Effects store my footage inside the project file?
No. A project stores references to files, which are paths. Those paths make sense on the computer where you built the project and may not resolve on another. Templater can also store the data source, footage folder and output folder references within the project file as presets, so you can set them deliberately for the render machine.
Can Templater use footage that is not on the render machine’s disk?
Yes. Templater can reference local or cloud-based footage, so a row can point at a file hosted online. The render machine then needs network access to that address, and a slow or unavailable source will slow or fail that row. Our post on Smart URL Processing covers how Templater taps remote footage.
Do fonts and plugins travel with the project?
No. They are installed on the computer, not stored in the project. Install every font and plugin the project uses on each render machine before the first job. QUE’s FAQ says the same for satellites: you must verify that all required assets and resources, including fonts and plugins, are available on any satellite you assign a job to.
Can I render on a cloud virtual machine?
Yes. You can run Templater on Windows Server machines in a cloud environment such as AWS, and Dataclay requires no special license for that. After Effects must be installed there, though, and Adobe’s standard license does not permit After Effects on a server, so you need to speak with Adobe about the right license.
What is the quickest way to test a new render machine?
Render one real row, then export spot checks of the awkward frames with Templater Pro or Bot. If a font was substituted or a footage layer is blank, it will show in the still. Read the Templater log if anything looks wrong, because it records what the plugin did at each step.
What does Templater Rig do for a render machine setup?
Rig lets an artist prepare an After Effects project for a different machine running Pro or Bot. It maps data to composition layers and previews how layers change as data is processed. It does not render batches, so it suits the person who builds and checks the project while Pro or Bot machines do the rendering.
