How After Effects network rendering works: aerender, watch folders, render engines, image sequences, plugin and license requirements, plus a pre-flight checklist.
After Effects cloud rendering can use more than one machine, but the rules are stricter than most people expect: a movie file cannot be written by several machines at once, plugins and fonts must exist on every node, and the project must be set up for multi-machine rendering. This guide summarizes Adobe’s documented options and lists what to check before you send an After Effects project to a farm or render it on several computers.
Contents
Short answer
- Use aerender, the command-line renderer, for scripted or farm rendering. Without the comp argument it renders the entire render queue as it is set up.
- For several machines working on one comp, render to an image sequence and use the setting “Skip Existing Files (allow multi-machine rendering)”. Adobe states that multiple render engines cannot render one movie file at the same time, but they can render a still-image sequence that you convert to a movie afterwards.
- Every machine needs the same fonts, effects, codecs and third-party plugins, and the plugin license must allow the extra copies.
Adobe’s multi-machine options
- aerender is installed in the After Effects Support Files folder on Windows and in the application folder on macOS. It can run on a farm or as a batch on one computer. By default it starts a new After Effects instance even if one is running; the reuse option makes it use the running instance. Documented arguments include project, comp, start and end frames, render settings and output module templates, output path, memory usage, multi-frame rendering and a log file.
- Watch-folder rendering uses render engines, which are render-only installs of After Effects. Adobe notes that watch-folder mode applies to a folder on the local computer, and recommends a dedicated server for the watch folder instead of rendering on the machine that serves it.
- For CS6 and later, aerender or a watch folder can run in a non-royalty-bearing mode on a render-only machine, which does not require serialization. Adobe describes enabling it by installing After Effects, signing out, quitting and creating a blank file named ae_render_only_node.txt in the documented location. Check the current Adobe documentation and your license terms before using this on a rented or shared machine.
Project and network requirements from Adobe
- Use absolute paths or mapped drive letters, not relative UNC-style paths.
- Give each Mac and each drive a unique name.
- Do not render to the root of a volume or a shared folder; use a subfolder.
- Set the output folder to a location every rendering computer can reach.
- Install all fonts, effects and encoders on every computer. If one is missing, the render fails.
- For still-sequence farming, do not share plugins across the network; each computer needs its own plugins folder.
- Do not use multiple output modules together with “Skip Existing Files (allow multi-machine rendering)”.
After Effects cloud rendering pre-flight checklist
- Collect files so footage, precomps and fonts travel with the project, and re-link anything that points to a local drive.
- List every third-party plugin and confirm each one is available, licensed and the same version on the render machines.
- Choose the output format deliberately: an image sequence for multi-machine work, a movie file only when one machine renders the whole comp.
- Render a short test range on the target machine and check time per frame and memory use.
- Plan for out-of-memory failures. Heavy comps can exhaust RAM or VRAM; see After Effects out-of-memory and export fixes.
- Keep a record of failed frames and re-render only those.
Cinema 4D and After Effects pipelines
Many motion graphics projects pass between Cinema 4D and After Effects. Keep the 3D render and the compositing render as separate steps so a problem in one does not force a full re-render of the other. For the 3D side, see the Cinema 4D cloud rendering guide.
In practice, After Effects cloud rendering works best when the project is prepared for multi-machine output from the start. Render to an image sequence rather than a single movie file, make sure plugins and fonts exist on every node, and test a short range before queuing the whole composition. These steps apply to After Effects cloud rendering on a managed farm and to a set of your own computers alike.
Related reading
- Why your animation render keeps crashing: troubleshooting guide
- How to render animation faster
- How to choose the best render farm for your projects
FAQ
Can several machines render one After Effects movie file at once?
No. Adobe states that multiple render engines cannot render one movie file at the same time, but they can render a still-image sequence that you convert to a movie afterwards.
Which setting enables multi-machine rendering in After Effects?
Select “Skip Existing Files (allow multi-machine rendering)” in Render Settings, and do not combine it with multiple output modules.
What does aerender do?
aerender is the command-line renderer. It can run on a render farm or as a batch on one computer, and without the comp argument it renders the whole render queue as set up.
What must be installed on every render machine?
All fonts, effects and encoders, plus any third-party plugins. If one is missing the render fails, and the plugin license must allow multiple copies for network rendering.
COMMENTS