An After Effects render farm is just a group of machines that each run After Effects and split a pile of renders between them. You can get one for free if you already own the machines. You can rent one online. Or you can build your own, and the right choice depends far more on the shape of your work than on the price of any single option.
People search for “free” and “online” in the same breath, and that tells us something. Picture someone with a deadline, a stack of versions, and one computer that is already busy. They want to know whether somebody gives away capacity, whether they have to pay by the minute, or whether it is time to set up machines of their own. This guide takes the options in order, says what each one really costs you in setup and attention, and says where we would send you somewhere else. We build Templater, an After Effects plugin that fills a template from data and renders it, so we are not neutral. We will mark where that matters.
What a render farm is for, and what “free” can honestly mean
Start with the job, because the word “farm” hides two different problems. The first problem is that one machine is too slow for the volume. Each video takes a while, there are a lot of them, and the total is longer than you can wait. The second problem is that your work arrives in bursts. Most weeks are quiet, then a campaign or an event lands and everything is due at once. A farm solves the first problem with more machines running at the same time. It only solves the second if you can add those machines quickly and drop them again.
Here is a scene that makes the difference clear. A producer at a small agency has one After Effects template for a retail offer. A client sends a data file with a few hundred rows, each row a different store, a different name, a different photo. The producer used to export each version by hand. That stopped being possible the day the file had more rows than hours in the afternoon. What the producer needs is not a faster computer. It is a way to fill the template from the data automatically, and then a way to run that work on more than one machine if the clock demands it. The farm is the second half of that sentence. The first half is the data connection, and no farm replaces it.
So what can “free” honestly mean? We can think of four honest answers, and only some of them come with Dataclay software.
The first is machines you already own. A workstation that sits idle in the evening is a free render node. This is a plain, familiar approach and it works. You pay nothing extra for hardware, and the cost shows up instead as your own attention, because somebody has to set those machines up and keep them matching each other. We say more on that below.
The second is a trial of the software. The Templater free trial runs thirty days and contains all features for all versions, with a watermark added to the dynamic layers. The trial is a fully featured version of Templater Bot, so you can test an automated setup before you commit to anything. The one extra requirement is that the option to send replicates to Adobe Media Encoder has to be enabled. A trial is a good way to learn how much capacity you really need, which is the number that every other decision hangs on. It is not a free farm, because the watermark means the output is for testing.
The third is the free tier of a data and job service. The QUE free trial is limited to 50 jobs by default. That is enough to prove a pipeline works end to end. It is not enough to run production.
The fourth is a hosted farm that gives away rendering with no strings. We cannot point you to one, and we do not want to guess at one. This is general practice, not a Dataclay fact. Rendering After Effects costs the host real machine time, and the After Effects software has its own license terms. When a hosted service offers unlimited rendering at no charge, ask what the catch is, and ask who holds your files while it renders. A free trial with a cap is normal. A farm that costs nothing and has no limits deserves a skeptical read of its terms.
Four free options
What ‘free’ can honestly mean
| Option | What you get | The real limit |
|---|---|---|
| Machines you already own | Idle workstation as a free render node | Your attention to set up and keep machines matching |
| Templater free trial | All features, fully featured Bot, thirty days | Watermark on dynamic layers; output is for testing |
| QUE free trial | Prove a pipeline works end to end | Limited to 50 jobs by default; not enough for production |
| Hosted farm, no strings | Rendering with no charge claimed | Ask what the catch is; read terms before trusting with files |
We would rather tell you that plainly than let a search result suggest something we cannot back up. The real choice is between machines you own, machines you rent, and a service that rents them for you. The rest of this guide takes those in turn.
The ways to get a farm, from cheapest to most hands-off
Think of this as a ladder. Each rung removes a chore and adds a cost, and the right rung is the lowest one that gets you through your worst week.
One machine, rendering more at once. Before you add a second computer, use the first one properly. Projector, our app for rendering customized videos, uses the After Effects rendering engine in parallel based on the number of cores in the machine. Each core it uses renders a different video at the same time. By default Projector uses half of your cores, and a slider in Mission Control lets you change how many it uses. That is a free capacity gain on hardware you already own. We cannot promise how large the gain is on your template, because it depends on the machine and on how heavy the composition is. Test it on a real row before you plan around it.
A few of your own machines. The next rung is a small set of machines you control, each running Templater Bot. Bot checks the data source for new rows and starts renders on its own, which means nobody has to press a button on each machine. Our FAQ describes the arithmetic plainly. Run Bot on several machines at the same time against the same data source, and the total production time is cut in half with two machines, to a third with three, and so on. The setup details are in our post on running one Bot or many Bots on one data source.
The honest cost of this rung is sameness. Every machine has to be a faithful copy of the others. The same After Effects version, the same Templater version, the same fonts, the same plugins, and the same access to the footage. A machine that is missing a font will render a different video from its neighbor, and you may not notice until a client does. Build one machine, test a real row on it, and copy that setup. The whole point is that a new machine can render a row without anybody touching it.
Rented machines that you run. When you need more machines than you own, but only for a few days, you can rent them. Our FAQ says you can run Templater on one or more Windows Server machines in a cloud environment from one of the large cloud providers, which lets you scale past what your desktops can do. Dataclay does not require a special license for this. But there is a catch that catches people. Templater needs After Effects installed and running on that machine, and Adobe’s standard license agreement does not permit After Effects on a server. You have to speak to an Adobe salesperson about the right license. Do that before you plan a launch around rented machines, not during it.
What you get from this rung is control. Your templates, your data, and your pipeline stay yours, and you turn the extra machines on for the busy stretch. What you give up is the chore of building and maintaining that setup. If you already run Bot on your own machines, adding rented ones is a smaller step than changing platforms. If you have never set up a Windows machine for rendering, it is a bigger step than it looks.
A hosted platform. A third path is to hand the machines over entirely. Plainly, a platform for After Effects automation, describes itself as using a cloud-based After Effects infrastructure to render your videos. You upload your templates, connect a data source, and the videos render and distribute automatically. Its plans include a set number of rendering minutes, there is no limit on the number of videos but the output is capped by those minutes, and concurrency depends on the plan. For prices, see their pricing page. If you have no wish to run machines at all, that is a complete answer, and it can be the better fit than ours. We wrote a longer comparison in our guide to choosing between cloud and on-premise automation.
If your work does not start in After Effects, a different kind of tool may suit you better. Creatomate and Shotstack build and render video in their own cloud tools and offer APIs, and neither homepage mentions After Effects. They are a different kind of choice rather than a cheaper version of a farm.
A metered option on our side. We offer a way to pay by use as well. QUE Meter lets Templater draw on a pool of credits instead of a subscription, and any active Templater key, whether Rig, Pro or Bot, can connect to the pool. Several machines can draw on the same credits. There is a limit of 1,000 credits per QUE Meter account, and once someone exceeds 1,000 outputs in a single month, a QUE subscription becomes the more affordable route. For a team with occasional work and several seats, that is a sensible fit. For steady heavy work, it is not.
What a farm will not fix
More machines do not help when the slow part is somewhere else. This is where teams can lose a week, because they buy capacity for a problem that was never capacity.
The template. A heavy template is slow on one machine and slow on ten. Rendering time depends on the average length of the videos, the output resolution, the hardware, the ratio of dynamic to static frames, how processor-intensive the effects are, and how you build the template. That list comes from our FAQ, and it is worth reading as a to-do list. Trimming a template is cheaper than adding a node. Our post on render time costs of After Effects techniques at scale goes through which techniques cost the most.
The data. If rows reach the farm at the speed of a person typing into a spreadsheet, extra machines sit idle. And if a bad row gets through, you get a bad video, multiplied across every machine that picks it up. Check that the data is correct when it arrives, not after the render. Our post on monitoring a Bot queue so one bad row does not stall the batch covers how to catch it.
The footage. Several machines pulling the same large files from one shared drive will slow each other down. Per-row images fetched from a remote server may be limited by that server. Test with the number of machines you intend to use, not with one. Footage that renders fine on your desk can go missing on another Mac, which we cover in managing linked footage when a project renders on another Mac.
The licenses. A Standard License is activated and used on one machine at a time. A floating key comes with a number of seats, anywhere from one to however many you need, and the number you pick should match how many machines or people work at the same time. If at most six are active at once, the floating key needs six activations. This one is easy to miss until a deadline. You can have a dozen machines ready and still be limited by the seats you bought. Count the machines that will render together before the busy day, and read the Templater licensing guide first.
Before you scale up
Fix these before adding a single machine
- Trim the template, a heavy template is slow on one machine and slow on ten
- Check that the data is correct when it arrives, not after the render
- Test footage with the number of machines you intend to use, not with one
- Count the machines that will render together before the busy day, then buy the right number of license seats
- Settle the Adobe server license before you plan a launch around rented machines
Job assignment. If you use QUE to manage work across machines, there is a limit to know. QUE does not load balance jobs between satellites at this time. You assign jobs to specific satellites yourself, so you are the scheduler. That is workable for a small fleet you know well, and a burden for a large one that keeps changing. It also means each satellite you assign work to must have the fonts, plugins and assets the job needs.
Delivery. Finished files often have to be transcoded, uploaded and registered somewhere. Those steps take time too, and the deadline has to include them. Projector can transcode as part of the render and send finished videos to supported platforms, which keeps that stage in the same automated chain.
One more option sits between the render and the delivery. Adobe Media Encoder can handle output formats that After Effects does not include on its own. In Templater you can use Replicate instead of Render. Replicate inserts the data and saves a copy of the project, and Media Encoder then processes that copy. We cannot tell you Media Encoder is faster, because our documentation does not say so. Use it when you need the format.
How to choose, and a bottom line
Go back to the agency producer with the data file. Suppose that producer has a steady stream of these jobs, spread across the year, and the same two or three templates reused for each client. That producer should buy time on machines they own, because the machines stay busy and the extra renders cost almost nothing once the hardware is paid for. A few computers running Bot, plus Projector’s use of every core, will go a long way. Add rented Windows machines only for the rare week when everything lands at once, and sort out the Adobe license before that week.
Now suppose a different producer, at a small studio, who gets one large campaign a quarter and has no one on staff who enjoys maintaining machines. For that producer, a hosted platform is the sensible choice, because they pay only when work exists and never babysit a computer. The same template, the same data, a different answer. What changed was the shape of the work and the people available to look after the machines. We go deeper on that cost comparison in our post on when in-house hardware is cheaper than cloud rendering by the minute, and on sizing from the deadline backward in how to size a render farm for unpredictable, deadline-sensitive volume.
Which setup fits you
Steady work vs. rare bursts: different answers
- Best machine setup
- Steady stream of jobsOwn machines running Bot
- One large campaign a quarterHosted platform
- Why it fits
- Steady stream of jobsMachines stay busy; extra renders cost almost nothing once hardware is paid for
- One large campaign a quarterPay only when work exists; never babysit a computer
- Who looks after machines
- Steady stream of jobsSomeone on staff
- One large campaign a quarterNo one needed on staff
What changed was the shape of the work and the people available to look after the machines.
If you are not sure which producer you are, the cheapest test is a small one. Render a single video that looks like the rest of the set, on a machine comparable to the one you would use in production. Multiply that time by the number of videos. Divide by the machines you could run at once. Now you have a number to compare with your deadline, and the decision is a lot less abstract. If you want to run that test with Bot, the command line guide shows how Bot is driven from a shell, and the trial is a fully featured Bot you can test it on.
Here is the short version. If you already own idle machines, start there and use them well. If your volume comes in rare bursts, rent capacity for the burst, and settle the Adobe license first. If you want no machines at all, use a hosted platform and check what its plan caps. If you need a farm for free and nothing else, be skeptical of anyone who promises it without limits. In every case, fix the template and the data before you add a single machine, because a farm runs a slow pipeline faster, and runs a broken one at scale.
Before you go, a few quick answers to the questions people ask us when they are sizing up this decision.
Frequently Asked Questions
Can I get an After Effects render farm for free?
You can build one for free from machines you already own, since an idle workstation is a free render node. You can also test the software at no charge. The Templater free trial runs thirty days with all features and a watermark on dynamic layers, so its output is for testing. We cannot point to a hosted farm with unlimited rendering and no cost, and we would read the terms of any service that claims one before trusting it with your files.
Can I run Templater on cloud machines like AWS?
Yes. You can run Templater on one or more Windows Server machines in a cloud environment from one of the large cloud providers. Dataclay does not require a special license for that. After Effects must be installed and running on the machine, though, and Adobe’s standard license agreement does not allow After Effects on a server. You need to talk to an Adobe salesperson about the right license before you plan around it.
How many machines do I need to hit a deadline?
Render one typical video on a machine like the ones you will use, then multiply that time by the number of videos. Divide by the number of machines running in parallel. Two machines cut the total time in half, three cut it to a third. Test a heavy row as well, plan with the slower time, and leave room for failed rows and for delivery after the render ends.
Does a render farm replace the data connection?
No. A farm runs renders. It does not fill your template from a spreadsheet or a feed. Templater connects a template to data sources such as Google Sheets, files exported from Excel, and JSON, and then renders each row. Without that step you are still exporting versions by hand, only on more computers. Fix the data connection first, then add machines if the clock still demands it.
What does the Templater trial include?
The free trial contains all features for all versions, with a watermark added to the dynamic layers. It is a fully featured version of Templater Bot. The one extra requirement is that the option to send replicates to Adobe Media Encoder has to be enabled. That makes the trial a practical way to test your setup before you buy anything.
Do floating licenses let every machine render at once?
Only up to the number of seats on the key. A floating key has anywhere from one seat to as many as you need, and it works through a licensing server. If at most six people or machines are active at the same time, the key needs six activations. Count the machines that render together on your busiest day before you buy.
Does QUE balance jobs across my render machines?
Not at this time. QUE does not load balance jobs between satellites, so you assign jobs to specific satellites yourself. That works well for a small, known set of machines. Every satellite you assign must have the fonts, plugins and assets the job needs.
