Opens in a new tab
Guide

After Effects Server Rendering: How to Render on a Server

Published November 13, 2026

Rendering After Effects on a server means running a full copy of After Effects on a machine nobody sits at, and letting software feed it work. There is no separate server version of After Effects to install. The server is a Windows Server machine, in the cloud or in your own rack, running the same After Effects you use at your desk, with Templater driving it from a data source or a command line.

That sentence is short and the project behind it is not. Most of the trouble people hit comes from three questions asked in the wrong order. Is the After Effects license allowed on a server at all? How will the Templater license survive a reboot or a new virtual machine? And what will tell you a job failed at three in the morning? This guide takes them in that order, because the first one can end the project before you spend an hour on the others.

We build Templater, so we are not neutral, and we are only describing what runs with our software. If you need a single composition rendered with no data in it, a server setup built around Templater is more than you need, and we say where that line sits near the end.

What a server really is, and the license you settle first

Picture a producer named Dana at a studio that makes personalized spots. Her team rigs a master composition, a marketing system adds a row of data every time a customer signs up, and each row should become a finished video within the hour. Today a motion designer opens the project on a workstation and starts a batch whenever someone remembers to ask. Dana wants that person out of the loop and the workstation back for real work. So she asks IT for a server.

The first thing IT needs to hear is that Templater does not replace After Effects. It operates it. Our own pages say that Templater requires After Effects to be installed and running in the environment where the work happens. Every video that comes off the server was rendered by After Effects on that machine, with Templater swapping in the data for each row first. The server is a place for After Effects to run unattended.

That is why the Adobe question comes first. Our FAQ answers it directly. You can run Templater on one or more Windows Server machines in a cloud environment from one of the large cloud providers, and Dataclay requires no special license for that. But Adobe’s standard End User License Agreement does not permit After Effects to be installed on a server. You have to contact Adobe for the appropriate license, and you will need to speak to an Adobe salesperson to get it. We are repeating this because it surprises people. Our software is not the obstacle. The After Effects license is the thing to settle before anyone provisions a machine, and before anyone promises a delivery date based on it.

If Adobe’s answer is no, or slow, the project has to wait. Whether any other machine setup, such as a desktop-class computer left running, counts as a server under Adobe’s agreement is a question for Adobe, not for us, so put it to them in writing before you rely on it.

The operating system list is the second early check. Our system requirements say Templater works with After Effects on Windows 7 or newer and on macOS from 10.15 through 15.x, on Intel or Apple Silicon, with After Effects CS5 and later. We add a plain caveat there. We do our best to keep legacy versions working, but we cannot guarantee every combination of operating system release and After Effects version. If you are choosing a Windows Server release and an After Effects version for a new box, pick a pair that is current together, and render a real job on it before you commit. Our install guidance also points out that older After Effects releases need the Legacy installer, which is for After Effects 2021 and earlier.

Two more requirements decide whether a server is practical for you. Templater needs an internet connection for activating some features, validating edition features, reaching cloud-based footage sources, connecting to QUE and using Google Sheets as a data source. If you use Sheets, the machine has to be able to reach your Google Drive account from inside your network, so a firewall or security tool that blocks Google’s servers will stop the Bot cold. Plan these with IT on day one, because they are the kind of rule a locked-down server tends to have by default.

Before You Go Live

What to settle before the server takes real jobs

  • Contact Adobe and get the appropriate server license before provisioning any machine
  • Decide between node-locked and floating license before you buy, key type is fixed at purchase
  • Run Dataclay License Manager on physical hardware inside your own network, on a machine of its own
  • Confirm the server can reach Google’s servers if you use Google Sheets as a data source
  • Install every font the project uses on the server itself
  • Register an event script that emails or texts you after a job or batch, and test it with a deliberately broken row

Making the machine something you can forget about

A render server earns its keep when nobody has to log in. Three things threaten that, and each one has a documented answer.

The first is the Templater license. Our standard license is node-locked, which means it belongs to one computer at a time. If you move it, you deactivate it and activate it again somewhere else, either from Templater Preferences or from your Dataclay account on the website. That works well for a workstation. On virtual machines it is a nuisance, and our documentation says so in a tip. With a node-locked license, every time you reboot or spin up a new virtual machine, Templater needs to be deactivated and reactivated by hand. A server that gets rebuilt, or a cloud machine that you start only for a busy week, would turn that into a chore.

The floating license exists for exactly that situation. You activate a floating key once, on a small licensing server running Dataclay License Manager, and each machine that renders leases a seat from it. When After Effects quits, the seat returns to the pool. If a machine disappears, the manager releases its seat after a time you configure. Jon, our support lead, gave us a simple way to size the key. If at most six people or machines are active at once, the floating key needs six activations. More machines can have the floating build installed and pointed at the licensing server, and they check out a seat as seats come back. Our explainer on floating licenses covers the rules in more depth, and the key type is fixed at purchase, so decide before you buy. A standard key and a floating key use different Templater builds, and they are not interchangeable.

License Types

Node-locked vs. floating license for render servers

Best fit
Node-locked licenseOne workstation at a time
Floating licenseVirtual machines and cloud servers
On reboot or new VM
Node-locked licenseDeactivate and reactivate by hand
Floating licenseSeat leases automatically, returns when After Effects quits
Sizing rule
Node-locked licenseOne machine per activation
Floating licenseSix activations if at most six machines are active at once
Key type fixed at
Node-locked licensePurchase, not interchangeable
Floating licensePurchase, not interchangeable

The floating license exists for exactly that situation.

Where you put the licensing server matters more than people expect. Our guidance is to run DataclayLM on physical hardware inside your own network, preferably on premises, and to give it a machine of its own. The reason is specific. The licensing mechanism fingerprints the machine it is activated on. If DataclayLM sits on a cloud virtual machine, a server reboot changes that fingerprint, and the license manager falls out of sync with our licensing server. Deactivating from the machine then fails, and you have to deactivate the key through the website before you can activate it again. You can avoid that afternoon by not putting the license manager on a machine that reboots into a new identity. The manager also needs to stay on and reachable. Open its port to the render machines, and with Templater 3.0 or later you can list up to two failover servers in Preferences.

Dana’s version of this is plain. One small machine in the studio’s own network runs the license manager. The render servers, wherever they live, point at it. If IT rebuilds a render server over the weekend, it asks the manager for a seat on Monday and nobody opens a ticket.

The second threat is activation at boot. If a server starts itself and has to be licensed before anyone can open After Effects, you can activate and deactivate Templater from the command line. For copies downloaded from aescripts and aeplugins, the Templater Settings effect has to be registered and activated first. You then set the bot_activate value in the tasks object of the templater-options.json file to true, set every other task to false, and launch Templater from the command line. For copies downloaded from Dataclay, you email support and ask for a command line utility. A machine with no internet at all has an offline activation route through two XML files. We laid out each of these in our guide to automating After Effects rendering from the command line, so we will not repeat the steps here.

The third threat is slow decay. A Bot left enabled for hours or days can get slower, and our documentation points at After Effects caching. Layer caching and disk caching help a person who is working by hand, because they let you step back through changes. They do nothing useful for a machine that versions one composition after another. On a dedicated render machine, disable the layer cache in the hidden Secret preferences, set the number of frames to purge during Make Movie to zero, and turn off the disk cache. Since After Effects 24.3, Templater’s preference to purge all memory caches after each job no longer empties the disk cache, so the disk cache is worth a deliberate decision. If the same machine is also somebody’s workstation, leave the disk cache on and empty it by hand. The full steps are in our piece on optimizing After Effects for the Bot.

Then there is the environment, which is where most first renders on a new machine go wrong. After Effects stores paths to footage, not the footage. A project that renders perfectly at a desk will fail on a server if the footage folder, the per-row images or a brand font are missing there. Our error code 1003 means Templater could not find a footage file in the network, and 1002 means a remote download failed. Decide where every dependency lives, make that place reachable from the server, and install the fonts on the server itself. We walk through the choices in managing linked footage when a project renders on another machine. One more warning belongs here. If you send replicates to Adobe Media Encoder, our documentation warns that a cloud-based output folder can cause errors. Use a local or networked folder for Media Encoder’s watch folder.

One question we cannot answer from our own pages is how a particular server keeps a signed-in desktop session alive after a restart. After Effects is a desktop application, and that is a general practice matter, so ask your IT lead how the machine will sign itself in, stay awake and recover. Put the answer in writing before the server goes into service.

Feeding the server work, and knowing when it fails

A server with no work is an expensive heater. There are three ways to hand it jobs, and they suit different teams.

The first is a data source and the Bot. You enable the Bot, and Templater enters a server mode and checks your data on a schedule. It picks up every row marked ready, changes the status to queued, then to processing as it works through each one, and finally to done. If something fails, the status becomes an error code such as ERR::MEDIA for an asset problem or ERR::AFXHOST for an After Effects problem. The default check interval for new data is thirty seconds. The shortest we allow is about eighteen seconds for Google Sheets and about twelve for JSON sources, and setting it lower can make After Effects behave unexpectedly. Dana’s marketing system only has to add a row and mark it ready. Everything after that belongs to the machine.

Mind the queue setting. The Bot holds at most twenty rows at a time, and twenty is the default and the ceiling. That sounds small and is deliberate. You can mark ten thousand rows ready and let the Bot work through them in batches of twenty, which keeps the memory Templater needs under control. If you use a URL feed as the data source, remember that the Bot cannot write render-status back to a feed that lives on someone else’s system. You must register an event script that updates the status after each job, or the same ready rows will be rendered again. Our guide to the Bot settings that matter goes through each preference.

The second way is the command line. The Bot has a command line interface, and nearly every control in the Templater panel can be set through the templater-options.json file. Developers like it because a render becomes one more step that a scheduler, a deploy script or a web service can call. It also gives you the best logging. Templater writes templater.log, templater.err and templater.out to the folder named by the log_location property, and the launcher scripts report the last logged message and the last error when a run ends. You can watch templater.out live with a tail command on a Mac. Each error is written as a single line with a code, a short description, the After Effects message, details and a timestamp. A quit_on_errors list lets you force After Effects to quit on the first occurrence of a specific code, which keeps one broken asset from leaving a server in a half working state.

The third way is QUE, our cloud app for jobs held as JSON. Here the render machines are called satellites. A satellite is an authorized machine with After Effects and Templater installed. You add it from Templater’s preferences by loading the machine profile with your organization key and clicking Add to QUE, and the satellite takes the name of the host. That is where a server setup usually trips on the first day. Each satellite needs a unique name, so a rebuilt server that reuses a host name can collide with the old one. A host name with spaces or punctuation can fail to register, and the simplest fix is a short plain name. Your QUE plan also caps how many satellites you can add. For a developer, the QUE API is how an application inserts jobs and reads their status, and the render-status values run through ready, queued, processing, done and canceled, plus the error codes. Our posts on running one or many bots on one data source explain the sheet-based version of the same idea.

Scaling is where the license and the data source meet. Our FAQ says you can run several machines with Templater Bot in parallel, and that two machines cut total production time in half, three cut it to a third, and so on. We would add one condition from our own documentation. Several machines reading one list need a clear way to avoid doing the same row twice, so give each Bot a name and a matching column in the data source. The machines can sit in different places, because a Google Sheet lives in the cloud. When you need to know how many machines you need, do not guess. Render one video, or a small batch, on a machine comparable to the production one, multiply by the number of videos, and divide by your machine count. Our guide to sizing a render farm starts from the deadline instead of the average, and that is the right order.

Last, decide who gets the alarm. Neither the Bot nor the command line sends you a message by itself. Our event scripts can, because a script can run after every job or batch and can email or text you when a video finishes or fails. Without that script, a server that stalls will look healthy until someone asks where a video is. Write the alert before you go live, and test it by breaking a row on purpose.

When a server is the wrong answer

A server is not always the right move, and we would rather say so than sell you one. Some cases call for something simpler.

If a person decides when each batch starts, you do not need a Bot or a server. That is the Pro edition, which renders batches on a machine where someone presses go. It is simpler to run and has fewer places to fail. If the volume is a few videos a quarter, a server and an Adobe server license cost more effort than the work is worth, and metered output through QUE may suit a team better than a standing machine. And if your data cannot leave your network, a cloud server makes that review harder, so keep the rendering on hardware you control. Our comparison of cloud and on-premise video automation is built to help you decide that.

There is also the question of cost and care. A render server needs patching, monitoring, a spare machine plan and a person who owns it. Templater Bot comes with no front end, so if customers should request videos through a page or an app, someone has to build that part. You should budget for it. We cannot promise a specific speed for your templates, because rendering time depends on length, resolution, hardware, how processor-heavy your effects are and how the template is built. A trial run on your own project beats any number we could quote.

If you want to find out whether the setup works before anyone orders a server, our 30-day free trial includes every feature of Templater Bot, with a watermark on dynamic layers. Run a real batch on a spare machine, read the logs when something breaks, and bring what you learn to IT and to Adobe.

Dana’s studio did one sensible thing in this story. They settled the Adobe license in the first week, put the license manager on a machine that never changes identity, and wrote the failure alert before the first real job. The servers themselves were the easy part. Get the license, the licensing machine and the alarm right, and a server turns After Effects into a background service. Get one of them wrong, and you own a very quiet, very expensive computer.

We covered a lot of ground above. Here are the questions people bring us most when they ask about putting After Effects on a server.

Frequently Asked Questions

Can I install After Effects on a cloud server for rendering?

Technically yes, but the license is the catch. Templater runs on Windows Server machines in a cloud from one of the large cloud providers, and Dataclay needs no special license for that. Adobe’s standard End User License Agreement does not permit After Effects to be installed on a server, though. You need to contact Adobe and talk to a salesperson to get the right license. Settle that before you provision anything, since every render on the server is an After Effects render.

Does Templater need After Effects running on the server?

Yes. Templater operates After Effects, it does not replace it. Every video is rendered by After Effects on the machine, after Templater swaps in the data for the row. The Bot lets you customize and render without operating the After Effects user interface, so nobody has to sit there and click. After Effects still has to be installed, licensed and running on that machine for the work to happen.

Do I need a floating license for virtual machines?

Not required, but it is the better fit. A standard node-locked license has to be deactivated and reactivated by hand every time you reboot or spin up a new virtual machine. A floating license leases seats from a Dataclay License Manager server, and a seat returns to the pool when After Effects quits. If at most six machines are active at once, the key needs six activations. The key type is set at purchase, so choose before you buy.

Where should the license manager run?

On physical hardware inside your own network, preferably on premises, and on a machine of its own. The manager fingerprints the machine it runs on. If it sits on a cloud virtual machine, a reboot changes that fingerprint and desynchronizes it from our licensing server. Then you have to deactivate the key through the website before you can activate it again. Keep it always on, open its port to the render machines, and add up to two failover servers with Templater 3.0 or later.

How do I know a render failed on an unattended server?

Read the logs and the status, and add an alert of your own. Templater writes templater.log, templater.err and templater.out to the folder in the log_location setting, and each error is a single line with a code and details. In a data source, a failed row gets a status such as ERR::MEDIA or ERR::AFXHOST. Neither one pages you. Register an event script that emails or texts you after a job or batch, and test it with a deliberately broken row.

How many machines do I need?

Measure it, because we cannot quote a number for your templates. Render one video, or a small batch, on a machine comparable to the production one, then multiply by the number of videos in the batch. Running Bots in parallel divides that time, so two machines cut it in half and three cut it to a third. Give each Bot a name so the machines do not render the same row twice. Start from your deadline, not from the average day.

Leave the first comment

Sign up

Stay up to date with Datclay's newsletter. We won't spam your inbox.

Newsletter Signup
Name
Name
First
Last

By submitting your email, you agree to our Terms and Privacy Policy. You can opt out at any time.